Play an asset
Learn how to play assets with Livepeer
In this guide, we demonstrate how to play back assets in your application.
We do not recommend using “CORS-enabled” API keys - they will be deprecated in an upcoming release. We recommend making requests from your backend to the Livepeer Studio API.
Using the Livepeer React Player
The example below shows how to use the Livepeer React
Player
to view a video asset, with some custom
styles to demonstrate what’s possible.
Play Video
This guide assumes you have configured a Livepeer JS SDK client with an API key.
We can use the Player
with a playbackId
, which we
created previously when uploading a video asset.
Check out the Player docs for more details on the video primitives you can use to build custom viewing experiences.
Using your own player
Using Livepeer UI Kit is the recommended way to play back an asset - it handles prioritizing HLS & MP4 renditions, errors from the API, and is composable to allow advanced video apps without writing a custom integration. However, if you want to use an alternative, you can do so by following the instructions below.
Fetch the playback URL
To play back a livestream in other players, you’ll need to fetch the playback URL(s). By default, all content has an HLS endpoint. HLS is a protocol that allows you to stream video and audio content over HTTP.
Short-form assets will also have one or more MP4 source URLs.
Below, we show how to do this in Typescript using the playback info API endpoint, but we have a similar interface across all SDKs.
Source playback
When an asset is initially created, we will provide a “source playback” URL in the list returned from the playback info endpoint. This is a non-transcoded version of the asset that can be played immediately, while processing happens in the background. The playback info endpoint will then automatically update with the transcoded renditions when processing is completed.
Handling various playback sources
The playback info endpoint can return multiple sources in the response. These may include short form MP4 playback URLs, which allow you to obtain alternative URLs for your video asset to enable applications (and CDNs) to cache short videos for instant playback of subsequent videos. This means that viewers can experience instant time-to-first-frame (TTFF) when watching short videos.
It is important to note that short form playback URLs are only available for video assets that are less than 2 minutes in duration.
If there are MP4 renditions or HLS playback available, the playback info endpoint will return:
There are multiple renditions you can choose from, and it is up to you to decide how you want to prioritize each source for your custom player.
When you make a request for playback URLs, in the response MP4 URLs are always listed before HLS URLs. Additionally, each MP4 URL includes additional metadata about the video, such as its width, height, bitrate, and size. This metadata can be useful for mobile applications that want to optimize playback quality and size based on the viewer’s device and network conditions.
Use the playback URL in a player
You can use the playback URL with any video player that supports HLS. Here is a list of popular players that support HLS:
- Video.js
- Plyr.io
- JW Player
- Bitmovin Player
- HLS.js (requires custom logic to wire to a video element)
Here is an example of how to use the playback URL in video.js player.
Embeddable Player
Livepeer Studio maintains an embeddable version of the Livepeer Player that is suitable for iframing.
If you are using React, consider using Livepeer UI Kit instead.
This is one of the easiest ways to play back a video on your website. You can embed the player by using the below code snippet.
You can replace the PLAYBACK_ID
with your video’s playback id.
Configuration
If you are using the iframe for livestreams as well as assets, see the livestream embed docs for how to set up low latency, clipping, and other configs for streams.
You can override the default muted
and autoplay
behavior with &muted=false
and/or &autoplay=false
. These are set to true by default. Looping can also be
set with &loop=true
.
Was this page helpful?