Sign Up for Free

RunKit +

Try any Node.js package right in your browser

This is a playground to test code. It runs a full Node.js environment and already has all of npm’s 400,000 packages pre-installed, including @hola.org/videojs-contrib-media-sources with all npm packages installed. Try it out:

var videojsContribMediaSources = require("@hola.org/videojs-contrib-media-sources")

This service is provided by RunKit and is not affiliated with npm, Inc or the package authors.

@hola.org/videojs-contrib-media-sources v3.1.0-12

A Media Source Extensions plugin for video.js

**Table of Contents** *generated with [DocToc](https://github.com/thlorenz/doctoc)*

videojs-media-sources

A Media Source Extensions shim for video.js.

Media Source Extensions (MSE) is a W3C draft specification that makes it possible to feed data directly to a video element. MSE allows video developers to build functionality like adaptive streaming directly in javascript.

Getting Started

On browsers that natively support Media Source Extensions, the HTML implementation will be used. If you're running in an environment without MSE, a Flash-backed polyfill will be used. Currently, the Flash polyfill only supports video content encoded in the FLV file format. For information on how FLVs are structured, Adobe hosts the latest version of the spec on their site.

The Flash polyfill attempts to balance throughput to the FLV with end-user responsiveness by asynchronously feeding bytes to the SWF at a fixed rate. By default, that rate is capped at 4MB/s. If you'd like to play higher bitrate content, you can adjust that setting:

// 8MB/s at 60fps
videojs.MediaSource.BYTES_PER_SECOND_GOAL = 8 * 1024 * 1024;

Setting the BYTES_PER_SECOND_GOAL too high may lead to dropped frames during playback on slower computers.

Check out an example of the plugin in use in example.html.

Options

You can configure some aspects of the MediaSource polyfill by specifying a hash of options when you construct it:

var mediaSource = new videojs.MediaSource({ mode: 'html5' });

mode

Type: string Values: 'auto', 'html5', 'flash' Default Value: 'auto'

How to determine the MediaSources implementation to use. With the default value of auto, the presence of native MediaSources is detected at construction time and they're used if available. Choosing html5 or flash will force the use of that respective MediaSource implementation, even if it does not appear the browser supports it.

Release History

  • 1.0.0: throw an error if appends are called during an update
  • 0.3.0: Delegate SourceBuffer.abort() calls to the SWF
  • 0.2.0: Improve interactivity by batching communication with Flash.
  • 0.1.0: Initial release

License

See LICENSE-APACHE2.

RunKit is a free, in-browser JavaScript dev environment for prototyping Node.js code, with every npm package installed. Sign up to share your code.
Sign Up for Free