I think this generally falls under the "must be easily available freeware" clause. If your plugin (or your modified version of an open source plugin) is not publicly released, that seems like a problem. Though, I've used custom JSFX in Reaper for scripted MIDI processing and parameter automation without pushback. I suppose that's partly because it's not a traditionally compiled plugin, and partly because processed MIDI can be rendered to MIDI clips if necessary.December’s synth was open source. Is there a OSC rule which either allows or disallows modifications of the source code? [...]
Does a similar OSC rule already exist governing use of open-source effects plugins?
And then there is potential use of closed-source plugins by those of us who have written plugins which have not been publicly released.
I'm not sure how the rules on unreleased plugins work in rounds with special exceptions to allow commercial effects. It doesn't seem permitted according to the letter, as they're not really commercial, either. But it seems to me it ought to be considered equivalent as a plugin that is not freely available to everyone.
As far as modifying the synth of the month, personally, I would consider it fair play to make modifications to get it working on your system, or modify the interface to your liking, as long as the engine is unchanged such that your DAW project would load and play the same for someone with the publicly available version. Adding synthesis capabilities to your own personal version doesn't seem acceptable, even if you made it public.
Statistics: Posted by FrogsInPants — Sat Jan 06, 2024 5:35 pm