Topic: ADI-2 DAC: Sound output cracked or skipping with Win10 ASIO

Hello guys,

I got ADI-2 DAC FS months ago and I loved it very much.

Wihle one issue got me frustrated as sometimes the playback will "crack"  or "skip" by 0.x second during ASIO MADIface USB mode selected,

I saw some familiar feedback before like that, but my situatioin gets some different since usually happens when (but not limited to):
- apps like Chrome/new Edge with Chromium core are being operated, open new tab/session especilly
- system interface poped, e.g, when I click out the notification panel from the right-down corner of win10 screen
- when using other apps those mostlikely to show themseves, you know, like ims/chat apps, who usually req much resource and system responce priority
- the issue not only impact DSD, but also to PCM ouput when I'm playing FLAC or wav files under ASIO MADIface USB (in foobar, under DSD: ASIO: ASIO MADIface USB)

When I just use music app+ASIO to playback and leave other apps not operated, the issue disappears. (e.g Chrome, either closed or leave to background works to mitigate the issue.)

OK that looks like to be a driver or session priority issue, so I have done the followings to debug:
- swap USB cables (in box one or other brand cables), or USB ports (all on board original ones suppose driven by intel chipset)
- Upgrade all drivers to latest, including ADI-2 DAC, PC component drivers, system etc
- reset ADI-2 and upgrade the FW to latest
- uninstall RME app/driver completely, and re-install driver and leave everything default setup
- Install latest Chrome and disable all add-ons
- change the music playback apps between foobar, Qobuz, or others with ASIO output supported
- manual set the related playback sessions to highest system priority (real time)
- of course, restart windows or apps

But the issue is still there.

There're just fews things helped when I tried:
- uninstall RME app/driver completely, just use Win10 built-in driver (UAC2?), then select DSD:WASAPI (Push): Analog (1+2) (RME ADI-2 DAC) in foobar or other familiar modes in other apps, help reduced the issue happen.  (yeah push mode, because event mode will output real crack sound continuesly, I don't know why)
- use system default interface, DS mode or something like that, yes that works without crack but the sound quality is like using,  you know, on board Realtek,


Does anyone meet same issue as I got?

Guys can you help advice anything I can do to mitigate the crack/skip case when I'm listening music and doing some works at the same time?

Thank you!


ADI-2 DAC FS info:
Driver:    9716
HW:    27

PC SW/HW:
Win 10 Pro 1909
i7-8700 + 32G DDR4 + GTX1070 with latest driver

Playback routing:
PC -> USB - > ADI-2 DAC FS - > Genelec 8020

Re: ADI-2 DAC: Sound output cracked or skipping with Win10 ASIO

add some more:
- I disabled on baord audio chip so should be no driver or devide conflict as ADI-2 is the only audio device in the system
- I don't run high loading tasks in system when listening to music, browse webpage via Chrome and chat with friends with chat app (no any audio usage when met the skipping issue) are mostly used.  i7 8700+32G DDR4 should be enough to cover those tasks.

3

Re: ADI-2 DAC: Sound output cracked or skipping with Win10 ASIO

Check your system with Latency Monitor from Resplendence. Motherboard type?

Regards
Matthias Carstens
RME

Re: ADI-2 DAC: Sound output cracked or skipping with Win10 ASIO

MC wrote:

Check your system with Latency Monitor from Resplendence. Motherboard type?

hi, thank you for replying my post!

Motherboard is ASUS PRIME B360-PLUS. 
I used on board USB port instead of PC front panel audio jack or anything beyond mainboard original port.

here's the test result (surry i have no image server yet)
- 1st one for system without any playback, everything silent. 
- 2nd one for foobar playing normal flac via ASIO output.



Test 1 without any playback
_________________________________________________________________________________________________________
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:20  (h:mm:ss) on all processors.

_________________________________________________________________________________________________________
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):   268.50
Average measured interrupt to process latency (µs):   5.364218

Highest measured interrupt to DPC latency (µs):       223.30
Average measured interrupt to DPC latency (µs):       1.836715


_________________________________________________________________________________________________________
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):              299.332707
Driver with highest ISR routine execution time:       dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation

Highest reported total ISR routine time (%):          0.059898
Driver with highest ISR total time:                   dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation

Total time spent in ISRs (%)                          0.060009

ISR count (execution time <250 µs):                   3248
ISR count (execution time 250-500 µs):                0
ISR count (execution time 500-999 µs):                1
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):              318.813283
Driver with highest DPC routine execution time:       nvlddmkm.sys - NVIDIA Windows Kernel Mode Driver, Version 451.67 , NVIDIA Corporation

Highest reported total DPC routine time (%):          0.041358
Driver with highest DPC total execution time:         nvlddmkm.sys - NVIDIA Windows Kernel Mode Driver, Version 451.67 , NVIDIA Corporation

Total time spent in DPCs (%)                          0.089869

DPC count (execution time <250 µs):                   48016
DPC count (execution time 250-500 µs):                0
DPC count (execution time 500-999 µs):                4
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:                 msmpeng.exe

Total number of hard pagefaults                       2
Hard pagefault count of hardest hit process:          2
Number of processes hit:                              1








Test 2 with playback on


_________________________________________________________________________________________________________
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:36  (h:mm:ss) on all processors.
_________________________________________________________________________________________________________
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):   916.10
Average measured interrupt to process latency (µs):   3.938565

