Have a feature request or suggestion? Post your idea here!

Publication

4 abonnés S’abonner
0
Avatar

Crackling noises with DDJ-1000, please help

A few weeks ago I got my ddj-1000, upgrading from the 400 and since the first moment I tried it I've been getting a lot of popping and crackling noises on RB5. They appear on playback and recording too. Most of the time they happen when I press buttons or move knobs, pretty much anything can trigger them, sometimes I don't even move anything and it happens. So I googled and found a plethora of fixes like the 99% fix, disabling Intel's turboboost, etc. And it got a bit better but still nowhere near acceptable (tbh the only acceptable thing would be absolutely 0 crackling but at this point having a few every couple hours would be fine by me).

So I formated my laptop, clean W10 install and just downloaded RB5, tried and noises are still happening, bummed, so then I did the 99% fix while disabling turboboost at the same time, updated my audio and NVIDIA drivers, updated the bios and they're still there. I tried another version of RB5, still same problem. You get my point, so I'll just list the things I've tried and some potential fixes that I haven't tried yet.

Stuff I tried: 99% fix, disabling turboboost, turning off wi-fi, closing all apps, the thing where you change the values of some windows stuff (I'll link it at the end), updating all drivers, and maybe some more stuff I don't quite remember at the moment.

Stuff I haven't tried: Turning off network devices (a bit confused about that one, wil, post a screenshot so I can do it without messing something up), disabling my nvidia gpu while using RB5, disabling hyperthreading.

My laptop is relatively new, bought it around last year's september, HP 16-a0001la, 10th gen I5 processor, 8gb ram, 500gb SSD, etc. So it shouldn't have any trouble running pretty much anything. I also ran LatencyMon and it turns out the system issues with latency, but it all points out to the wdf01000.sys driver, which doesn't seem to have a clear fix. Also some comments on hp forums indicate that this might be a common problem with hp laptops, but I think it's more on the windows side. Maybe windows is just that awful at audio and I'll just have to get a Mac, which is really far from ideal since I don't use my laptop only for music. Anyways I'll include the LatencyMon text report on a comment so it doesn't clutter the post more.

https://imgur.com/a/a3eDkrd latencymon screenshots + network devices thing

 

ps: I'll note that I got a few crackles here and there with the ddj-400 the last few months I had it, but they were very sporadic and it didn't alarm me at all compared to this, but it might be indicative of an issue with windows

Sebastian S. Répondu

Cette publication n’accepte pas de commentaire.

3 commentaires

0
Avatar

_________________________________________________________________________________________________________
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. Also one or more ISR 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 0:05:26 (h:mm:ss) on all processors.


_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name: LAPTOP-90FTM3N1
OS version: Windows 10, 10.0, version 1903, build: 18362 (x64)
Hardware: HP Pavilion Gaming Laptop 16-a0xxx, HP
CPU: GenuineIntel Intel(R) Core(TM) i5-10300H CPU @ 2.50GHz
Logical processors: 8
Processor groups: 1
RAM: 7963 MB total


_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed: 2496 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): 711,80
Average measured interrupt to process latency (µs): 3,556003

Highest measured interrupt to DPC latency (µs): 709,70
Average measured interrupt to DPC latency (µs): 1,76840


_________________________________________________________________________________________________________
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): 3424,426282
Driver with highest ISR routine execution time: Wdf01000.sys - Motor en tiempo de ejecución del marco de controlador en modo kernel, Microsoft Corporation

Highest reported total ISR routine time (%): 0,163996
Driver with highest ISR total time: Wdf01000.sys - Motor en tiempo de ejecución del marco de controlador en modo kernel, Microsoft Corporation

Total time spent in ISRs (%) 0,167826

ISR count (execution time <250 µs): 467003
ISR count (execution time 250-500 µs): 0
ISR count (execution time 500-1000 µs): 38
ISR count (execution time 1000-2000 µs): 0
ISR count (execution time 2000-4000 µs): 39
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): 3483,840545
Driver with highest DPC routine execution time: Wdf01000.sys - Motor en tiempo de ejecución del marco de controlador en modo kernel, Microsoft Corporation

