Serum 2 Guidelines for Optimizing CPU Usage

To achieve the best performance and maintain high-quality sound design in Serum2, here are two key areas to focus on for CPU optimization:

1. Manage Unisons Effectively

• Keep Unison Counts Low:

  Using more than 3-7 unisons per oscillator is often unnecessary and can be a red flag for inefficiency. Higher unison counts not only increase CPU usage significantly but also introduce phasing issues, potentially degrading your sound quality.

  Chorus vs. Unisons:

  Instead of stacking unisons to create a thick, chorused sound, use a dedicated FX bus with a chorus effect. This approach is:

  • CPU-Friendly: Applies the effect once instead of processing it for every voice.
  • More Flexible: Allows easier tweaking and layering of effects without duplicating processing effort.

2. Prioritize FX Bus Over Per-Voice Effects

• Understand How Effects Are Applied:

  In Serum2, effects applied to an oscillator are processed per voice (i.e., for each note being played). While this can be powerful for creating rich, detailed sound designs, it also dramatically increases CPU usage since the effects are calculated for every active voice.

  Use FX Bus for Shared Processing:

  Whenever possible, route your sources to an FX bus and apply effects there. This method:

  • Reduces CPU Strain: Processes the effects once for all voices combined.
  • Maintains Cohesion: Ensures a consistent and unified effect across all sources.
  • Works Best for: Reverb, delay, EQ, and similar effects that don’t require voice-level manipulation.

• When to Use Per-Voice Effects:

  Use effects at the oscillator level only if you need specific sound interactions per voice, such as uniquely modulated or wrapped effects that cannot be achieved through bus processing.

By keeping unison counts reasonable and leveraging FX buses effectively, you'll save significant CPU resources, improve workflow, and retain high-quality sound output in Serum2.