Omnisphere - Crash with Kontakt

[kdm]

Since I've owned Omnisphere, it has had serious bugs within Nuendo.

(Yeah, I know, it's my system - likely my desktop wallpaper of my company logo, or something to do with the Native American pottery sitting on my desk..... :icon_rolleyes:)

In earlier versions (before 1.04g), it would randomly start issuing a 0dbFS hum from one of its' outputs. I covered that in another thread here (http://cubendo.com/showthread.php?t=484).

They fixed that in 1.04f after I sent several reports on it and how to repro. 1.04f was later replaced by 1.04g for reason I never figured out. I have 1.04g running now.

Now a new similar bug has arisen that was not in the previous version:

ASIO mutes and Nuendo crashes when a note-on message is sent to an Omnisphere instrument, with any version of Kontakt in the project. I get a serious error from Nuendo. Obviously, when the first note is played, Omni (or any sampler/synth) is loading ram, and accessing the DAW's ASIO layer. Kontakt is fine as long as I don't send a note on to an instrument in Omni, and Omni does have to have an instrument loaded - it's fine if I just load an empty instance of Omni.

I can run Omni alone in a project, but have to be sure to close Nuendo, not just the project, before starting a project with Kontakt in it. Whatever it is doing is causing a residual problem within Nuendo, so if I start a new project without first closing Nuendo, then load Kontakt, the project will immediately crash with a serious error.

No other VSTi has any issues with Kontakt - not Play, Kontakt 2 with 3, not RMX 1.7, Rapture, etc. Only Omni.

Now Spectrasonics is asking me to pursue this with NI since they don't have a copy of Kontakt. I have of course asked them to buy a copy. I'm not a paid troubleshooter.

My patience with companies pushing back on the customer to solve problems like this is wearing thin. This DAW was built by Sonica. It has little on it besides Nuendo and VSTis - Sequoia, Reaper, Sonar, Adobe Web CS3, MS Office 2003 and Vegas 8. That's it.

Omni is fine in Reaper and Sonar. This only exists with Nuendo, Kontakt and Omni, and Omni and Nuendo are the only common denominators.

[TAFKAT]

Hey Dedric,

You are not an island with Omnisphere having issue in Cubendo, I have numerous clients complaining to me about it being unpredictable..

Some have simply gone back to using multiple instances of Atmosphere, one client easily running as many as 20 + instances on a Dual Quad, with no issue, where Omnisphere on the same system would load 3-4 patches and become flakey, hopeless..

Here as an interesting working around tho.., Omnisphere via FXT on a satellite system , 2 instances fully loaded.., stable, go figure.

Worth a shot.. ;-)

[kdm]

Eventually it will go on a satellite system, but I'm fresh out of PCs at the moment. All are loaded to the gills with the orchestra libs.

I'll run it in Bidule on a slave eventually. Better on the host due to tempo sync needs. That's sketchy on a slave system, esp. with the latency involved, but I haven't tried running sync through Bidule.

Good to know I'm not the only one. I already know NI's answer - never heard of it - must be a Nuendo or Omnisphere problem... I'll actually agree with them there.

[RiffWraith]

"Spectrasonics is asking me to pursue this with NI since they don't have a copy of Kontakt. "

Am I the only one that finds that extremely difficult to believe?

[kdm]

You aren't the only one. But in a way it doesn't surprise me that they didn't test with other VSTis.

I think too many current developers (esp. VSTi devs) work in a bit of a vacuum intending for their products to be the only ones their customers use. Highly unrealistic of course.

Also some of these companies are just a handful of developers - maybe only 3 or 4 doing everything, including setting up their own test rigs.

[Andrew J]

I don't find it surprising they didn't find this themselves. It is surprising they don't want to jump all over it and fix it though!

I think I'll just keep delaying my upgrade from Atmosphere.

[kdm]

Apparently I'm the only one seeing this problem.

[mcmace]

I use Omni and K2 Player - seems good so far except for crashes when browsing sounds in either Omni or K2Player - it seems that the RAM doesn't get unloaded of previous samples that causes N4 to crash at some point.

Spectrasonics Tech Support told me they don't have Nuendo...so they can't test on it - seems that we are the ones on the island, in need of endless computer power and compatibility with everything.

But seriously, why can't SB just send a few copies over to Spectrasonics - I mean it's not exactly an unimportant VST-Instrument developer...:icon_rolleyes:

Do they just give a sh#@???

[RiffWraith]

" it seems that the RAM doesn't get unloaded of previous samples "

Same with RMX. I question whether or not this is a host thing, or a Spectrasonics sample player thing.