On Thu, May 28, 2009 at 6:20 AM, Julien Pommier <pommier(a)modartt.com> wrote: Well, we'd like FST to work with as many different plugins as possible, so a fix would be nice. I think Jules actually is making an unreasonable assumption when he mentions that JUCE is expecting the "initialize" and "open" calls to come in the same thread. "initialize" is purely about loading/initalizing the plugin DSP code - its entirely possible to run a VST plugin without ever opening its editor. The "open" is required only when the user asks to see the editor. Because of the way win32 event loops work, the thread that is going to wait for events on this window also needs to be the one that creates it. There is no obvious reason why this would be the same thread that was used to initialize the plugin. There are several other thread "wrappers" such as the Waves shell which face the same issues as JUCE but work just fine with FST. I'm entirely open to a fix in FST if there is one that doesn't look like a grotesque hack :)