02-Jun-2016, 15:03
Interesting article from Digital Audio Review. Here is a link http://www.digitalaudioreview.net/2016/0...bluesound/ to the full story. Below is an excerpt:
How a Bluesound streamer will handle an MQA file warrants closer inspection. Consider the Node 2. It’s a streamer with digital and analogue outputs.
Putting aside concerns about MQA’s current catalogue size, the degree to which MQA will improve the sound quality heard from a Node 2 will not only depend on the recording but also which of its outputs is tapped.
A quick recap on MQA’s proposition:
1) better sounding source files via MQA’s ‘deblurred’ encoding
2) better sounding playback from a pre-DAC corrective filter
3) unfolding of any hi-res content within the MQA file
The time domain correction of number 1 is embedded in the file and can potentially benefit ANY DAC whether it’s inside an MQA-capable Bluesound device or not.
On top of that, end users who connect their Node 2’s analogue outputs to an amplifier will get the benefits of Numbers 2 and 3. Why? The MQA software that sits inside the Bluesound streamer will unfold the hi-res portion of the file and apply an MQA-coded digital filter to the signal before it reaches the DAC chip. This filter has been specifically tailored by MQA to the Node 2’s internal DAC and its filters because each are known quantities in the playback chain.
This scenario is precisely what I heard in the Lenbrook room at CES 2016.
However, listeners who wish to bypass the Node 2’s internal DAC in favour of their own decoder will connect an external box to one of the Bluesound’s S/PDIF outputs.
In this scenario, the MQA software within the Node 2 will unpack any hi-res content and send the entire, unfolded file to the external D/A converter over S/PDIF. How much hi-res unfolding takes place will depend on the maximum sample rate handling of the Node 2’s coaxial and Toslink outputs.
Now comes a slight catch: the MQA software inside the Node 2 isn’t ‘externally DAC aware’; it knows not which DAC has been connected to its rear panel and therefore cannot apply its custom, pre-corrective filter. No number 2 for you.
This leaves Bluesound users looking for the complete MQA fix to answer this question: does an uptick in sound quality brought by MQA’s pre-corrective DAC filter offset the sound quality foregone by not deploying one’s (presumably superior) external D/A converter?
An interesting conundrum for Bluesounder's.
How a Bluesound streamer will handle an MQA file warrants closer inspection. Consider the Node 2. It’s a streamer with digital and analogue outputs.
Putting aside concerns about MQA’s current catalogue size, the degree to which MQA will improve the sound quality heard from a Node 2 will not only depend on the recording but also which of its outputs is tapped.
A quick recap on MQA’s proposition:
1) better sounding source files via MQA’s ‘deblurred’ encoding
2) better sounding playback from a pre-DAC corrective filter
3) unfolding of any hi-res content within the MQA file
The time domain correction of number 1 is embedded in the file and can potentially benefit ANY DAC whether it’s inside an MQA-capable Bluesound device or not.
On top of that, end users who connect their Node 2’s analogue outputs to an amplifier will get the benefits of Numbers 2 and 3. Why? The MQA software that sits inside the Bluesound streamer will unfold the hi-res portion of the file and apply an MQA-coded digital filter to the signal before it reaches the DAC chip. This filter has been specifically tailored by MQA to the Node 2’s internal DAC and its filters because each are known quantities in the playback chain.
This scenario is precisely what I heard in the Lenbrook room at CES 2016.
However, listeners who wish to bypass the Node 2’s internal DAC in favour of their own decoder will connect an external box to one of the Bluesound’s S/PDIF outputs.
In this scenario, the MQA software within the Node 2 will unpack any hi-res content and send the entire, unfolded file to the external D/A converter over S/PDIF. How much hi-res unfolding takes place will depend on the maximum sample rate handling of the Node 2’s coaxial and Toslink outputs.
Now comes a slight catch: the MQA software inside the Node 2 isn’t ‘externally DAC aware’; it knows not which DAC has been connected to its rear panel and therefore cannot apply its custom, pre-corrective filter. No number 2 for you.
This leaves Bluesound users looking for the complete MQA fix to answer this question: does an uptick in sound quality brought by MQA’s pre-corrective DAC filter offset the sound quality foregone by not deploying one’s (presumably superior) external D/A converter?
An interesting conundrum for Bluesounder's.
Devialet Expert 220 Pro Kinki EX-M7 power amp tethered to a fiber-fed Lumin X1 streamer via Grimm XLRs, Vivid B1 Decade speakers in Rosso Barchetta red (only 200 produced in a limited edition), Roon Nucleus with a Samsung 860 EVO 2TB SSD, etherREGEN switch fed by a Sonore opticalModule (and Sonore-supplied transceivers and 1M optical cable) with a SOtM dCBL-Cat7 cable to my Nucleus and a DH Labs Reunion Cat8 to my Lumin T2 streamer, Keces P8 linear power supply feeding a (to come) NUC and EtherREGEN switch with an external AfterDark OCXO clock., and opticalModule (5V/1A), AudioQuest Niagara 1000 power conditioner, ASI LiveLine loom (purchased directly from Franck Tchang when I lived in France), Less Loss Firewall for Speakers and Roon lifetime license with Tidal streaming.
