Menu

Expand
Rate this page:

JavaScript Player SDK Changelog

The Twilio Player JavaScript SDK uses Semantic Versioning.

1.0.1 (November 4, 2021)

Changes

  • The Player's default HTMLVideoElement is now configured for inline playback on iOS browsers. If you want to attach your own HTMLVideoElement to the Player, then we strongly recommend that you do the same as shown below. (VIDEO-7515)
const videoElement = document.querySelector('div#container > video');
videoElement.playsInline = true;
player.attach(videoElement);

1.0.0 (October 19, 2021)

Changes

1.0.0-preview.10 (October 5, 2021)

Changes

  • Moved Player to the Live namespace. Now, you can import the SDK APIs as shown below. (VIDEO-7097)
// TypeScript or ES Modules
import { Player } from '@twilio/live-player-sdk';

// CommonJS
const { Player } = require('@twilio/live-player-sdk');

// <script src="path/to/twilio-live-player.js">
const { Player } = Twilio.Live;

Bug Fixes

  • Fixed a bug where the Player, when running on Firefox, did not transition to the ended state when a live stream was ended. (VIDEO-6015)

1.0.0-preview.9 (August 4, 2021)

Changes

Breaking API Changes

  • Player.connect(token, options) has been updated to accept a Twilio Access Token with a PlaybackGrant whose type is a JSON object instead of a stringified JSON. Providing a playback grant as stringified JSON as recommended from 1.0.0-preview.5 through 1.0.0-preview.8 will result in an AccessTokenInvalid error.

API Updates

  • Player.connect(token, options) has been updated to accept a token with a RecordingPlaybackGrant to allow playback of recorded media. This is currently supported on Chrome browser.

  • Added player.duration property. The duration is Infinity if the media is a live stream, otherwise a positive number in seconds.

  • Added player.seekTo(position) for changing the player's position to a specified time in seconds. The player state might change to buffering if there is not enough buffered content in the specified position. This is only supported for recorded media and will throw an error if invoked on a live media. This is currently supported on Chrome browser.

New Player Events

  • Added Player.Event.DurationChanged event which is raised whenever Player.duration property changes.

  • Added Player.Event.SeekCompleted event which is raised when the player seeked to a given position (as requested by Player.seekTo).

New Telemetry Events

Bug Fixes

  • player.setVolume(...) will now emit a Player.Error for any invalid parameters.

1.0.0-preview.8 (July 29, 2021)

Changes

  • The SDK now officially supports playing video contents of a live stream. Check out the README for more information on how to render a live stream.

1.0.0-preview.7 (July 28, 2021)

Changes

  • The SDK will now retry connecting to a stream when a recoverable error is detected upon the first invocation of Player.connect(...).

1.0.0-preview.6 (July 22, 2021)

Changes

  • Player.Error now includes an optional explanation property that provides more details about the error that occurred.

  • Player.Error now includes constant definitions for all the unique error code values.

1.0.0-preview.5 (July 9, 2021)

Breaking API Changes

  • Player.connect(token, options) has been updated to accept a Twilio Access Token with a PlaybackGrant. Please note that the 1.0.0-preview.5 Player SDKs are not backwards compatible with the previously generated AccessTokens.

  • Removed the following properties: Player.sid, Telemetry.Data.Connection.playerSid, Telemetry.Data.Playback.playerSid, Telemetry.Data.PlaybackQuality.playerSid, Telemetry.Data.PlaybackState.playerSid and Telemetry.Data.TimedMetadataTelemetry.playerSid.

1.0.0-preview.4 (July 1, 2021)

Improvements

API Updates

Added a static property Player.isHighLatencyReductionEnabled that is true by default. The Player SDK considers a player.liveLatency value greater than 3 seconds as an occurence of high latency. When this property is enabled, the Player SDK will periodiocally inspect player.liveLatency and perform the following when high latency is observed:

  1. If the live latency is between 3 and 5 seconds, the Player will increase the playback rate to a value that should not be perceptible to a user. The increased playback rate will allow the Player to catch up to the live source, and will be reverted once the live latency drops below 3 seconds. Application of this strategy may result in audio pitch distortion.

  2. If the live latency is greater than or equal to 5 seconds, the Player will seek ahead to near the end of the Player's buffered content. The user will notice skips in the media content when this strategy is applied.

New telemetry events

Added two new telemetry events: HighLatencyReductionApplied and HighLatencyReductionReverted.

1.0.0-preview.3 (June 11, 2021)

Changes

  • The Telemetry API enables you to subscribe to event and metric data reported by the Player SDK. This data can be used to track stream quality, triage issues, and better understand your application's usage of the Player SDK. The current list of reported events and metrics can be found here. You can subscribe to them as shown below. (VIDEO-5620)
import { Player } from '@twilio/player-sdk';

Player.telemetry.subscribe(data => {
  // Do something with the data.
});

If you want to subscribe only to certain events and metrics, you can pass a predicate as a second argument to Player.subscribe() as shown below.

