Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create ShakaPlayer Controller #758

Merged
merged 5 commits into from
Jan 3, 2024

Conversation

juanfadev
Copy link
Contributor

ShakaPlayer is a much more versatile and improved player over the default one. It allows for HLS and DASH play with custom arguments such as DRM. I have included an example of this DRM usage using ClearKey but Widevine or others can be used.

Create ShakaController to interact with ShakaPlayer
@juanfadev
Copy link
Contributor Author

@balloob could you please check this PR or get someone to check it? I think it will improve a lot the posibilities for playing any media.

@@ -0,0 +1,131 @@
"""
Example on how to use the BubbleUPNP Controller to play an URL.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Stale docstring

@emontnemery
Copy link
Collaborator

emontnemery commented Nov 21, 2023

Is the shaka player chromecast interface documented somewhere, what arguments does it accept and so on?

We document the bubble upnp player as a backup in the Home Assistant documentation, should we document also the ShakaPlayer?

@Lamarqe
Copy link

Lamarqe commented Dec 21, 2023

Google says, they will switch to Shaka player as the default media player as soon as its mature enough:
https://developers.google.com/cast/docs/web_receiver/shaka_migration

The Web Receiver SDK will transition to using Shaka Player as the default player for HLS content playback. This will be done in a phased approach to guide partners through the migration process.

  1. Oct '22 The Cast Web Receiver SDK introduces APIs to opt-in to play HLS content on Shaka Player.
  2. H2 '24 The Cast Web Receiver SDK changes the default player to Shaka Player for HLS content playback.

I dont think pychromecast needs to be extended while shaka player is still in this beta-ish phase.
If you want to use it, you can still do it, based on a custom controller.

@emontnemery emontnemery merged commit f50bbfd into home-assistant-libs:master Jan 3, 2024
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants