Recenltly i noticed that if i active the monitor of a track if i check the meter the asio guard meter completely dissapears and the peak meter instead is very high
But if i deactivate the monitor button it changes again, my question is this normal??? It is a feature or a bug?
There is another way to monitor???
I also have the bug that disables asio guard when creating a new proyect but i find the workaround in another post( deleting and creating a new top most stereo bus)
I also have Studio One 7 and there is no problems working in that one, everything works super fast, stable and good.
I love Cubase is my favorite DAW ever but right now is unusable to work with
I am on Cubase 14.0.20 Native Mode
MacOS Ventura 13.7.4
MacBook Pro 16 M1 Pro
This is by design. ASIO Guard is a buffer for all tracks that are not in “live” mode, ie. that are not armed for recording or monitor their input.
As soon as you arm/monitor a track it will be removed from the ASIO Guard buffer system and will therefore put stress on the real-time = peak meter.
Thank you so much for the insight!!
And now another question is that if its normal that kind of peak in the meters, its just 1 channel i know i am at 96khz 32bit float 192 buffer size, but with the exactly same buffer and sample size on studio one with that plugins and more plugins, more channels, overall the meter is only showing me that i am using 10 or less percent which is kinda weird with cubase, i have my mac very optimized for audio, almost no tasks running in the background, only native plugins, with all my other audio and video apps my mac is a monster in terms of performance but with cubase i cant even use it well, i been had so much problems and performance issues wich are non existent with any other app, i hope the asio guard and stability overall gets the main attention with updates which we are in very dire need
You can’t compare the performance meters in Cubase with those in other applications. They don’t show exactly the same thing.
Unless you’re having actual issues, such as drop-outs when you don’t think you should, I wouldn’t worry about those meters at all.
As mlib said, these meters are not comparable. They do not have a scale, so we don’t even know what they actually display.
For the peak meter I would assume it shows an amount of time it takes when Cubase sends something to the operating system in order for it to come back to Cubase. But which time value is shown? Microseconds, milliseconds? Or is it showing something else like a percentage of the ASIO buffer?
And what does S1 show on their meter? Which scale are they using?
Exactly, IMO. Unless one is looking to see if they need to lessen the load on the computer before tracking (e.g., if the meter is hovering at a very high value before record arming, may want to disable or freeze some tracks, etc., to help prevent dropouts and ruination of a performance, etc. )
