[SOLVED] BUG: Cubase 13 PRO: Processing overload, sound dropouts, sound interruption

arkdzo · November 13, 2023, 7:16pm

I created a new project from the blank and added 1 VST - Spectrasonics Keyscape (everything is up to date). I began to play with my MIDI keyboard Novation Launchkey 61 MK3 and after 2-3 seconds I heard the sound of dropouts.

Cubase 13.0.10 PRO
RME Babyface PRO (128 samples)
Windows 10 PRO
Intel Core i9-12900KF
DDR4 32 GB RAM
NVIDIA Geforce 3060ti

LatencyMon Report while playing (1 VST in the project)

SEE THE FULL REPORT!

FULL REPORT

CONCLUSION

Your system appears to be suitable for handling real-time audio and other tasks without dropouts.
LatencyMon has been analyzing your system for 0:00:40 (h:mm:ss) on all processors.

SYSTEM INFORMATION

OS version: Windows 10, 10.0, version 2009, build: 19045 (x64)
Hardware: MS-7D25, Micro-Star International Co., Ltd.
BIOS: A.90
CPU: GenuineIntel 12th Gen Intel(R) Core™ i9-12900KF
Logical processors: 24
Processor groups: 1
Processor group size: 24
RAM: 32655 MB total

CPU SPEED

Reported CPU speed (WMI): 320 MHz
Reported CPU speed (registry): 3187 MHz

Note: reported execution times may be calculated based on a fixed reported CPU speed. Disable variable speed settings like Intel Speed Step and AMD Cool N Quiet in the BIOS setup for more accurate results.

MEASURED INTERRUPT TO USER PROCESS LATENCIES

The interrupt to process latency reflects the measured interval that a usermode process needed to respond to a hardware request from the moment the interrupt service routine started execution. This includes the scheduling and execution of a DPC routine, the signaling of an event and the waking up of a usermode thread from an idle wait state in response to that event.

Highest measured interrupt to process latency (µs): 376.0
Average measured interrupt to process latency (µs): 7.232438

Highest measured interrupt to DPC latency (µs): 316.60
Average measured interrupt to DPC latency (µs): 1.344530

REPORTED ISRs

Interrupt service routines are routines installed by the OS and device drivers that execute in response to a hardware interrupt signal.

Highest ISR routine execution time (µs): 14.294948
Driver with highest ISR routine execution time: Wdf01000.sys - Kernel Mode Driver Framework Runtime, Microsoft Corporation

Highest reported total ISR routine time (%): 0.000514
Driver with highest ISR total time: Wdf01000.sys - Kernel Mode Driver Framework Runtime, Microsoft Corporation

Total time spent in ISRs (%) 0.000514

ISR count (execution time <250 µs): 14607
ISR count (execution time 250-500 µs): 0
ISR count (execution time 500-1000 µs): 0
ISR count (execution time 1000-2000 µs): 0
ISR count (execution time 2000-4000 µs): 0
ISR count (execution time >=4000 µs): 0

REPORTED DPCs

DPC routines are part of the interrupt servicing dispatch mechanism and disable the possibility for a process to utilize the CPU while it is interrupted until the DPC has finished execution.

Highest DPC routine execution time (µs): 563.364920
Driver with highest DPC routine execution time: nvlddmkm.sys - NVIDIA Windows Kernel Mode Driver, Version 536.67 , NVIDIA Corporation

Highest reported total DPC routine time (%): 0.008382
Driver with highest DPC total execution time: Wdf01000.sys - Kernel Mode Driver Framework Runtime, Microsoft Corporation

Total time spent in DPCs (%) 0.016713

DPC count (execution time <250 µs): 31415
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-10000 µs): 2
DPC count (execution time 1000-2000 µs): 0
DPC count (execution time 2000-4000 µs): 0
DPC count (execution time >=4000 µs): 0

REPORTED HARD PAGEFAULTS

Hard pagefaults are events that get triggered by making use of virtual memory that is not resident in RAM but backed by a memory mapped file on disk. The process of resolving the hard pagefault requires reading in the memory from disk while the process is interrupted and blocked from execution.

