Hi, a Q for people that support this - I’ve just played around with the HostPluginDemo as I’m thinking of adding plugin support, and it keeps crashing when scanning - do people in the real world launch a new process to scan each plugin to deal with this?
On the surface, adding this support seems fairly easy (apart from the scanning), but I’m guessing there are plenty of gotchas to make it more interesting.
Any comments and insights welcomed, thanks!
Some plugins will crash because of their copy protection when run under the debugger. That is extremely irritating when one needs to do the plugin scanning step when developing a host. But it may also just be some other incompatibility problem between Juce’s plugin hosting and the plugins you have installed. The Juce plugin hosting certainly isn’t perfect and there are of course all kinds of problematic plugins around that require hosts to do workarounds to support them.
These days it should be pretty much standard procedure to do at least the plugin scanning with external processes. You might also want to consider allowing the actual hosting and processing to happen in a separate process, too. (The latter is kind of involved to implement, though…)