Highest measured interrupt to DPC latency (µs):       913.80
Average measured interrupt to DPC latency (µs):       1.357219
_______________________________________________________________________________________
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):              184.984336
Driver with highest ISR routine execution time:       dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation

Highest reported total ISR routine time (%):          0.029480
Driver with highest ISR total time:                   dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation

Total time spent in ISRs (%)                          0.031666

ISR count (execution time <250 µs):                   12435
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):              958.778822
Driver with highest DPC routine execution time:       nvlddmkm.sys - NVIDIA Windows Kernel Mode Driver, Version 451.67 , NVIDIA Corporation

Highest reported total DPC routine time (%):          0.061795
Driver with highest DPC total execution time:         Wdf01000.sys - 内核模式驱动程序框架运行时, Microsoft Corporation

Total time spent in DPCs (%)                          0.103239

DPC count (execution time <250 µs):                   81968
DPC count (execution time 250-500 µs):                0
DPC count (execution time 500-999 µs):                20
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:                 dllhost.exe

Total number of hard pagefaults                       83
Hard pagefault count of hardest hit process:          73
Number of processes hit:                              4

5

Re: ADI-2 DAC: Sound output cracked or skipping with Win10 ASIO

You did not mention the ASIO Latency (Buffer size) that you use (in the RME Settings dialog). For ASIO you could go to the max size and check if the same happens again. For WDM set 256 or 128.

These two points:

> - apps like Chrome/new Edge with Chromium core are being operated, open new tab/session especilly
->  system interface poped, e.g, when I click out the notification panel from the right-down corner of win

look like system sounds are played via the ADI-2 DAC. Go to Sounds panel and set your onboard soundcard as default playback device.

You can also let the Settings dialog open all the time so you can see if USB errors show up or the sample rate changed.

Regards
Matthias Carstens
RME

6 (edited by pumpkinknight 2020-07-28 17:13:53)

Re: ADI-2 DAC: Sound output cracked or skipping with Win10 ASIO

Oh sure here's the setup for buffer size and sample rate I set:

ASIO Latency buffer size:
- DSD or high bite rate PCM:        8192 samples  (seems to be automatically up to this one)
- normal PCM (up to CD rip):        2048 sample  (the setup i put as default)

sample rate:
- DSD or high bite rate PCM:        176400 or 192000 hz  (seems to be automatically up to this one)
- normal PCM (up to CD rip):        44100 hz  (the setup i put as default)


Usually I set the buffer size to largest as I can, and I can see the buffer size will automatically change depend on the bit rate of the playback. (is that good or bad if changes automatically?)

Sample rate, I just leave it to default and looks it will change by itself as same as buffer size.

Is that a better idea to have onboard soundchip to cover brower and system sounds? That will req separate cables to my speaker and also I got a bit worried whether it will conflict with ADI-2 DAC.

If i want to use ADI-2 DAC to cover all sounds in the system, does that mean I have to suffer this issue since any system sound or brower generated sound will interupt ASIO output and bring a skipping/crack?

Thank you





MC wrote:

You did not mention the ASIO Latency (Buffer size) that you use (in the RME Settings dialog). For ASIO you could go to the max size and check if the same happens again. For WDM set 256 or 128.

These two points:

> - apps like Chrome/new Edge with Chromium core are being operated, open new tab/session especilly
->  system interface poped, e.g, when I click out the notification panel from the right-down corner of win

look like system sounds are played via the ADI-2 DAC. Go to Sounds panel and set your onboard soundcard as default playback device.

You can also let the Settings dialog open all the time so you can see if USB errors show up or the sample rate changed.

7

Re: ADI-2 DAC: Sound output cracked or skipping with Win10 ASIO

The point here is to first find out what is the problem cause. Then we can discuss further. If you are running WDM (OS audio) constantly at 192 kHz then I woudn't be astonished if Chrome etc freak out. If OS audio switches between high sample rates and lower ones then the same applies. As I said: open the Settings dialog and find out what your system is really doing.

Regards
Matthias Carstens
RME

8 (edited by pumpkinknight 2020-08-02 08:18:29)

Re: ADI-2 DAC: Sound output cracked or skipping with Win10 ASIO

OK here're the snapshot of Setting page (is that?)

the buffer size and sample rate do variate when system playback different bit rate medias



The one at playback after 1 hour
https://i.loli.net/2020/08/02/OXxUgVI8ZMinY6J.jpg


idle statues
https://i.loli.net/2020/08/02/HQ8DZJYbKSRErOW.jpg


page2, just keep as default
https://i.loli.net/2020/08/02/vkFMr3O78mgcDEw.jpg

MC wrote:

The point here is to first find out what is the problem cause. Then we can discuss further. If you are running WDM (OS audio) constantly at 192 kHz then I woudn't be astonished if Chrome etc freak out. If OS audio switches between high sample rates and lower ones then the same applies. As I said: open the Settings dialog and find out what your system is really doing.

9 (edited by pumpkinknight 2020-08-08 14:39:52)

Re: ADI-2 DAC: Sound output cracked or skipping with Win10 ASIO

Update today's test statues, still met skipping case when playback via ASIO/USB and browsing webpages with Chrome.
On board audio chip disabled.


Setting Panel Page 1
https://i.loli.net/2020/08/08/4jJecY9uGOzbDwV.jpg


Setting Panel Page 2
https://i.loli.net/2020/08/08/Hh8QozyYnpPBkev.jpg



LatencyMon
https://i.loli.net/2020/08/08/YPG4I3xlSw9Qjhp.jpg