Playing video and audio has been available in web applications without plugins for a few years now, but the basic features offered have really only been useful for playing single whole tracks. We can't, for example, combine/split arraybuffers. Streaming media has up until recently been the domain of Flash, with technologies like Flash Media Server serving video streams using the RTMP protocol.
With Media Source Extensions (MSE), this is changing. MSE allows us to replace the usual single track
src value fed to media elements with a reference to a
MediaSource object, which is a container for information like the ready state of the media for being played, and references to multiple
SourceBuffer objects that represent the different chunks of media that make up the entire stream. MSE gives us finer grained control over how much and how often content is fetched, and some control over memory usage details, such as when buffers are evicted. It lays the groundwork for adaptive bitrate streaming clients (such as those using DASH or HLS) to be built on its extensible API.
Creating assets that work with MSE in modern browsers is a laborious process, taking both significant time, computing power, and energy. The usage of external utilities to massage the content into a suitable format is required. While browser support for the various media containers with MSE is spotty, usage of the H.264 video codec, AAC audio codec, and MP4 container format is a common baseline. MSE also provides an API for runtime detection of container and codec support.
If you do not require explicit control of video quality over time, the rate at which content is fetched, or the rate at which memory is evicted, then the
<source> tags may well be a simple and adequate solution.
Dynamic Adaptive Streaming over HTTP (DASH) is a protocol for specifying how adaptive content should be fetched. It is effectively a layer built on top of MSE for building adaptive bitrate streaming clients. While there are other protocols available (such as HTTP Live Streaming (HLS)), DASH has the most platform support.
DASH moves lots of logic out of the network protocol and into the client side application logic, using the simpler HTTP protocol to fetch files. Indeed, one can support DASH with a simple static file server, which is also great for CDNs. This is in direct contrast with previous streaming solutions that required expensive licenses for propriety non-standard client/server protocol implementations.
The two most common use cases for DASH involve watching content “on demand” or “live.” On demand allows a developer to take their time transcoding the assets into multiple resolutions of various quality.
Live profile content can introduce latency due to its transcoding and broadcasting, so DASH is not suitable for real time communication like WebRTC is. It can however support significantly more client connections than WebRTC.
<video>element, such as number of dropped or corrupted frames. Returned by the
SourceBufferwith kind, label, and language information for tracks that do not contain this information in the initialization segments of a media chunk.
MediaSourceobject that can then be specified as the
srcvalue of an HTML media element to play a media stream.
MediaSourceobject is played by an HTML media element, this property will return a
TimeRangesobject that contains the time ranges that the user is able to seek to.
VideoPlaybackQualityobject for the currently played video.
SourceBufferthat created the track in question.
|Media Source Extensions||Recommendation||Initial definition.|
|Basic support|| 31
|Android webview||Chrome for Android||Edge Mobile||Firefox for Android||Opera for Android||iOS Safari||Samsung Internet|
© 2005–2018 Mozilla Developer Network and individual contributors.
Licensed under the Creative Commons Attribution-ShareAlike License v2.5 or later.