Vienna Symphonic Library Forum
Forum Statistics

182,262 users have contributed to 42,216 threads and 254,737 posts.

In the past 24 hours, we have 3 new thread(s), 22 new post(s) and 40 new user(s).

  • Small problem with VE Pro and SL/Logic 8

    I've recently installed VE Pro, and reinstalled damned near everything else. I've got a full template, with the following setup:

    2 Instances on a G5 Dual 2.5ghz. Filled with Brass, Woodwinds, and Percussion

    1 64 bit instance on host machine, with 4 gigs of Strings loaded.

    1 32 bit instance on host, with some 3rd party libraries.

    1 Play instance with SC with WB, 2 gigs.

    My machine is a Mac Pro Quad 3.0ghz, 16GB Ram. With everything loaded I have 11.52GB used, and 4.48GB free. Logic is using 646MB, so it's no where near the limit.

    The problem I'm having is that Logic slows down whenever anything is changed. If I load an effects plugin, I have to click and hold and wait for the beach ball to disappear. The same goes if I delete a track, or add a send to a track.

    I'm noticing that nearly every single action that I do in Logic, my VE instances on the host, and on the G5 (which would be 4 total instances) are auto-saving the project file, and holding at 99.9% CPU for the time the beach ball rolls.

    I have no idea to fix this, nor if there is a fix. But I wanted the team to know at least, as I don't really see a reason VSL needs to save everything I do something in Logic.

    A non-releated, but VSL related question:

    How exactly does the preserve function work? When I set the preserve function, it attempts to load another instance and leave the preserved one open anyway. They don't connect though. It doesn't seem to work as intended.