In Google Home under each units individual settings:audio do you have full dynamic range checked?
Yep I’ve been running them for years in hifi mode, but now they’re no longer made only the new HDMI ones are easy to find.
What do you cast to the CCA? It’s known that casting from Chrome browser gives a poor result.
Edit: I guess you must be casting from Roon. What is the music source?
Yes casting from Roon. It seems widely known that Chromecast just doesn’t sound as good as other streamer hardware, for what ever reason the difference is vast.
There should also be no difference between the new Ccast with Google tv and previous Chromecast, yet there is a very noticeable difference and these are via HDMI.
Ccast doesn’t seem to display any rate data so there doesn’t seem to be an easy way to check if it’s apples to apples data, but it sure sounds like apples to applesauce.
The Primare NP5 mkI or II should meet your needs.
How many times do I have to post this? Third time is the charm?
Widely known? Where? By whom? According to the measurements on Audio Science Review, the CCA works pretty well as a streamer. As an integrated streamer/DAC/pre-amp, less well, but hardly terrible.
I don’t actually use the mini toslink output on any of mine, using 3.5mm to twin RCA cable direct into analog inputs of various integrated amps.
So still relevant to my application but possibly not to the op IF every one of his six units are utilizing the mini toslink output.
But good information all the same
This is what I’m looking for and today is the last day of a complementary 2yr Roon sub! Just in time.
Chromecast stack is known to be pretty resource hungry and can take up limited resources in some hifi gear. Fine if its just a Chromecast device designed purely for that purpose but not so on other hifi systems that use limited shared resources to manage all the things they support. It definitely doesn’t sound as good as Airplay , UPnP or Roon on my Naim system This is down to the Chromecast stack using pretty much all of the memory resources available according to their lead software engineer. I don’t think the higher end consider these protocols as being the gold standard and are added purely as convenience for the consumer and for marketing to tick boxes.
That’s interesting. But of course with the CCA, as you say, that’s not an issue. And that still wouldn’t affect the sound, would it?
The thing about “other hifi systems that use limited shared resources to manage all the things they support” is that they are supposed to manage those resources. If they don’t do that properly, sure, you’ll have problems. But that’s on the designers of those systems, and the OS they use, not on individual apps.
It’s not exactly a protocol, is it? Rather, it’s a way to implement your own protocol, as Roon does with their Chromecast support (see Danny’s various posts on the subject). Something like the Roon Bridge, only programmable. I suppose if you do it poorly, you will get poor results. Or if you implement a bad protocol, you’ll get poor results.
All I know is that compared to RAAT on same device, RAAT is a winner in all ways.
Actually, I’m not sure about the protocol. I had the impression that Roon wasn’t using the Google Cast protocol to send the data, that they basically downloaded a version of Roon Bridge into the Chromecast device and talked to that using their own protocol, maybe even RAAT. But looking at the Cast SDK, I don’t see how they would do that.
I believe Roon is using the Google Cast protocol for streaming, which is why only Chromecast devices can be grouped and not shared with other Roon devices. This is similar to Roon’s AirPlay (ver. 1) grouping also, in that only AirPlay devices can be grouped.
There are some very technical, well-informed answers here, but I am wondering whether you have considered the simple solution of an HDMI splitter. I am using some generic brand HDMI splitter for audio from Chromecast. The splitter takes HDMI input and delivers HDMI video output and SPDIF audio output, which I feed to my high end DAC. It is a cheap solution that sounds quite listenable for video streams, though well short of what I expect from my streamer and DAC for Roon audio.
No it’s uses Google cast how else would it work. You can’t install your own protocol on a Chromecast, where on earth did you get that idea?
From something Danny wrote a couple of years ago:
This comment, plus the responses by @Edward12 point to a misunderstanding of how Chromecast works. There is no Chromecast audio protocol. There is no Chromecast video protocol. The Chromecast protocol is more like a programmable web browser, where Roon (and other apps) can tell it to load up custom code to do some logic in the browser. A media protocol on both ends is dictated by Roon (and other apps).
It’s open to interpretation. I guess Google Cast could still be the thing moving the bits between devices.
It’s actually explained fairly well here, but yes it’s pretty much per your quote from Danny:
sorry to dig this out, but I just would like to know the sample rate of the Chromecast audio as I’m thinking of buying one as a roon endpoint. Is it 24bit/192khz or 24bit/96khz?
I’m reading conflicting information on this.
I want to stream my collection of CDs which is sitting on my NUC with Rock to the Chromecast. My
playback device already has a Chromecast built-in so it’s 24bit/48khz…maybe it won’t make a difference but I’m still a beginner so forgive my candid questions