I’m hoping someone can shed some light on this extremely annoying error. I can easily reproduce it with SonarWorks Reference 4 when used as an insert for my mains in Control Room by toggling between different presets. I also get this randomly (and frequently) during playback or when editing various plugin settings in a fairly basic 96 kHz Cubase 10.5.20 project. What’s really irritating is when I attempt to change something like an EQ setting. Cubase loses focus when the error occurs, requiring me to Alt-Tab until I manage to make the error go away just so I can regain control of the plugin.
I’ve thrown pretty much everything I can think of at this problem, and it makes using Cubase a miserable experience. My power settings are set for high performance (I’m using Cubase’s power scheme). I also run a batch file prior to using Cubase that terminates or disables any TSRs or services I don’t need.
Things I’ve tried:
- Different BIOS versions
- 32-bit and 64-bit double precision audio processing settings
- Different ASIO Guard settings
- Changing from Adrenaline to Radeon Pro drivers (I have the current version of the Pro drivers installed)
- Disabling “Suspend VST3 plug-in processing when no audio signals are received”
- Hyper-threading turned on or off in the BIOS
- 1024 audio buffer for mixing
- PC tweaked beyond belief while testing with LatencyMon to make sure my system is stable
According to Steinberg, I don’t need the audio.properties workaround for multicore CPUs since I’m running a version newer than 10. That file has no impact on fixing the problem.
- ASUS X99-A system board
- Intel i7 5960X Extreme Edition (8-core up to 3.5 GHz)
- Corsair Vengeance LPX 32GB (4 x 8GB) DDR4 DRAM 2133MHz
- Sapphire NITRO+ RX 590 8G G5 SE video card (AMD Radeon)
- Separate SSDs for my system, projects, and samples (all of them are M.2)
- Windows 10 Pro 64-bit (20H2)
- Waves DiGiGrid IOS, IOX, and Extreme Server
- The latest versions of third-party plugins that includes Waves (v12, including SoundGrid Studio and the 64-channel version of eMotion ST), Eventide, Arturia, iZotope, SoundToys, and Plugin Alliance
I’ve previously generated a support incident for this, but I was told to call support, and they do not have the most convenient schedule. Because I’ve had this problem for a while, I’m hesitant to upgrade to Cubase Pro 11.
Audio playback does not drop out (even though the error comes up frequently). The only time I can hear audible artifacts is when switching presets for SonarWorks Reference 4. Regardless of the source that causes the error to occur, the only spikes I see at the time occur in Cubase’s performance meter. Performance spikes do not occur for any of the logical processors in Task Manager or any other performance areas at that time. A WhySoSlow analysis when the error is reproduced hints at kernel and app responsiveness issues, but I would presume that would be expected when running this kind of test during multitrack playback.
I’m not the average user. I work as a Senior Systems Analyst in IT and have a natural inclination to stay current with software, drivers, etc. I’m aware of the potential for problems that comes with that. Although I’m overdue for a hardware upgrade, my current hardware should be able to handle my projects, especially since the one I’m currently working on is a simple four-track recording I imported with a whopping total of only six tracks.
Any assistance is greatly appreciated.