Official Serum 2 thread!

[aMUSEd]

Still pretty new I guess eg The Unfinished released one this week that is still Serum 1 compatible because he was working on it before Serum 2 was released. I’m sure more will emerge very soon.

[liv]

There are tons of serum soundbanks being released all the time, but most of them (if not all) are serum 1 compatible. That means that those patches are not using the new engines nor the new filters. Why is that?
Also, by now i was expecting to see Omnsisphere like soundbanks on serum 2, since it allows multisampling. Haven't seen one of those yet. Brands have tons of produced sampled content that they could easily import to serum 2. I don't see this happening, anyone knows why?

Leap Into The Void is working on a new soundset for Serum 2 featuring dark eerie soundscapes and more, which is a derivative and continuation of v1.

Shadows Of Luring Attraction 2

[liv]

Here is a demo example.

https://soundcloud.com/leap-into-the-vo ... ravitation

[Ah_Dziz]

The biggest limitation with the sampler for me was having to do the chopping and editing in that really tiny window. For me, it was frustrating enough to not bother using it with anything but really short samples, which defeats the purpose of having slicing a little bit. I think someone earlier in this thread said that Steve is considering making that window expandable in the future, though.

It's still way better, as-is, than using an old school hardware sampler. Having the slices slightly off makes things sound interesting lots of the time in my opinion. With longer samples (multiple bars) you can still just go with the auto slicer (works great for drums and percussion). Having a full window would be great though. Especially if it gets incorporated into all the modes.

[concealed identity]

Well fortunately in 2025 there are a lot more choices than "old school hardware sampler" and "frustrating software sampler", and those choices give me the option to have slices slightly off or not. A full (or at least expandable) window would go a long way to making Serum 2's sampler a lot more usable, and from the sound of it the developers feel the same way.

[HHUKRadio]

I installed Serum 2 earlier (Windows 11 PC). I used the default installation locations for the VST3 file but Cubase cannot see it.

All my other VST3 files in the same location (Common Files/VST3) work fine and are listed in the Cubase plugins directory.

Anyone else had issues with Serum 2 integration into Cubase I wonder? Not sure what I'm doing wrong

[HHUKRadio]

I have fixed it. Cubase didn't like the folder in VST3 so I transferred the files to a new folder and renamed it and replaced the original.It now works fine in Cubase!

[Echoes in the Attic]

Do xferrecords answer support requests submitted on the website? I sent some technical questions last week on the web form but nothing yet.

[vanerio]

Do xferrecords answer support requests submitted on the website? I sent some technical questions last week on the web form but nothing yet.

I have not received a response for a month. I'm not sure what to do, I don't want to be a pain if they are busy or have a personal problem.

[AlQuzMar]

Yes. But CPU load builds up from there. I can easily create a preset in Pigment, that would kill my CPU too.
Some of newer filters do affect CPU indeed.

My CPU isn't the neewest, but I can run multiple instances of heavy Phase Plant or Vital patches. There are two synths that kill my CPU with ease though - Zebralette 3 and Serum 2. There are some bass patches in Serum 2 that my CPU can barely handle with low latency, even when I play them in a monophonic manner. That seems a bit excessive to me.

Could you name me that patch? I want to try and report back.

Okay, I finally had a look after upgrading my system. Now on Ryzen 5800x f.ex. a bass patch called "Kitchen Sink" hits good 50 per cent of real time CPU use with a single voice, so on my old system that would likely be hitting the limits. I'm on 512@48k so not even that tight latency there.

[nanostream]

Okay, I finally had a look after upgrading my system. Now on Ryzen 5800x f.ex. a bass patch called "Kitchen Sink" hits good 50 per cent of real time CPU use with a single voice, so on my old system that would likely be hitting the limits. I'm on 512@48k so not even that tight latency there.

Same preset, barely leaves a mark on a M4. 128@48k.

Screenshot 2025-06-06 at 00.42.45.png

[hcv242]

the patch BA - Kitchen Sink playing one note uses 20% of one of the cores of this macbook pro m1. The previous and next bass patches use 5% of cpu. 20% might sound a lot, but if you take in consideration that you have 8 cores, you can use 7 more of those cpu hungry patches and you will be fine. like super fine.

[vitocorleone123]

Okay, I finally had a look after upgrading my system. Now on Ryzen 5800x f.ex. a bass patch called "Kitchen Sink" hits good 50 per cent of real time CPU use with a single voice, so on my old system that would likely be hitting the limits. I'm on 512@48k so not even that tight latency there.

Same preset, barely leaves a mark on a M4. 128@48k.

Screenshot 2025-06-06 at 00.42.45.png

They didn't even get an AMD to test on until after they shipped. It's not a testament to Apple, but to rushing it out the door.

[Igro]

Yes. But CPU load builds up from there. I can easily create a preset in Pigment, that would kill my CPU too.
Some of newer filters do affect CPU indeed.

My CPU isn't the neewest, but I can run multiple instances of heavy Phase Plant or Vital patches. There are two synths that kill my CPU with ease though - Zebralette 3 and Serum 2. There are some bass patches in Serum 2 that my CPU can barely handle with low latency, even when I play them in a monophonic manner. That seems a bit excessive to me.

Could you name me that patch? I want to try and report back.

Okay, I finally had a look after upgrading my system. Now on Ryzen 5800x f.ex. a bass patch called "Kitchen Sink" hits good 50 per cent of real time CPU use with a single voice, so on my old system that would likely be hitting the limits. I'm on 512@48k so not even that tight latency there.

Yepp, 50% on my system (FL-Studio meter). 50% of one core.

The preset creater used 32 modulation targets and 20 effects for that preset. Plus unison. He needs to go back to school and complete education from scratch.

[aMUSEd]

Yes. But CPU load builds up from there. I can easily create a preset in Pigment, that would kill my CPU too.
Some of newer filters do affect CPU indeed.

My CPU isn't the neewest, but I can run multiple instances of heavy Phase Plant or Vital patches. There are two synths that kill my CPU with ease though - Zebralette 3 and Serum 2. There are some bass patches in Serum 2 that my CPU can barely handle with low latency, even when I play them in a monophonic manner. That seems a bit excessive to me.

Could you name me that patch? I want to try and report back.

Okay, I finally had a look after upgrading my system. Now on Ryzen 5800x f.ex. a bass patch called "Kitchen Sink" hits good 50 per cent of real time CPU use with a single voice, so on my old system that would likely be hitting the limits. I'm on 512@48k so not even that tight latency there.

Yepp, 50% on my system (FL-Studio meter). 50% of one core.

The preset creater used 32 modulation targets and 20 effects for that preset. He needs to go back to school and complete education from scratch.

I guess that’s why it’s called Kitchen Sink - probably created to test the limits of what Serum can do cpuwise