KVR Audio

cain · Post by **cain** » Sat Jan 10, 2009 7:59 pm

sorry took so long to respond but i have no errors yet. but when i get home tonight i will try again . i will try and browse patches for a longer while again . i will report back

but its is weird how some people have problems and some dont, well i will check again tonight.

cain · Post by **cain** » Sat Jan 10, 2009 8:59 pm

well one thing i did notice is that when ever the omnishere gui is open on the screen the cpu usage jumps up by 30 percent but when i close it it drops down about 30 percent.
example (patch 03 steps of eternity) holding down 4 keys with the omnisphere gui close i get about 8 percent on the windows task manager but if i have it open omnisphere gui it jumps up to 40 percent. when i close it it goes back down to 8 percent.

now the weird part is that this is on my e8500 3.1ghz dualcore with 4 gigs.
when i try it on my q6600 oc 3.2 with 4 gigs i dont get this behavior its stays about thw same with itn open or close, about 4 percent on the windows task manager. ( both pc have the same memory and the same gigabyte motherborad)

going to have to report that to the tech department, never noticed that happening weird one.. but yes there are some more bugs that they have to iron out

well now am going back to try and see if i can reproduce the memory error you guys are getting.

koolkeys · Post by **koolkeys** » Sat Jan 10, 2009 9:05 pm

I don't recall, but what host are you using?

Brent

cain · Post by **cain** » Sat Jan 10, 2009 10:10 pm

if me i using old cubase vst 5.2 and also testing reaper the latest. i get no problems just the cpu usage thats weird with gui open. but besides that omnisphere works great im just testing to see if i could get the memory errors they were getting. in cubase i could not get it to do the error so i started testing it in reaper but no dice either, just testing for that is when i noticed the cpu and gui thing.
it happens on both cubase and reaper, but besides that i really see anthing else. but i will keep looking .

koolkeys · Post by **koolkeys** » Sat Jan 10, 2009 10:20 pm

cain wrote:if me i using old cubase vst 5.2 and also testing reaper the latest. i get no problems just the cpu usage thats weird with gui open. but besides that omnisphere works great im just testing to see if i could get the memory errors they were getting. in cubase i could not get it to do the error so i started testing it in reaper but no dice either, just testing for that is when i noticed the cpu and gui thing.
it happens on both cubase and reaper, but besides that i really see anthing else. but i will keep looking .

Check your video card settings and see if anything helps. Turn the hardware acceleration off if it's turned on. Even try changing your resolution and bit depth. I don't KNOW that these things could help, but it's worth trying. Hosts handle graphics differently, so also check your host settings to make sure that there aren't any render settings that you can change.

I'm not saying that it isn't Omnisphere. Just giving ideas to narrow it down and rule out other things.

Brent

cain · Post by **cain** » Sun Jan 11, 2009 12:53 am

cool thanks i will check tthe settings

cain · Post by **cain** » Sun Jan 11, 2009 3:02 am

yes turning off the hardware acceleration is what did the trick now im getting the same cpu suage with or without the gui.
thanks koolkeys

yairhol · Post by **yairhol** » Sun Jan 11, 2009 3:39 am

Isn't it a problem if we need to turn off hardware acceleration?
The acceleration is there to help us and as far as I can see, all my other softwares know how to work with it turned on.
Cain, please report this to Spectrasonics.

Thanks.

Paul Russell · Post by **Paul Russell** » Sun Jan 11, 2009 5:36 am

That's daft.
Try running aero without hardware acceleration.
Not much point in having a dual head Nvideo 280 if some rogue VST wants hardware acceleration off.

cain · Post by **cain** » Sun Jan 11, 2009 6:49 pm

dont worry guys i am reporting what i find

RawTheory · Post by **RawTheory** » Fri Jan 16, 2009 12:50 am

So I've just gotten the same "Out of Memory" message on a mid sized project, just surfing through presets. After one big one that was over 500 mb, the message came pretty fast. I then selected one more sound and I got the c++ error and Reaper crashed along with 45 minutes of work. My CPU was way low when this error happened. Spectrasonics needs to fix this error before they get totally focused on their new products...

Zero dB · Post by **Zero dB** » Fri Jan 16, 2009 1:32 am

Sadly Spectrasonics seem pretty much in denial about this. I don't know why - REAPER is perhaps the easiest DAW to quickly download and demo. They could repro this within minutes if they tried.

All we seem to hear is excuses; really disappointing.

yairhol · Post by **yairhol** » Fri Jan 16, 2009 6:11 am

RawTheory wrote:So I've just gotten the same "Out of Memory" message on a mid sized project, just surfing through presets. After one big one that was over 500 mb, the message came pretty fast. I then selected one more sound and I got the c++ error and Reaper crashed along with 45 minutes of work. My CPU was way low when this error happened. Spectrasonics needs to fix this error before they get totally focused on their new products...

Can you please send this report to Spec. tech support?
We need to at least show them that we sent them the emails and that more people are having these problems. Last time I got an answer from GlenO he said that only 2 people reported this problem although I sent them reports from at least 5 or 6 more users who reported this.

RawTheory · Post by **RawTheory** » Sat Jan 17, 2009 11:00 pm

yairhol wrote:
RawTheory wrote:So I've just gotten the same "Out of Memory" message on a mid sized project, just surfing through presets. After one big one that was over 500 mb, the message came pretty fast. I then selected one more sound and I got the c++ error and Reaper crashed along with 45 minutes of work. My CPU was way low when this error happened. Spectrasonics needs to fix this error before they get totally focused on their new products...
Can you please send this report to Spec. tech support?
We need to at least show them that we sent them the emails and that more people are having these problems. Last time I got an answer from GlenO he said that only 2 people reported this problem although I sent them reports from at least 5 or 6 more users who reported this.

Well here's the thing. I now know that the memory Omni's addressing is virtual memory. My hard drive was almost full after the Omnisphere install, so that could ahve been the source of my problems. I called ADK Pro audio and they said they were surprised I wasn't running into problems already, which I was.
So now I've moved the 42GB STEAM folder into a fresh 500GB firewire hard drive, which should leave plenty of room for virtual memory.
If I run into the "Out of Memory" message again, then I'll definitely email Spectrasonics again...

yairhol · Post by **yairhol** » Sun Jan 18, 2009 3:38 am

I have 60GB left on my HD but get this message from time to time.

Omnisphere - Post purchase Questions, Issues, Problems