NOTE: some processes were hit by hard pagefaults. If these were programs producing audio, they are likely to interrupt the audio stream resulting in dropouts, clicks and pops. Check the Processes tab to see which programs were hit.

Process with highest pagefault count: cubase13.exe

Total number of hard pagefaults 87
Hard pagefault count of hardest hit process: 71
Number of processes hit: 7

PER CPU DATA

CPU 0 Interrupt cycle time (s): 0.421222
CPU 0 ISR highest execution time (µs): 14.294948
CPU 0 ISR total execution time (s): 0.004942
CPU 0 ISR count: 14607
CPU 0 DPC highest execution time (µs): 118.782240
CPU 0 DPC total execution time (s): 0.094978
CPU 0 DPC count: 22743

CPU 1 Interrupt cycle time (s): 0.139249
CPU 1 ISR highest execution time (µs): 0.0
CPU 1 ISR total execution time (s): 0.0
CPU 1 ISR count: 0
CPU 1 DPC highest execution time (µs): 0.0
CPU 1 DPC total execution time (s): 0.0
CPU 1 DPC count: 0

CPU 2 Interrupt cycle time (s): 0.156223
CPU 2 ISR highest execution time (µs): 0.0
CPU 2 ISR total execution time (s): 0.0
CPU 2 ISR count: 0
CPU 2 DPC highest execution time (µs): 9.580797
CPU 2 DPC total execution time (s): 0.000028
CPU 2 DPC count: 9

CPU 3 Interrupt cycle time (s): 0.159481
CPU 3 ISR highest execution time (µs): 0.0
CPU 3 ISR total execution time (s): 0.0
CPU 3 ISR count: 0
CPU 3 DPC highest execution time (µs): 0.0
CPU 3 DPC total execution time (s): 0.0
CPU 3 DPC count: 0

CPU 4 Interrupt cycle time (s): 0.913106
CPU 4 ISR highest execution time (µs): 0.0
CPU 4 ISR total execution time (s): 0.0
CPU 4 ISR count: 0
CPU 4 DPC highest execution time (µs): 563.364920
CPU 4 DPC total execution time (s): 0.057650
CPU 4 DPC count: 7203

CPU 5 Interrupt cycle time (s): 0.148432
CPU 5 ISR highest execution time (µs): 0.0
CPU 5 ISR total execution time (s): 0.0
CPU 5 ISR count: 0
CPU 5 DPC highest execution time (µs): 0.0
CPU 5 DPC total execution time (s): 0.0
CPU 5 DPC count: 0

CPU 6 Interrupt cycle time (s): 0.13990
CPU 6 ISR highest execution time (µs): 0.0
CPU 6 ISR total execution time (s): 0.0
CPU 6 ISR count: 0
CPU 6 DPC highest execution time (µs): 0.0
CPU 6 DPC total execution time (s): 0.0
CPU 6 DPC count: 0

CPU 7 Interrupt cycle time (s): 0.141517
CPU 7 ISR highest execution time (µs): 0.0
CPU 7 ISR total execution time (s): 0.0
CPU 7 ISR count: 0
CPU 7 DPC highest execution time (µs): 0.0
CPU 7 DPC total execution time (s): 0.0
CPU 7 DPC count: 0

CPU 8 Interrupt cycle time (s): 0.314494
CPU 8 ISR highest execution time (µs): 0.0
CPU 8 ISR total execution time (s): 0.0
CPU 8 ISR count: 0
CPU 8 DPC highest execution time (µs): 34.394415
CPU 8 DPC total execution time (s): 0.003363
CPU 8 DPC count: 920

CPU 9 Interrupt cycle time (s): 0.145288
CPU 9 ISR highest execution time (µs): 0.0
CPU 9 ISR total execution time (s): 0.0
CPU 9 ISR count: 0
CPU 9 DPC highest execution time (µs): 0.0
CPU 9 DPC total execution time (s): 0.0
CPU 9 DPC count: 0

