What’s the latency between the stream and the viewer?

Currently between 8 - 16 seconds.

What’s the difference between Livepeer Studio and Livepeer.org? Which one should I use for my hack?

Livepeer Studio is the hosted gateway to the Livepeer Network, which is represented at Livepeer.org. For your hack, you’ll most likely be using Livepeer Studio. If you think you should be using Livepeer.org for any reason, reach out to us to confirm.

How do I stream into Livepeer? How do my viewers watch it?

Check out Create a Livestream. You’ll need an encoder like OBS to stream into Livepeer and a HTML5 Player to view the stream.

I need to see how many viewers are watching my stream. How do I do that?

This isn’t functionality that Livepeer has out of the box at the moment, but some HTML5 players do support viewer count. Although many of these are players you have to pay to use, including JWPlayer and TheoPlayer.

Another (slightly less accurate) way of showing viewership - simply track how many people are viewing the webpage. This can be done by using tools like socket.io.

Do I need to build a backend or can I just send streams to Livepeer on the fly?

You’ll need to create a backend to use Livepeer’s API to generate ingest URLs and a stream key, which you’ll need to stream. Unless you have a single stream, in which case you can just create it in the dashboard and statically include the stream key in your broadcasting and playback applications.

I’ve hit a CORS error. What should I do?

This is usually because you are using the Livepeer.org docs or you are trying to call the Livepeer Studio API directly from your web application.

The Livepeer Studio API can only be used from a backend which can hold your API key securely without exposing it on a web page. If you already have a backend, you should create your own API with your frontend and then give access to the Livepeer.Studio API with your own business logic. If you don’t have a backend yet, you can get started quickly with the Web API Proxy to allow creating streams from your frontend and saving them on the user’s browser.