Official Serum 2 thread!

[swilow11]

Feel like I'm seeing improvement. Made a basic supersaw with all 3 wavetables oscillators at 16 voices, using the new ladder filter into the diffusor filter, using the clip launcher and a large FX chain. This should have really pushed my CPU but didn't really seem too burdensome at all. Oddly though, after I saved the patch, I started getting a few pops and crackles and Bitwig DSP graph was getting up there.

[liv]

Composed a video called "Inhabited majesty" with presets exclusively for Serum 2.

Shadows Of Luring Attraction 2.

Dark apocalyptic ambient. Please have a look.

I've heard your sounds for Bazille and Massive and they are great. I will have to check out your Serum presets, I'll bet they are amazing.

Cool. Thanks.
The big Serum 2 leap for me is the added second filter option. Brilliant move.

Yeah, it's a great feature. What sort of creative uses are you finding for it?

There are lots of added options available with this that kicks off my inspiration for creativity.
I enjoy a tuned comb filter with 100% feedback routed to filter 2 with inserted LP for example to tame it or to modulate a sequence.
Using two multi filters in series and automate movement on both with separate LFO's reveals very interesting colors when done right.
Another is for example routing osc A to F1 and osc B to F2 to enable morphing from one color or character towards another.
Maybe you have a favorite?

[Ah_Dziz]

So essentially, a wavetable is a table of tables—a collection of waveforms , where each waveform is itself a table of PCM samples (frames).

So let's ignore for a second the actual frames, interpolation between frames, etc.

Say you have a single frame with a single waveform cycle and a .wav file with a single cycle load into a sampler.

Are you actually saying that given a single cycle both a sampler and wavetable engine will do exactly the same thing? Eg: interpolating PCM samples for a particular pitch/speed rate?

Can anyone who has a technical knowledge confirm this?

Yep. A sampler is playing back a "known" table of 2048 samples of data and a wavetable osc is playing back a list of 2048 values that are constantly updated by the wavetable position and the interpolation used. If there's no modulation of the wavetable position then there would be no difference between the two.

[3lu5iv3]

Feel like I'm seeing improvement. Made a basic supersaw with all 3 wavetables oscillators at 16 voices, using the new ladder filter into the diffusor filter, using the clip launcher and a large FX chain. This should have really pushed my CPU but didn't really seem too burdensome at all. Oddly though, after I saved the patch, I started getting a few pops and crackles and Bitwig DSP graph was getting up there.

My macbook air m2 is glitching the heck out playing the supersaw i created with watching the Sound Killer's tutorial. It's a 768 voice supersaw.
U can watch it here.

[swilow11]

It's not really 768 "voices" though, is it?

[Igro]

I can't figure out why Serum 2 main envelop behaves so weirdly (or I'm missing something obvious). Just take a Saw wave and in you DAW arranger draw notes like it was a 4/4 kick. Set poly to Mono. Then set attack to the slowest position and release to the longest value. In this case, there almost shouldn't be any sound at all. But you will hear a constant saw sound. You can even bend attack curve to the minimum. Still the same. Tried that in PhasePlant and it worked as expected. So what's wrong with that?

[swilow11]

I can't figure out why Serum 2 main envelop behaves so weirdly (or I'm missing something obvious). Just take a Saw wave and in you DAW arranger draw notes like it was a 4/4 kick. Set poly to Mono. Then set attack to the slowest position and release to the longest value. In this case, there almost shouldn't be any sound at all. But you will hear a constant saw sound. You can even bend attack curve to the minimum. Still the same. Tried that in PhasePlant and it worked as expected. So what's wrong with that?

In mono, the envelope doesn't retrigger afaik but instead picks up at the value it ended at. Are you hearing the sawtooth sound build up over repetitions of the midi?

[Ah_Dziz]

