You don't need to manually block website IPs. IF you launched Serum while in "Block to Block", then it allowed conneetion by default. You can then go in to the firewall tab and click fire emoji for the corresponding service/ip to block it.

Set Glasswire to "Click to Allow" to train it on a case-by-case basis. So when you run and app in standalone, and daw mode afterward, Glasswire will ask your permission (if it wasnt already allowed in default mode). For Ableton, its not actually "Ableton Web Connect" that you need to block (unless that is crked too), but the "Ableton Plugin Scanner". The same method applies for other DAWs and standalone plugins.

Glasswire has never failed me (I also user Serum 2 and Ableton) and is actually worth the subscription.

 

Last edited: May 22, 2025

Go back? VPN disabled?

Xfer Records Serum v2.0.17 patch (Win64; AAX, VST3)

1. Install_Xfer_Serum2_2.0.17
2. Xfer Records Serum v2.0.17 patch

 

Last edited: May 22, 2025

Why would you want to do DPI when you already have access to the OS itself? Seems pretty stupid to waste computer resources when it's not needed. Most DPI is not interesting until it's decrypted (DPI was a thing back in 2003 when 80% of the Internet wasn't encrypted traffic. UDP isn't stateful by the way, it is stateless by definition. You forgot to mention all the other IP protocols available.DPI is mostly useless for encrypted traffic, you have to look at traffic patterns and behavior. Have fun with TLS Inspection btw, it's totally possible to do in certain scenarios, but you open up a can of worms when you realize what it takes to disrupt the end-to-end encryption for all sites, services and application that you use on your network. A lot of services and apps will not work. It's very rare cases it's needed anyways. If you have full control over the computers already, you don't have to act middle man to analyze the traffic..

Windows Firewall is what it is. But it's working and it doesn't take stupid of amount of resources. No problem blocking things with it (which is the point in this case). If you don't like the GUI, use powershell or bash or whatever to configure it.

How is it minimal and difficult? It is as simple as adding inbound as outbound rules. Please explain why it is difficult than any other OS? More difficult than what? iptables? nftables? pf?

What OS installs a real IDS or even a IPS solution? Have you ever worked with any? Why on earth would you have those installed on your local
computer. Does the user need to know that his/her computer was portscanned? A normal user could never see the difference in an attack or a simple network scanning. And what does it matter? If you need to auto-block "instrusion" tries, sure, Windows Firewall can't do it. But neither can any software firewall that comes with the OS. You can write your own script to do it with Windows Firewall (as any OS firewall) though.

True. But source-code is available for certain, even non-US governments, to read the code.

Wrong.

Except where the community forget to audit because they trust the developers. Source-code has been compromized on several occations. The most recent thing where someone actually succeeded. They spent 4 years to infiltrate as a developer adding real code for a certain package used in pretty much all Linux distributions. And then boom, one day they added a backdoor and the code was installed on
every linux-machine that updated their system before it was caught (by accident - not by audit).

Not really true anymore. Android is the prime target because it will get you the most money of you happen to develop a 0day root exploit. It will cost you like 10x more than a Windows one. Or earn if you're a blackhat looking for money on 0day markets.

Yes, but the same type of vulnerabilities has been found in all OSes. The question is, do they get fixed?

Yes, and that isn't unique for any specific OS... Android has larger issues because updates aren't applied by all manufacturors, and many stop sending updates after only 1 or 2 years. And updates aren't sent to many devices at all. Most updates for Android are sent long after 0day was discovered or published.....

Yes. Exploiting can be done in any OS, in different ways, but Windows have had certain architectural disadvantages.
Just don't run software you don't trust. MacOS people seems to disable security features to be able to run patched or cracked software, which is quite funny..

Disabling things like OneDrive - or telemetry is done via installation profile, it isn't even installed or enabled during installation.
Cortana? Cortana has never been installed on any of my machines. Is that a Home edition thing?

You don't have to, just do it in the installation profile you use when installing the OS.

Windows sends anonymous user data by default, which should be a crime in my book. But as I said, you can chose to not enable
anything of this with an installation profile.

Yes.. Every large US company cooperates with what the US government wants. Avoid any american services or companies if you're
worried about them cooperating with the current US government. A lot of things are happening right now in this area.


It was NO back door. Stay away from ALL american services and software if you are worried about the US government AT ALL.

The so called NSAKEY has NOTHING to do with the organization NSA. Can't believe why this is spread around still... Quite funny if you know the origin of it. Again, don't use any american service if you feel monitored and unsecure. Good luck not using any services hosted by or with Google, AWS, Microsoft in some way even when using another OS.

Was more true before, but isn't anymore.

Yea, so are SSH brute-force attacks against Mac and Linux. Who opens up SSH and RDP to the Internet?
Who in 2025 uses only username and password without MFA?

All OSes in enterprise environments, including MacOS, iOS, Android and Linux use centralized management and deployment of updates. You just don't push all updates to thousands of computers before doing a proper test. Risk assessments is done if there's any high risk vulnerability like a new RCE, for any OS. Sometimes updates are done before the planned "update-window". Sometimes other measures are taken.
There's no difference in between how updates are handled between OSes.

ZoneAlarm, Glasswire?? IT-professsional?? Wtf, who told chatgpt that? =)
pfSense isn't installed on Windows OS so it has NO meaning mentioning that.
You can't compare software firewalls running on the OS itself with external firewalls. ANY firewall running on the OS can be disabled, either by user or by "malicious code". Why even mention firewalls that are not running in the actual OS? pfSense is running on BSD, and it runs on it's own. Why don't mention real enterprise firewalls.

