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

Use CastPlayer using default receiver #528

Open
1 task
StaehliJ opened this issue May 6, 2024 · 1 comment
Open
1 task

Use CastPlayer using default receiver #528

StaehliJ opened this issue May 6, 2024 · 1 comment
Assignees
Labels
enhancement New feature or request
Milestone

Comments

@StaehliJ
Copy link
Contributor

StaehliJ commented May 6, 2024

As a user / integrator I want to play some content on my chromecast.

Acceptance criteria

  • When connected to a cast session, playback of some content is starting.
  • The cast receiver is the Media3 default.

Tasks

  • ...
@StaehliJ StaehliJ self-assigned this May 6, 2024
@StaehliJ StaehliJ converted this from a draft issue May 6, 2024
@StaehliJ StaehliJ added this to the Cast milestone May 6, 2024
@StaehliJ
Copy link
Contributor Author

StaehliJ commented May 6, 2024

When playing HLS fragmented mp4 and TS container format, we have to tell the receiver the format to use.

For video:

MediaInfo.setHlsVideoSegmentFormat(HlsVideoSegmentFormat.FMP4)

For audio:

MediaInfo.setHlsSegmentFormat(HlsSegmentFormat.FMP4)

Otherwise, the cast will load endlessly and plays nothing.

For urn content or content loaded by the receiver it should not be a issue but for url only it may be an issue. We can't store the information inside a MediaItem or if so we have to create a convention.

@defagos defagos moved this from 📋 Backlog to 🚧 In Progress in Pillarbox May 6, 2024
@MGaetan89 MGaetan89 added the enhancement New feature or request label May 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Status: 🚧 In Progress
Development

When branches are created from issues, their pull requests are automatically linked.

2 participants