In this Omnisphere tutorial, we are going to look at CPU Management. I think we all know what a resource hog Omnisphere can be, but there are ways of taming this beast.
Omnisphere itself is multitimbral, but unfortunately, it is not multi-core. Therefore, one instance will not scale across cores but rather be locked into the one core. If you have complex sounds playing on 4 or 5 parts you can start hitting issues.
The best way to explain this is by a video as you will see at the bottom of this post. At the start of this video, I demonstrate what having 5 fairly complicated patches does to quite a beefy PC. I am rocking a core i9 9900k with 80GB of ram, so it is no slouch. Please keep in mind that I am also screen recording so that is going to take out some CPU cycles and why I am still crackling at the end of the video.
As we progress through the video I open up separate instances of Omnisphere as each one will use a different core on the PC. We also look at lowering the voice count as this will also affect how much your computer will take before falling over.
The final coup de grace, so to speak, is by de-arming the track for recording and increasing your ASIO buffers. Although this gets rid of the crackling when playing back the track, it doesn't help if you are recording an instrument live as the delay will be horrendous and unworkable.
If you have read this far, thank you, your support is very much appreciated and I would very much like if you subscribed to the channel.