Make Omnisphere 2 Use Less Cpu
Excessive CPU load in Live can lead to dropouts, crackles or glitches in the audio and/or a sluggish response in Live. Follow these tips to help reduce the CPU load as much as possible. Note: The CPU meter in Live displays the amount of the CPU currently processing audio, rather than the overall CPU load.
Download virtual dj limited edition. Virtual DJ Software, MP3 and Video mix software. VirtualDJ provides instant BPM beat matching, synchronized sampler, scratch, automatic seamless loops.
Where can I purchase Omnisphere 2?
Download sales and Upgrades are now available for purchase in our Webstore/Techshop. Physical sales (boxed with USB drive) are handled exclusively through our Authorized Resellers.
If I already own Omnisphere, is there an Upgrade to Omnisphere 2?
Yes! If you already are an Omnisphere customer, you are eligible for the Omnisphere 2 Upgrade - available now in the Webstore/Techshop.
- Re: OMNISPHERE CPU load reduction- Eric, any advice? One thing you could do is to check the patches in the multi for proverbs and put those into bypass. Use one global proverb in the mixer over aux1 instead.
- Aug 10, 2019 Thank you for posting the question! In order to lower the CPU usage for any particular application or software (here, Fortnite): Note: Please make sure that you are logged in as the admin (on your Windows).
- Jun 30, 2015 The i5 will run at 4.4 GHz and, at that speed, performs a bit better than the other two because they can't hit that clock speed. Not a lot, but a bit. The CPU usage on the i5 is quite a bit higher than either of the i7s but you can get slightly more voices out of it than the i7s.
- Audio tracks require much less CPU than MIDI synthesizer tracks; this process also unloads the Omnisphere plug-in from memory. Once you freeze a track, you cannot edit its MIDI notes or control signals; you can still, however, add audio effects like reverb., delay and equalisation.
If I already own Atmosphere, is there an Upgrade to Omnisphere 2?
Yes! If you already are an Atmosphere customer, you are eligible for the Omnisphere 2 Legacy Upgrade - available now in the Webstore/Techshop.
Is there a DEMO version of Omnisphere 2 I can try?
Because of the size of our instruments, we don't offer Demo versions. However, you can contact one of our local dealers in your area in order to arrange a live demo of Omnisphere 2. To find a local dealer in your area, please contact your local Authorized Reseller.
How are Spectrasonics Instruments delivered to new users?
All Spectrasonics instruments are available in two different editions: Boxed and Download. The physical boxed editions now contain high quality USB drives and are sold exclusively to new customers through our Authorized Resellers. The download editions are now available and sold exclusively through our Webstore/Techshop.
Aren’t Spectrasonics Instruments delivered on DVD-ROMS?
They used to be, but this is no longer the case. All our physical boxed versions have now been revised with high-quality USB drives. For convenience, we now also offer download sales of new Spectrasonics Instruments direct to customers from our Webstore/Techshop. Both of these new delivery platforms offer much faster and more reliable installations than DVD discs.
If I buy the Boxed version, will I also be able to get a download in the future? If I buy the Download Edition, will I also be able to get a drive? If I have the DVD-ROM edition, will I be able to get the drive or future downloads if I need them?
Yes to all of the above! We are happy to announce that there are now alternative forms of installation available optionally to registered users - no matter which edition you have originally purchased.
Spectrasonics is keenly aware that many users no longer have computers with optical drives and there are numerous scenarios when the convenience of downloading or the speed of a USB drive would be a preferred form of installation for different types of users. To address all the various user needs and scenarios, Spectrasonics has a new Support Services area that offers Alternative Installation USB Drives and Additional Download Installations for optional purchase. These services are available for purchase in our Webstore/Techshop for registered users.
How is the Upgrade delivered? Is it downloadable? How big?
The Omnisphere 2 Upgrade package is a 60GB download which you can order through Webstore/Techshop.
Is the Omnisphere 2 Upgrade available as a physical product?
Not at this time. Our download service is highly reliable though.. even with slower connections.
Can I download the upgrade?
Yes. The upgrade is now exclusively available as a download in our Webstore/Techshop.
Does an Omnisphere 1 license need to be registered and authorized in my Spectrasonics User Account in order to qualify for the Omnisphere 2 Upgrade?
Yes.
Does Omnisphere 1 need to be installed on my computer before purchasing and installing the upgrade to Omnisphere 2?
No. Upgrading to Omnisphere 2 will supply the complete 60GB Omnisphere 2 sound library, which includes the sounds from Omnisphere 1. If Omnisphere 1 is already installed, you will not lose any custom user-created sounds or third-party libraries.
Do I need to have Atmosphere installed before purchasing the upgrade to Omnisphere 2?
No, but if you are an Atmosphere user you will need to have it authorized and registered to qualify for the Legacy upgrade.
Is there a student discount price for Omnisphere 2?
Spectrasonics doesn't offer student discounts, however qualifying schools and institutions can participate in our EDU program.
Does Spectrasonics allow for used sales/license transfers of Omnisphere 2?
Please see the License Transfer FAQs area of the Knowledgebase for more info on our License Transfer Policy.
Can I upgrade if I bought a used copy of Omnisphere v1?
Yes, but only if that copy of Omnisphere has been properly license transferred through Spectrasonics.
Can I upgrade if I bought a used copy of Atmosphere?
Yes, but only if that copy of Atmosphere has been properly license transferred through Spectrasonics.
If I upgrade my Atmosphere to Omnisphere 2 can I later resell and transfer the license of either instrument used to someone else?
No. Customers who participate in a special upgrade program for any Spectrasonics virtual instruments are not eligible for license transfers either for the original instrument or its subsequent upgrade. For example, if an original owner of Atmosphere takes advantage of our special “legacy” upgrade program to Omnisphere 2, the owner is not permitted to resell either instrument and no license transfer will be granted.
If I upgrade my Omnisphere v1 to Omnisphere 2 can I later resell and transfer the license of either instrument used to someone else?
Since it is the same original license, Omnisphere 2 would still be eligible for a future license transfer. However, Omnisphere 1 cannot be transferred as a separate product.
Are Omnisphere 1 and Omnisphere 2 different instruments/products?
No. Omnisphere 2 is simply the next major version of Omnisphere.
Is Omnisphere 2 a Stand-alone app or a Plugin?
Omnisphere 2 includes a standalone application and VST/AU/AAX plug-in platforms that work in all the major DAWs and hosts.
What is the STEAM engine?
STEAM™ is our in-house core technology that is the foundation of Omnisphere, Trilian and a new generation of Spectrasonics instruments.
So does Omnisphere replace Atmosphere?
Yes, Omnisphere is Atmosphere's successor.
What are the minimum system requirements for Omnisphere 2?
You can view them HERE.
Is it compatible with xxx?
Check our Compatibility FAQs in the Knowledgebase which we keep up to date with the latest info.
Will Omnisphere 2 replace my Omnisphere plug-in?
Yes. Omnisphere 2 is the next version of Omnisphere. When installed, the Omnisphere 2 Upgrade contents (20GB) merge with the existing Omnisphere 1 library and become one product, replacing Omnisphere 1 as a plug-in.
When opening older projects which use sounds from Omnisphere 1, will they load the same?
Absolutely - it is still Omnisphere! Version 2 is fully backwards compatible with version 1 projects.
Will custom saved patches/multis be negatively affected when upgrading to Omnisphere 2?
No. They will open and operate the same as always.
Will third party patches be negatively affected when upgrading to Omnisphere 2?
No. All third-party Omnisphere v1 libraries are fully compatible with Omnisphere 2.
Does Omnisphere 2 use Copy Protection?
Yes, please see the Copy Protection FAQs area of the Knowledgebase for more information on our system.
Does Omnisphere 2 include a manual?
All our instruments include a comprehensive online Reference Guide, which is accessible directly through the plug-in. The integrated Reference Guide is searchable and we can keep it up to date with the software releases. You can check out the Reference Guide HERE.
How fast of a computer will I need to run Omnisphere 2?
As with all virtual instruments - the faster the better. Omnisphere 2 is designed to run optimally on modern computers. See the System Requirements for more information.
Does Omnisphere 2 need more CPU power than Omnisphere v1?
Not significantly more. Some newer patches require more resources than older ones. However, many new patches do not require more resources.
Does Omnisphere 2.5 need more CPU power than Omnisphere 2.4?
Not significantly more. Some newer patches require more resources than older ones. However, many new patches do not require more resources.
Is Omnisphere 2 compatible with 32-bit and 64-bit systems?
Omnisphere 2.4 and earlier are compatible with both 32-bit and 64-bit systems. Omnisphere 2.5 and higher are compatible exclusively with 64-bit systems.
Can I easily switch back and forth between Omnisphere 2.5 and Omnisphere 2.4?
Yes! We have a rollback installer that’s easy to use for this purpose if you are unsure if you are ready for 2.5 or not.
Does Omnisphere 2 use streaming?
Yes! Omnisphere 2 streams from the drive for quick loading of the sounds. Drive streaming is configurable as well.
Can I selectively install parts of the Omnisphere 2 library since it is so large?
Because of patch compatibility, Omnisphere 2 must always be installed with the complete library. However, you can install the 60 Gigabyte library to a secondary or external drive if you wish.
Will Omnisphere 2's streaming benefit from a faster hard drive?
Fast drives are a smart way to go of course. There's a chapter in the Reference Guide devoted to optimizing Performance with Omnisphere 2.
Can I install Omnisphere 2 on a different drive?
Yes, you can definitely install the library to a secondary or external drive.
Can I Use My Own Audio in Omnisphere 2?
Yes! You can now use any WAV or AIFF audio files in Omnisphere as soundsources for creating your own amazing sounds! Omnisphere 2 supports bit depths up to 24-bit files and sample rates up to 192kHz.
Will the audio import in Omnisphere 2 be for single audio files or multi-samples?
Omnisphere 2 supports one audio file of any length per soundsource. You can layer up to four soundsources in a patch and 8 patches in a multi. Keep in mind that Omnisphere's focus is as a synthesizer and will never be a sampler with multiple velocities, key-mapping, round-robin, etc. - there are other instruments out there that do that very well.
Make Omnisphere 2 Use Less Cpu Usage
Omnisphere 2 allows you to easily turn your audio files and even your audio tracks/mixes into synthesis source for Omnisphere 2's powerful oscillators. It's remarkable how much you can creatively mangle one sound and transform it into something awesome!
Illustration: Maria Chimishkyan
Since its Rent-to-Own launch, Serum also happens to be the top seller on Splice’s Plugins store. Producers love its powerful wavetable tools, myriad modulation options, and functionality-packed UI. Some critics, however, have opined that Serum uses a disproportionate amount of processing power.
First, the synth uses a LOT of processing power. I hit a note on a super saw and saw my i7 dual core processor spike at 20%-30%. That’s a lot of number crunching for one instrument! This can be mitigated somewhat by using effects to simulate “unison” voices and (MAYBE) using a lower draft quality global setting. It’s just a function of math, if you want rich, fat, CLEAN sound, it’s just something we have to live with. If your computer isn’t beefy, you may have to drop your MIDI tracks to audio so you don’t kill your CPU.
Serum needs to be immediately put at the very top of any synthesist’s shopping list. It’s insanely powerful and sounds phenomenal.
PROS: Morphing oscillators. Flexible unison modes/ Built-in wavetable editor. Magnificent sound. Outstanding effects. Incredible modulation options.
CONS: Can hit your CPU hard.
STRENGTHS: Powerful wavetable synthesis. Extensive modulation and tone-shaping features.
LIMITATIONS: Can be CPU-intensive. No standalone version.
Despite near-universal praise for Serum’s sound, many reviews mention CPU efficiency issues. In this post, I’ll examine Serum’s CPU usage to determine whether these are valid complaints. I’ll find out why CPU issues might occur, take recommendations from Xfer devs, and test out those recommendations in comparison to fellow wavetable workhorse Massive.
Why is this happening to me?
Steve Duda of Xfer Records remains active in many online Serum communities including the Serum subreddit (where he’s the sole moderator) and Xfer support forums, where he has repeatedly encountered users who ask how to reduce Serum’s share of CPU usage. According to Mr. Duda, efficiency issues are typically attributable (at least in part) to user error:
Most CPU complaints I have found first and foremost come from heavy voice count compounded by not watching poly limits sensibly (lower-right fraction in Serum). Some synths won’t let that number exceed 64, so it’s good to keep an eye on it yourself and be sensible with unison (16 can sound great, but isn’t always better sounding!)
Omnisphere 2 Cheap
Sam Leggett, former Xfer dev, and current Splice audio scientist concurred:
Anything that is going to automate each voice separately increases the problem space by the number of voices, and if you have a lot of notes playing, e.g. in a chord stack, that will multiply said problem space by that many notes.
In other words, users may complain about high CPU usage if they crank up the voice count. Any digital synth must perform a certain number of calculations per voice in order to output audio. By the same token, when users increase the voice count, they’re also increasing the amount of numbers that their synth has to crunch in order to produce the desired sound. Since these calculations are performed by the computer’s CPU, increasing the voice count will increase CPU usage no matter what digital synth you use.
This post from Duda throws a little bit of shade at NI’s Massive, which caps the voice count at 64 and automatically redistributes voices to allow polyphony once the limit is reached. This prevents Massive from spiking the user’s CPU, even if the user raises the voice count and unison setting to their maximums. While voice count is not a bottleneck in most musical contexts, there may be legitimate cases where this limit is restrictive.
Imagine you wanted to play a dominant 13th C chord (C13) using a Serum patch with 2 oscillators on Unison settings of 8 each. That’s 7 notes (C E G B♭D F A), times 2 oscillators, times 8 = 112 voices. In Massive, these settings would trigger the voice cap, altering the timbral characteristics of the final output. Serum, on the other hand, does not limit voice count, meaning our 112-voice chord would use more CPU – although not on a per-voice basis, and without limits as to the patch’s desired timbre.
Another common potential cause of CPU inefficiency that Duda identified is excessive oversampling:
2x is all that is needed for normal oscillators, you shouldn’t hear any audible difference running 4x so it is indeed overkill. The 4x (oversampling) will be most noticeable when using FM warp modes, as it runs the oscillators at a higher sample rate which reduces digital artifacts. It will make some difference when using other warp modes as well.
Oversampling sounds like a cool parameter that will increase sound quality if you crank it up, but as usual Duda is correct. According to the Nyquist-Shannon sampling theorem, it should be possible to perfectly replicate a signal if sampled at or above the Nyquist rate (twice the highest frequency component in the signal). Therefore, an oversampling rate of 2x should be more than adequate for accurate representation of most signals.
What can I do about it?
For starters, it’s worth making sure that your copy of Serum is updated to the latest version. Updates to the codebase over the years have improved CPU usage, which may actually explain some of the efficiency criticism in the reviews. It should go without saying that a cracked Serum will result in degraded performance since it’s likely to be outdated and no updates can be applied. If you’re looking to own a legitimate copy of Serum, you can Rent-to-Own Serum for an easy $9.99 a month.
But let’s assume you’re all up-to-date and put Sam and Steve to the test. Below, we’ll try out some of the parameters they identified as potential CPU bottlenecks, determine their actual CPU impact, and assess their effect on Serum’s final output.
Will it work?
To test this out, I’ll be using my rMBP and the Splice studio Mac Pro.
For this test, I’m going to be be using Ableton Live 9 because there’s no standalone version of Serum. To measure CPU, I’ll use Live’s built-in CPU usage monitor, which monitors the peak usage across one processor core output from Live. I know what you’re thinking: “But I have 18-core hyp3rthr3ading d00d??!!!1” As a matter of fact, Serum uses only two core threads. Let’s hear again from Duda:
There’s a DSP thread and a GUI thread. This is the most optimal way to be for a typical project use, as the DAW will delegate instances (tracks) across cores. Running multiple DSP threads comes at a price and only allows for more out of a single instance, which tends to not be needed once people learn to limit polyphony reasonably.
It’s possible to capture more in-depth data using techniques like CPU usage profiling in Xcode’s Instruments, but since there’s no standalone version of Serum, there’s not much of a point in profiling its CPU usage independent of a DAW anyway.
Based on the recommendations I gleaned from Steve’s forum posts and talking to Sam, I’m going to test the following parameters’ impact on CPU usage peak within Live:
Voice count
- 32 (Serum and Massive)
- 64 (Serum and Massive)
- 128 (Serum only)
Oversampling
- 1x (Serum 1x, Massive Eco)
- 2x (Serum 2x, Massive High)
- 4x (Serum 4x, Massive Ultra)
Env1 release time
- 200ms
- 1000ms
- 32000ms
Reverb
- All settings 100%
Besides the above parameters, I’ll use an init preset with two saw oscillators. Oversampling will be set at 2x, Serum’s default, unless otherwise noted. Release times for Massive are estimated. I’ll play the same chords on all tests except for the voice count test. Each parameter will be tested three times and the final result will be the average of each run.
What happened?
Tl;dr
As the data demonstrates, CPU usage is positively correlated with voice count and oversampling for both Massive and Serum. Reverb may have had a slight CPU impact, as well as long envelope release times, but these correlations are much less severe than voice count and oversampling.
It would appear that Serum’s CPU usage inefficiencies are largely overstated. Compared to Massive, a popular competing wavetable synth, Serum performed significantly better on both desktop and laptop.
That said, I was able to get the Ableton processor meter up to 20% on the Mac Pro simply by asking it to generate 128 voices. This is a significant task even with a relatively simple synth patch.
The lesson here is clear: don’t crank up the voice count or the oversampling unless you really need them. Even 32 voices for one instrument is a relatively high number in a normal musical context. According to Duda, “7” Unison is the sweet spot for stacks/chords.” Your mileage may vary, but keep in mind that if you’re rendering 512 voices in real-time, you’re probably going to max out your processor.
If you absolutely must use hundreds of voices on your crazy FM patch with 4x oversampling and all fx maxed out, Sam Leggett has some suggestions for you:
One potential workaround for users who need fat chord stacks with tons of voices might be for instance to write your chord patterns with a lower voice cap, then when you’re ready, bring it up to where you want it and freeze.
In the menu at the top, there are options to resample to Osc A or Osc B. These will take the current output of the sound and its tail and put that into OSC A/B as its own wavetable. So if you do, for instance, a 16 voice unison with a little detune at the beginning, you can hit resample to Osc A and it will bounce that wavetable into Osc A as a single voice. It will also calc fx and everything else, so I would suggest maybe doing it right as you init your patch so you can still mess around with it after
Does Serum still spike your CPU? Are you ripping through renders with your Ryzen rig? Do you have other suggestions for saving CPU power? Let me know at @rewakmusic!
January 12, 2018