Chromecast Sample Rates?

Now I really have to work on my artist pictures.

Some nice PMC speakers there! :+1:t2:

I’m itching to see if my Q Acoustics Q-TV2 soundbar copes with 24/48 from a first gen Chromecast, but I’ve gotta wait for my daughter to relinquish the damn iPad (to view the DSP option) :neutral_face:
Wonder if Roon plan to improve the App experience for iPhone? :thinking:

Get a tablet, phones are just too small to get the best of what Roon can deliver…

The entry level iPad is cheaper than a Roon lifetime subscription. It is excellent value for money (not often one can say that about an Apple product). Roon remote is effectively designed for it I think, with other remotes being slightly compromised in one way or another.

1 Like

Second hand Mini 3 here.

AppleTV has their own graphic design for now-playing data, so it shows some stuff, but not as nicely.

On Chromecast, we control the rendering, since a Chromecast is (more or less) an embedded web browser, so we did our own design for that screen in @RBM’s screenshot.

We have some work to do on this, too. Sourcing or crowd-sourcing better artwork will help, but the other thing we really need content-aware cropping/positioning of images on the display side.

We call this the “foreheads problem”:


The idea is to identify the most salient portion of the image (red bounding box), the center-of-mass of salience (red dot), and any human faces (blue boxes) in the image.





Using this extracted information, we can come up with cropping rules that avoid chopping faces in half and focus attention on the most interesting parts of an image.

The exact crop rectangles different from situation to situation, but the idea is that for each display scenario–whether it’s a 16:9-ish like Chromecast, or a square image in a grid, or a 4:3 on the artist browser, we’ll be able to intelligently crop the image for the situation.

Anyways–we have the computer vision/feature extraction part working well, but there is a lot of “plumbing” work involved in getting it deployed for real and then distributing the benefits to all the relevant places in the product.


Impressive thinking.
Surprising places it takes you, the simple concept of browsing and playing music.

Ah, basterds! :stuck_out_tongue_winking_eye:
Seriously though, that was about the saddest excuse of a :soccer:-game i’ve witnessed in quite some time. England deserved the win, no argument… The best of luck to the English in the next game!

1 Like

What is this “Sweden” you guys talk about?
Nerver heard of it.


Thanks for the insight Brian. I am very interested in this display-only capability. My core will be near my TV system and it would be nice to be able to stream digital audio from my core to my preamp while the Chromecast creates a nice display on the screen. However as it stands now Chromecast devices cannot be grouped with other types of devices right? So the only way to have video on the Chromecast linked to a separate audio output is if that audio output is a Chromecast audio, which is only slightly better than the Chromecast. Correct me if I’m wrong but this means that you will be changing the system so we can group different types of outputs together no?

1 Like

As I read it @brian is suggesting that at some point we will be able to link a Chrome Cast video device as a non-Audio Zone to any other zone regardless of the protocol used by the other zone.

I would presume not having to sync the audio makes this feasible without expending tons of development resources.


Also really happy to hear about display only casting planned, came here to ask about it. :+1:


Yeah, exactly. That’s a fair description of the technical approach.

I’m not sure if we will use the “linking” or “grouping” terminology to describe this, or other words. The display technology exists (obviously), so most of the remaining work is about product presentation, making it simple/comprehensible, etc.


I thought that might be the case but then if there is no sync that means the time counter will be either incorrect or disabled which reduces the usefulness of this feature to me.

No…it doesn’t mean that at all.


Alright cool, can’t wait then. Thanks Brian.

So, in effect, you are creating a video only endpoint. Can this be expanded to PC’s and other devices used in Home Theaters? For example, I’m playing audio to my SB3 endpoint and also sending the video to RoonBridge on a HTPC connected to a TV. Why keep all the fun for Chromecasts? :grinning:

1 Like

The Chromecast UI that you can see today was built on web standards and is displayable by any modern web browser. What’s missing is a way to configure it/kick it off in some of these other situations.

That will come with time–Chromecast was just the first/easiest target, and we really needed to do a nice display to consider the Cast feature complete.


That feature, been able to cast songs-info-cover-pictures to a regular chromecast while audio streaming to a Chromecast audio or other audio zone, would be literaly awesome. I´m actually streaming audio to a chromecast audio in the kitchen and share the roon remote screen of an Android table to a regular chromecast connected to a monitor close to the kitchen´s speakers. It works, but certainly not as easy, elegant, visual and clean as the new regular-chromecast visual feature you´re talking about Brian. Hope it´ll be ready sooner than later :). Loving Roon so far (six months using it). Thanks to all the team for your work!


Brian, how about having that display functionality through HDMI too (no chromecast)?

I am using Nucleus via HDMI into my processor in my home theatre and it would be neat to be able to see “something” like pictures on the theatre screen while listening. I amsure plenty of HT users would really like that as currently only a DOS lookalike message displays.

Christmas present? :slight_smile: Hope you can make it happen! Thank you!

1 Like