CPU 10 Interrupt cycle time (s): 0.160891
CPU 10 ISR highest execution time (µs): 0.0
CPU 10 ISR total execution time (s): 0.0
CPU 10 ISR count: 0
CPU 10 DPC highest execution time (µs): 15.770003
CPU 10 DPC total execution time (s): 0.000215
CPU 10 DPC count: 68

CPU 11 Interrupt cycle time (s): 0.146745
CPU 11 ISR highest execution time (µs): 0.0
CPU 11 ISR total execution time (s): 0.0
CPU 11 ISR count: 0
CPU 11 DPC highest execution time (µs): 0.0
CPU 11 DPC total execution time (s): 0.0
CPU 11 DPC count: 0

CPU 12 Interrupt cycle time (s): 0.127522
CPU 12 ISR highest execution time (µs): 0.0
CPU 12 ISR total execution time (s): 0.0
CPU 12 ISR count: 0
CPU 12 DPC highest execution time (µs): 0.0
CPU 12 DPC total execution time (s): 0.0
CPU 12 DPC count: 0

CPU 13 Interrupt cycle time (s): 0.130354
CPU 13 ISR highest execution time (µs): 0.0
CPU 13 ISR total execution time (s): 0.0
CPU 13 ISR count: 0
CPU 13 DPC highest execution time (µs): 0.0
CPU 13 DPC total execution time (s): 0.0
CPU 13 DPC count: 0

CPU 14 Interrupt cycle time (s): 0.142408
CPU 14 ISR highest execution time (µs): 0.0
CPU 14 ISR total execution time (s): 0.0
CPU 14 ISR count: 0
CPU 14 DPC highest execution time (µs): 0.0
CPU 14 DPC total execution time (s): 0.0
CPU 14 DPC count: 0

CPU 15 Interrupt cycle time (s): 0.142052
CPU 15 ISR highest execution time (µs): 0.0
CPU 15 ISR total execution time (s): 0.0
CPU 15 ISR count: 0
CPU 15 DPC highest execution time (µs): 0.0
CPU 15 DPC total execution time (s): 0.0
CPU 15 DPC count: 0

CPU 16 Interrupt cycle time (s): 0.219015
CPU 16 ISR highest execution time (µs): 0.0
CPU 16 ISR total execution time (s): 0.0
CPU 16 ISR count: 0
CPU 16 DPC highest execution time (µs): 23.665202
CPU 16 DPC total execution time (s): 0.000334
CPU 16 DPC count: 52

CPU 17 Interrupt cycle time (s): 0.182032
CPU 17 ISR highest execution time (µs): 0.0
CPU 17 ISR total execution time (s): 0.0
CPU 17 ISR count: 0
CPU 17 DPC highest execution time (µs): 77.655162
CPU 17 DPC total execution time (s): 0.000446
CPU 17 DPC count: 30

CPU 18 Interrupt cycle time (s): 0.194408
CPU 18 ISR highest execution time (µs): 0.0
CPU 18 ISR total execution time (s): 0.0
CPU 18 ISR count: 0
CPU 18 DPC highest execution time (µs): 64.566363
CPU 18 DPC total execution time (s): 0.000689
CPU 18 DPC count: 97

CPU 19 Interrupt cycle time (s): 0.197665
CPU 19 ISR highest execution time (µs): 0.0
CPU 19 ISR total execution time (s): 0.0
CPU 19 ISR count: 0
CPU 19 DPC highest execution time (µs): 33.097898
CPU 19 DPC total execution time (s): 0.000210
CPU 19 DPC count: 28

CPU 20 Interrupt cycle time (s): 0.754574
CPU 20 ISR highest execution time (µs): 0.0
CPU 20 ISR total execution time (s): 0.0
CPU 20 ISR count: 0
CPU 20 DPC highest execution time (µs): 147.432382
CPU 20 DPC total execution time (s): 0.001781
CPU 20 DPC count: 173

CPU 21 Interrupt cycle time (s): 0.181320
CPU 21 ISR highest execution time (µs): 0.0
CPU 21 ISR total execution time (s): 0.0
CPU 21 ISR count: 0
CPU 21 DPC highest execution time (µs): 28.144336
CPU 21 DPC total execution time (s): 0.000095
CPU 21 DPC count: 18

