Again, if we are talking Tidal MQA, then there will be no support for it over Chromecast and an external DAC supporting MQA will need to be connected to the phone for output. There is no need for another DAC here unless a wired DAC is connected to the phone and then a cable from it to the receiver's analog inputs is used to cut the ChromeCast Audio out of the mix altogether. The optical connection to the receiver should be sending 24/96 if it is being sent to the Chromecast Audio in the first place. This doesn't help 24/192 folk as Chromecast is limited to 24/96, but I digress. Now, the Chromecast protocol supports 24/96 and it can be sent over Wi-Fi to a Chromecast Audio. Ok, so anyway, wired connections from iOS or Android phones will be limited to 24/48 with a wired connection UNLESS a DAC is in between the phone and audio output device. If Amir says anything different he is full of you know what. He has proved to me that streams through Chromecast do NOT triangulate and go straight from router to the Chromecast device, and that passes it straight through to the AVP via the HDMI port. My eldest son is chief engineer for a large company and works with the digital domain. The point of this, is that with the way I do it, the quality of streaming via Chromecast is equal in quality to other methods of capturing the same stream.īottom line, is that if you are having an audio quality issue, it is external to the Chromecast dongle. I now note many companies are only offering their recordings via download. I recently downloaded a disc from Signum Classics and the quality I think would equal that of the CD. I do occasionally buy a CD online and download it to the DAW. The only other thing I download is BBC iPlayer to the APC and record audio to the DAW from iPlayer via the DAW and use the Fireface 802 to control the recording to WaveLab. I should state that I do not download media to my mobile devices. I tested qbuzz with my sons iPhone as he has a subscription. It is clear to me you have fed in nonsense troughs.Ĭlick to expand. I would say 90% or more that is out there is just nonsense. Stop reading audio articles and reviews by arts graduates from journalism school and start listening to proper engineers. There is absolutely nothing in common, or similar about the two. When engineering digital systems, you have to leave your old analog way of looking at streams and connections in a totally different way. Almost always money spent of better speakers would have a real impact on better sound, and a $1000.00 dollar or more DAC will not make a wit of difference. There is so much money wasted on these exotic DACs which are a waste of and it doesn't end there, with mountains of false information. The Solomon code error correction is robust and a total correction. About the latter there is also nonsense floating around, about that. The fact is bits are bits, and on any device there is also robust error correction. I think someone has indoctrinated you about all this. You can also hard wire an ethernet cable to some Chromecast devices, and that is what I do. That is the beauty of the system and why it is so robust. Your remote device never sends any stream to the Chromecast directly. Then the your router sends the stream straight to your Chromecast, and your device is out of the equation. Your iPhone, computer, or what ever you stream with, just becomes the control device one you press the Chromecast icon. Click to expand.No, your router sends the signal to the Chromecast.
0 Comments
Leave a Reply. |