Hello Pioneer team,
I'm using a DDJ-SX3 with Serato installed on a Dell XPS 15 Laptop (Intel Core i7 2.80 GHz, 16 GB RAM).
I'm having recurrent trimming and audio dropouts (the yellow and red lights shows on serato's upper right hand corner).
It seems more and more that in many cases this happens exactly when I tap a button or move a fader. Mostly the left Cue button, and Channel 3's fader (maybe also the EQs).
It feels like there's a "bad contact" issue.
FYI, Serato shows 15%-25% on the CPU Meter. No More.
I'm running only Serato. All other programs are closed. Computer is on Airplane Mode, so no WiFi or Bluetooth. Power source connected.
Please let me know how to address this problem.
Best,
Omri
Publicação fechada para comentários.
Chances are you have something else causing issues in your system - try running the Latency Monitor tool with Serato DJ open and playing tracks for about 10 minutes, then generate a report and paste it in a reply.
I ran the Latency Monitor for about two hours while mixing.
Here is the report:
_________________________________________________________________________________________________________
CONCLUSION
_________________________________________________________________________________________________________
Your system appears to be having trouble handling real-time audio and other tasks. You are likely to experience buffer underruns appearing as drop outs, clicks or pops. One or more DPC routines that belong to a driver running in your system appear to be executing for too long. 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 1:55:05 (h:mm:ss) on all processors.
_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name: DESKTOP-42GANQ4
OS version: Windows 10 , 10.0, version 1903, build: 18362 (x64)
Hardware: XPS 15 9560, Dell Inc., 0YH90J
CPU: GenuineIntel Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz
Logical processors: 8
Processor groups: 1
RAM: 16235 MB total
_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed: 2808 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): 43079,60
Average measured interrupt to process latency (µs): 9,611139
Highest measured interrupt to DPC latency (µs): 41879,90
Average measured interrupt to DPC latency (µs): 3,537202
_________________________________________________________________________________________________________
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): 273,325499
Driver with highest ISR routine execution time: ACPI.sys - Pilote ACPI pour NT, Microsoft Corporation
Highest reported total ISR routine time (%): 0,032289
Driver with highest ISR total time: Wdf01000.sys - Runtime de l’infrastructure de pilotes en mode noyau, Microsoft Corporation
Total time spent in ISRs (%) 0,033838
ISR count (execution time <250 µs): 6097882
ISR count (execution time 250-500 µs): 0
ISR count (execution time 500-999 µs): 5
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): 43854,641738
Driver with highest DPC routine execution time: dddriver64Dcsa.sys - Dell Diags Universal Device Driver, Dell Inc.
Highest reported total DPC routine time (%): 0,717704
Driver with highest DPC total execution time: Wdf01000.sys - Runtime de l’infrastructure de pilotes en mode noyau, Microsoft Corporation
Total time spent in DPCs (%) 0,786964
DPC count (execution time <250 µs): 19998767
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-999 µs): 5193
DPC count (execution time 1000-1999 µs): 40
DPC count (execution time 2000-3999 µs): 12
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: nvidia web helper.exe
Total number of hard pagefaults 959
Hard pagefault count of hardest hit process: 261
Number of processes hit: 33
_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 847,073597
CPU 0 ISR highest execution time (µs): 151,891382
CPU 0 ISR total execution time (s): 17,880099
CPU 0 ISR count: 6081835
CPU 0 DPC highest execution time (µs): 43854,641738
CPU 0 DPC total execution time (s): 420,678555
CPU 0 DPC count: 19462962
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 314,743847
CPU 1 ISR highest execution time (µs): 273,325499
CPU 1 ISR total execution time (s): 0,596025
CPU 1 ISR count: 12627
CPU 1 DPC highest execution time (µs): 42465,793803
CPU 1 DPC total execution time (s): 11,583029
CPU 1 DPC count: 354872
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 253,522267
CPU 2 ISR highest execution time (µs): 256,172009
CPU 2 ISR total execution time (s): 0,216194
CPU 2 ISR count: 3425
CPU 2 DPC highest execution time (µs): 868,918803
CPU 2 DPC total execution time (s): 1,445196
CPU 2 DPC count: 48480
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 215,081305
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): 372,701923
CPU 3 DPC total execution time (s): 0,105444
CPU 3 DPC count: 17177
_________________________________________________________________________________________________________
CPU 4 Interrupt cycle time (s): 182,603397
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): 436,358262
CPU 4 DPC total execution time (s): 0,171478
CPU 4 DPC count: 21584
_________________________________________________________________________________________________________
CPU 5 Interrupt cycle time (s): 191,799254
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): 403,481125
CPU 5 DPC total execution time (s): 0,380071
CPU 5 DPC count: 61569
_________________________________________________________________________________________________________
CPU 6 Interrupt cycle time (s): 175,600211
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): 547,766382
CPU 6 DPC total execution time (s): 0,301506
CPU 6 DPC count: 30396
_________________________________________________________________________________________________________
CPU 7 Interrupt cycle time (s): 165,684690
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): 257,339031
CPU 7 DPC total execution time (s): 0,064641
CPU 7 DPC count: 6990
_________________________________________________________________________________________________________