[go: nahoru, domu]
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.

Sign up for GitHub

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

Jump to bottom

Chromecast (Ultra, Gen3,...) VOD playback stop #7395

Open
Iragne opened this issue Oct 4, 2024 · 3 comments · May be fixed by #7446
Open

Chromecast (Ultra, Gen3,...) VOD playback stop #7395

Iragne opened this issue Oct 4, 2024 · 3 comments · May be fixed by #7446
Assignees
@Iragne
Labels
platform: Cast Issues affecting Cast devices priority: P2 Smaller impact or easy workaround type: bug Something isn't working correctly
Milestone
v4.12

Comments

@Iragne
Copy link
Contributor
Iragne commented Oct 4, 2024

Have you read the Tutorials?
Yes

Have you read the FAQ and checked for duplicate open issues?
Yes

If the question is related to FairPlay, have you read the tutorial?

NO

What version of Shaka Player are you using?
Latest + 4.9 latest

What browser and OS are you using?
Chrome cast when casting

Please ask your question

On the following devices, we experience playback freeze with the default shaka configuration on the simple big buck bunny.
The only option to make the stream play until the end was to initialSegmentLimit at 50.

Today we are not 100% sure of this impact but it clearly solve our issue on low performance devices.

My questions are the following

  • What should be a correct value and what is the impact of this initialSegmentLimit at 50
  • Second, should we set automatically that value at 50 for those following devices
@Iragne Iragne added the type: question A question from the community label Oct 4, 2024
@Iragne Iragne changed the title Chrome cast (Ultra, Gen3,...) VOD playback stop Chromecast (Ultra, Gen3,...) VOD playback stop Oct 4, 2024
@joeyparrish
Copy link
Member

manifest.dash.initialSegmentLimit limits how many segments are generated in memory during the initial parsing of a DASH manifest. You may lower it to reduce startup memory at the expense of the amount of content that can be seeked on startup of a live stream. You may also want to consider manifest.availabilityWindowOverride, which limits the seek range. These are both for tuning live content.

Does this help?

@Iragne
Copy link
Contributor Author
Iragne commented Oct 6, 2024 •
edited
Loading

Thanks @joeyparrish Yes we are considering it for live. My point was, should we set manifest.dash.initialSegmentLimit to a low value for any Chromecast platform by default. Today on Ultra cc3 ..., we can't even play a vod with default setting.

Happy to release a PR if needed

@avelad
Copy link
Member
avelad commented Oct 18, 2024

@Iragne please create a PR with the change. thanks!

@avelad avelad added type: bug Something isn't working correctly priority: P2 Smaller impact or easy workaround platform: Cast Issues affecting Cast devices and removed type: question A question from the community labels Oct 18, 2024
@avelad avelad added this to the v4.12 milestone Oct 18, 2024
@Iragne Iragne linked a pull request Oct 20, 2024 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Iragne Iragne

Labels
platform: Cast Issues affecting Cast devices priority: P2 Smaller impact or easy workaround type: bug Something isn't working correctly
Projects
None yet
Milestone
v4.12
Development

Successfully merging a pull request may close this issue.

fix(DASH): Update Configuration for Chromecast devices Iragne/shaka-player
3 participants
@Iragne @joeyparrish @avelad