Xfer Records – Serum v2.0.24 Update – CE-V.R & TCD (AAX, VST3) [WIN x64]

By | November 24, 2025

 

Year/Release Date: November 23, 2025
Version: v2.0.24
Developer: Xfer
Developer’s Website: https://xferrecords.com/products/serum-2
Format: AAX, VST3
Bit Depth: 64-bit
Tablet: Cured
System Requirements: Win 10+

  • 18.1 MB

Description:
The legendary Serum Wavetable oscillator has been improved and made more flexible. Smooth interpolation mode allows for a virtually infinite number of positions in the wavetable (without the need for morphing). Filtering, FM, PD, ring mode, distortion, and new waveform deformations are available. We have yet to fully explore the capabilities of the dual deformations available for all major oscillator types.

 


Additional Information:

Distribution updated! Xfer Records Serum 2 v2.0.24-V.R, TCD

Release Notes
x64: SAL, AAX, VST3, FL
Easily install over any full-fledged system.
-TCD

TCD Note:
This is a reworked version of the initial (and currently only)
release of the same version. 2.0.24.

Changes:
Enable CLIP drag-and-drop.
Enable “Enable CPU Graph” option: true. The line should be
accounted for according to the settings, enabled or disabled, not always 100% disabled.
Check for updates has been removed from the user menu.


4 thoughts on “Xfer Records – Serum v2.0.24 Update – CE-V.R & TCD (AAX, VST3) [WIN x64]

  1. rudi m

    i get an error window when opening serum 2 in my DAW saying that Serum 2 Preset Folder was not found – i located it on my Disc on Documents/Xfer/Serum 2 Presets and clicked it but still not working… im on PC – does anyone has a solution for this problem? :/

    Reply
  2. Bartek Drywa

    Hello everyone.

    I have a very weird issue with “Limit same note polyphony to 1” function. Because it doesn’t work. Or actually, even worse- it works even if I don’t want it to. No matter if this setting is checked or not, it behaves as if it was on. It is EXTREMELY frustrating, when I’m playing live on my keyboard I can’t bear with that. The last update where I didn’t have the issue was 2.0.16, but I have to use 2.0.20. since I’ve bought a preset pack that has been made on a 2.0.20. Anyone has any idea how to fix it? Is it even FIXABLE by myself? And, maybe most importantly, do y’all encounter the same issue? Thanks.

    Reply

Leave a Reply to Bartek DrywaCancel reply