Thread Rating:
  • 1 Vote(s) - 4 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Roon 1.7 and MQA device setting
#11
See Roon's explanation of the info displayed in the Signal Path and the meaning of the different colours in this page on their website: https://kb.roonlabs.com/Signal_Path

That page dates from May 2017 and your image contains a similar path description with identical colour coding to the details and examples given in the page from Roon's site.
Roon Nucleus+, Devilalet Expert 140 Pro CI, Focal Sopra 2, PS Audio P12, Keces P8 LPS, Uptone Audio EtherREGEN with optical fibre link to my router, Shunyata Alpha NR and Sigma NR power cables, Shunyata Sigma ethernet cables, Shunyata Alpha V2 speaker cables, Grand Prix Audio Monaco rack, RealTRAPS acoustic treatment.

Brisbane, Qld, Australia
Reply
#12
I have one question regarding choosing this MQA setting in update 1.7
First. Enable MQA Core Decoder is set to “Yes” in all 3 examples here.

One example file: When I play via USB. Or when I go via Wi-Fi and then set the Devialets MQA Capabilities to “Render only” in Roon I get MQA Core decoder “to 96kHz 24 bit with MQA signalling”, in the signal path.
If I choose “No MQA Support” I get MQA core decoder “to 96kHz 24 bit”.
I´m new to Roon so I wonder what this ad on “with MQA signalling” actually means, turning up or not turning up, in MQA Core Decoder, in the Signal path?

Best regards Ulf
Reply
#13
The Devialet provides no MQA support and I believe the default setting in Roon's configuration should be that rather than "Renderer Only" which is the current s setting.

The original MQA stream contains data for 2 MQA processing steps. If you enable the MQA Core Decoder, Roon will do the first of those 2 processing steps which is the main one, but the second step can't be done by Roon. If you set the MQA Capability setting to "Renderer Only", Roon passes the rest of the MQA data to the Devialet for the Devialet to do the second step processing but the Devialet actually has no MQA capabilities so it simply ignores the MQA data. If you set the MQA Capability Setting to "No MQA Support", Roon strips the remaining MQA data from the stream it passes to the Devialet. Either way, the second processing step isn't done, Roon does the first processing step, and you hear exactly the same result.

In the Signal Path data you will see exactly what you report. If you set the MQA Support setting to Renderer Only, the signal path info tells you that Roon is sending the 96/24 data with MQA data for the second processing step. If you set MQA support to No MQA support, the signal path info tells you that Roon is sending the 96/24 data without the MQA data for the second processing step which the Devialet cannot do anyway.

The default MQA Support setting of "Renderer Only" is wrong, the default should be "No MQA Support". Whichever setting you use makes a small difference in Roon's processing but that will make no difference at all to what you hear. The end result of the Devialet receiving MQA data it ignores and the Devialet not receiving that data is simply that nothing happens with the data for the second processing step, it isn't used. Either Roon ignores it and "throws it away" or the Devialet receives it and ignores it but either way that last bit of MQA data doesn't get used. The first processing step, the one Roon does when you enable the MQA Core Decoder, is the main processing step and delivers most of the benefit of MQA.
Roon Nucleus+, Devilalet Expert 140 Pro CI, Focal Sopra 2, PS Audio P12, Keces P8 LPS, Uptone Audio EtherREGEN with optical fibre link to my router, Shunyata Alpha NR and Sigma NR power cables, Shunyata Sigma ethernet cables, Shunyata Alpha V2 speaker cables, Grand Prix Audio Monaco rack, RealTRAPS acoustic treatment.

Brisbane, Qld, Australia
Reply
#14
I´m aware that Expert Pro CI (for now) doesn´t do the second MQA-unfolding. Nevertheless it wasn’t immediately clear for me how to interpret “with MQA signalling” coming and going when changing settings. IT IS NOW, tanks David

In the same manner I wonder if I can set a USB path so Enable MQA Core Decoder is set to “Yes”, but “with MQA signalling” is deactivated in MQA Core decoder? Meaning MQA Core decoder only saying “to xxkHz xx bit”.
Best regards Ulf
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)