Skinning the Free Airwindows Plugins!

[jinxtigr]

Cool, hopefully more people will drop by (including the dev himself) to shed a bit more light on this. Thanks, Gary!

This got by me, but finally spotted it

The plugins are all a lot free-er than most I have Patreon, and that is all about 'do people want me to keep working and doing new stuff, every week or even more, and getting gear to do plugins of'. That's what the Patreon is for. You can think of it as 'X number of $50 plugins a year', or not even. Up to you.

As for skinning the plugins, _I_ ain't gonna do that! I've got a bunch of other things that I need to learn about. if I'm lucky I'll get help and be able to make a metering plugin and do stuff I can't do with the regular plugins. Most of my attention is DSP in one way or another: there hasn't been anybody working on processing minimalism that I've seen, so there's a whole range of stuff I need to explore in the vein of 'how simple can I make the calculations to do various audio tasks'.

But they're all open source. SO open that they're more liberal in licensing than GPL, which has expectations on what you can do. MIT license means you can make your own plugins out of all of mine. In fact you can skin ALL the plugins and make your own patreon or anything else, and get paid to do it. For all I know you'll get paid more than me: depends on how badly people want that SP1200 plugin(s). if I can make it you can skin it, and then give away or sell the one you made, as long as you honor the MIT license. It's one of the most lenient licenses you can work with.

Go ahead, with my blessing. That's what I always say. I will keep supplying the raw materials you'll work with, plus if you're clever you might try combining plugins into one. People are constantly, constantly asking me for "X + Y + Z" plugin, and I don't make them that way. Go ahead and do that and skin it and make it look pretty, and sell it.

If you change too much, or don't pay attention to why I do the stuff I do, my plugins might sound better than yours. But YOURS would have the GUI and pretty looks, so you might still do just fine

[QCGroove]

Go ahead, with my blessing. That's what I always say. I will keep supplying the raw materials you'll work with, plus if you're clever you might try combining plugins into one. People are constantly, constantly asking me for "X + Y + Z" plugin, and I don't make them that way. Go ahead and do that and skin it and make it look pretty, and sell it.

Hey Chris, I would love to do this. Any tips on how to start out if my goal is to make Vector GUIs like some of the audiodamage and valhalla stuff, add your algorithms together to make 'new' plugins, and export them for PC and macOS use? I have some object oriented programming experience, but mainly in high level languages like Ruby and Some frameworks like jQuery. No c++ experience, for instance. I greatly appreciate your advice.

[aMUSEd]

Tracktion has many airwindows plugins skinned. They come with it when you buy.

Ugly skins though - tbh I would prefer if they just used the generic view in Waveform.

[resynthesis]

I'm not Chris but I'd certainly suggest you learn the language the plugins are developed in, you don't want to make some innocuous looking change and break things do you!? You'd probably need that to integrate multiple plugins too. As for graphics, IPlug2 seems to be relatively easy to pick up and doesn't have the same costs as developing with JUCE.

[jinxtigr]

Hey Chris, I would love to do this. Any tips on how to start out if my goal is to make Vector GUIs like some of the audiodamage and valhalla stuff, add your algorithms together to make 'new' plugins, and export them for PC and macOS use? I have some object oriented programming experience, but mainly in high level languages like Ruby and Some frameworks like jQuery. No c++ experience, for instance. I greatly appreciate your advice.

I love the look of Valhalla stuff! Sean's got a great vibe, and it's SCALABLE I believe iPlug is geared to working with scalable vector graphics, though I could be unclear on the subject.

I can't help with that at ALL. If I could, I'd be doing something like that myself (not for all the plugins, though, just the occasional something)

What I can tell you is that my plugins are EASY to understand without much C++ experience, and are organized in such a way that if you can get any one of them to work, you pretty much have them all. Surge's got an import script going, making it very easy for them to bring new plugins into their FX section as native Surge functionality, and I tweaked a few details just to make it even more seamless for them. It's idiosyncratic code but NOT hard to see how it works: sort of 'C++ as C as ASM all unrolled and stuff'. Look over what's on my Github and see if you can make any sense of it. For instance, look up BitShiftGain, which is really about as simple as you can get. If you can build that, you can build the others

[Russell Grand]

Cool, hopefully more people will drop by (including the dev himself) to shed a bit more light on this. Thanks, Gary!

This got by me, but finally spotted it

The plugins are all a lot free-er than most I have Patreon, and that is all about 'do people want me to keep working and doing new stuff, every week or even more, and getting gear to do plugins of'. That's what the Patreon is for. You can think of it as 'X number of $50 plugins a year', or not even. Up to you.

