KVR Audio

wagtunes · Post by **wagtunes** » Sat May 16, 2015 10:57 am

In going over the patches causing this (only a few) I have also noticed that granular was on as well.

FTR, with Omni 1, I was able to run 42 instances of the plug before my PC couldn't take it anymore. So I do not believe this is a matter of poor hobbyists weak PCs not being able to handle the program. I believe this is a serious bug that needs to be addressed.

noiseboyuk · Post by **noiseboyuk** » Sat May 16, 2015 11:29 am

wagtunes wrote:In going over the patches causing this (only a few) I have also noticed that granular was on as well.

FTR, with Omni 1, I was able to run 42 instances of the plug before my PC couldn't take it anymore. So I do not believe this is a matter of poor hobbyists weak PCs not being able to handle the program. I believe this is a serious bug that needs to be addressed.

Same CPU hit here overall as with 1 with patches and tech from 1, I'm seeing no difference there at all. The new granular mode is CPU-heavy, they mentioned that they might be able to optimise this in time. You can compare with the original algorithm by hitting legacy mode in granular - the CPU does drop here for me, but the new version is not particularly excessive on a quick test patch on the 4930. With everything turned up to 11 in granular I'm getting about 20% cpu, in legacy mode is more like 10%.

I think there are a couple of issues being conflated. It sounds to me like some people with issues are using the most CPU-intensive granular patches on less powerful systems, while others may just be hitting the end-stop audio-wise on the louder patches.

wagtunes · Post by **wagtunes** » Sat May 16, 2015 11:39 am

noiseboyuk wrote:
wagtunes wrote:In going over the patches causing this (only a few) I have also noticed that granular was on as well.

FTR, with Omni 1, I was able to run 42 instances of the plug before my PC couldn't take it anymore. So I do not believe this is a matter of poor hobbyists weak PCs not being able to handle the program. I believe this is a serious bug that needs to be addressed.
Same CPU hit here overall as with 1 with patches and tech from 1, I'm seeing no difference there at all. The new granular mode is CPU-heavy, they mentioned that they might be able to optimise this in time. You can compare with the original algorithm by hitting legacy mode in granular - the CPU does drop here for me, but the new version is not particularly excessive on a quick test patch on the 4930. With everything turned up to 11 in granular I'm getting about 20% cpu, in legacy mode is more like 10%.

I think there are a couple of issues being conflated. It sounds to me like some people with issues are using the most CPU-intensive granular patches on less powerful systems, while others may just be hitting the end-stop audio-wise on the louder patches.

Yeah, as I'm not a super techy, it's really hard to say what's causing the problem and what the actual problem is.

But make no mistake about it. This is a problem that needs to be addressed in the future.

noiseboyuk · Post by **noiseboyuk** » Sat May 16, 2015 1:50 pm

wagtunes wrote:Yeah, as I'm not a super techy, it's really hard to say what's causing the problem and what the actual problem is.

But make no mistake about it. This is a problem that needs to be addressed in the future.

Unless there are other system specific things which are causing additional problems for people, I wouldn't describe it as a problem that needs to be addressed. One of the features is moderately CPU-heavy at the moment - there's plenty of other synths out there that are CPU-heavy and folks work with them. Of course if Spectrasonics can optimise it more then great, but given that the new granular engine only takes up a small fraction of the patches and synthesis capabilities of the synth, imo it's a long way from the highest priority on the 2.1 list.

I have a long non-CPU related wish list on that score...

mhog · Post by **mhog** » Sat May 16, 2015 2:32 pm

Can Omni1 and Omni2 live together in the same DAW (like e.g. Kontakt, Dune etc.), or they are mutually exclusive?

wagtunes · Post by **wagtunes** » Sat May 16, 2015 2:39 pm

mhog wrote:Can Omni1 and Omni2 live together in the same DAW (like e.g. Kontakt, Dune etc.), or they are mutually exclusive?

No.

Acid Mitch · Post by **Acid Mitch** » Sat May 16, 2015 3:02 pm

wagtunes wrote:
mhog wrote:Can Omni1 and Omni2 live together in the same DAW (like e.g. Kontakt, Dune etc.), or they are mutually exclusive?
No.

No they aren't mutually exclusive or no they can't live together ?

wagtunes · Post by **wagtunes** » Sat May 16, 2015 3:02 pm

Acid Mitch wrote:
wagtunes wrote:
mhog wrote:Can Omni1 and Omni2 live together in the same DAW (like e.g. Kontakt, Dune etc.), or they are mutually exclusive?
No.
No they aren't mutually exclusive or no they can't live together ?

They can't live together.

MachineClaw · Post by **MachineClaw** » Sat May 16, 2015 6:52 pm

Omnisphere 2.0.2d updater has been released for Mac /PC and is in your user account.

one thing that the new 2.0.2d addresses is up/down arrows used in browser.

this is the 2nd updater since release of Omnisphere 2.

I am running Omni 2 in Win 7 - 64bit i7-4770 running at 3.5ghz w/32gb ram and fast SSD drives with a Focustire saffire PRo 24 w/firewire 400.

I have not experienced any popping, sound glitches etc. some patches are a bit louder than others, I have experienced that (noticed it in Omni 1 as well).

Try installing the latest updater to Omni 2 and make sure that the updater has not addressed your issue with Omni 2.

Ciberithm · Post by **Ciberithm** » Sun May 17, 2015 2:55 am

I hope the update helps. In my case, I don't think it's CPU overload, but the signal being too hot and causing clipping. Playing one or two notes usually sounds OK, but when adding a third note, the crackling begins. Ableton shows the master bus going over 0db. I can lower the master gain in Omni, but then adding a fourth note causes it to start clipping. None of my other VSTs have this issue when playing multiple notes at the same time.

I'm going to try to install it on Windows tomorrow to see if this is a Mac only issue.

Kinh · Post by **Kinh** » Sun May 17, 2015 11:19 am

Im not hearing any crackling or pops at all with several tracks, even instances. i7 4730 32g.
Granular's the only thing I have an issue with in that regard. But technically its not an issue because I cant see myself using it, I mean why would you? Its useless, just turns a perfectly good sound into noise...whoopie shit!

wagtunes · Post by **wagtunes** » Sun May 17, 2015 11:26 am

Kinh wrote:Im not hearing any crackling or pops at all with several tracks, even instances. i7 4730 32g.
Granular's the only thing I have an issue with in that regard. But technically its not an issue because I cant see myself using it, I mean why would you? Its useless, just turns a perfectly good sound into noise...whoopie shit!

But that's the problem. Granular DOES produce unwanted artifacts and there are people who DO want to use it. And yes, it CAN be used musically.

It's just like any other tool. It's the user, not the tool itself.

db3 · Post by **db3** » Sun May 17, 2015 12:13 pm

Not heard a single Onmi crackle thus far on my mac. Perhaps share the name of presets causing the issue?

wagtunes · Post by **wagtunes** » Sun May 17, 2015 12:51 pm

db3 wrote:Not heard a single Onmi crackle thus far on my mac. Perhaps share the name of presets causing the issue?

Don't use presets. I do my own sound design. When I use granular and Innerspace, depending on the sound source used, I have been able to duplicate this problem.

db3 · Post by **db3** » Sun May 17, 2015 12:55 pm

wagtunes wrote:Don't use presets. I do my own sound design. When I use granular and Innerspace, depending on the sound source used, I have been able to duplicate this problem.

I was referring to the OP.
"It seems just about every preset in Omni 2 pops and crackles if playing more than two or three notes at the same time".

Omnisphere 2: $500 Crackle Effect?