William Grant
New Member
I recently tried running one of Airwindows' plugins, he makes a lot of super interesting boutique audio plugins (that are free thanks to Patreon!)
One of his hallmark 'styles' is that he doesn't code explicit GUIs, favoring to keep it simple and only expose parameters.
Unfortunately OBS doesn't seem to know what to do with this.
Here is a screenshot showing what REAPER does for VST plugins with no specific GUI, it just gives you sliders for the parameters.
Here is what Ableton Live does for VST plugins. You *always* have the ability to control parameters in a 'native' format.
As well as the option to interact with the plugin's bundled GUI via the little 'wrench' button.
Finally, here is a little mockup of what I think a logical change to the VST plugin filter could be.
Always add sliders for every exposed control to the filter window.
This would allow these GUI-less plugins to work in the sense that users could still adjust parameters, without you having to build some "GUI generator" like REAPER seems to be using.
I think this might also allow for some convenience in terms of copy/pasting filters, as you could store the parameter values with the same mechanism you already do for the 'native' filters.
One of his hallmark 'styles' is that he doesn't code explicit GUIs, favoring to keep it simple and only expose parameters.
Unfortunately OBS doesn't seem to know what to do with this.
Here is a screenshot showing what REAPER does for VST plugins with no specific GUI, it just gives you sliders for the parameters.
Here is what Ableton Live does for VST plugins. You *always* have the ability to control parameters in a 'native' format.
As well as the option to interact with the plugin's bundled GUI via the little 'wrench' button.
Finally, here is a little mockup of what I think a logical change to the VST plugin filter could be.
Always add sliders for every exposed control to the filter window.
This would allow these GUI-less plugins to work in the sense that users could still adjust parameters, without you having to build some "GUI generator" like REAPER seems to be using.
I think this might also allow for some convenience in terms of copy/pasting filters, as you could store the parameter values with the same mechanism you already do for the 'native' filters.