Servus,
ich nutze Cubase Artist 10.5. Aktuell kriege ich bei fast jedem Projekt die Fehlermeldung “Audioaussetzer ermittelt”. Das passiert sogar schon wenn ich nur zwei Spuren recorde.
Ich habe 64gb Ram, den neuesten Intel 9 Prozessor(Intel Core i9 9900K 8x 3.60GHz) und auch ansonsten ist das ne sehr flotte Kiste.
Hab keine Ahnung woran das liegen könnte, vll kann mir jemand weiterhelfen? Wäre darüber sehr dankbar! Danke:)
Welches Audiointerface?
Welcher ASIO-Treiber?
Welche Buffer Size (= Latenz) hast Du für den ASIO-Treiber eingestellt?
Was machst du denn genau, wenn die Fehlermeldung aufpoppt?
ich habe das Focusrite Scarlett 18I8 3 Generation und auch dessen ASIO-Treiber.
Wenn die Fehlermeldung aufploppt,ist die Spur (Gesang/E-Gitarre oder Native Instruments) eh schon versaut sodass ich die Meldung dann wegklicke
Also Buffersize ist 480, Sample Rate 44100.
Focusrite USB ist der Treiber.
Aus Deinen Angaben kann ich erstmal nichts Auffälliges entnehmen, so dass eine Ferndiagnose schwer fällt.
Ich persönlich bin leider auch kein IT-Fachmann 
Sind irgendwelche Plugins mit im Spiel, insbesondere solche, die nicht von Steinberg stammen?
Schau Dir vielleicht mal diesen Artikel an:
Im englischen Forum finden sich auch einige Threads zum Thema “dropouts”, z.B.
Nur Native Instruments. Aber die Aussetzer sind auch schon bei normalen Gesangs- und Gitarrenspuren. Völlig unverständlich 
Trotzdem danke für s Antworten!
Kannst du etwas mehr zum Computer sagen?
Verwendest du USB3?
Ist der Rechner neu ? Ist es auf diesem Rechner schonmal einwandfrei gelaufen ?
Ggf. mal mit dem Tool Latencymon den Rechner checken. Manchmal ist es ein anderer Treiber, z.B. Netzwerkkarte, der so etwas verursacht, weil er die CPU ausbremst.
Edit: Steht ja auch im oben verlinkten Steinberg Artikel …
Hi, also der Rechner ist relativ neu (3 Monate) die ersten Wochen lief eigentlich alles problemlos. Sowohl Native Instruments als auch die Aufnahmen. Kam erst in den letzten 14 Tagen vermehrt auf.
Ich habe mir den PC zusammenstellen lassen und von einem IT-Fachmann zusammenbauen lassen.
USB 3.0. habe ich beim Cubase-Stick.
Zusammensetzung:
https://www.mindfactory.de/product_info.php/Intel-Core-i9-10900K-10x-3-70Ghz-So-1200-Tray_1361856.html
MSI MAG B550M Mortar WIFI MSI MAG B550M Mortar WIFI | Preisvergleich Geizhals Deutschland 147€ (inkl. WLAN & Bluetooth)
Crucial BL2K32G32C16U4B Crucial Ballistix schwarz DIMM Kit 64GB, DDR4-3200 | Preisvergleich Geizhals Deutschland 254€
Thermalright Macho 120 Rev. B Thermalright Macho 120 Rev. B ab € 53,90 (2024) | Preisvergleich Geizhals Deutschland 44€
Gigabyte GTX 1650 Super Windforce OC 4G GIGABYTE GeForce GTX 1650 SUPER Windforce OC 4G | Preisvergleich Geizhals Deutschland 167€
PNY XLR8 CS3030 2TB PNY XLR8 CS3030 2TB ab € 149,90 (2024) | Preisvergleich Geizhals Deutschland 278€
Seasonic Focus GX 550W Seasonic Focus GX 550W ATX 2.4 ab € 118,22 (2024) | Preisvergleich Geizhals Deutschland 84€
Antec P5 Antec P5 ab € 69,90 (2024) | Preisvergleich Geizhals Deutschland 51
Wo steckt denn dein Audio Interface drin? USB3? Probier mal einen USB2.0 Port falls du hast
Tönt für mich so als wär der Asio-Guard deaktiviert. Den aktivieren und wenns nicht hilft, Audiotreiber de- und wieder installieren. Cubase-Einstellungen zurücksetzen.
Hast du das auch in einem neuen, leeren Projekt ohne Plugins wenn du nur 1 Monospur aufnimmst?
Hab seit ähnlich langer Zeit genau das gleiche Problem! Passiert völlig willkürlich selbst bei einfachen Recordings in Monospuren. Vorher lief es immer einwandfrei. Habe nichts geändert seitdem. Ich kann es mir nicht erklären.
Der Asio-Guard war/ist leider aktiviert. Auch eine Neu-Installation des Focusrite´s hat nix gebracht. Es ist wie verhext…
Hallo Machinemadegod,
installier doch mal Latencymon (kostenfrei) lass es mal für ein paar Minuten lauf und schau Dir mal die Ergebnisse an oder stell sie hier ins Forum.
Kann sein, dass Dir die Grafikkarte oder das Netzwerk-Interface da rein spielen.
Vielleicht hilft das den Grund für das Problem näher zu kommen. Alles andere ist nur ein stochern im Nebel.
Solange der ASIO-Guard nicht aktiviert ist, sehe ich nicht ein, warum weiter nach Fehler gesucht werden sollte. Ist der nicht aktivierbar?
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:01:24 (h:mm:ss) on all processors.
\
SYSTEM INFORMATION
Computer name: DESKTOP-C6JI5JP
OS version: Windows 10 , 10.0, build: 18363 (x64)
Hardware: MS-7C81, Micro-Star International Co., Ltd., MAG B460 TOMAHAWK (MS-7C81)
CPU: GenuineIntel Intel(R) Core™ i9-10900K CPU @ 3.70GHz
Logical processors: 20
Processor groups: 1
RAM: 65471 MB total
\
CPU SPEED
Reported CPU speed: 3696 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.
WARNING: the CPU speed that was measured is only a fraction of the CPU speed reported. Your CPUs may be throttled back due to variable speed settings and thermal issues. It is suggested that you run a utility which reports your actual CPU frequency and temperature.
\
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): 84,10
Average measured interrupt to process latency (µs): 3,135798
Highest measured interrupt to DPC latency (µs): 82,20
Average measured interrupt to DPC latency (µs): 1,035322
\
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): 195,705628
Driver with highest ISR routine execution time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation
Highest reported total ISR routine time (%): 0,011214
Driver with highest ISR total time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation
Total time spent in ISRs (%) 0,012186
ISR count (execution time <250 µs): 11076
ISR count (execution time 250-500 µs): 0
ISR count (execution time 500-999 µs): 0
ISR count (execution time 1000-1999 µs): 0
ISR count (execution time 2000-3999 µ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): 259,153680
Driver with highest DPC routine execution time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation
Highest reported total DPC routine time (%): 0,004609
Driver with highest DPC total execution time: rspLLL64.sys - Resplendence Latency Monitoring and Auxiliary Kernel Library, Resplendence Software Projects Sp.
Total time spent in DPCs (%) 0,010941
DPC count (execution time <250 µs): 125325
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-999 µs): 1
DPC count (execution time 1000-1999 µs): 0
DPC count (execution time 2000-3999 µ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: ksde.exe
Total number of hard pagefaults 3009
Hard pagefault count of hardest hit process: 2975
Number of processes hit: 9
\
PER CPU DATA
CPU 0 Interrupt cycle time (s): 2,471547
CPU 0 ISR highest execution time (µs): 0,0
CPU 0 ISR total execution time (s): 0,0
CPU 0 ISR count: 0
CPU 0 DPC highest execution time (µs): 123,143939
CPU 0 DPC total execution time (s): 0,083616
CPU 0 DPC count: 100699
CPU 1 Interrupt cycle time (s): 1,022701
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): 136,369048
CPU 1 DPC total execution time (s): 0,004954
CPU 1 DPC count: 956
CPU 2 Interrupt cycle time (s): 2,084094
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): 132,902056
CPU 2 DPC total execution time (s): 0,019035
CPU 2 DPC count: 7837
CPU 3 Interrupt cycle time (s): 2,131213
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): 100,768398
CPU 3 DPC total execution time (s): 0,000276
CPU 3 DPC count: 28
CPU 4 Interrupt cycle time (s): 1,595680
CPU 4 ISR highest execution time (µs): 162,116342
CPU 4 ISR total execution time (s): 0,007445
CPU 4 ISR count: 215
CPU 4 DPC highest execution time (µs): 89,726732
CPU 4 DPC total execution time (s): 0,003332
CPU 4 DPC count: 701
CPU 5 Interrupt cycle time (s): 2,363808
CPU 5 ISR highest execution time (µs): 195,705628
CPU 5 ISR total execution time (s): 0,181060
CPU 5 ISR count: 2856
CPU 5 DPC highest execution time (µs): 259,153680
CPU 5 DPC total execution time (s): 0,057709
CPU 5 DPC count: 6280
CPU 6 Interrupt cycle time (s): 1,908425
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): 74,926948
CPU 6 DPC total execution time (s): 0,000970
CPU 6 DPC count: 319
CPU 7 Interrupt cycle time (s): 1,989620
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): 192,673160
CPU 7 DPC total execution time (s): 0,000613
CPU 7 DPC count: 38
CPU 8 Interrupt cycle time (s): 2,038995
CPU 8 ISR highest execution time (µs): 11,913961
CPU 8 ISR total execution time (s): 0,000168
CPU 8 ISR count: 68
CPU 8 DPC highest execution time (µs): 40,162338
CPU 8 DPC total execution time (s): 0,000182
CPU 8 DPC count: 76
CPU 9 Interrupt cycle time (s): 2,178407
CPU 9 ISR highest execution time (µs): 121,011364
CPU 9 ISR total execution time (s): 0,015966
CPU 9 ISR count: 7834
CPU 9 DPC highest execution time (µs): 153,834957
CPU 9 DPC total execution time (s): 0,005729
CPU 9 DPC count: 7864
CPU 10 Interrupt cycle time (s): 2,045812
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): 94,304654
CPU 10 DPC total execution time (s): 0,000129
CPU 10 DPC count: 8
CPU 11 Interrupt cycle time (s): 2,103241
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): 1,571429
CPU 11 DPC total execution time (s): 0,000003
CPU 11 DPC count: 2
CPU 12 Interrupt cycle time (s): 2,056738
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): 76,223485
CPU 12 DPC total execution time (s): 0,000231
CPU 12 DPC count: 20
CPU 13 Interrupt cycle time (s): 2,069557
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): 96,408009
CPU 13 DPC total execution time (s): 0,000268
CPU 13 DPC count: 29
CPU 14 Interrupt cycle time (s): 1,846699
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): 77,060065
CPU 14 DPC total execution time (s): 0,001453
CPU 14 DPC count: 125
CPU 15 Interrupt cycle time (s): 1,812112
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): 32,612013
CPU 15 DPC total execution time (s): 0,000095
CPU 15 DPC count: 31
CPU 16 Interrupt cycle time (s): 1,932834
CPU 16 ISR highest execution time (µs): 0,934524
CPU 16 ISR total execution time (s): 0,000002
CPU 16 ISR count: 2
CPU 16 DPC highest execution time (µs): 77,313312
CPU 16 DPC total execution time (s): 0,000802
CPU 16 DPC count: 87
CPU 17 Interrupt cycle time (s): 1,907148
CPU 17 ISR highest execution time (µs): 7,392857
CPU 17 ISR total execution time (s): 0,000205
CPU 17 ISR count: 101
CPU 17 DPC highest execution time (µs): 113,031926
CPU 17 DPC total execution time (s): 0,00360
CPU 17 DPC count: 141
CPU 18 Interrupt cycle time (s): 1,929022
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): 112,978355
CPU 18 DPC total execution time (s): 0,000635
CPU 18 DPC count: 53
CPU 19 Interrupt cycle time (s): 1,898833
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): 47,957792
CPU 19 DPC total execution time (s): 0,000281
CPU 19 DPC count: 32
ich frag einfach nochmal… USB2 oder USB3?
probier das Interface mal an einem USB2 Port (neben dem PS/2)
WARNING: the CPU speed that was measured is only a fraction of the CPU speed reported. Your CPUs may be throttled back due to variable speed settings and thermal issues. It is suggested that you run a utility which reports your actual CPU frequency and temperature.
Probier Mal, die Prozessor-Taktung festzusetzen, damit bei variabler Belastung immer gleiche Leistung vorhanden ist.
Hi Machinemadegod,
schalte doch mal zur Probe Deinen “Kaspersky Antivirus” aus.
Vorher den Hinweis von JD zur Taktung beachten.
Bei meinem 9700K habe ich probehalber wieder auf “dynamisch” (mit Boost) eingestellt, aber keine Probleme gehabt.
Und auch den Hinweis von st10ss ausprobieren: Anschluss des Focusrite an USB2
Aber warum ermittelt denn das LatencyMon Folgendes ?!
OS version: Windows 10 , 10.0, build: 18363 (x64) => ist OK, 19H2 aka 1909
CPU: GenuineIntel Intel(R) Core™ i9-10900K CPU @ 3.70GHz => ?! => hat er doch einen 9900K mit 8 cores + HT
Logical processors: 20 => s.o. , dürften ja nur 16 sein
Naja, aber sonst ganz brauchbar das Tool.
VG, Paul