@AntonVorozhtsov like I said, they are NOT the same thing anymore. One of the C12 changes was to the performance meter. So you cannot compare C11 meter to C12 because they do not show the same thing.
Our investigations here refer to audible performance issues with C12, where C12 is failing to playback the projects dropout-free, which played just fine in C11. Please consider when posting .
Just some remarks on the Performance Meter:
the redesigned Performance Meter in C12 is showing four values, aiming to give users a more detailed info about the systemās momentary load:
ā Realtime: how much of the available time (in % of the real time latency, set by your audio buffer size) is consumed by real time processing? This value is averaged over several buffers, and therefor moving slowly. It gives an impression of the overall load of time-critical processing in your project.
ā Asio Guard: how much of the available time (in % of the Asio Guard latency, set by the Asio Guard level Low/ Normal/ High) is consumed by prefetched (= non-real time) processing? This value is averaged over several Asio Guard buffers, and therefor moving slowly. It gives an impression of the overall prefetch load of your project.
ā Peak: this value shows the recent maximum values of the time-critical processing; it gives an impression if there are load peaks, caused by - e.g. - certain instruments, song structure (plenty of Midi notes starting at the same time,ā¦) or FX. This can help you find and omit certain bottle necks.
It is not averaged, and can therefor look jumpy, especially with small real time buffers. It also reflects the jitter of your audio hardware. A heavy jitter can limit the performance with small buffer sizes.
ā Disk Cache: showing the read/ write buffer fill level, referred to the max. throughput (you mostly only see it move on cursor relocate or playback start)
and here is the bit that is very different to C11 - It is not averaged, and can therefor look jumpy, whereas C11 was an average and therefore smootherā¦does not explain performance issues but does help when comparing.
Itās almost as if they donāt even beta test the updates before releasing them. Especially something as obvious as the midi notes being off grid - how could that have possibly been overlooked?
No problem since yesterdays crash. I tried to recreate my last scenario multiple times but Cubase 12.0.40 kept running stable on my mac studio ultra. maybe it was just a quirk. loving the maintenance updates so far!
Yep i have the same issues on win 11. almost every time at opening cubase gets either stuck or crashes at different loading stages. without any crash dumps. usually i have to restart
my whole computer to get it working again.
I try to load a previous project- cubase freezes mid loading and the only way to close it is to force quit via windows task manager.
Same happens at quit. Cubase always gets stuck as a background process. And if you try to open it again- poof crash
Middle of a project- poof crash without any crash dumps. When i finally manage to start c12 again i get the grey screen(to delete preferences,ā¦) and the top issue area where the issue (and crash dump) should be located is blank.
all my other audio software works without a glitch.
This has really been a nightmare since its release in March. Not a single version of c12 is usable for me. Ive tried too reinstall it from scratch several times but no dice. Ive been on board since v6 but now I give up, I have to much work to be troubleshooting for hours.
Please contact Steinberg Support if youāre facing any issues that youāve not been able to fix yourself.
Make sure that the Steinberg Activation Manager is up to date (1.3.1.698 or later) and that nothing is getting in the way of its operation (for example, an overzealous antivirus program). If you have plugins that still use the USB-eLicenser dongle, try connecting it directly to another USB port.
I tried contacting support in the past and the quickest answer i got was after 31 days telling me to restart my computer. After that they stopped responding. So thanks but no thanks but the official support is useless. Also my country doesnt offer direct support so i had to sent it directly to info mail adress. ecause I cannot create a ticket in MySteinberg area.
Same here on Win 10 - almost everytime I open Cubase it gets stuck - sometimes force quit helps and re-open and sometimes I need to restart the whole computer. I am extremely dissapointed with version 12 so far.
Steinberg support is the painā¦ I am owner of Ableton live 11 as wellā¦ and they support is fast. And they always reply to your ticket. And regarding Steinberg again - itās crazy that some countries canāt attach the ticketā¦
yup. I have ableton also. Their support is fast.they usually answer in a day or two.
I also never understood that policy regarding direct support unavailable in some areas. but thats Yamaha for you.
@Janko_Kezar can you open your eLicense and perform maintenance, does that all work fine ?
Did you update from the download manager or direct from the steinberg website ? if it was from their website you would need the latest activation manager download too.
I think they have been more concerned about getting the M1 sorted and left us to get on with it . Piano rolls fine in .30 , ive not had any problems with .30 and donāt know why i updated really , iāll sit back here until the forum comes up with positive feed back about 12ās new releases
Am I missing something or must I download the entire 12.0.40 application to upgrade, and if so why is this not explained Download Assistant or the announcement? There is nothing in Download Assistant that says Cubase 12 update. And am I supposed to reinstall all the other features? Can you please make you interface clear.
Itās a Cubase update. You just have to download Cubase. The Cubase installer can both install the DAW application from scratch or update an existing installation.
If we donāt get replies on our SB tickets we are told to use the forum, now itās the other way round.
With SB its always the customer who does everything wrong.
The goal is to ensure that the user will be able to receive the help they need, not to shift blame. He didnāt mention if he had contacted support about this issue.
.
