Sorry if this has been addressed before, but I couldn't find an answer on any of the previous posts- I'm having serious streaming/glitching/freezing problems using Omnisphere and I wanting to see if there was something simple I missed that might help with the work flow which has been halted.
Here's the setup in ProTools: 3 tracks- click, omnisphere, and TLspace. That's it! Omnisphere has four patches with a couple of filter tweaks and no additional FX than what normally loads with the patch. I can play simple melodies, but if I play a chord with more than 3 notes, the output glitches and/or freezes. Very Frustrating.
In PT, the H/W Buffer size is 1024 (I don't mind the latency as the tempos are slow), I've tried 1 and 2 Processors, and I've modified the CPU Usage between 90-99%. No Luck.
In Omnisphere, Streaming is ON, Pre-Load is normal or maxed, NumBytes is normal, min, or max, etc., I haven't found the magic setting. Also, when it glitches, the code starts with either a 21- or a 25-, not a 5-10# like the Spectrasonics support page says for Streaming issues. So perhaps it's not a streaming issue?
Currently I have my audio/session files on one ext. drive and my samples on another ext. drive. Has anyone had more/less success running the Omnisphere samples from the system drive?
I'm stumped and would love (and need) to keep using Omnisphere, but can't at this rate.
Also, my setup has run great on an array of previous sessions, including mixing 40+ tracks with 30+ plugins, and more complex sessions running several instances of Kontakt with multiple patches loaded on each one + other instrument plug-ins all at once. No glitching.
Any help with this would be VERY appreciated.