DP and Omnisphere problem

[gavspen]

I beg your indulgence. I know this isnt the Spectrasonics forum, but this would appear to be a problem between DP and Omnisphere, and if anyone has a clue I'd be grateful.

I have a small project which includes an instance of Omnisphere playing 5 parts. When all 5 Omnisphere parts are playing it causes voices to be cut off here and there. (I rendered one of the parts to audio and got around it like that.)

I sent the file to Spectrasonics who say that it plays fine there, obviously indicating that the problem lies within the relationship between DP and Omnisphere on my rig. As we all know, everyone's situation is unique.

Does anyone have any idea what I might tweak in DP, and or Omnisphere to make this problem go away?

I have upped the buffer in DP to no effect; dialed up the voices count on Omnisphere, likewise; dont know what "Work Priority" or "Host Buffer Multiplier" are (and neither is mentioned in the manual; real helpful).

Does anyone have a suggestion? As I say, I would be most grateful.

Gavin

[hammerman]

You definitely have enough horsepower. Sometimes I have issues with Omnisphere and Trillian when the plug window is closed and the plug is in Pre-Gen mode (pre-rendering). If I have the plug window open, all is fine, even if it is in the background. Hope this makes sense. Maybe DP 8 will solve this little problem. Sometimes a bounce will have voices cut off of play when they are not supposed to. Again, if I do a bounce and that plug window is open somewhere, all is well.

[rickorick]

Did you try increasing the voices in DP?
Just a thought.

[gavspen]

Did you try increasing the voices in DP?
Just a thought.

I didnt know I could. How do I do that? There's nothing in the manual.

[cowtothesky]

I think your running into a ram overload. Since DP is 32 bit, you can only use up to 2GB of Ram on vi's. I used to have problems with Omnisphere when I had more than 4 patches loaded up. When I got VE Pro and was able to utilize all of my ram, my problems went away. I suspect that DP8 will take care of this problem for you, since it is 64 bit and you will be able to use all 6gb's of your ram. In the meantime, I would load up no more than 3 patches on Omnisphere, bounce it down to an audio file, and then load up the other 2 patches with the audio file.

[doodles]

not sure about the raising voices thing, but sounds to me like a memory problem. (i.e. you've maxed omnisphere out in DP). The max you can use is about 3 gigs of ram in DP, until the 64-bit version. Omnisphere and Trilian are HUGE memory hogs. (But also awesome!). You'll easily max it out. I offload them onto VE Pro, but if you use it in DP, you're gonna need to freeze quite a lot.

[gavspen]

You're probably right, doodles and cow, but I here's what I dont get. I sent this DP project to Spectrasonics (pared down to just the Omnisphere parts) and they opened it up and had it play fine. If this is a "DP is only 32 bit/you're outta ram" problem, why didnt it happen to them too?

I realise you dont know the answer, and on Monday I'll check with them that they actually did open it up in DP, rather than load it into Logic, or something.

Just wondering out loud.

[spire10r]

Hey Gavin,

Since you mentioned it, does your system still freak if you disable all the other parts and just try to run the 5 omnisphere voices? Could be something else in the project that's tipping the CPU load vs when the Spectrasonics guys tested on their rig? Just throwing it out there...Who knows that they didn't test it on Skynet or whatever beastly system they use to develop their stuff

I'd also be curious to know where your sample libraries are stored in relation to the project file. Could be an overworked HD in the chain?? especially if your CPU usage meter looks ok. I haven't used Omnisphere much personally but I'd imagine there are some disk-streaming preferences that may help out if this is the problem.

[gavspen]

Hey Gavin,

Since you mentioned it, does your system still freak if you disable all the other parts and just try to run the 5 omnisphere voices? Could be something else in the project that's tipping the CPU load vs when the Spectrasonics guys tested on their rig? Just throwing it out there...Who knows that they didn't test it on Skynet or whatever beastly system they use to develop their stuff

I'd also be curious to know where your sample libraries are stored in relation to the project file. Could be an overworked HD in the chain?? especially if your CPU usage meter looks ok. I haven't used Omnisphere much personally but I'd imagine there are some disk-streaming preferences that may help out if this is the problem.

Yes, I still get the dropouts. As mentioned, the file I sent to Spectrasonics was pared down to nothing but Omnisphere and apparently it plays fine there, but not so here. (Again, I'm assuming they opened it in DP but I'll make sure tomorrow. Be kind of silly for them to try to troubleshoot a DP problem by opening it in something else, and if there's one thing the good folks at Spectrasonics arent, it's silly)

My sounds are on a different HD than the project. Although the original project was on a third drive, the "Omnisphere Test" file, which is what I sent to Spectrasonics, is on the system drive. I see very rare CPU spikes even when playing this tiny file, not in any regular predictable way, and not during the dropouts, but CPU spikes on such a small file make me think there's a fundamental problem, perhaps.

I'm not sure about disk-streaming prefs in Omni, I'll hunt around, but I think Spectrasonics would have suggested it by now.

I cant help but feel it's unique to my set up, or Spectrasonics would have heard of the problem many times by now, dont you think? Very VERY annoying.

Gavin

[gavspen]

For those that still care, Spectrasonics tested the file in DP, on an iMac with 8gig ram and Lion, and it played fine, so it must be a problem unique to me.

Not that that helps solve it.

[spire10r]

Any idea if they tested on 7.24? Not that it would make a difference but your profile says you're using 7.22. It's a long shot but worth looking at any differences between the two systems. If there isn't a particular reason you're sticking with 7.22, updating would be MY next move.

[gavspen]

Any idea if they tested on 7.24? Not that it would make a difference but your profile says you're using 7.22. It's a long shot but worth looking at any differences between the two systems. If there isn't a particular reason you're sticking with 7.22, updating would be MY next move.

I missed your post spire; they did use 7.24, and so have I been for a while, but I forgot to change the sig. Done.

Anyway, for anyone else having similar problems, there's a happy ending. Spectra sent me this link....

http://www.spectrasonics.net/support/kn ... egoryID=13" onclick="window.open(this.href);return false;

....and doing the tweaks listed there fixed it. Whaddya know?

Thanks all
Gavin

[toodamnhip]

You definitely have enough horsepower. Sometimes I have issues with Omnisphere and Trillian when the plug window is closed and the plug is in Pre-Gen mode (pre-rendering). If I have the plug window open, all is fine, even if it is in the background. Hope this makes sense. Maybe DP 8 will solve this little problem. Sometimes a bounce will have voices cut off of play when they are not supposed to. Again, if I do a bounce and that plug window is open somewhere, all is well.

I too have found that stuck notes and other problems were occasionally relieved by leaving plugs windows open. If you use "spaces" you can devote one to plugs and leave them all open.