-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
fix: Disable seek retry cooldown on most platforms #7010
Conversation
Previously, we added a 1 second "cooldown" period between attempts to perform a corrective seek. This was for the benefit of old v1 Chromecasts, which found the process of seeking so slow that they would sometimes get stuck in an infinite loop trying to start a presentation. However, that cooldown period was causing issues in some situations during seeking, so this PR removes the restriction on everything but pre-Android Chromecast devices. Issue shaka-project#4393
Based on some practical testing I did, it seems like v2 Chromecasts are probably safe from this issue? |
Incremental code coverage: 65.62% |
static isSeekingSlow() { | ||
const Platform = shaka.util.Platform; | ||
if (Platform.isChromecast()) { | ||
if (Platform.isAndroidCastDevice()) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
And Fuchsia?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For reference...
I didn't have a Fuchsia device to test with, so I can't say for sure it's not a problem in them. It's probably fine, I was just being purposefully conservative with this change.
@shaka-bot test |
@avelad: Lab tests started with arguments:
|
Previously, we added a 1 second "cooldown" period between attempts to perform a corrective seek. This was for the benefit of old v1 Chromecasts, which found the process of seeking so slow that they would sometimes get stuck in an infinite loop trying to start a presentation. However, that cooldown period was causing issues in some situations during seeking, so this PR removes the restriction on everything but pre-Android Chromecast devices. Fixes #4393 Fixes #5202 --------- Co-authored-by: Álvaro Velad Galván <[email protected]>
Previously, we added a 1 second "cooldown" period between attempts to perform a corrective seek. This was for the benefit of old v1 Chromecasts, which found the process of seeking so slow that they would sometimes get stuck in an infinite loop trying to start a presentation. However, that cooldown period was causing issues in some situations during seeking, so this PR removes the restriction on everything but pre-Android Chromecast devices. Fixes #4393 Fixes #5202 --------- Co-authored-by: Álvaro Velad Galván <[email protected]>
Previously, we added a 1 second "cooldown" period between attempts to perform a corrective seek.
This was for the benefit of old v1 Chromecasts, which found the process of seeking so slow that they would sometimes get stuck in an infinite loop trying to start a presentation.
However, that cooldown period was causing issues in some situations during seeking, so this PR removes the restriction on everything but pre-Android Chromecast devices.
Fixes #4393
Fixes #5202