Audirvana _Cannot detect like Full MQA decoder in Khadas tone pro 2 using ASIO Driver

Connection with external Audio Devices
#1

Hi, your support to find the cause, due the the audirvana cannot detect the DAC like a full MQA decoder with Khadas tone 2 DAC. Important to mention the problem is only when I used ASIO driver. When I used WASAPI driver Audirvan coul detect the Khadas Tone Pro 2 DAC like full MQA decoder.

When I used ASIO Audirvana couldn`t detect the DAC full MQA decoder however the DAC display color is detecting the full MQA decoder function. In that sense may colud be a bug in the audirvana screen.

I´m attaching a

20210224_142407
20210224_1424074032×3024 3.77 MB
20210224_143101
20210224_1431014032×3024 3.03 MB

Thanks in Advanced
Regards

2021-02-24T06:00:00Z

#2

It’s not that unusual, with some DACs the detection doesn’t work well. That’s why you have the option to override it.

#3

This whole thing confused me too but what I have learned (and I hope I’m right!) is that when you configure the DAC as a full decoder per your first image, Audirvana will do nothing to the data stream because it must be presented unaltered to the decoder. You are seeing 32 bits because the computer to DAC interface is at that width. Only 24 bits are in use however. The 48KHz is the music file’s original sample rate. The DAC will then do ALL the unfolding/decoding to generate a sample rate as shown by the DAC’s own display colour and as shown on the left in Audirvana.

#4

Thanks I get it. But the strange thing is what I used Wasapi, audirvana can detect the dac like full MQA decoder and there are any problem. This issuw is happens only when I use ASIO

#5

Probably a driver issue.

#6

Hello @Mauricio_Montalvo,

MQA do not have auto detection possible for ASIO driver, it’s not a driver bug, it’s just it doesn’t exist. You then need to change the MQA setting manually to MQA decoder.