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

Re-think gap-jumping and stall-detection #3673

Open
joeyparrish opened this issue Sep 29, 2021 · 6 comments
Open

Re-think gap-jumping and stall-detection #3673

joeyparrish opened this issue Sep 29, 2021 · 6 comments
Labels
priority: P2 Smaller impact or easy workaround type: enhancement New feature or request
Milestone

Comments

@joeyparrish
Copy link
Member

I believe gap-jumping and stall-detection could use a redesign. It's not clear that the current algorithms were built with the right requirements in mind.

Let's use this issue:

  1. to discuss requirements and decide what we should be designing/building
  2. to track progress on rebuilding gap-jumping and stall-detection

In #3188 (comment), I suggested:

I would like to get rid of the "small/large" gap concept, to always jump gaps by default, and to completely rethink the behavior and triggers of gap-jumping. I also think it would benefit from combining with stall detection.

Here are other issues that may be related to gap-jumping and could/should be solved by whatever we do next:

@joeyparrish joeyparrish added type: enhancement New feature or request priority: P2 Smaller impact or easy workaround labels Sep 29, 2021
@shaka-bot shaka-bot added this to the Backlog milestone Sep 29, 2021
@avelad
Copy link
Member

avelad commented Sep 30, 2021

I would also like to remind this problem: #3163 which happened only on some platforms.

@avelad
Copy link
Member

avelad commented Oct 7, 2021

@joeyparrish Do you think it would be possible to apply this also when we use the src= mode?

@joeyparrish
Copy link
Member Author

I could be wrong (I can't memorize the codebase any more 😁), but I thought gap-jumping and stall-detection were applied generically regardless of playback type. If they aren't yet, we can make that a requirement for the new system.

@OrenMe
Copy link
Contributor

OrenMe commented Oct 20, 2021

Would be great to get some of the ideas suggested taken into consideration.
For us the main issues are around playback on smart TVs where the play pause definitely doesn't always help and we have added our own mechanism to combine small seeks as well to get out of player getting stuck.

@beka-discovery
Copy link

What is the process of Redesigning the feature @joeyparrish? We might be able to contribute and possible stay on top of design and execution. As long as we have a clear understanding of the process and what you have in your head.

@zuzzurro
Copy link

As @beka-discovery I'm myself extremely interested in any news about this story. Do you guys have anything to say about the development?
I think I have seen in the changelog for 5.0 that you got rid of the big gap handling, is that change related to this issue?
Any news would be extremely welcome because we are suffering a lot from gap handling in SSAI ads.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority: P2 Smaller impact or easy workaround type: enhancement New feature or request
Projects
Status: To do
Development

No branches or pull requests

6 participants