Node 2i Digital Coaxial MQA pass through
Answered
Hey team, I've got a question regarding how MQA files are handled via digital coaxial to an MQA Certified external DAC.
In my case, I plan on streaming Tidal MQA through the Node 2i and passing the rendering stage of the MQA file onto my Gustard X16 which is an MQA certified renderer via coax.
I have done quite a bit of combing through community posts on the Bluesound site regarding this topic but one thing is still unclear. I understand that the Node 2i can pass the file at 1/2 the original rate (192>96, 96>48), but is the Node able to do this while maintaining the MQA "core" file?
It is important that the Node is able to pass the MQA "core" file and not just a regular 96khz stream so that the Gustard X16 DAC can handle the final unfold and provide MQA files in their full glory at 192khz+.
Any response will be greatly appreciated. Thanks in advance!
Hunter
-
Official comment
Hi Hunter
The NODE is fully certified and can be used as an MQA DAC itself or as a rendered for an external MQA DAC by selecting MQA External Dac in the Audio Settings.
Please see www.mqa.co.uk for more details. -
Hunter,
There is another thread on here specifically regarding the X16, to which Tony is providing the same generic cut and paste answer. BTW, www.mqa.co.uk provides zero details for any part of your question.
What I can say is that personally, even if the coax cuts the signal from 96 to 48k it sure as heck does not look as though the Gustard is identifying it as an MQA encoded file. So either the Bluesound is not pushing the MQA encode across coaxial or the Gustard is not receiving it as such. When I use my roon server, it passes the MQA encode right to the Gustard no problem, so I know the issue is not on the Gustard end, unless Gustard does not recognize MQA via coax input.
0 -
I would contact Gustard as we would be seeing issues with other DAC manufacturers (such as Mytek) if it was a Bluesound issue. Thanks for understanding.
0 -
Thanks Erik and Tony.
Erik- by chance is the Gustard displaying OFS when being fed an MQA track from the Node? I found a response from Gustard on Audio Science Review saying that this is normal per MQA specs. Seems like it's still playing MQA in this case, curious to hear if that's what you are getting.
0 -
Hi Hunter,
We are currently having that same discussion over at this link:
Hopefully we can amalgamate both threads this way.
A quick aside, here is what OFS means -
OFS - This behaviour is mandated by MQA, a DSP processed stream is called “MQB” by MQA LTD and the display must show OFS instead of MQA.
Unless the Bluesound is running the signal through some sort of DSP, it should not show up as such.
Erik
0 -
On that note Erik I'm closing this thread out so everything can be localised to the thread you linked.
Regards,
Sam R.0
Post is closed for comments.
Comments
6 comments