Dash 4.5.2, HLS 1.2.9 working with Virtual Channel #4
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When trying to use uapi.js to create the Virtual Channel demo page, I realized that dash 4.0 and also HLS.js seemed to not support Virtual Channel transitions.
So, I updated the players to the latest version and they now seem to work.
Updating HLS.js was straightforward.
Updating Dash.js needs some tweaking because of the breaking API changes introduced in version 4
Shaka strangely works with Virtual Channel in the public shaka demo page but the same player in uapi does not. It must be due to some settings (!?) and I did not try to fix it for the moment.
Jamie/Dirk, I've seen you both had worked on updating players recently and there are also other branches opened for this. Maybe you want to review before merging this?