I wonder if I missed the 'trigger' of some kind during those couple of hours of testing. Maybe I've got a really good serial? But people claim that Serum checks its website, often when changing patches.ĭoes anybody have something to add? This test encouraged me to use this version, unpatched, with my main audio computer. TCP/UDP tracer haven't logged anything suspicious the whole time, and I didn't even use the patched version!Ĭould it be that Serum uses some services like firewall, background transfer, or some other service that I have disabled? I know it doesn't like those entries that block its website in the Windows hosts file, too. I saved the project and loaded it, everything fine. I wonder why? I've been using like 5-6 instances of Serum, browsing presets like mad just to try to trigger something and nothing happened. It actually didn't log anything since I started the daw and exited it. To cut to the chase, I've been playing with the Serum for hours and the TCP/UDP tracer didn't detect anything coming from the Reaper 4 DAW or Serum plugin. I have firewall disabled, no AV, only hosts file that blocks some websites and 2 xfer records websites, for just in case. You know, encouraged by this thread and the thread called 'Xfer Serum 1.3.0b1 calling home' that I cannot find for some reason, I installed v1.3.0b6 from the sister site, with a serial number that works - which means you don't get any weird messages when you press the preset browser button, in a VirtualBox VM Windows 7 optimised for audio my way in Linux Debian 9 and installed a TCP/UDP tracer from Nirsoft to be able to see if Serum is calling home.

Xfer serum serial number windows