Highest reported total DPC routine time (%): 0,908462
Driver with highest DPC total execution time: Wdf01000.sys - Motor en tiempo de ejecución del marco de controlador en modo kernel, Microsoft Corporation

Total time spent in DPCs (%) 0,966764

DPC count (execution time <250 µs): 1888434
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-10000 µs): 550
DPC count (execution time 1000-2000 µs): 0
DPC count (execution time 2000-4000 µs): 2
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: chrome.exe

Total number of hard pagefaults 3154
Hard pagefault count of hardest hit process: 860
Number of processes hit: 73


_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 32,794020
CPU 0 ISR highest execution time (µs): 3424,426282
CPU 0 ISR total execution time (s): 4,325253
CPU 0 ISR count: 429320
CPU 0 DPC highest execution time (µs): 3483,840545
CPU 0 DPC total execution time (s): 22,914645
CPU 0 DPC count: 1626991
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 4,063747
CPU 1 ISR highest execution time (µs): 3317,620192
CPU 1 ISR total execution time (s): 0,039940
CPU 1 ISR count: 25337
CPU 1 DPC highest execution time (µs): 711,569712
CPU 1 DPC total execution time (s): 0,636484
CPU 1 DPC count: 37408
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 4,253101
CPU 2 ISR highest execution time (µs): 41,685096
CPU 2 ISR total execution time (s): 0,010593
CPU 2 ISR count: 8951
CPU 2 DPC highest execution time (µs): 3383,411859
CPU 2 DPC total execution time (s): 0,730591
CPU 2 DPC count: 79097
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 2,268894
CPU 3 ISR highest execution time (µs): 21,314904
CPU 3 ISR total execution time (s): 0,001639
CPU 3 ISR count: 1832
CPU 3 DPC highest execution time (µs): 258,904647
CPU 3 DPC total execution time (s): 0,038514
CPU 3 DPC count: 10926
_________________________________________________________________________________________________________
CPU 4 Interrupt cycle time (s): 3,672371
CPU 4 ISR highest execution time (µs): 5,761218
CPU 4 ISR total execution time (s): 0,000154
CPU 4 ISR count: 143
CPU 4 DPC highest execution time (µs): 344,983173
CPU 4 DPC total execution time (s): 0,549274
CPU 4 DPC count: 80846
_________________________________________________________________________________________________________
CPU 5 Interrupt cycle time (s): 2,100724
CPU 5 ISR highest execution time (µs): 19,209135
CPU 5 ISR total execution time (s): 0,000646
CPU 5 ISR count: 828
CPU 5 DPC highest execution time (µs): 63,161859
CPU 5 DPC total execution time (s): 0,028604
CPU 5 DPC count: 4672
_________________________________________________________________________________________________________
CPU 6 Interrupt cycle time (s): 2,973661
CPU 6 ISR highest execution time (µs): 6,464744
CPU 6 ISR total execution time (s): 0,000045
CPU 6 ISR count: 38
CPU 6 DPC highest execution time (µs): 209,762821
CPU 6 DPC total execution time (s): 0,283550
CPU 6 DPC count: 42459
_________________________________________________________________________________________________________
CPU 7 Interrupt cycle time (s): 1,940593
CPU 7 ISR highest execution time (µs): 6,403045
CPU 7 ISR total execution time (s): 0,000510
CPU 7 ISR count: 631
CPU 7 DPC highest execution time (µs): 95,469551
CPU 7 DPC total execution time (s): 0,042384
CPU 7 DPC count: 6587
_________________________________________________________________________________________________________

Sebastian S. 0 votes
Actions pour les commentaires Permalien
0
Avatar

The best option to avoid that is to incraise the latency to the point that you cannot hear them. It is a botch, but it is the only thing that can be done today.

The optimization between rekordbox and the ddj 1000 is horrible and has not been improved since October 2019 like many other bugs and glitches. It's a shame.

Alberto G 0 votes
Actions pour les commentaires Permalien