Multi-instance Live TV: API and client proposal #18483
PietroS-ITA
started this conversation in
Feature Proposals
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
The existing feature request #3503 already asks for multiple named Live TV views for different purposes. This discussion is a technical follow-up, not a duplicate feature request.
Current behavior
Jellyfin can configure multiple tuner hosts and listings providers, but the server stores them in one global Live TV configuration. It exposes one internal Live TV view and the
/LiveTv/...APIs operate on the aggregate.ILiveTvServicesupports backend integrations; it does not create independently navigable Live TV views.The clients also need changes. Jellyfin Web has a fixed Live TV route. Android TV and Roku have native Live TV flows that call the global APIs. Android mobile, iOS, webOS and Tizen primarily use or package the Web client.
Relevant code: LiveTvOptions, LiveTvManager, UserViewManager, LiveTvController, Web Live TV route, Android TV channel loading, and Roku Live TV API.
Proposed behavior
Feedback requested
Before I start a cross-repository implementation, I would like maintainer guidance on the model and API boundary:
I am interested in implementing this and can prepare the server and client changes once the project agrees on the compatibility and API approach.
All reactions