Hi,
Anyway - I haven't used it at all in the past 3 months, then last night I required it on a project. I fired up a VSL instance in my Logic 9 session, and was dismayed to see that when I clicked the "Show Window" button on the plugin window, Vienna Instruments would come up, and be followed by the "Beach ball of doom". This is where it stayed, permanently (crashing both the plugin and the host). I tried loading the standalone version, and the same thing happened. Here's the thing, according to Activity manager, the software is immediately taking up something like 80 - 100 % of the CPU, while only chewing through about 50 mb of memory.
So here are the obvious things I tried to fix the problem :
* Updated Logic with Software Update to be up to date.
* Updated to the latest version of Elicenser Control Center. No issues.
* Made sure the Vienna Directory manager points to the right drives - no issues there either.
* Updated Vienna Instruments interface from Version 1.1.1. (!) to the Latest Mac OSX Build.
* Performed disk repair permissions on my system/Logic drive
None of these have solved the problem.
Has anybody come across something like this before? I'm kind of at a loss as to what to do from here, and I really do need to get this library up and running soon - I was lucky enough to fire it up a week or so before I have to use it in a session, rather than the day before, but I really do need to fix the problem ASAP.
Thanks,
Alex
P.S. - One odd quirk I did notice : In the "Plugin window" in Logic, you can actually save "Presets" for a Vienna Instruments Instance. I had one preset set for a Bosendorfer piano. I noticed that if I just clicked the preset, the sample loaded ok, and I could use it in the session. However, once I tried to click "Show window" (which loads the VSL Server Interface), the beachball problem returns.
