Hi there. I have a mac mini M2 chip running Sonoma with Cubase 14 on it. My problem is that I can’t for the life of me figure out why serum 2 of all things sounds so thin compared to what I had before opening the project just hours ago. I updated it to the latest version and still the issue persists. I checked on some forums and found nothing so hopefully someone can help me out?
Thanks in advance.
What exactly did you do? Load serum in Cubase, choose a preset, save the project and open it later to find the serum sound different than before?
Does this always happen or is this just one preset? Can you reproduce the behavior in another project or with other presets?
Do you use any other effect plugins after serum?
Was there perhaps mapping to the mod wheel and on reloading the cc1 defaulted to 0?
Unless automated or not set to reset controllers on stop, CC1 will always reset to zero. Ideally Cubase should not change the values of controllers you haven’t touched.
Well I played a part and then while I was playing it, the patch changed to a 8 bit type of sound (not my vibe), lol and then I was stumped why it did that so I am now updating all of my drivers for my controllers as well as my plugins. Could it be a plugin in the project that is doing this?
I thought this might be possible so I went ahead and unplugged all of my controllers as well as updated them. Still no luck. When I open it in another project the presets are completely fine. Seems to be a CPU issue. Which is strange cause I could easily run 70 some tracks before today and everything works like a dream. Now it’s kind of a nightmare.
I set everything on the mod wheel to unity so I’m not sure if that’s the case cause it happened “while” I was playing the patch itself. Very strange. A bug perhaps? I even updated cubase.
It looks like what I’m going to have to do is reset the patches to their default state then adjust till it sounds how it did again and bounce them down so they won’t be altered again. Really sucks as I have so many projects with synths and this has happened before but it “fixed” itself somehow. Thanks.