jhwalker Posted January 21, 2016 Share Posted January 21, 2016 For full implementation how does MQA identify the DAC used absent two way communication with the DAC? Id be happy if you're right about that. If I understand correctly, the stream coming is is always identical; i.e., there is not a different MQA stream depending on what DAC is on the other end. The code to properly decode / filter the incoming stream resides *in* the DAC; therefore, no two-way communication needed. John Walker - IT Executive Headphone - SonicTransporter i9 running Roon Server > Netgear Orbi > Blue Jeans Cable Ethernet > mRendu Roon endpoint > Topping D90 > Topping A90d > Dan Clark Expanse / HiFiMan H6SE v2 / HiFiman Arya Stealth Home Theater / Music -SonicTransporter i9 running Roon Server > Netgear Orbi > Blue Jeans Cable HDMI > Denon X3700h > Anthem Amp for front channels > Revel F208-based 5.2.4 Atmos speaker system Link to comment
jhwalker Posted January 22, 2016 Share Posted January 22, 2016 I agree, its all about what is upstream of the DAC, both hardware and software. My Auralic Vega DACs USB input has never been a bottleneck to achieving better SQ from upstream enhancements. And having extensively tested all of its inputs, the Vega implementation of USB sounds better than it's other inputs. It's the sum of the parts that matters, so I would respectfully suggest that focusing on one aspect, the USB input, is too simplistic. While not perfect, my system has reached a plateau where musical performance trumps any sound quality distractions. All done with USB. It took two years of experimentation and I am delighted with the results. Thanks to the many people of CA whose contributions to these forums served as guidance on this journey. As a computer guy, I would think the exact opposite; i.e., a properly designed output device (i.e., DAC) should handle *whatever* it is thrown from "upstream" without producing garbage; e.g., if the DAC is receiving "dirty" power along with data from the source, it should be able to filter or be non-reactive to that as it processes the data coming across the other wires. That's the ideal, of course - in reality, cost / price always plays a part, as do any number of other factors, I suppose. John Walker - IT Executive Headphone - SonicTransporter i9 running Roon Server > Netgear Orbi > Blue Jeans Cable Ethernet > mRendu Roon endpoint > Topping D90 > Topping A90d > Dan Clark Expanse / HiFiMan H6SE v2 / HiFiman Arya Stealth Home Theater / Music -SonicTransporter i9 running Roon Server > Netgear Orbi > Blue Jeans Cable HDMI > Denon X3700h > Anthem Amp for front channels > Revel F208-based 5.2.4 Atmos speaker system Link to comment
jhwalker Posted January 23, 2016 Share Posted January 23, 2016 I think someone else has already mentioned this, but . . . Why don't DACs use the USB file-transfer mode instead of streaming? It would seem logical to put a large (say, 128GB) buffer onboard the DAC, then just transfer the file to the DAC and let it "stream" from the internal buffer? Seems that would get rid of any concerns about timing / jitter, power supply "pollution", etc., over the USB cable. I'm sure there's a reason for it, I'm just ignorant and asking the question John Walker - IT Executive Headphone - SonicTransporter i9 running Roon Server > Netgear Orbi > Blue Jeans Cable Ethernet > mRendu Roon endpoint > Topping D90 > Topping A90d > Dan Clark Expanse / HiFiMan H6SE v2 / HiFiman Arya Stealth Home Theater / Music -SonicTransporter i9 running Roon Server > Netgear Orbi > Blue Jeans Cable HDMI > Denon X3700h > Anthem Amp for front channels > Revel F208-based 5.2.4 Atmos speaker system Link to comment
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now