I can't figure out why Serum 2 main envelop behaves so weirdly (or I'm missing something obvious). Just take a Saw wave and in you DAW arranger draw notes like it was a 4/4 kick. Set poly to Mono. Then set attack to the slowest position and release to the longest value. In this case, there almost shouldn't be any sound at all. But you will hear a constant saw sound. You can even bend attack curve to the minimum. Still the same. Tried that in PhasePlant and it worked as expected. So what's wrong with that?

In mono, the envelope doesn't retrigger afaik but instead picks up at the value it ended at. Are you hearing the sawtooth sound build up over repetitions of the midi?

Some DAWs will send midi data like what you described and send it a one big note. Generally "mono" mode should retrigger the envelope. The behavior I get from serum 2 is a retrigger of the main volume envelope on each MIDI note-on message. I can get some odd behavior in legato mode, (with and without mono mode on) but it will reset to the proper behavior if you reduce the release value to the minimum for a split second.

[Igro]

I can't figure out why Serum 2 main envelop behaves so weirdly (or I'm missing something obvious). Just take a Saw wave and in you DAW arranger draw notes like it was a 4/4 kick. Set poly to Mono. Then set attack to the slowest position and release to the longest value. In this case, there almost shouldn't be any sound at all. But you will hear a constant saw sound. You can even bend attack curve to the minimum. Still the same. Tried that in PhasePlant and it worked as expected. So what's wrong with that?

In mono, the envelope doesn't retrigger afaik but instead picks up at the value it ended at. Are you hearing the sawtooth sound build up over repetitions of the midi?

You can pick Per note retrigger in OSC menu. The result will be the same. However, if you skip the ENV1, but use ENV2 instead, everything will work as expected. I said in mono, but it doesn't matter. ADSR envelope should work as an envelope. Seems like a bug.

[swilow11]

I think Steve Duda has written that it is intentional because it's more like how analogue synths work.

[Igro]

I think Steve Duda has written that it is intentional because it's more like how analogue synths work.

He wrote about a different thing (Per Not retriggering in Mono mode). Not about the ENV1 that shoud work differently from ENV2.

[kraster]

I can't figure out why Serum 2 main envelop behaves so weirdly (or I'm missing something obvious). Just take a Saw wave and in you DAW arranger draw notes like it was a 4/4 kick. Set poly to Mono. Then set attack to the slowest position and release to the longest value. In this case, there almost shouldn't be any sound at all. But you will hear a constant saw sound. You can even bend attack curve to the minimum. Still the same. Tried that in PhasePlant and it worked as expected. So what's wrong with that?

In mono, the envelope doesn't retrigger afaik but instead picks up at the value it ended at. Are you hearing the sawtooth sound build up over repetitions of the midi?

You can pick Per note retrigger in OSC menu. The result will be the same. However, if you skip the ENV1, but use ENV2 instead, everything will work as expected. I said in mono, but it doesn't matter. ADSR envelope should work as an envelope. Seems like a bug.

I think it's a bug too.

ENV 1 is indeed a special use case but this behaviour is odd.

It's like the voice starts accumulating if you do your test.

If you disable ENV1 for the oscillator (if it's routed to Main or direct) in the mixer section, max it out and use ENV 2 then it works as intended.

Voice triggering is tied to ENV 1 but you can hack your way around it.

Still think it's a bug though.

[Igro]

Here the answer from the Discord from one of the developers:

"This is because Serum envelopes don't restart from 0 when you retrigger them, so if the release phase wasn't finished it starts the attack from wherever it got to. This is not reflected in the GUI graph.
This also happen in Serum 1, so is intentional behaviour of Serum 2 and not a bug."

And

"Env 1 is the one that restarts from current level, because it is hard-wired to amp. It does this to avoid clicks when stealing a voice."

[swilow11]

Sort of confused. They're mentioned "envelopes" plural and then just envelope 1.

[Igro]

Sort of confused. They're mentioned "envelopes" plural and then just envelope 1.

I'm wondering too. How Pigments managed to do this differently? Or PhasePlant? And 100 more synths.
So if I don't use ENV1 (set max values for decay and release), then ENV2 will be clicky when applied to OSC1 volume? What a puzzle...