CPU 22 Interrupt cycle time (s): 0.205221
CPU 22 ISR highest execution time (µs): 0.0
CPU 22 ISR total execution time (s): 0.0
CPU 22 ISR count: 0
CPU 22 DPC highest execution time (µs): 77.533417
CPU 22 DPC total execution time (s): 0.000537
CPU 22 DPC count: 51

CPU 23 Interrupt cycle time (s): 0.184073
CPU 23 ISR highest execution time (µs): 0.0
CPU 23 ISR total execution time (s): 0.0
CPU 23 ISR count: 0
CPU 23 DPC highest execution time (µs): 28.629746
CPU 23 DPC total execution time (s): 0.000238
CPU 23 DPC count: 25

Tony_ST · November 13, 2023, 9:12pm

Hello, try turning on Steinberg Audio Power Scheme and see if there is any difference ? And try increasing the latency to about 10 ms.

arkdzo · November 14, 2023, 2:44pm

I solved my problem.

Method #1

Fix your registry problems, invalid links with some software, for example Ccleaner
Reboot PC
Close all unnecessary programs from the tray, like messenger (WhatsApp, Viber, Telegram etc), auto-updaters and game launchers (Steam, UPlay etc)
Close all opened browsers (Chrome, Opera, Firefox)
Activate the Steinberg Audio Power Scheme (Studio - Studio Setup - Audio System)

image726×806 33.6 KB
Check that it is set to Steinberg Audio Power [Active] Control Panel\All Control Panel Items\Power Options\Edit Plan Settings

Method #2

Download Audiogridder server (1.2.0) (Free)
Download Audiogridder VST plugin (1.2.0) (Free)
Run Audiogridder server
Go to the settings, and set the Screen Capture Mode: Disabled (Local Mode). Press the Save button.

Start the Cubase.
Add a new instrument track - AudioGridderInst

Press + button and add your instrument

image672×607 45 KB
Now you will not hear any dropouts

Irene_Dimitriadou · November 16, 2023, 5:14am

Thank you for this. I am experiencing dropouts and clicks from the very first moment I used Cubase 13.
I heard a click on pressing play on the spacebar, then another one as I pressed it again to stop.
And then numerus dropouts and clicks when playing audio wrapped or quantized parts.
Never had such a behavior in Cubase 12.

I will try both solutions today, starting from #1 and then move to #2.
If none succeed, I will move back to 12 till an update comes out. Happened with 12 as well and had to get back to 11 for a while.

My thoughts though are, that no matter the good will and faith most of us have for Steinberg, it is totally unacceptable to face such issues with the release of an update and have paid 100€ for it.

New features mean nothing if you can’t use the software…

Glenans · September 12, 2024, 8:27pm

First, thank you - it’s worked but…

When I ran the Audiogridder server there was no page like you’ve shown above, it just goes straight into action with a little box going through all my plugins. So no Settings page or any other page and it goes through the process over and over again and eventually as I couldn’t stop it I did a hard reboot. When I rebooted and loaded Cubase the same small screen appeared but this time just for a moment and Cubase loaded normally. Seems to have done the job. Here’s hoping.

Well I quickly found I still had the same problem. When I next booted Cubase the Audiogrid server hadn’t connected and told me my server was blocked. So I quit Cubase and ran Audiogrid server again but it just went through all my plugins each time starting again from the beginning so a hard reboot and a re-install but that didn’t solve the problem.

Just to be clear - there were two problems, pops and crackles, drop outs and a peculiar jerky movement of the tracks on the screen.

I found by elimination (muting all the tracks and then unmuting one by one until I got the culprit) that there was a problem with my Bolt plugin. Bolt have recently gone over to I-Lok. If I muted Bolt the problem went away. To be sure I soloed Bolt, it wasn’t playing. So muting it stopped the problem but why wasn’t it playing unmuted? I checked and on the I-Lok it was showing as activated in the cloud but not on my desktop. I activated it on my desktop, loaded Cubase and my track and the problem has gone.