Equipment: M1 Max, 64GB, 2TB SSD, Sierra, Cubase 14, Apollo x4, 512 sample buffer, 96,000, 32 bit float.
I need to mix in headphones. When I attempt to use the SoundID Reference with the VM add-on, the audio breaks up with red box peaks measured in the Cubase Audio Performance Monitor when playing back several VST instruments such as The Legend HZ, VSL Reiger Organ, or EastWest Opus. Granted, these are high-processor bandwidth instruments, so the playback Peaks are higher than with other instruments, but they are easily playable until the VM is engaged. When the VM add-on is engaged, the processor peaks double in magnitude and the audio becomes unusable.
Has anyone else seen this? Do you have a fix or workaround? I have stripped away everything I am able to remove. Thanks!
3 comments
I should have mentioned that this problem does not occur when using other virtual monitoring apps such as Wave NX series, Immerse Virtual Studio, DearVR Monitor, etc. However, it occasionally manifests when using the Waves StudioVerse NX Preset, where four of the Waves NX models are aggregated in a single interface. This leads me to think the problem is likely related to how processor threads are handled in the Virtual Monitoring Add-on. All the best!
Hi Robert - I experience the same issue with an M1 Pro and Ableton. Sonarworks works great with low CPU usage until turning on Virtual Monitoring, which causes severe CPU spikes at basically all buffer settings. I have an open support ticket with them, and my rep has been very kind but it seems like they couldn't reproduce the problem and didn't have other users flagging this as an issue. I think it would really help us both if you opened a support ticket! One workaround I found in Ableton was running Ableton in Rosetta mode inexplicably eliminates any CPU spikes. However, then the rest of my session performs much worse and other plugins misbehave in Rosetta so it's not a good solution for me. This is the only example I've ever seen of software running WORSE in Native ARM rather than Rosetta. Very weird!
Hi,
Fred Thanks for your answer and posting here! As you may have noticed, I just replied to your follow up inquiry in our ticket.
@... Sorry for the late response. We have reported this issue and I created a ticket for you so we can link your ticket to keep you informed. We'll be in touch shortly.