As for skinning the plugins, _I_ ain't gonna do that! I've got a bunch of other things that I need to learn about. if I'm lucky I'll get help and be able to make a metering plugin and do stuff I can't do with the regular plugins. Most of my attention is DSP in one way or another: there hasn't been anybody working on processing minimalism that I've seen, so there's a whole range of stuff I need to explore in the vein of 'how simple can I make the calculations to do various audio tasks'.

But they're all open source. SO open that they're more liberal in licensing than GPL, which has expectations on what you can do. MIT license means you can make your own plugins out of all of mine. In fact you can skin ALL the plugins and make your own patreon or anything else, and get paid to do it. For all I know you'll get paid more than me: depends on how badly people want that SP1200 plugin(s). if I can make it you can skin it, and then give away or sell the one you made, as long as you honor the MIT license. It's one of the most lenient licenses you can work with.

Go ahead, with my blessing. That's what I always say. I will keep supplying the raw materials you'll work with, plus if you're clever you might try combining plugins into one. People are constantly, constantly asking me for "X + Y + Z" plugin, and I don't make them that way. Go ahead and do that and skin it and make it look pretty, and sell it.

If you change too much, or don't pay attention to why I do the stuff I do, my plugins might sound better than yours. But YOURS would have the GUI and pretty looks, so you might still do just fine

Thank you for replying, Chris!

[Russell Grand]

Go ahead, with my blessing. That's what I always say. I will keep supplying the raw materials you'll work with, plus if you're clever you might try combining plugins into one. People are constantly, constantly asking me for "X + Y + Z" plugin, and I don't make them that way. Go ahead and do that and skin it and make it look pretty, and sell it.

Hey Chris, I would love to do this. Any tips on how to start out if my goal is to make Vector GUIs like some of the audiodamage and valhalla stuff, add your algorithms together to make 'new' plugins, and export them for PC and macOS use? I have some object oriented programming experience, but mainly in high level languages like Ruby and Some frameworks like jQuery. No c++ experience, for instance. I greatly appreciate your advice.

It'd be awesome if you gave it a shot - if you're still up for it!

[Scrubbing Monkeys]

Go ahead, with my blessing. That's what I always say. I will keep supplying the raw materials you'll work with, plus if you're clever you might try combining plugins into one. People are constantly, constantly asking me for "X + Y + Z" plugin, and I don't make them that way. Go ahead and do that and skin it and make it look pretty, and sell it.

Hey Chris, I would love to do this. Any tips on how to start out if my goal is to make Vector GUIs like some of the audiodamage and valhalla stuff, add your algorithms together to make 'new' plugins, and export them for PC and macOS use? I have some object oriented programming experience, but mainly in high level languages like Ruby and Some frameworks like jQuery. No c++ experience, for instance. I greatly appreciate your advice.

It'd be awesome if you gave it a shot - if you're still up for it!

+1

[mothergarage]

Out of curiosity I tried to wrap one of the plugins with Max for Live. Can anyone test it?
Is it even necessary in Live, when the paramaters are exposed in Live's GUI anyway.

Dropbox

[satYatunes]

This has been on my to do list since a very long time. I couldn't get to it because of other commitments. Hopefully will find some time next year.

[Scrubbing Monkeys]

This has been on my to do list since a very long time. I couldn't get to it because of other commitments. Hopefully will find some time next year.

If you do get around to this.....one thing that would be great is certain combinations grouped into a single gui.

[jinxtigr]

If you do get around to this.....one thing that would be great is certain combinations grouped into a single gui.

You're welcome to do so, and under some circumstances this could make the result sound better and be more CPU-efficient

The plugins run a long double internal buss. So you'd pick things like that, and then keep the denormalization at the beginning (or pick the denormalization from very recent plugins and use that: I've been evolving it this whole time), run the plugins sequentially (or in parallel, anything: just retaining that long double buss) and when you're done, do the dithering to the DAW's floating point buss as I have it in recent plugins, and do that ONCE.

You'll be using the multiple plugins, but running them on an internal multiple-plugin buss that's either deeper, or WAY deeper, than the DAW provides. In particular it'll be way deeper than CoreAudio on the Mac, or many implementations of VST (those that aren't using DoubleReplacing() )

You could also turn everything into floats, not dither or denormalize, and max out the CPU efficiency. That would also work, it's just not the choices I make

[Scrubbing Monkeys]

I will put together a my wish list of combinations. I have done several in Mutools Mux with great results.

[wikter]

No news?

[ssseladsss]

A little bit old post, but to whom it may help,

I just realized that opening the Airwindows Plugins inside Bluecat's Patchwork will open it with a skin.