Using URL Parameters and Embed API for Custom Players

The standard IBM Watson Media embed offers an easy and fast way to put the IBM Watson Media player on your own site with no coding needed, except for a simple copy and paste. For information on standard embedding, please see How to embed a stream or video on your site This article covers advanced embedding functions and customizing the player.

Using URL Parameters with the IBM Watson Media player

You can override the default behavior of the embedded player by using URL parameters.

For example, embedding the player with autoplay=true will make the player start automatically when it is loaded on the page. Or embedding the player with volume=0 will mean the player will always start with the volume completely off.

By default the channel or video title is shown on the bottom left corner of the player. With this parameter you can hide it.

true

wmode

Flash wmode parameter override.

opaque

available values: direct, opaque, transparent, window. Parameter does not apply for HTML5 player.

forced-quality

Sets default stream playback quality.

low,med,high

Available values: low, med, high. Playback starts with the highest, medium or lowest available quality/resolution

Using Javascript Embed Player API to control the IBM Watson Media player

The IBM Watson Media Javascript Embed Player API allows you to control the action of the player embedded in your webpage and also listen for events happening in the player to control other elements of your webpage. This could be used for any of the following applications:

Changing the player dynamically to switch between live streams or recorded video content

Changing the state of the player based on other actions the user takes on your webpage (or inside a mobile experience) for example, you could automatically pause or mute a live stream when the user interacts with other media on your page.

Listening to events inside the player such as when a recorded video reaches its conclusion so that you could change the page state dynamically based on the video content.

Polling a current player status, such as the concurrent viewer count, to display this elsewhere on the page, or program actions to occur based on it.

Developing your own custom interface and look for the player to replace the default player controls (chrome)