If the channels are Instrument Tracks then this is normal because selecting the tracks will make the instrument go in monitor mode. The ASIO-Guard will also drop when an instrument is in monitor mode, and depending of the instrument load the Realtime and Peak meters will vary.
1 Like
Iāve resolved this issue by removing the CPU monitor. It serves no useful purpose. The only monitor you need is your ears.
You are probably right there as some sounds max the peak meter out until you disengage and re-engage the monitor outputs. Then ok for workaround.
The thing is my ears do not hear any glitches when the peak meter maxes out.
The meters are there to put the wind up yer!! 
I also render each instrument track as i go along after editing.
That way no overloads
The funny thing is that the real time meters are always pretty low and the average and peak meters dance about, shotgun !!
To expand on @Louis_Rās anwser,
In:
Preferences > Editing > Project & MixConsole
You can disable āEnable Record on Selected xxxx Trackā. This will let you select tracks without them going into Monitor Mode and bypassing the ASIO Guard.
You can also look at the setting for Auto Monitoring in:
Preferences > VST > Auto Monitoring
1 Like
THX for all the answers!
Iām aware of the monitoring impact on the performance meter - I just wanted to point out that since 12.0.20 itās way more noticeable than on 12.0.1 on my machine, and itās not consistent - it depends on from which channel I switch to the next one (look for the blue āchopsā channel in my .gif).
But reading all the answers, I think this is only on my machine.
Itās not that big deal. As some of you mentioned, there is a workaround by turning off āauto aimā.
Iāll roll with that for the moment.
THX again!
Ahh didnāt even see that first one in there thanks for thatā¦ I dont have an āAuto Monitoringā entry in the VST section though? Windows only thing or?
This may be off topic but where can I get some of these performance spices ?
2 Likes
Just a heads up to anybody using Kontakt 6 in their projects:
I only had 3 tracks in the entire project and was getting CPU overload popups that would not go away - so much to the point where I could not hit stop on my project because the popup warning box kept popping up so fast that the moment you closed it, it would come back again before I could press my space bar to stop playback.
- One track had Ivory 2 on there, with the ambience, sustain resonance, and release samples enabled.
- One track of Kontakt 6 player with one instance of MM-Bass amped loaded.
- One synth track with different synths, trying to get it not to overload (would overload with various synths).
Then I went and checked Native Access for an update for Kontakt 6 player and surely enough, there was an update. I installed it, tried the project again, and now Iām not getting that CPU overload popup anymore. YMMV but update Kontakt 6 via Native Access if you ever use it, or the full version.
If the overload box comes back, I will give an update.
At least on my end, it seems to be an issue with Cubase 12. Iāve created projects of the same songs using different DAWās (Logic, Studio One) and no issues whatsoever. Itās a shame I paid so much for this upgrade. 128, 1025, buffers sizes doesnāt matter.
Ah, and using same vstāsā¦ Superior Drummer 3, Kontaktā¦ etc.
Thanks, thatās useful, Iāll look for that update.
You probably are already aware, but just in case youāre not, you can turn the CPU overload pop up off in preferences.
1 Like
Ah thatās right, I forgot about that, thanks! I like to leave it on so that I know when Iām running into issues, but come to think of it, maybe I should just turn it off.
With the newest Mac Monterey 12.4 update from today, I was able to work on 7 Projekts without a crash on exit 
I set aside some time today to experiment with the Alder Lake 12900k issue that sometimes sees Cubase use E-Cores instead of P-Cores and using the Steinberg Power Scheme.
Experiment 1. First I needed to know if the E-Cores was the issue, so I went into the Bios, enabled PER-E CORE which will give u extra settings, I then disabled the E-Cores, started up PC, loaded Cubase and the CPU usage was fine, no spikes, no problems.
Experiment 2. I now wanted to find out what is actually going on, so I re-enabled the E-Cores and again booted up Cubase but this time also the taskmanager CPU resource monitor. I noticed many of the E-Cores were parked.
Experiment 3. I decided to re-install Bitsum Lasso which will give me more control over the CPU, loaded up Cubase, disabled the E-Cores in Lasso but the CPU spikes remained.
Experiment 4. I thought core parking seems to be a link here, soā¦ I decided to turn off Steinberg Power Scheme and instead use Lasso and turn on Performance Mode, this prevents core parking at the cost of a higher energy bill lol. The CPU issue had gone.
Experiment 5. Repeated using the bitsun lasso profile several times on several sessions including a blank session with no problems.
Conclusion: Besides from Cubase obviously trying to use E-Cores before P-Cores there seems to be a link to parking.
QUICK FIX: Previously I was able to stop the CPU spikes by deactivating the outputs in Control Room and Re-Activating again, this is a quick fix if u do not have Lasso or any similar software but does sometimes break over time so you may have to repeat.
Time for a cup of coffeeā¦ lol
Ryan
3 Likes
Great work!
Cubase 12.0.20.263 64bit 2022.5.3 11.18.43.804.dmp (1.2 MB)
I am having so many issues I do not even know where to start. The program crashes on start and sometimes I have to restart 3-5 times to get it to work. It crashes on exit, and it crashes randomly when using it. HELP!
The crashdumps do not seem to be working properly either - lots showing up at 0 bytes. Perhaps because I am not even getting past the splash screen most times. How can I begin to fix this mess? I attached a crash dump of the last one that worked.
I am using Windows 10, i9900k , 32 GB ram, CB 12 pro. Cubase 11 ran on the same system and was stable.
1 Like
Do you have anything that still needs the old elicense and dongle ?
I have several items on my dongle including sound packs and GrooveAgent 5 and Halion 6 and Vengeance plugins.
Basically I cannot use C12 without the dongle but I also need the new activation manager. Sometimes my elicense stops working so I pull out the dongle and put it back in and restart my machine and then check the elicense app to make sure it opens fine.
Try that and see if it works. There are license issues in the dump file but also encryption issues too. That could be because it cannot find the license. You have not encrypted your drive have you ?
Iād the new activation manager working okay as well ?
Actually, the only thing I have on eLicensor is Cubase 11.5. I ran the update for that and so far CB12 has started up 3 times in a row without crashing. I thought the eLicensor wasnāt required for 12?
Thanks for the adviceā¦lets see how this works in the coming days. I really like Cubase and I want it to work!
1 Like
I missed that one
hahaā¦well spotted. CB 11 I meant