feat: added support to Apple managed media source #341
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.
Sources:
https://bitmovin.com/managed-media-source
https://caniuse.com/?search=media%20source (partially supported, is supported fully only in ipadOS)
Proposal:
Since iOS doesn't support Media Source Extensions API (MSE), but supports Managed Media Source API (MMS). These changes are intended to make
import { MediaSourceAppender } from "modelfusion-experimental/browser"to work even in iOS devices.From the blog bitmovin:
"As the MMS supports all methods the “old” MSE does, this is all to get you started (...)”
There are some new events exclusive to MMS that accordingly to the post can unleash the full potential of Apple API, but I did not implement in this PR for the sake of simplicity, since the goal of this PR is to support iOS devices.