No OS have "sufficient monitoring" by-default. Rule-based blocking is exactly what Windows Firewall does btw.

Windows offers sandboxing since a couple of years... chatgpt needs to updates. ;)

 

thank you all for your support, but its not working for me.
must be doing something wrong. maybe after all im gonna buy it

 

LOL guys look what just popped up: Xfer-Records-Serum-2-v2018 WTfix - vr_tcd_x
"WTFix" stands for wavetable import fix.

Its working! I imported like 50 wavetables one after another. No melting GUI.
Before this patch I timebombed within the first 10 seconds.

So it was not only me! There was actually a problem with importing wavetables.

 

@colorado1337, congratulations...finally you're really lucky and have a serum that works!

Xfer Records Serum 2 v2.0.18WTFix-V.R_TCD_X
"WTFix" stands for wavetable import fix. Enjoy!

 

Ok I get it now. Loading wavetables in Constant Frame size (Pitch Average) and FFT (258) is what triggers the issue. It's not a "timebomb" it is an anomaly most likely to do with the cracking. Just repro-ed it with a single wavetable imported @ FFT (258).

[edit]
Patch works - tested all possible import modes and no issues. Use with v2.0.18.

 

Last edited: May 22, 2025

WFW + defender are two of the first things to chop when doing final optimization on a win build. I would agree that seemingly it's rules at least in theory do what you would think they would do. However I have tested the rule integrity of the WFW and to be perfectly honest, it sux. Make a rule and fill in all the fields that make sense for that rule to do what you want it to do. Then apply it. Like say you're trying to keep the windows file explorer limited to local lan/domain ONLY no internet access (which by default it will attempt to make connections if you don't ride its ass).. So you set that up seemingly. Then watch as other windows shit starts to break - like all local area network connectivity to the machine shutting down for no good reason. Fucking ridiculous. WFW acts wonky like that majorly when you attempt to use it to block parts of the windows OS like services, dll's, apps, etc... Which btw, with a proper 3rd party FW, doing this sort of thing is second nature and doesn't break shit.

WFW does not do real time network traffic monitoring - a must for figuring out which pesky service or DLL (or possible vst) is accessing the internet (for those that insist on connecting their production boxen to the net).

If you want PROPER network management (like the big boys do) you'll shit-can defender+wfw and run a smart 3rd party network firewall (and A/V) along with NetLimiter. Use the firewall to do the harder-core network stuff and NetLimiter to easily block stuff at the app and service level. Presumably your choice of firewall will have a real time network monitor that shows <the process name or id #> <local addr:port> <remote addr:port> <status of the connection> <bytes in> <bytes out> at the very least, all in real time as it happens. Netlimiter can also display and block at the app and service level what network traffic is being used by what and log where a process has gone how much bandwidth it has used, etc which is extremely handy to have as well. So with a good FW and NL you have complete coverage of network activity at your fingertips.

 

Last edited: May 23, 2025

great news, thanks for confirming!

 

Of course not, but that's not a "problem", it's just more protection. DMG Audio plugins are great, amazing in fact. But that developer working on this synth only for effects only would have been a waste of his apparent talents when it comes to adding time bombs and these other new action-based "features" like GUI melts. It's very likely people will continue to run into more of them, and probably one reason why many people complain about CPU usage with this version. Some v1 versus v2 in s1 compatibility mode with the same preset comparisons might be interesting to see.

All you can really do is continue to report them, and keep actually testing out new revisions. Or buy it (and maybe a new computer to run more instances of it). It makes running legit iLok'd Falcon seem like opening a text file for me.

 

I have gui issue when I start workig in the matrix I'm on macos xfer serum 2.0.16 macos from sister site
And body have any ways to fix this can I block host to get rid of issue


Also please tell me how can I remove the serum 2 completely from macos which folder should I remove

 

Remove applications: Drag the Serum 2.0.16 app to the trash.
Delete library and support files: These are usually located in the following folders:
/Library/Application Support/Serum
/Library/Preferences/com.xferserum.plist
~/Library/Application Support/Serum
~/Library/Preferences/com.xferserum.plist

Delete cache files: These can be found in:
~/Library/Caches/com.xferserum

 

Hello
Did there's a fix for serum 2 multiple instance crashing on ableton ?

I know people have the issue, others don't

I can launch multiple instance on fl studio it doesn't crash, on ableton if i put more that one instance it crash. I recently changed my whole pc from AM4 to AM5 so new windows etc, it still crash.

Any idea ? Maybe we should wait like one year to have it working till people buy it, like the crack guy is offering that to xfer ?

 

Spoiler: Source: Grok KI

The issue of Serum 2 crashing Ableton Live when using multiple instances, particularly on a Windows system with an AM5 upgrade, seems to be a known problem based on user reports, though it’s inconsistent across setups. Since you’ve confirmed it works fine in FL Studio but not in Ableton, and you’re on a fresh Windows install with new AM5 hardware, here are some potential causes and fixes based on available information and troubleshooting logic:

Potential Causes

1. Serum 2 Performance Issues: Serum 2 is reportedly more CPU-intensive than Serum 1, with some presets causing significant spikes even on high-end systems. This could overwhelm Ableton’s processing, especially with multiple instances.
2. Ableton-Specific Compatibility: User reports suggest Serum 2 has issues specifically with Ableton, while other DAWs like FL Studio and Bitwig handle it better, pointing to a potential incompatibility or optimization issue with Ableton.
3. Corrupted Preset Database or Installation: Corrupted Serum files, especially the preset database (Serumpresetdb.dat), have historically caused crashes when loading or switching presets, and this could extend to multiple instances.
4. Driver or System Conflicts: Your AM5 system and new Windows install might have driver conflicts (e.g., graphics or audio drivers) that interfere with Ableton’s handling of Serum 2. A specific case linked crashes to NVIDIA drivers (nvwgf2umx.dll).
5. Plugin Format or Settings: Using the wrong plugin format (e.g., VST2 vs. VST3) or mismatched bit versions (32-bit vs. 64-bit) can cause instability.
6. Ableton Live Version: Certain versions of Ableton (e.g., Live 11 or 12) have been reported as less stable with Serum, especially with CPU-intensive plugins.

Troubleshooting Steps
Here’s a step-by-step approach to address the issue:

1. Update Software:
   • Ensure Ableton Live and Serum 2 are fully updated. Check Xfer Records’ website or Splice for the latest Serum 2 version and Ableton’s website for Live updates. Outdated plugins are a common cause of crashes.
   • If you’re using a rent-to-own Serum via Splice, verify the Splice client is updated (Windows version 1.2.15 or later).
2. Test Plugin Format:
   • Confirm you’re using the 64-bit VST3 version of Serum 2, as your Ableton Live installation is likely 64-bit. Mismatched bit versions can cause crashes.
   • Try switching between VST2 and VST3 formats in Ableton’s plugin settings to see if one is more stable.
3. Clear Serum’s Preset Database:
   • Navigate to C:\Users\<YourUsername>\AppData\Roaming\Xfer and delete the Serumpresetdb.dat file and the Serum folder. Reopen Ableton and let Serum rebuild the database. This has resolved preset-related crashes in the past.
   • After rebuilding, go to Serum’s Menu > Rescan folders on disk to ensure proper indexing.
4. Check for Driver Conflicts:
   • Since you’re on a new AM5 system, update all drivers, especially graphics (NVIDIA/AMD) and audio drivers. A known issue with NVIDIA driver nvwgf2umx.dll caused crashes with Serum and other plugins. Use Display Driver Uninstaller (DDU) to remove and reinstall the latest NVIDIA/AMD drivers.
   • Test with no graphics driver installed (as a diagnostic step) to see if the issue persists, as one user reported stability without the driver.
5. Adjust Ableton Settings:
   • Increase the buffer size in Ableton’s Preferences > Audio to reduce CPU load (e.g., 512 or 1024 samples).
   • Disable unused audio inputs/outputs in Ableton to minimize CPU and latency issues.
   • Enable “Reduce Latency When Monitoring” in Ableton’s Options menu to manage plugin latency.
   • Freeze tracks with Serum instances to reduce CPU load, as Serum is known to be resource-intensive.
6. Test in a New Project:
   • Create a new, empty Ableton project and add one Serum 2 instance. If it’s stable, gradually add more instances to identify the crash threshold. If it crashes with a single instance, the issue might be installation-related.
7. Lower Serum 2’s Resource Usage:
   • In Serum 2, reduce the quality setting (e.g., from “Ultra” to “Good”) in the Global tab to lower CPU usage.
   • Avoid CPU-heavy presets (e.g., “STR-Pedal Chords” or “PD Celestial Light”) and reduce polyphony (voice count) in presets.
8. Disable Plugins Temporarily:
   • Launch Ableton while holding [ALT]/[OPTION] to disable all plugins, then re-enable only Serum 2 to test if other plugins are contributing to the issue.
9. Check CPU and RAM Usage:
   • Monitor CPU usage in Ableton (top-right corner) and Task Manager. Serum 2 can spike to 50-100% CPU with certain presets, even on high-end systems.
   • Ensure RAM isn’t maxed out, as high memory usage (e.g., nearing 3GB in 32-bit Ableton) can cause crashes. Use 64-bit Ableton if possible.
10. Reinstall Serum 2:
    • Uninstall Serum 2 completely, delete the C:\Users\<YourUsername>\AppData\Roaming\Xfer folder, and reinstall from Splice or Xfer Records. Ensure no old Serum 1 files remain, as they can cause conflicts.
11. Contact Support:
    • If the issue persists, contact Xfer Records support ([email protected]) with your system specs, Ableton version, Serum 2 version, and crash logs from C:\Users\<YourUsername>\AppData\Roaming\Ableton\Live Reports.
    • Also reach out to Ableton support ([email protected]) with crash reports to check for DAW-specific issues.

Notes on Your Situation

• AM4 to AM5 Upgrade: Your new system should be more capable, so hardware limitations are unlikely the root cause. However, ensure your motherboard chipset drivers and BIOS are updated, as AM5 platforms (e.g., Ryzen 7000 series) can have early firmware issues.
• FL Studio Stability: Since Serum 2 works in FL Studio, the issue is likely specific to Ableton’s plugin handling or a conflict with your system configuration in Ableton. This aligns with reports of Serum 2 performing better in FL Studio and Bitwig.
• Crack Comment: Your mention of “crack guy” and waiting a year suggests frustration with Serum 2’s stability. Using cracked software can introduce additional instability (e.g., corrupted files or incomplete installations), so ensure you’re using a legitimate copy from Xfer or Splice.

Speculation on Waiting
Serum 2’s performance issues are well-documented, with users reporting CPU spikes and crashes in Ableton as recently as March and April 2025. Xfer Records may release patches to improve optimization, but there’s no guarantee of a timeline. Waiting a year might not be necessary if the above steps resolve the issue, but monitoring Xfer’s updates or their forums for fixes is wise.





Next Steps
Start with steps 1-3 (update software, test plugin format, clear preset database) and monitor CPU usage. If crashes persist, focus on driver conflicts (step 4) and contact Xfer/Ableton support with detailed logs. Since FL Studio works, compare Ableton’s audio settings (e.g., buffer size, sample rate) to FL Studio’s to identify discrepancies.

If you can share your system specs (CPU, RAM, Ableton version, Serum 2 version), I can tailor the advice further. Let me know how these steps go or if you’ve tried any already!