Official Serum 2 thread!

[sempondr]

...you'd want something with high-speed single-core performance first and foremost.

I second that. My 16-Core Ryzen doesn't make any difference when it comes to Serum 2 spiking.
Edit: I'm talking about single instance of Serum.

[HcDoom]

Looks like multicore support is not properly coded. Still, great synth.

[Gam456]

...you'd want something with high-speed single-core performance first and foremost.

I second that. My 16-Core Ryzen doesn't make any difference when it comes to Serum 2 spiking.

Look after parking core off

[VELLTONE MUSIC]

Serum 2 is absolutelly amazing for pads and atmospheric stuff,made few nice ,demoing it and love these filters.
Sound is way more organic and deep,compared to v.1
Cpu overload is the issue ...
Plan to assemble more powerful pc this year.
Did anybody test it with 8 cores vs 16 cores,is there any significant difference?
Cheers

Others can come in and correct me if I'm wrong, but in my brief time with the demo, the issue seems to be that it's going to max out a single core pretty easily with some patches. And there's no multi-core option like some U-he synths. Throwing more cores at the problem alone won't solve it because the core Serum will be running on may still be spiking. If you're trying to eek out more Serum 2 instances, you'd want something with high-speed single-core performance first and foremost.

That's serious issue,if it is the case...
Cakewalk use multi-core process 'something',if enable it as option and i guess that's helpful when have more than 4 cores and work on let say 30-40 tracks mix.
I hesitate is it worth extra money for cpu with 16 cores,if can't use them...
Cheers

[Bartone]

I think Serum2 will get some upgrade/fix for the CPU matter since it seems to affect so many people with different DAWs and different systems (it seems it is not just Mac users or windows users but all across if I am not wrong). But let’s see when

[sempondr]

Cakewalk use multi-core process 'something',if enable it as option and i guess that's helpful when have more than 4 cores and work on let say 30-40 tracks mix.
I hesitate is it worth extra money for cpu with 16 cores,if can't use them...

Multiple cores will be used on multitrack project, it's the single instance of Serum that's not very well distributed across cores.

[audiojunkie]

I don’t think the Serum1 factory presets come with Setum2, can you get them if you buy Serum2 or only the factory presets for Serum2?

If you buy Serum 2, you also get a Serum 1 licence added to your Xfer account. After you install Serum 1, the S1 presets appear in S2

Really, I can get the Serum1 and use it if Serum2 is too much?
If/when I buy Serum2, where can I download Serum1?

From your user account. Sam place as you will be able to download ver.2

Interesting! I use Linux, and I know that Serum 1 works with WINE, but I'm not sure about Serum 2. Can both Serum 1 and Serum 2 be installed concurrently on the same machine and run independently?

[mabian]

I would like to know if Serum 2 plays well in Wine, too.

Thanks,
Mario

[Ah_Dziz]

The performance issues I keep hearing about on here just don't seem to be affecting me. I've only noticed problems with the granular oscillator and then only with settings that sound extremely bad. 2 regular osc 1 spectral plus noise and sub along with both filters using all warp slots and two pages of modulation allows me to run hundreds of voices on my little laptop. I didn't stress test on my "real computer" but having not seen any real CPU issues, I didn't feel the need. I don't tend to make many synth patches that need more that 16 voices (actual voices meaning notes playing simultaneously) and even that's a stretch.

[tumface]

The performance issues I keep hearing about on here just don't seem to be affecting me. I've only noticed problems with the granular oscillator and then only with settings that sound extremely bad. 2 regular osc 1 spectral plus noise and sub along with both filters using all warp slots and two pages of modulation allows me to run hundreds of voices on my little laptop. I didn't stress test on my "real computer" but having not seen any real CPU issues, I didn't feel the need. I don't tend to make many synth patches that need more that 16 voices (actual voices meaning notes playing simultaneously) and even that's a stretch.

Yeah. On some computers, it performs a lot worse than Serum 1 for the same patches. On others, no change. On my Ryzen (Whitehaven, Zen 1) PC, Serum 2 uses 2x-3x the same amount of CPU for the same patches as Serum 1. On my M1 MacBook Pro, Serum 2 uses the same amount of CPU for the same patches as Serum 1.

Which CPU were your tests with? Did you compare the same patch made in Serum 1 by loading it in Serum 2?

[Ah_Dziz]

It was with my crappy little laptop. I only checked it out because of what I read here. The laptop is a little windows 10 i5 with 16 GB ram. Tested it in maschine 2. I mostly only used features that are only in serum 2. Patches were made from scratch. They were all using at least 1 spectral osc and lots of audio rate modulation. I do notice that having the number of "available" voices set extremely high tends to make the CPU use higher even without those voices being in use. It was nothing like a scientific test. I haven't noticed any high CPU on my main workstation. Also Intel windows.

So far the granular oscillator is the only thing I have a problem with. It's easy to make it sound bad and seems to use far more CPU than many of the other granular tools I have. So I've just left it be.

[jrwaltb]

I think Serum2 will get some upgrade/fix for the CPU matter since it seems to affect so many people with different DAWs and different systems (it seems it is not just Mac users or windows users but all across if I am not wrong). But let’s see when

Some people do not have it like me on the M1, Phaseplant hits the cpu the same way Serum 2 does.
It is chipset specific and I think even Steve confirmed it.

[User3]

How to make the panning automatically follow only the release curve of the ADSR envelope in Serum 2 (but not the other parts of the ADSR envelope)?

[Morty-C-137]

How to make the panning automatically follow only the release curve of the ADSR envelope in Serum 2 (but not the other parts of the ADSR envelope)?

Set the ADSR envelope to 'BMP'. Pick an LFO to modulate the pan and set the delay time (the tine it takes for the LFO to kick in) to match the beat division of the decay stage of the ADSR envelope.

EDIT: maybe this screenshot will help clarify..

[enCiphered]

Serum 2 just got updated to v2.0.19:

- Added new improved Spectral "Pitch Shift" warp mode, the old one has been renamed to "Pitch Blend"
- Added persistence of preset folder collapse / expand state
- Double-click params reset preference now applies to Envelope & LFO curves
- Fixed alt-drag from LFO to WT controls
- Fixed automatable params resetting after host loading state from session file in Pro Tools
- Fixed drag from LFO to noise menu / noise sample display
- Fixed Filter 2 On button not displaying correctly until selected
- Fixed Granular/Sample/Spectral Osc playhead jumping into loop region when scan direction reversed
- Fixed LFO modulation busses getting deleted unexpectedly
- Fixed LFO point multiselection via Ctrl/Cmd-drag
- Fixed LFO submenu not always showing when the selected destination of a mod slot
- Fixed LFOs behaving erratically after adding a large number of FX units
- Fixed MIDI aftertouch, CC and pitch bend messages not getting passed to output in AU version
- Fixed MIDI output not working in AAX version
- Fixed Noise Osc "Audio Input" selection in FX version
- Fixed preset pack checking & handling of invalid file names
- Fixed Sample Osc clicks on changing loop direction when using PD and Xfade
- Fixed Spectral Osc xfade when loop direction changes
- Fixed Unison Stereo Width modulation range for S1 presets
- Improved compatibility of Serum 2 FX with FL Studio