Xfer Serum 2 Just Landed: What the New Oscillator Modes Do to My Bass Patches

Serum 2 is out, and the first thing I did after installing it was load every bass patch I’ve built on Serum 1 over the last few years and see what breaks. Some of them did. A few got better the second I touched the new oscillator modes. Here’s what actually changed in practice, and where I think the update pulls its weight in a drum’n’bass session versus where it’s just more knobs to ignore.

The new oscillator modes, and why bass patches care

If you’ve spent time in Serum’s wavetable engine, you know the drill: pick a table, set the position, modulate it, done. The Serum 2 oscillator section adds modes that change how that table gets read, and this is where the low-end story lives. For sub and mid-bass work, the difference between “wavetable played straight” and “wavetable mangled by a new read mode” is the difference between a patch that sits under a break and one that fights it.

Take a reese. On Serum 1, I’d stack two saw tables, detune them, and lean on the unison and the filter to keep the phase mess musical. On Serum 2, the new modes give you more ways to create that harmonic movement inside a single oscillator, which means fewer voices competing for headroom on the sub. On a d’n’bass reese, fewer detuned voices doing the work means a tighter, more controllable bottom end, and less phase cancellation landing in bad places when the bass sits next to a kick. That’s not marketing language. That’s what happens when you stop brute-forcing width with unison and start shaping it in the oscillator.

What I noticed on sub patches first

My pure sine subs didn’t change much. They don’t need to. A sine is a sine. But the moment a patch had any upper harmonic content (a 20 to 80 Hz fundamental with a bit of second or third harmonic to translate on small speakers), the new modes gave me grip on that harmonic content without reaching for the filter. Being able to push the harmonic character from inside the oscillator is a cleaner move than stacking an EQ boost at 200 Hz, which is where the Sennheiser HD 480 Pro review I keep coming back to reminds me a lot of monitors lie: there’s a dip around 200 Hz in those cans, so a “flat” bass on them reads differently than on the room. Do your bass shaping in the source, not on the monitoring chain.

Where it beats Serum 1, and where it’s fiddly

The new modes are most useful when you want the bass to evolve over a bar without automating the wavetable position. That’s the honest win. If your bassline is one held note under a two-bar loop, the evolving read modes give you motion for free, and motion is what makes a bass feel alive instead of sampled.

The fiddly part is CPU and predictability. Serum was never light, and the new modes add processing per voice. If you’re running a big unison patch with the modes engaged, watch your buffer. Getting the driver side sorted is the flip side of the same coin, so: set your buffer size before you start blaming the plugin. On a busy project, a 256-sample buffer on a decent interface is fine for tracking, but if the new oscillator modes are pushing your CPU and you’re getting crackles, raise the buffer to 512 for the mixdown rather than swapping oscillators. Buffer first, plugins second.

Predictability is the real trade-off. Serum 1’s wavetable read is something you can predict once you’ve used it a while. The new modes are less forgiving. A table that sounded perfect in Mode A can sound like a cardboard box in Mode B. That’s not a bug. It’s the point. But it means your existing patches don’t translate one-to-one. Expect to reprocess a lot of presets.

The broader wavetable context (what Serum 2 is competing with)

Serum doesn’t exist in a vacuum. The wavetable space has gotten crowded in the last few years, and it’s worth putting the update in that frame. Vital still does the most aggressive wavetable work for free, and Surge XT covers the rest with a broader synthesis engine (FM basses, analogue-style pads, experimental textures). Waldorf’s Iridium desktop mk2 throws six synthesis engines per oscillator (Wavetable, Waveform, Particle, Resonator, Kernel, Seeds), which is a completely different design philosophy: you pick the engine per oscillator rather than committing to one wavetable read. That’s where the industry is going, and Serum 2’s new modes are Xfer’s answer. If you already own Serum, the update is a no-brainer. If you don’t, and you mainly want wavetable bass, Vital is free and does 80% of it.

Practical bass-chain notes for the new modes

After a week of rebuilding patches, here’s what held up:

  • Sub plus texture in one oscillator. Use a mode that gives you harmonic content on top of the fundamental so you can carve the fundamental with a gentle filter and the texture with the mode. Two jobs, one oscillator, less phase trouble.
  • Unison down, modes up. On reese patches, cut unison voices from 7 to 3 and let the new modes create the movement. The sub stays cleaner.
  • Filter and mode are not the same tool. The mode shapes the source; the filter shapes what’s left. Reach for the mode before the filter when you want character, and the filter when you want to remove.
  • Bounce and check. A bass patch that sounds huge solo can vanish under a break. Bounce the whole loop, listen on the HD 480 Pro’s slight 30-50 Hz hump and on a small speaker, and rebalance before you commit.

Should you update today?

Yes, if you produce drum’n’bass or anything bass-forward and you own Serum. The new oscillator modes earn their keep on evolving sub and reese patches, and they’re the first update to Serum in years that actually changes how I build sounds rather than just adding modulation slots. My honest complaint is that it makes old presets sound dated and the CPU cost is real. But that’s the deal with an oscillator engine that finally gives you more than one way to read a table. Spend an afternoon rebuilding your three best bass patches with the modes. If they don’t sound better, you’ve learned something about how you patch. If they do (mine did), you’ve got a new starting point.

One housekeeping note: install the VST3 version cleanly and check your DAW rescans plugins before you panic about the update “breaking” your projects. Nine times out of ten, a missing-sound complaint after a synth update is a plugin scan problem, not a synth problem.