Skip to main content

What is Playback?

When you stream video, you need two things: a way to send video (ingest) and a way for viewers to watch it (playback). This guide focuses on the playback side, how viewers watch your stream.

The Playback Paths

There are different playback paths you can use to watch your stream:

Direct WebRTC/WHEP (Ultra-Low Latency)

Best use case is for small audiences (under 1,000 viewers), interactive streams, real-time applications.

Workflow Diagram

HLS/DASH via CDN (Scalable)

Best use case is for large audiences, reliable playback, broad device support

Workflow Diagram

Livepeer Studio

Livepeer Studio supports both WebRTC and HLS protocols within a single workflow. Best use case for development and testing. Livepeer Studio can also be used on a smaller scale for production

Choosing the right playback path

Example Players for Playback

Eyevinn

As the SDP Offer/Answer exchange is WebRTC media server specific this WebRTC player is designed to be extended with Media Server specific adapters. You can either use one of the included media server adapters or build your own custom adapter. Visit Eyevinn Player

OvenPlayer

OvenPlayer is a JavaScript-based Player that can play Low Latency HLS (LLHLS) and WebRTC streams optimized for OvenMediaEngine. It provides various APIs, so you can build and operate your media service more easily. Visit OvenPlayer

HLS.js

HLS.js is a JavaScript library that allows you to play HLS streams in the browser. It is a port of the native HLS.js library for Node.js. Visit HLS.js

DASH.js

DASH.js is a JavaScript library that allows you to play DASH streams in the browser. It is a port of the native DASH.js library for Node.js. Visit DASH.js

Example Code