Official Serum 2 thread!

[Morty-C-137]

Are there other skins now?

I am working on it

[Bartone]

Is the CPU problem solved?
I demoed Serum2 earlier and it was really difficult to use (I could sometimes run 1 instance of Serum2 fine, but adding second Serum2 started to be a bit too heavy).

I am using the latest FL Studio if that matters.
I don’t use any physical instruments at the moment nor record vocals (maybe later). Could I do some optimization in Fl Studio to make Serum2 run better?

I really like the layout and some presets of Serum2 (and the fact that there are HUGE amount of tutorials out and presets to get). But the CPU seems to be problem :/

[audio/fault]

Is the CPU problem solved?
I demoed Serum2 earlier and it was really difficult to use (I could sometimes run 1 instance of Serum2 fine, but adding second Serum2 started to be a bit too heavy).

I am using the latest FL Studio if that matters.
I don’t use any physical instruments at the moment nor record vocals (maybe later). Could I do some optimization in Fl Studio to make Serum2 run better?

I really like the layout and some presets of Serum2 (and the fact that there are HUGE amount of tutorials out and presets to get). But the CPU seems to be problem :/

i‘ve heared a lot about cpu problems with serum2 but can honestly say it‘s totally fine on my mac mini m2 with logic and live. can‘t compare with serum1 as i just bought it recently.

[Igro]

Is the CPU problem solved?
I demoed Serum2 earlier and it was really difficult to use (I could sometimes run 1 instance of Serum2 fine, but adding second Serum2 started to be a bit too heavy).

I am using the latest FL Studio if that matters.
I don’t use any physical instruments at the moment nor record vocals (maybe later). Could I do some optimization in Fl Studio to make Serum2 run better?

I really like the layout and some presets of Serum2 (and the fact that there are HUGE amount of tutorials out and presets to get). But the CPU seems to be problem :/

Are you talking about CPU usage on presets? Many presets are made completely unprofessionally - to many parts are in use to get a result, that can be achieved with 60-70% less modules and LFOs. How much CPU it takes just when you are playing the init preset? This is how you need to evaluate a synth. Make sure your PC (?) uses the "performance mode".

[nanostream]

i‘ve heared a lot about cpu problems with serum2 but can honestly say it‘s totally fine on my mac mini m2 with logic and live. can‘t compare with serum1 as i just bought it recently.

YMMV, but using the granular and/or spectral engine with lots of grains and voices easily maxes out my M4 pro machine.

Most of the time it’s relatively easy to get around that, so it’s not a deal breaker for me. But I certainly hope some optimizations will deliver performance on par with Pigments or other (granular) synths at least.

[MrJubbly]

Are there any examples of some Serum 2 factory presets which certain users are finding to be particularly taxing on their CPU?

[nanostream]

Are there any examples of some Serum 2 factory presets which certain users are finding to be particularly taxing on their CPU?

There are a few xfer forum threads with examples, KY Dream keys might be one of those punishing factory presets, I believe:

https://xferrecords.com/forums/serum/cp ... nformation

[MrJubbly]

Are there any examples of some Serum 2 factory presets which certain users are finding to be particularly taxing on their CPU?

There are a few xfer forum threads with examples, KY Dream keys might be one of those punishing factory presets, I believe:

https://xferrecords.com/forums/serum/cp ... nformation

Ah yes. I can see that example as being a problem preset for many people. Definitely more resource hungry than most plugins sounds. That preset seems to average around 25% CPU when playing a medium speed arpeggio sequence. Which is quite a bit higher than I'm used to in most other plugins.

Hopefully, there are ways to mitigate some Serum 2 processes for such use cases.

[sempondr]

Hopefully, there are ways to mitigate some Serum 2 processes for such use cases.

As it is now, you can change the quality in Global settings to "Good".

[swilow11]

Ways around the CPU issues that I'm using- Lower polyphony, shorter releases, using hyperdimension or chorus instead of unison, quality setting on "good" except when rendering, not using the arp, bouncing out spectral sounds and reimporting them into the sampler engine, being cautious when using the S2 filters (especially the SVF which is awesome but really thrashes my cpu), lower grain count with granular. It's disappointing that the spectral engine is so taxing because it's brilliant but rendering out stuff works for now.

[Andrei Marchenko]

Folks, is it me only or after 2.0.18 update we got the same old poppy & clicky fella on start of the sound? I have just checked my bass presets that I did on previous version of Serum 2 and kind of surprised. I'm on MacOS using VST3 version of the plugin

[bitcrusher]

2.0.18 is fixes and not related to voicing, it's more likely something has changed with your playback. A perfect low sine starting from silence can sound like a defined click on headphones or laptop speakers, for instance.

[swilow11]

Folks, is it me only or after 2.0.18 update we got the same old poppy & clicky fella on start of the sound? I have just checked my bass presets that I did on previous version of Serum 2 and kind of surprised. I'm on MacOS using VST3 version of the plugin

On the start of what sound in particular?

[tumface]

No change in 2.0.18 audio for me.

[AlQuzMar]

Are you talking about CPU usage on presets? Many presets are made completely unprofessionally - to many parts are in use to get a result, that can be achieved with 60-70% less modules and LFOs. How much CPU it takes just when you are playing the init preset? This is how you need to evaluate a synth. Make sure your PC (?) uses the "performance mode".

That's useful when you only use the init preset