Forum

I too am running 2.0.74 (Pro) with Mountain Lion and can save user setups based on (Pico) Factory Setup 1. But now you come to mention it, I do recall having to Force Quit EigenD on one occasion. JOOTT, I thought. But maybe there's a bad agent in there that you're tweaking and I'm not...?

The only times I have to force quit EigenD is when an AU crashes (typically an NI AU)

I've always had to force quite Eigen D on my macbook pro - every OS version, every eigenD pro version, every time. I've always put it down to the AUs I use (usually bidule, usually running multiple instances of Zebra/Zebrify and Pianoteq, occasionally Octopus - and usually with lots of midi and OSC stuff going on). Closing AU windows before quit doesn't help. So I just force quit it and don't think about it anymore.

Have had the same issue for many versions of EIgenD. Geert analyzed some bug reports I sent in and pointed to Alchemy as the cause. I'm sure there may be/have been a problem with Alchemy, but no other AU hosts I use behave the way EigenD does (won't quit).

Yes, very often it's the AU/VST plugins for the very simple reason that the plugin specifications are not well written enough. A lot of plugin authors just test in the popular hosts and whatever works in there should work elsewhere. Often this leads into problems on alternative hosts and many of them can never get it to fully stabilise since there's often no way to know what's going on. Randy, Camel Audio actually confirmed that Alchemy bug and should have fixed it in the latest version, it's not because other hosts work that there are no bugs.

bhinton, Bidule is a known problematic plugin since it increases the compatibility problems by adding another layer of hosting. I've had Bidule crash Logic, Reaper and Cubase many times.

So in the end, we did the best to make the plug in hosting as reliable as possible but it's an endless stream of new strange behaviour that takes an eternity to track down, with often not a real solution that can be found.

Note that we use Juce (http://juce.com) for the plugin hosting, which is the most popular open source solution for this. We've contributed back a large series of work arounds, but even in the smallest Juce-only host some problems still remain with certain AUs/VSTs. In the end we put the accent on making sure that the live-performance which using the plugins is as reliable as possible and did our best to make the shutdown as good as possible.