Does this break non-ultra chromecasts?
InAnimaTe opened this issue · 4 comments
Just wondering if using this profile (thanks so much for this btw) breaks other Chromecast's which might not have as much support as the Ultra?
Hello @InAnimaTe
I don't have non-Ultra Chromecast to test it, but I think it can prevent some high-end files to be read on regular Chromecast (4k, DTS pass-thru…), if those files can be read on Ultra ones.
The main issue on Plex still is that we cannot have separate Profiles for each of these.
As a tangent, I recommend updating the README to state that as I had the same question.
I tend to agree with @eduncan911 on that. I've decided not to use this or else it breaks compatibility for those clients.
I think the best solution to this problem is to tune your app's transcode settings prior to playing that media, which is a massive PITA but really the only way.
@ambroisemaupate have you been tracking any issue or ticket with Plex on this getting fixed (other than this)? Would like to know without drooling over the changelog if they've even attacked this problem yet.
You can actually have both:
- This config file to support your one Chromecast Ultra connected to a 4K system
- Handbrake (transcode) lower res 1080p versions for your other Chromecasts.
Then, when casting to a lower res Chromecast, you can select which Version to play within Plex.
It's a limitation long complained about in the Plex forums - like, for 3 years that their "Chromecast Profile" is a single one-size-fits-all config, and they should split it up into multiple files.
This config file will make your Plex server support all Chromecast versions and direct play almost all of it, Ultra and originals. It's up to you what media you play on it. So, if you have lower res Chromecasts, make sure you transcode your media to what those devices will support.