-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
With live streaming, shaka keeps refreshing previous manifest #369
Comments
It could be a caching issue. What exact sequence of events are you following? E.g.,
Or do you mean that after calling |
Ok I got it. It's happening because on every player.load call, I'm doing this:
Now I'm doing abr.stop() on the previous abr instance to avoid this problem. |
Ah, good catch. I see the problem in player.js now. |
* Set this.parser_ to the correct property in load() (stops old manifests from being fetched). * Stop load() from unloading first when the Player is a new instance. * Handle multiple repeated calls to load(). * Fully cleanup after partial loads. * Add additional destruction checks. Issue #369 Change-Id: I43d5ed90c8119b1040b87a0dc187f52738e1c683
@aletorrado This should be fixed in |
After switching between different live streaming manifests using
player.load('manifest.mpd')
, shaka keeps fetching previous manifests indefinitely.The text was updated successfully, but these errors were encountered: