Omnisphere - Post purchase Questions, Issues, Problems

[rcat]

I'd just like to thank all the folks out there, especially at this point in our economic history, that are willing and able to spend $500 on a piece of software that for whatever reason, may or may not work for them. They're the ones that, whether planned or not, truely cut through the hype and let the rest of us who aren't so financially well off, know whether or not a product is ready for prime time. Either that or a company could adaquately beta test their product before putting up it for sale. If said company felt that they didn't have enough resources to fully beta test their product themselves, they could always send us out here in the ether enough preliminary copies to cross reference as many systems as possible. What do you think? Am I being negative here?

[zerocrossing]

Not sure what you mean by "More Solid"? If you mean you believe you've found a bug in Omnisphere, then please contact tech support ASAP and we'll get right on it.

Yup. I will. The only reason I haven't already is the silly need to provide your serial number to report a bug. I'm a registered user... why can't I just log in and have access to support?

[koolkeys]

I'd just like to thank all the folks out there, especially at this point in our economic history, that are willing and able to spend $500 on a piece of software that for whatever reason, may or may not work for them. They're the ones that, whether planned or not, truely cut through the hype and let the rest of us who aren't so financially well off, know whether or not a product is ready for prime time. Either that or a company could adaquately beta test their product before putting up it for sale. If said company felt that they didn't have enough resources to fully beta test their product themselves, they could always send us out here in the ether enough preliminary copies to cross reference as many systems as possible. What do you think? Am I being negative here?

It depends on if you are talking in generalizations or trying to dig at Omnisphere or a specific product. There is NEVER a way to 'fully' beta test something. When would you say that enough beta testing is really enough? I've beta tested for dozens of apps and plugins, most of which are full blown NDA, non-public testing. You can try as hard as you want. You will never find all the bugs.

Brent

[GlennO]

I don't doubt for a moment that you know exactly what you're talking about, but please realize:


1) Users with problems, pc or mac, are few in number. I see the reports that come into tech support. I monitor northernsounds. The vast majority of issues that come up are about installation or system configuration, not bug reports with the software.
2) Your problem is important to us. I've been there myself... when I'm experiencing a problem, I don't want to hear that I'm an unusual case. But, I do take solace in that case, and I hope you will too, from the knowledge that if many other people are not having problems, then a solution for my situation is probably close at hand.
3) We do not develop primarily for the mac. I don't know who told you that, but they are incorrect. We develop on mac and pc in parallel.

- Glenn

Glenn - the evidence of my experience and of *many* others I've read on forums confirms that PC users ARE indeed having significant problems. Please, please get yourselves some PCs and various PC-based DAW software in-house and rigorously test Omnisphere on them. Like zircon I've been using DAWs for decades and, I believe, know what I'm talking about.

[topaz]

Omnisphere has been the most stable feature rich v.1 product I have ever owned, I am stunned at how well it runs on my Pc and Mac for such a powerful and deep instrument, any minor bugs where fixed lightning fast, the atmosphere patches where released as promised and on time.

the only recent product I can compare to is Alchemy and so far that has REAL issues that need to be fixes ASAP, some are Major bugs and some are oversights in design.

from what I have seen most problems users are having with omnisphere is down to old machines running on bare minimum specs.

hats off to spectrasonics

[C-note]

Omnisphere has been the most stable feature rich v.1 product I have ever owned, I am stunned at how well it runs on my Pc and Mac for such a powerful and deep instrument, any minor bugs where fixed lightning fast, the atmosphere patches where released as promised and on time.

the only recent product I can compare to is Alchemy and so far that has REAL issues that need to be fixes ASAP, some are Major bugs and some are oversights in design.

from what I have seen most problems users are having with omnisphere is down to old machines running on bare minimum specs.

hats off to spectrasonics

+1

[RawTheory]

Omnisphere has been the most stable feature rich v.1 product I have ever owned, I am stunned at how well it runs on my Pc and Mac for such a powerful and deep instrument, any minor bugs where fixed lightning fast, the atmosphere patches where released as promised and on time.

the only recent product I can compare to is Alchemy and so far that has REAL issues that need to be fixes ASAP, some are Major bugs and some are oversights in design.

from what I have seen most problems users are having with omnisphere is down to old machines running on bare minimum specs.

hats off to spectrasonics

+2

[Zero dB]

Great. Good for you.

But this thread isn't an Omnisphere popularity contest or a poll of who's not having problems. Read the title and the OP; it's about issues and problems *with* Omnisphere. Anecdotal "it's working great for me" posts don't really help those of us who are having real issues.

Appreciating Glenn's input though, and others who are being constructive. Us Z guys should stick together

ZdB

[koolkeys]

Great. Good for you.

But this thread isn't an Omnisphere popularity contest or a poll of who's not having problems. Read the title and the OP; it's about issues and problems *with* Omnisphere. Anecdotal "it's working great for me" posts don't really help those of us who are having real issues.

Appreciating Glenn's input though, and others who are being constructive. Us Z guys should stick together

ZdB

It's not a popularity contest. But it was stated as if it was completely useless on PC or something. Others have said "they should have tested it better". Useless statements like that do NOTHING to fix problems, and they don't add to a thread like this either. Just as it's not a popularity contest, it's also not an Omni bashing thread. It's here to help solve problems. And those statements do nothing to solve them, nor do they represent reality.

If you or anyone else wants to believe that we're making it a popularity contest, that's your parogative. But that's not the case at all.

Brent

[koolkeys]

Also there ARE in fact problems with 1.0.2 that haven't been addressed. I know this for a fact because I've reported one!!! Tech support even acknowledged it. "Obie Snow Swell" simply causes a huge burst of noise in FL unless you change the filter settings. It otherwise completely messes up the audio buffer and forces you to restart the program. I sent a project file in, as a matter of fact, to prove it.

I can confirm this and say that the noise is VERY annoying. Actually, it's almost painful. I just tried it to have another voice. But that patch does indeed create the most obnoxious noise in FL Studio. Yikes.

Anyways, it doesn't need proven. It definitely happens.

Brent

[GlennO]

Yes, there is a known problem in the Chorus Echo effect in 1.0.2. I believe it only occurred in Fruity Loops. Changing the Chorus Echo mode from BPM to Echo should work as a temporary workaround and it is fixed in the upcoming 1.0.3 update

- Glenn

Also there ARE in fact problems with 1.0.2 that haven't been addressed. I know this for a fact because I've reported one!!! Tech support even acknowledged it. "Obie Snow Swell" simply causes a huge burst of noise in FL unless you change the filter settings. It otherwise completely messes up the audio buffer and forces you to restart the program. I sent a project file in, as a matter of fact, to prove it.

I can confirm this and say that the noise is VERY annoying. Actually, it's almost painful. I just tried it to have another voice. But that patch does indeed create the most obnoxious noise in FL Studio. Yikes.

Anyways, it doesn't need proven. It definitely happens.

Brent

[koolkeys]

Excellent! I only use FL Studio occasionally, and I had never used that patch before. I only tried it because of zircon's post. But good to know that it's been fixed!

Brent

[zircon]

But I'm not talking about "Chorus Echo", I'm talking about Obie Snow Swell... I know the Chorus Echo bug, but the Obie problem is with the UVI filters. When you change the filter to Crisp it works fine. Has nothing to do w/ fx.

[koolkeys]

But I'm not talking about "Chorus Echo", I'm talking about Obie Snow Swell... I know the Chorus Echo bug, but the Obie problem is with the UVI filters. When you change the filter to Crisp it works fine. Has nothing to do w/ fx.

Oh. I tried it, but didn't really try to find what the issue was. I know the problem does happen, but I guess this may not be the same bug then?

Brent

[GlennO]

There were two bugs in Obie Snow Swell. The second one was with the use of the Spread parameter with the UVI HP filter. That also occurred with Warm Pad Ice, but again, only in Fruity Loops. Anyway, that is also fixed in 1.0.3. Sorry about the confusion.

- Glenn