MQA signalling not passing to BluOS (NAD M10) with Roon DSP applied

Answered

Comments

7 comments

  • Official comment

    Hi R.B.

    Your question posed that was marked SOLVED was about Proximity Sensing and was updated by Vishnu on March 3rd. Please ensure you have whitelisted bluos.net and bluesound.com - check your JUNK Filter too.

    As for this above issue, your concerns are with the ROON Software - I would contact them. That being said, I am guessing as soon as you enable any sort of change to the DSP, you are violating MQA process so are no longer hearing MQA because you are altering the audio content.

    Comment actions Permalink
  • Avatar
    R.B.

    Hi Tony, 

    That was not what I was talking about and yes, it was solved. The reference for the ticket I am talking about is #220487. Sadly cannot paste the link here. Have checked my junk folder and there is nothing there. 

    As for your comments on this being a Roon issue, they are saying it is not. As mentioned, the signal path in Roon shows MQA is signalled to my streamer and this should receive MQA to play.

    Either the signal path in Roon is lying or BluOS does not interpret the signalling as MQA (which it is apparently according to Roon).

    Dirac Live is also a form of DSP and I have no issues playing MQA when this is applied from your app. 

    Not sure how DSP would violate MQA process. See here from Roon:

    Can I use DSP with MQA content in Roon?

    Yes. Roon is the only music player that seamlessly integrates DSP with MQA content, while preserving your MQA DAC’s ability to fully render the post-processed stream. First, Roon will decode the MQA file or stream it to an MQA Core stream. This produces a PCM audio stream at 88.2kHz or 96kHz which contains MQA signalling information that your DAC needs to render the MQA signal properly

    Looking forward to your thoughts on this.

     

     

     

    0
    Comment actions Permalink
  • Avatar
    R.B.

    Hi Tony, can you please let me know if you will be looking into this?

    0
    Comment actions Permalink
  • Hi R.B.

    I spoke with our QA Team about your issue - they concur the issue is best handled with ROON as the ROON interface or software is causing the issue. Please continue to work with ROON to find a solution.

    If ROONLabs confirms it is a problem with how the NAD M10 acts as a ROON endpoint, ROON will work with us behind the scenes to resolve in the near future.

    Thanks for understanding.

    0
    Comment actions Permalink
  • Avatar
    R.B.

    Cheers Tony and will do. 

    0
    Comment actions Permalink
  • Avatar
    R.B.

    Hi Tony, 

    Spoke with Roon support and this was their reply:

    "it looks like Roon passes along the MQA rendering information to the device. Any changes you see starting from your device is dependent on the device itself.
     
    Reaching out to Bluesound to find out why the device isn't being used as a decoder and what happens when only rendering information is passed to the device, would be a great next step."
     
    Here is a link which describes how Roon DSP engine works with MQA https://help.roonlabs.com/portal/en/kb/articles/audio-setup-basics#MQA_Capabilities 
     
    The NAD M10 running BluOS is Roon Ready and I would expect both parties to work towards solving this "mystery" :)
     
    Looking forward to your thoughts on how this can be further investigated and hopefully solved. There are several other discussions on this over on Roon's community forums and no one seems to know why this happens. 

    I am happy to help with screen grabs of the signal path or anything else you may require. 

    0
    Comment actions Permalink
  • Avatar
    Tony W. - Product Support Manager

    Hi R.B.

    We have escalated your issue to ROON on your behalf. ROON will be in touch on how to correct this for you.

    0
    Comment actions Permalink

Post is closed for comments.