Originally Posted by DaveC
It seems that 64bit for OSX won't take
that long anymore, in fact, I read that
Giancarlo is testing it now.
Now if the RAM footprint can be reduced
with distribution across multiple instances,
than I'm a happy camper!
I did notice that too... just as a test, I loaded half a dozen of the lower latency versions... and they spiked one of 8 cores. Frustrating... but not nearly as much as all the problems from running one single instance of the high latency version (reverb) If that's just the way it is in Logic, then so be it, but the lack of answers, documentation, etc is really quite surprising considering how problematic it is. This is not like most plugs. Most plugs just work. The issues I've had here are issues I've never had before with hundreds of plugs tried.
There really needs to be (WITHOUT digging through forums) a clear, and simple one page readout PER DAW that reads like the following:
The reverb version uses higher latency. This has the benefit of reducing CPU load, and will let you run programs with longer tails, etc. These higher latency settings are recommended for Nebula use in general, but are not default on the non-reverb version for the non-reverb instances that don't require it because the latency settings can cause issues.
First, be aware that if you use even one instance of the reverb version anywhere in your session, your playhead position shown on the screen will no longer match your audio position. You will see your playhead cross a song position first, and the audio will follow noticeably later. This has to do with the way Logic compensates for the unusually high latency settings.
Second, if you do additional latency-inducing routing... like taking the output of a reverb buss with a reverb instance of Nebula and sending it to a subgroup, this may cause logic to be unable to properly handle the latency, and may cause delay compensation issues with various tracks (especially virtual instruments.) Instruments may begin to play out of sync with the rest of the audio. Additionally, this may cause overload messages which will cause the session to stop.
For these and other reasons, it is suggested that you do not use nebula reverb until you are ready for mixing and use simplified routing when you do use it.
If I had seen that simple disclaimer up front, it would have saved me a week of headaches. Instead, I had to dig... and dig... and dig... and dig... and dig...