HOW TO optimize Omnisphere? Any tips on reducing overloads?

[Korg Supporter]

Omnisphere is actually one of the most cpu-friendly synths I own!

[zerocrossing]

It's always a good idea to set your polyphony to as low a number as possible and avoid voice stealing. Make sure you have enough RAM to comfortably run all your software and store samples. Do a google search of "Sweetwater tips for audio production on [name of OS]." Follow the recommendations.

[MachineClaw]

hi guys, when I use Diva and other VSTs i check about the polyphony or specific quality settings to save some memory etc.

but where/how can you check what might cause too much CPU overload/usage within Omnisphere?
I got some patches it seems which are sucking too much performance and i want to see if i can minimize it somehow and keeping the same sound or if i then have to export the layer(s).

thx

On the Main menu you can change the # of voices that are used. here is what the manual says:
The VOICES parameter determines the number of simultaneous notes (also called polyphony) that are playable in a single Part. Omnisphere is capable of up to 64 voices of polyphony per part, and the VOICES selector determines the maximum number of voices that the Patch will have.
The higher the number of voices that the Patch has, the more CPU power it will use, so this is a very important parameter in Omnisphere. The best approach is to only set it to the maximum number of notes that are needed for the given musical application.
The factory Patches have all been set conservatively, so if more polyphony is needed, increase the number of voices.
Range 1-64

So if you have Voices set really high and muti parts then you will be using a lot of CPU. may help to lower the Voices number a bit to only what you need. Really depends on the patch being used, synth + samples, and how many parts you are layering. can hog the CPU, but most of the factory patches have been set at a minimum setting so 3rd party patches can sometimes not be set correctly or set really high and lowering the Voices setting can help. if it's a patch you have created don't raise the Voices to a large number just depends.

[Caine123]

thanks a lot guys, I will post some examples and also will check the settings.

yes the topic is about optimizing it , when i got problems with heavy patches in Pigments for example I know to check the polyphony and also if i use Granular to check the density for example.

[Caine123]

hi guys, when I use Diva and other VSTs i check about the polyphony or specific quality settings to save some memory etc.

but where/how can you check what might cause too much CPU overload/usage within Omnisphere?
I got some patches it seems which are sucking too much performance and i want to see if i can minimize it somehow and keeping the same sound or if i then have to export the layer(s).

thx

On the Main menu you can change the # of voices that are used. here is what the manual says:
The VOICES parameter determines the number of simultaneous notes (also called polyphony) that are playable in a single Part. Omnisphere is capable of up to 64 voices of polyphony per part, and the VOICES selector determines the maximum number of voices that the Patch will have.
The higher the number of voices that the Patch has, the more CPU power it will use, so this is a very important parameter in Omnisphere. The best approach is to only set it to the maximum number of notes that are needed for the given musical application.
The factory Patches have all been set conservatively, so if more polyphony is needed, increase the number of voices.
Range 1-64

So if you have Voices set really hi and muti parts then you will be using a lot of CPU. may help to lower the Voices number a but to only what you need.

this should be it!
thanks so much, read it after my reply will check tomorrow asap in the studio

[el-bo (formerly ebow)]

https://vimeo.com/17379714