airwindows
airwindows copied to clipboard
Port to VCV Rack
Hello Chris, I like to port some of your plugins over to VCV Rack as virtual modules. I already did a proof-of-concept and as I am quite familiar with VCV Rack's API it was an easy task. TapeDelay will be really fun to use :-) Though your licence allows me to do so I'am asking if I can keep your original names for the plugins and name the modules accordingly. Also, if you like I can make them available with brand "airwindows" as all credit for the DSP code goes to you obviously. Otherwise I will choose my own naming which would be fine too. The licence of the modules will be GPLv3. Cheers, Ben
Can you give me one working example under the MIT license? Any one :) that way I can do them too. Apart from that you can do as you please, but I would rather you not identify yourself AS Airwindows, especially if you're not using the same license I use.
I will assemble a complete example for one plugin in the next few days which you can compile yourself then. I have a working prototype but it won't help you very much in its current state.
Here are the instructions for setting up a build enviroment for VCV Rack plugins: https://vcvrack.com/manual/Building#building-rack-plugins
On Jan 5, 2020, at 3:01 PM, Ben [email protected] wrote:
I will assemble a complete example for one plugin in the next few days which you can compile yourself then. I have a working prototype but it won't help you very much in its current state.
Here are the instructions for setting up a build enviroment for VCV Rack plugins: https://vcvrack.com/manual/Building#building-rack-plugins
Out of curiosity, are you even able to put out a MIT licensed Rack plugin, or is the use of GPL because Rack itself requires the plugins to have it? If it’s the latter, that’s GPL working as intended and I withdraw my objection (but will still want to see a working model :) )
Chris
Hey guys,
chiming in because I ported some Airwindows plugins to Rack already for my own pleasure. Adjustments are still necessary, but overall they work great and are a blast to use. While I think it's worth releasing them to the public, I'm hesitant to publish anything without you, Chris, being cool with it. The way I see it these are still Airwindows modules as it is mostly Airwindows code and I want them to live up to the same standard as their VST/AU counterparts. Currently they are branded "Rackwindows" to indicate their roots.
Also, I'm not a DSP person, therefore I would be more than happy to collaborate on this and ensure everything is working as intended. The repository is private at the moment, but if you are interested I'll send you an invite for you to check it out yourself. Here is a screenshot of the modules ported so far.
As for the license: According to VCV Rack's plugin licensing guidelines the MIT license is fine. Actually any license is allowed as long as the plugin is offered free of charge.
Same thing. Can you give me a working example of any one? The MIT license doesn't mandate that you do this but I just want to make sure you're OK with the result of your invite: I would be interested, but I'll want to take a copy, Airwindows-ize it, and use it as a template for me to do what you're doing. (which doesn't mean you have to stop doing it! :) )
I'll send you an invite to the repository. I'm on Windows and I have never compiled for Mac so far, so you better build the modules yourself. Check this guide, it's pretty straightforward. If the environment is set up correctly, it's basically one "make install" and all modules should show up in Rack.
Of course you can copy and use whatever you like. That's what I did with your stuff :)
If you are serious about creating modules for Rack yourself (which would be great) I'm not sure I should release mine to avoid duplication. And like I said before, I see them as your work anyway. Need to think about it.
On the contrary. If I create modules, I might not pick the same ones and I would certainly make them look different :) which means even with DSP code, you would be doing your own thing! That is the very reason I use MIT license. You could even do a Patreon or something, try to get support for taking on the very large task. I certainly won't be able to do 'em all even if I find I can do stuff, plus I might find I want to do totally different things for VCV Rack. I don't even know if it'll run well on my machine but now I have an extra reason to try :) By all means go forward with anything you would like to see in your collection (which is also mine), your way. You might have a totally different idea of how to structure a module than me. Also if you include things like meters or indicators I'd be very interested to see how that is done. We can do all the duplication we want, or try different things. This could be awesome :)
Fair points. I'm all for variety and will go ahead then and try to get these modules ready to be unleashed on the public :)
I would like to ask for a favour though: If you find the time please do check sometimes and confirm the modules I'm porting are sounding the way they are supposed to. I have some doubts about Tape in particular (and to a lesser extent MV), where I had to do some nasty hacky gain padding to get them to behave and not clip (internally), while all other modules pretty much worked out of the box. Also, surely I'll have a question once in a while where I would like ask for clarification and advice regarding the DSP parts if you don't mind. What would be your preferred channel of communication then? Email?
I have yet to play with meters, but there is a simple implementation of lights in Vibrato already, where the brightness is set according to the values of 'sweep' and 'sweepB' respectively. Otherwise have a look at how lights are done in the Fundamental modules or other well kept repositories like Geodesics or Audible instruments.
Oh btw, of course the modules will be open source too. I want them to be available for everyone to mess with. And if it drives some traffic or interest your way, even better.
Did anyone release some Airwindows plugins in a VCV Rack format? it would be great to include some in https://github.com/DISTRHO/Cardinal if you did.