…but, as I have explained earlier, when I replace ** Audirvana ** with foobar2000 there are zero issues with playback when playing PCM (up to 192kHz) and DSD (64, 128, 256), which is why it leads me to troubleshoot the combination with Audrvana in the chain.
In the case of DSD files, disable DoP… change Native DSD streaming method to ‘None, convert to PCM’ Chord DACs decimate DSD files to PCM internally and up-convert to high sample-rate multi-bit PCM for output.
If it is a conflict with the Chord driver and Audirvāna, then Chord must be made aware, as you see here, that the Audirvāna team has not found reason to step into this thread as they have already, with other Chord devices found in the “Plāys With Audirvāna”
Do you mean “click the lock icon in Audirvana” - if so, then that stops playback, which doesn’t help.
Have switched off Exclusive access via Windows Sound Settings as seen below, but it doesn’t make a difference since Audirvana reverts to exclusive access on playback:
Again no joy, the symptoms are exactly the same as before. Also, I did visit the page linked to above (and then on to the one relevant to the Mojo 2), and, at first, used the settings recommended therein.
Further, I believe the ASIO driver is common to all Chord DACs, which is probably why the model name doesn’t appear when ‘Debug Info’, is generated, but it does for WASAPI settings since that driver is specific to the model.
Local devices found : 4
Device #0: ASIO Chord 1.05
Manufacturer:
Model UID: ASIO Chord 1.05
UID: ASIO Chord 1.05
Model name: ASIO Chord 1.05
Device #1: USB DAC ASIO
Manufacturer:
Model UID: USB DAC ASIO
UID: USB DAC ASIO
Model name: USB DAC ASIO
Device #2: Vinshine DENAFRIPS USB DAC
Manufacturer:
Model UID: Vinshine DENAFRIPS USB DAC
UID: Vinshine DENAFRIPS USB DAC
Model name: Vinshine DENAFRIPS USB DAC
Device #3: Zorloo USB Audio ASIO Driver
Manufacturer:
Model UID: Zorloo USB Audio ASIO Driver
UID: Zorloo USB Audio ASIO Driver
Model name: Zorloo USB Audio ASIO Driver