Chromecast

[Encoder0]

I feel like I need to abandon using Jellyfin with Chromecast. I have the simplest setup, and it's barely functional.
Server (Windows PC) -> Android App Casting (Phone) -> Chromecast (built into tv)

Casting from chrome web browser on pc doesn't work anymore at all.

Casting from Android App:
Unstable build has been completely unfunctional for years now.
Stable has a bunch of bugs that make it difficult and painful to use.

• Will lose control or just freeze after being connected for about ~40mins or so
  
• Chromecast controls themselves don't show up in google home app, only in notification bar
  
• If you get a video to play, the now playing bar will slide up, video starts, and then the controls disappear (video still playing), only showing up after you play again
  

This is on top of the bigger problem like casting requiring secure contexts now (https certs), which I don't want to have to set up, and (allegedly) shouldn't be required for local network casting.
Why should I go through the effort of buying a cert, setting up a reverse proxy and/or intercepting my own chromecast's dns requests, when I can just spend 50$ on a CCWGT, and it just works™ because the androidtv app is being maintained?

Has Jellyfin team given up on Chromecast?

[Venson]

Hey @Encoder0,

Tbo Chromecast apart from 1st party apps kinda suck. That is my personal evaluation of that topic overall.

1. Unstable build is meant to be the rolling test of new features. Its by definition _Unstable_. Most forget that, think of it even pre-alpha piece of software. It ist mostly for testing new features.
2. The issue with the abort after some time i also have also observed on my YouTube app, i think its something with how your device handles apps that go to sleep
3. Requireing a secure context (https) is not something we control, but is a requirement from google. There is nothing we can do about it. you can however get a free SSL certificate from providers such as LetsEncrypt.
4. We have not given up on Chromecast, its unfortunately not perfect but its not our protocol to fix.

[ginger-tek]

Tbh, I got so tired of not being able to use casting properly with a reverse proxy (which honestly should not matter) out-of-the-box, that I decided to lookup the Chromecast API spec. I spent no more than 5 hours making a simple web interface JUST so I can cast from my JellyFin server using a reverse proxy: https://jellycast.gingertek.repl.co

Despite using the default receiver, it works. And it works without doing any of the confusing network address parsing that the official casting app does when running on the casting device. Maybe whoever originally made the implementation overengineered it, but you can look at the my code on Replit and see that this really isn't that complicated of a feature to have working.

"Well, why haven't you submitted any PR's then, huh?!" In Github responses, I've been discouraged to try fixing the existing repo, and to literally "just use the TV app"

[I-G-1-1]

I spent no more than 5 hours making a simple web interface JUST so I can cast from my JellyFin server using a reverse proxy: https://jellycast.gingertek.repl.co

can you please explain how to set up your "web interface" to use jellyfin with my chromecast devices (Google home, Google Hub, Google TV)?
As reverse proxy I'm using nginx on Debian. Jellyfin is also running on another Debian machine.

Thanks

[34626]

Is background activity allowed and have you set it not to optimized Jellyfin in battery settings?

I also use Chromecast, it works quiet well with up to 4k content..