I recently upgraded to Cubase 14 and am having an issue with audio to the point where I can’t use 14. I am running this on the same computer and hardware as Cubase 13, where I have no issues and very good audio performance. I’ll put my system specs and screen caps of performance and settings below for the two versions of Cubase. Any help would be greatly appreciated.
System:
Windows 10 22H2
RME FireFace 800 (latest drivers)
both versions tested at 44.1 kHz, 64 samples, only analog channels 1-8 active
Cubase Pro 13.0.51 and Cubase Pro 14.0.10
first tested with no project loaded (empty), then with the Venus Theory demo song
In the Audio Settings the Adjust for Record Latency is checked in C13 but not in C14.
I wasn’t totally sure what that does, so I asked Copilot. The response feels a bit generic.
What does the Cubase setting ‘Adjust for Record Latency’ do
The ‘Adjust for Record Latency’ setting in Cubase is used to compensate for the delay (latency) that occurs when recording audio or MIDI. This latency is caused by the time it takes for your computer to process the audio signal through the audio interface and any plugins or effects that are in the signal chain.
When you enable the ‘Adjust for Record Latency’ option, Cubase automatically shifts the recorded audio or MIDI events to align correctly with the playback position, effectively eliminating the latency during recording. This ensures that the recorded audio or MIDI is in sync with the rest of your project.
Would you like more details on how to enable this setting or any other specific information?
can it effect performance
Yes, enabling the ‘Adjust for Record Latency’ setting in Cubase can have an impact on performance. Here’s how:
Impact on Performance
CPU Load: Compensating for record latency requires additional processing power, which can increase the overall CPU load. This can be especially noticeable if you’re working with a large number of tracks or using multiple effects and plugins.
System Resources: The process of adjusting for latency involves real-time calculations, which may consume more system resources, potentially affecting the responsiveness of your DAW.
Buffer Size: The buffer size settings on your audio interface can also influence performance. Smaller buffer sizes reduce latency but increase CPU usage, while larger buffer sizes decrease CPU usage but increase latency.
Managing Performance
To manage performance effectively while using the ‘Adjust for Record Latency’ setting:
Optimize Buffer Size: Find a balance between latency and CPU load by adjusting the buffer size in your audio interface settings.
Freeze Tracks: If you’re using resource-intensive VST instruments or effects, consider freezing tracks to reduce CPU usage.
Monitor System Performance: Keep an eye on the performance meter in Cubase to ensure your system isn’t being overloaded.
By optimizing these settings, you can achieve a smooth recording experience without significantly impacting your system’s performance. If you encounter any specific issues, feel free to ask!
That suggests 13 and not 14 should have worse performance based on that setting.
Hi Raino - thanks for the reply and looking into this. As you surmised, checking the ‘Adjust for Record Latency’ didn’t improve things.
The symptom is constant crackling during playback. I took a screen cap of the perf. meter during playback:
Now if I crank up my buffer to 256 samples and set ASIO Guard to High, I can get noise-free playback, but should I have to quadruple my buffer and increase ASIO Guard on a newer version of Cubase when every other parameter is a constant?
I suppose I should put in a support ticket?
After the update to version 14 of Cubase, ASIO behaves very strangely and does not hold those projects that worked smoothly in 13. The asio guard is peaking, but the peak and rial time meter are at zero. how to fix this?
Hello, yes bit depth and sample rate are the same:
The Control Room is on in both. I have heard back from Steinberg and that was an issue they had me test. Apparently the monitoring connections when setup from the preferences of a previous version of Cubase can sometimes cause this issue. So I removed all preference files and restarted, but this did not fix the problem for me.
I normally run NUGEN Mastercheck, Waves Nx Ocean Way Nashville, and Sonarworks SoundID in my CR slots. Mastercheck and NX OW still caused high usage but Sound ID did not. So temporarily I at least have a partial fix in that I can run Sound ID in my CR which is the one I care about most.
I have VST2 plugins on my system still, but none are in use or show up in Cubase in the plugin manager.
The task manager mirrors what I see in the Performance meter: the Cubase usage is Very High when MC and NX are in the CR, but only Moderate when those 2 VSTs are removed.
Thanks for letting us know. It appears that there is a plug-in incompatibility. Consider reporting the issue to the plug-in makers. I have been in contact with Waves, and they have been responsive.
