Only when starting - or stopping a project, there comes a peak and the red led/ cpu overload in the Audio performance monitor. No errors, no glitches and never when playing the song. It happens allready when starting a project even in a empty part of the song?
I have a very fast modern pc ( fastest i could buy ) Windows 11 - Cubase 15 pro
AMD Ryzen 9 9950x3d 16-core 4.30 Hz - 64GB ram/6400MT/s AMD Radeon 8GB RX7600 etc. Asio guard is on at high- Steinberg audio power scheme is activated.
Input latency is 2.608ms Output latency is 3.152ms ( Asio fireface USB- RME UCX II ) Latest drivers installed, everything updated.
The only way to prevent this is to increase the buffer size to 256 samples. But should I ?
Even when i set it on 48 samples, there are no errors! It only happens when starting or stopping a song? All energy saving settings are of. I don’t know what else I can do?
Is there a way to just simple turn the anoying performance monitor completely of please
And is this a This temporary red light ( at the start and stop of playback) a common quirk in Cubase ?
There are four meters in the performance monitor window - Real Time, ASIOGuard, Peak and Disk Cache. Which one of them is actually overloading?
First that meter doesn’t show the cpu load, to see that you should use the Performance tab in Task Manager. The meter shows the overall performance of the entire VST engine - which while that does include cpu, it also includes disk access, memory use etc.
First, can you hear any artifacts - clicks, dropouts, etc? If it only happens on start/stop it’s probably only a bunch of Inserts, Instruments, automation all trying to reset at the exact same time. Basically that meter isn’t telling you that something absolutely needs fixing, just that you might want to take a look. If it isn’t impacting what you hear, I’d ignore it.
Absolutely. The only reason to use low buffer sizes is when you are Tracking (or using outboard hardware effects). When Tracking a larger buffer size causes an often disorienting delay in your headphones - especially bad for singers. So reduce it for that, but only enough that the audio latency isn’t bothersome. But when you are working and all your audio sources are in the box, crank that buffer up.
@KT66, thanks for your responce,
Its the peak a gues? When starting a song, the white horizontal bar (far left on the taskbar) shoots all the way to the right, and the small square red LED lights up, after which everything calms down again; the red LED, however, remains active.
@ raino, also thanks for your responce,
There are no artifacts - clicks, dropouts, etc? Every thing works fine- even when buffer size is set to 48 samples, thats what I bought the fast expencive pc for- I don’t notice any latency which I do with some vst’s when i use 256. The same for my audio interface, its a RME UCX2 so i guess the hardware can’t be the problem
I have found the root cause. It turns out to be caused by a single VST: “VI Labs Modern D” piano. I don’t understand the reason behind it, though; this VST sounds fantastic and I couldn’t buy better hardware (PC and audio interface).
As indicated, it happens when starting and stopping the song. In any case, replacing the VST for another type solves the problem. What I also found strange was that deactivating the track in which this VST was used didn’t solve it, by the way. It was necessary to actually remove the VST.
Once it gets triggered it just stays red until you reset the meter. It’s not like a fader’s meter that holds the peak for awhile and then releases it. On my DAW just loading a project triggers it.
You’re solving a non-problem. If you prefer the sound of the original VSTi, you should use that.
You are of course right raino, and although there are more serious problems, the fact remains that the red LED appears (albeit incorrectly), and without wanting to be a nitpicker, I would still rather see it wouldn’t. But I understand that it won’t do any harm.
Thanks a lot for your help !