import { Player } from '@twilio/player-sdk';

// Report to your analytics provider whenever the live stream's latency is
// greater than or equal 5 seconds.
Player.telemetry.subscribe(data => {
  analytics.send(data);
}, data => {
  return 'playerLiveLatency' in data && data.playerLiveLatency >= 5;
});
  • Player.quality is now settable, which means you can change the quality of the live stream by setting it to one of the Quality objects in Player.availableQualities. (VIDEO-5594)
  • Added a new property streamerSid to Player, which identifies the PlayerStreamer to which the Player is connected to. (VIDEO-5594)

1.0.0-preview.2 (June 1, 2021)

Improvements

  • Fixed an issue with audio playback of malformed mono input streams. (VIDEO-5334)
  • Fixed a rare playback error that could occur when playing content outside the live HLS window. (VIDEO-5334)
  • Improved the Player's ability to play standard HLS live and recorded streams. (VIDEO-5334)
  • Improved the accuracy of Player.liveLatency. (VIDEO-5334)
  • Improved the ABR (adaptive bitrate streaming) algorithm to increase video quality more quickly when network connections improve. (VIDEO-5334)
  • Improved player stability by reducing occurrences of rare crashes. (VIDEO-5334)

Changes

  • Added a new value Off to the LogLevel enum, which allows you to disable logging for all the Player instances running in your application. (VIDEO-5267)
  • Added a new API setLogLevel() to the Player class, using which you can change the log level of all the Player instances running in your application. (VIDEO-5267)
  • Moved logLevel from the Player instance to the Player class, so that it now represents the log level of all the Player instances running in your application. (VIDEO-5267)
  • Moved the following APIs and types from the Player SDK exports to the Player class:
    • connect()
    • isSupported
    • version
    • VideoDimensions
    • TimedMetadata

The Player class is now the only export of the SDK. (VIDEO-5267) - Player.Options now has only one property playerWasmAssetsPath, which points to the folder where the application hosts twilio-player-wasmworker-x-y-z.min.js and twilio-player-wasmworker-x-y-z.min.wasm, where x.y.z is the version of the files. (VIDEO-5403)

1.0.0-preview.1 (May 6, 2021)

The Twilio Player SDK allows you to play a live stream in your web application.

Live Streaming a Video Room

Please refer to the Twilio Live guide for starting a live stream of a Video Room from your application server. At the end, you will have an AccessToken which you can use to join the live stream.

Checking for Browser Support

You can check whether the SDK supports the browser on which the application is running as shown below:

import { isSupported } from '@twilio/player-sdk';

if (isSupported) {
  /* Load your application */
} else {
  /* Inform the user that the browser is not supported */
}

Joining a Live Stream

You can now join the live stream from your application using the AccessToken as shown below:

import { connect } from '@twilio/player-sdk';

const {
  host,
  protocol,
} = window.location;

// Join a live stream.
const player = await connect('$accessToken', {
  vendorWasmBinaryPath: `${protocol}//${host}/path/to/amazon-ivs-wasmworker.min.wasm`,
  vendorWasmWorkerPath: `${protocol}//${host}/path/to/amazon-ivs-wasmworker.min.js`,
});

In order for the SDK to run, your application must host the following assets which are available in node_modules/@twilio/player-sdk/dist/build:

  • amazon-ivs-wasmworker.min.wasm
  • amazon-ivs-wasmworker.min.js

Live Stream Playback

You can perform the following playback actions on the live stream:

// Start playback.
player.play();

// Pause playback.
player.pause();

// Mute audio.
player.isMuted = true;

// Unmute audio.
player.isMuted = false;

// Set volume.
player.setVolume(0.5);

Rendering the Live Stream

In order to render the live stream, you can use the default HTMLVideoElement created by the Player in your application as shown below:

const container = document.querySelector('div#container');
container.appendChild(player.videoElement);

Alternatively, if you want to render the live stream in your own HTMLVideoElement, you can do so as shown below:

const videoElement = document.querySelector('div#container > video');
player.attach(videoElement);

Disconnecting from the Live Stream

You can disconnect from the live stream as shown below:

player.disconnect();

This is a terminal operation on the Player, which is no longer useful to the application.

Rate this page:

Need some help?

We all do sometimes; code is hard. Get help now from our support team, or lean on the wisdom of the crowd by visiting Twilio's Community Forums or browsing the Twilio tag on Stack Overflow.

        
        
        

        Thank you for your feedback!

        We are always striving to improve our documentation quality, and your feedback is valuable to us. Please select the reason(s) for your feedback or provide additional information about how we can improve:

        Sending your feedback...
        🎉 Thank you for your feedback!
        Something went wrong. Please try again.

        Thanks for your feedback!

        Refer us and get $10 in 3 simple steps!

        Step 1

        Get link

        Get a free personal referral link here

        Step 2

        Give $10

        Your user signs up and upgrade using link

        Step 3

        Get $10

        1,250 free SMSes
        OR 1,000 free voice mins
        OR 12,000 chats
        OR more