Re: Why VST??
Posted: Sat Jan 14, 2017 5:43 pm
That's true.Drumfix wrote:You don't know the history of my fight for an external UI extension for VST.
Such idea has a right to exist.Drumfix wrote:The simple idea (also used by Linuxsampler) is to completely separate the GUI code into its own application. Therefor once and for all solving the problem of different GUI toolkits not working together well when used inside the same host.
That's really bullshit.Drumfix wrote: Unfortuantely host developers refuse to implement it with even the most ridiculous excuses for not doing so. (not scalable, too complicated for plugin developers, "i want my host have control over the window", "i want my host to embedded the your plugin window", you name the bullshit).
Such decision is arguable. Different generations of the same framework (like GTK or Qt) can not coexist in the same address space. But developers still want to do nice and beautiful UI for the software, so they can spend more time by implementing toolkit or spend less time by using some another toolkit.Drumfix wrote: So whenever i see some plugin developer again complaining about the toolkit problems and start to code his own i only have a sarcastic LOL.
It's a good solution. But maybe all is not so bad that we really need to run UI as an external process.Drumfix wrote: My own plugins use the external UI extension (even though it is not supported by any host but my own proof of concept host) and have a (simple, but not so nice) fallback so they can be used in any linux VST host ever written, from the very first energyXT from 2006 to the lastest ardour/reaper/bitwig ...
Oh shit... And what do developers of Reaper say about that they don't call effEditOpen/effEditClose?Drumfix wrote: As for the reaper hint: While reaper never calls a plugins "effEditOpen"/"effEditClose" it does call "effEditGetRect" every second time the GUI button is pressed. So a wrapper plugin can use this as the trigger to create a new window and supply it to the "effEditOpen" of the hosted plugin.
Such a wrapper could host LV2 plugins as well of course.