Leistungsspitzen bei Cubase, die nicht sein dürften

Hallo liebe Communitiy! Ich bin neu hier und habe gleich mal ein ernstes Problem! :-/

Ich habe mir einen neuen Laptop gekauft um richtig gut, ohne Probleme mit Cubase arbeiten zu können. Dabei benutze ich auch viele Virtuelle Instrumente, wie NI Studio Drumm, Scarabee Bass, Session Horns Pro, einige EastWest Instrumente (Hollywood Strings,…)

Mein Laptop hat folgende Konfiguration:
SCHENKER W704 mobile Workstation 43,9cm (17.3")
. 43,9cm (17.3") Full-HD (1920*1080) Non-Glare
. AMD Radeon R9 M290X 4096MB GDDR5
. Intel Core i7-4910MQ - 2,90 - 3,90GHz 8MB 47W
. 32GB (4x8192) SO-DIMM DDR3 RAM 1600MHz Crucial
. 1000GB SATA-III SSD Samsung 840 EVO Series (MZ-7TE1T0BW)
. 1000GB SATA-III 7200U/Min HGST Travelstar 7K1000 (HTS721010A9E630)
. Blu-ray Brenner (Blu-Ray Lesen- Schreiben / DVD Multinorm) -ohne Softw.
. Intel Wireless-AC 3160 (inkl. Bluetooth)
. Microsoft Windows 8.1 Pro 64 Bit
. Cubase Artist 7.5

Das Problem:

Trotz des eingeltich doch recht üppigen Prozessors, SSD Platte und des großen Arbeitsspeichers kommt es auch schon bei kleineren Projekten zu Leistungsspitzen, die zu Ruckeln und Knacksern führen (mein alter PC konnte das besser ahndeln udn der war deutlich schlechter aufgestellt…)
Ich habe auch bereits Latency Mon und DPC Latency Checker ausgeführt.
Ergebnisse:
Latency Mon:
Der Balken der Highest reported hard pagefault resolution time ist am Anschlag.
Nach Abschluss heißt es: “Your system seems to have difficulty handling real-time audio and other tasks. You may experience drop outs, clicks or pops due to buffer underruns. One problem may be related to power management, disable CPU throttling settings in Control Panel and BIOS setup. Check for BIOS updates.”
Unter Drivers kann man sehen, dass “Wdf0 1000.sys” die höchste Execution von 0,274591 ms hat und bei Total Execution steht 21835,184740.

Ist das normal? Habe schon herausgefunden, dass “Wdf0 1000.sys” eine Windows Datei ist und der Schädling wohl eher ein Treiber ist, der ständig darauf zugreift.


Hier noch das “Stats”-Ergebnis:


CONCLUSION


Your system seems to have difficulty handling real-time audio and other tasks. You may experience drop outs, clicks or pops due to buffer underruns. One problem may be related to power management, disable CPU throttling settings in Control Panel and BIOS setup. Check for BIOS updates.
LatencyMon has been analyzing your system for 0:04:43 (h:mm:ss) on all processors.

\


SYSTEM INFORMATION


Computer name: TSASSE
OS version: Windows 8 , 6.2, build: 9200 (x64)
Hardware: P17SM-A , Notebook
CPU: GenuineIntel Intel® Core™ i7-4910MQ CPU @ 2.90GHz
Logical processors: 8
Processor groups: 1
RAM: 32684 MB total

\


CPU SPEED


Reported CPU speed: 2893,0 MHz
Measured CPU speed: 3711,0 MHz (approx.)

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): 1261,375919
Average measured interrupt to process latency (µs): 5,065816

Highest measured interrupt to DPC latency (µs): 1259,606312
Average measured interrupt to DPC latency (µs): 1,237407

\


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): 69,138265
Driver with highest ISR routine execution time: Wdf01000.sys - Kernelmodustreiber-Frameworklaufzeit, Microsoft Corporation

Highest reported total ISR routine time (%): 0,165541
Driver with highest ISR total time: Wdf01000.sys - Kernelmodustreiber-Frameworklaufzeit, Microsoft Corporation

Total time spent in ISRs (%) 0,171635

ISR count (execution time <250 µs): 586730
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): 274,591082
Driver with highest DPC routine execution time: Wdf01000.sys - Kernelmodustreiber-Frameworklaufzeit, Microsoft Corporation

Highest reported total DPC routine time (%): 0,798453
Driver with highest DPC total execution time: Wdf01000.sys - Kernelmodustreiber-Frameworklaufzeit, Microsoft Corporation

Total time spent in DPCs (%) 0,986331

DPC count (execution time <250 µs): 2009543
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-999 µs): 2
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: cubase7.5.exe

Total number of hard pagefaults 1041
Hard pagefault count of hardest hit process: 945
Highest hard pagefault resolution time (µs): 84012,435880
Total time spent in hard pagefaults (%): 0,026548
Number of processes hit: 6

