Closed nielsvanvelzen closed 10 months ago
I'll work on the server part 👍
I can work on the web part in about a week or so, unless someone else volunteers to do the web part. It should be fairly easy with basic knowledge about the jellyfin-web codebase.
🍿
I've seen mentioned this kind of a change might make it into Jellyfin (server?) 10.9. Is that a reliable/achievable milestone? I don't entirely know how frequently minor version changes roll out for Jellyfin server/etc. So unsure what realistic napkin-math timeline to temper my anticipation with. Excited! :)
With half of the implementation already done this is extremely likely to be in 10.9 yes.
Closing as resolved. Both the server and client changes are merged for 10.9!
Will these settings be configurable via the webGUI for the Admin section of Jellyfin? In... addition to CLI? Also, how exactly can one know acceptable values for said fields? Since the "id" value seems to accept what I assume is git hashes, not sure exactly the best way a human can determine possible workable values in said fields (CLI/webGUI whatever).
No you cannot change the list of cast receivers via the webui/cli. You'll need to modify the configuration file. This is done because this configuration is only for advanced use cases like development or when self-hosting the receiver, both require a Google Cast developer account (which is not free) and the expectation is that not a lot of users will do this.
The ids are not git hashes, those are the cast receiver ids Google generates.
both require a Google Cast developer account (which is not free)
Well I didn't even know this part lol! That's absolute bonkers self-hosting that data (as opposed to pulling from github?) requires a Google Cast developer account. Does the github (current?) method involve a Google Cast developer account somehow? 🤔
The current method uses cast clients hosted by the Jellyfin team.
To ease cast client development and make it easier to use third-party/self hosted implementations I propose some changes to how we deal with the cast receiver id in the server/web. The main changes of this proposal are:
I'm searching for someone to tackle the server part of this proposal. I can do the web part myself (although if someone from the web team wants to do that, please do!).
Jellyfin server changes
Add "CastReceiverApplications" to system.xml
Stable (F007D354)
andUnstable (6F511C87)
(our current application ids)Add "CastReceiverApplications" to
/System/Info
endpoint Sample JSON:Clients should use the user preferred cast client or they must use the first returned application.
Add "CastReceiver" to UserConfiguration
Migrate the existing chromecastVersion property from the usersettings to the new user configuration property
Jellyfin web changes
This effectively supersedes #7 (which I noticed existed after I made this draft).