Roon's MQA features with dCS products

Hi Andrew, can you share the reason/s why this is general best practice?

Feel free to go deep ‘into the weeds’ if you have to :grin:

Hi Keith

A while back I posted a feature request to provide the option of
two separate paths through the Roon DSP section, one for PCM and one for DSD, see

[Akin to, but more flexible than, the “DSD Pass-Through” feature of the Vivaldi Upsampler.]

Seems like it should be three paths rather than two: PCM, DSD and MQA.

Regards, Mike

2 posts were merged into an existing topic: Audio dropouts with MQA on dCS Rossini and Roon 1.5 (B320)

Hi Andrew, just in case you missed my earlier question, just wondering if you can share the reason/s why this is considered general best practice?

Cheers in advance

I should have chosen my words more carefully :wink:

How about, “MQA’s recommendation is that the decoding process happens as close to the renderer as possible.”

In terms of reality there’s no difference between the decoding process happening in the DAC or halfway around the world. It’s just data transfer at that point. The issue is what digital processing components get inserted. A simple digital volume control inserted in the signal path will potentially compromise the MQA signaling information if MQA isn’t taken into account ahead of time.

Hehe much the same. Still had me scratching my head but… see below.

This is why my eyebrows raised. I was thinking the same but… see below.

Noted. I had guessed this was the background to your comment / MQA’s recommendation.

Thanks!