\


PER CPU DATA


CPU 0 Interrupt cycle time (s): 8,498049
CPU 0 ISR highest execution time (µs): 53,623228
CPU 0 ISR total execution time (s): 0,428795
CPU 0 ISR count: 81733
CPU 0 DPC highest execution time (µs): 274,591082
CPU 0 DPC total execution time (s): 4,121353
CPU 0 DPC count: 827175


CPU 1 Interrupt cycle time (s): 9,601504
CPU 1 ISR highest execution time (µs): 50,920498
CPU 1 ISR total execution time (s): 1,002732
CPU 1 ISR count: 142278
CPU 1 DPC highest execution time (µs): 194,323194
CPU 1 DPC total execution time (s): 4,437455
CPU 1 DPC count: 185645


CPU 2 Interrupt cycle time (s): 10,436642
CPU 2 ISR highest execution time (µs): 54,358106
CPU 2 ISR total execution time (s): 0,204880
CPU 2 ISR count: 41644
CPU 2 DPC highest execution time (µs): 186,340477
CPU 2 DPC total execution time (s): 3,645498
CPU 2 DPC count: 569491


CPU 3 Interrupt cycle time (s): 15,995489
CPU 3 ISR highest execution time (µs): 69,138265
CPU 3 ISR total execution time (s): 1,900805
CPU 3 ISR count: 258192
CPU 3 DPC highest execution time (µs): 197,169029
CPU 3 DPC total execution time (s): 7,623464
CPU 3 DPC count: 331317


CPU 4 Interrupt cycle time (s): 3,233408
CPU 4 ISR highest execution time (µs): 57,765296
CPU 4 ISR total execution time (s): 0,083203
CPU 4 ISR count: 14599
CPU 4 DPC highest execution time (µs): 203,209471
CPU 4 DPC total execution time (s): 0,587535
CPU 4 DPC count: 22358


CPU 5 Interrupt cycle time (s): 4,955346
CPU 5 ISR highest execution time (µs): 51,106810
CPU 5 ISR total execution time (s): 0,103394
CPU 5 ISR count: 19246
CPU 5 DPC highest execution time (µs): 210,248185
CPU 5 DPC total execution time (s): 0,789293
CPU 5 DPC count: 28738


CPU 6 Interrupt cycle time (s): 3,040349
CPU 6 ISR highest execution time (µs): 59,205669
CPU 6 ISR total execution time (s): 0,044532
CPU 6 ISR count: 8758
CPU 6 DPC highest execution time (µs): 185,770480
CPU 6 DPC total execution time (s): 0,369380
CPU 6 DPC count: 15422


CPU 7 Interrupt cycle time (s): 4,930077
CPU 7 ISR highest execution time (µs): 41,062219
CPU 7 ISR total execution time (s): 0,118126
CPU 7 ISR count: 20280
CPU 7 DPC highest execution time (µs): 226,906326
CPU 7 DPC total execution time (s): 0,760263
CPU 7 DPC count: 29399




DPC Latency Checker:
Zeigt permanent eine Latenz von um die 1 ms an mit einer Spitze von 2,677ms und dem Ergebnis:
“Some device drivers on this machine behave bad and will probably cause drop-outs in real-time audio and/or video streams. To isolate the misbehaving driver use Device Manager and disable/re-enable various devices, one at a time. Try network and W-LAN adapters, modems, internal sound devices, USB host controllers, etc.”

Das ist doch nicht normal für einen Computer der oben genannten Konfiguration, oder?
Ich habe auch schon den Modus für optimale Audioleistung von Steinberg aktiviert.
Übrigens diese Leistungsspitzen treten auch auf, wenn ich gerade nichta uf Play gedrückt habe!

Wäre Euch wirklich enorm für Eure Hilfe dankbar!!!
Viele Grüße!
Tobi
LatencyMon3.jpg
LatencyMon2.jpg
LatencyMon1.jpg

hi jack,

hast ja vielleicht ein paar freie tage zum lesen… :wink:

http://www.steinberg.net/forums/viewtopic.php?f=234&t=71871

mw

Hallo Jack,

hast Du das Problem inzwischen gelöst? Falls nein: ich bin hellhörig geworden bei der Erwähnung von Eastwest-Instrumenten. Nicht wenige User haben das Problem, dass unter Cubase die PLAY-Version 4.2 nicht vernünftig läuft und Leistungsspitzen, Knackser etc. erzeugt, die nicht durch eine zu schwache Hardware verursacht sein können. Es gibt dazu auch eine ausführliche Debatte im englsichen Cubase-Forum.
Vielleicht kommst Du so weiter.
Gruß - Clemens

Hallo Clemens!

Ach vielleicht liegt es tatsächlich an den East West Instrumenten! Das prüfe ich heute nochmal! Danke für den Tipp!! :slight_smile: