Getting Started

Open Live Studio is the browser-based production controller for the Open Live platform. It provides a collaborative interface for managing live productions, controlling sources, switching video, mixing audio, and coordinating broadcast workflows entirely from the browser.

Open Live Studio is the frontend component of the Open Live stack. It connects to an Open Live backend instance and must be deployed as a separate service. If you are setting up Open Live from scratch, follow the Open Live Setup Guide which walks through deploying all components in the right order.

Prerequisites

  • A running Open Live backend instance. The backend must be fully started before you create the studio instance.

Step 1: Get your Open Live backend URL

Navigate to the Open Live service and click on your running instance. Copy the instance URL — it will look like:

https://<name>.eyevinn-open-live.auto.prod.osaas.io

Step 2: Create an Open Live Studio instance

Navigate to the Open Live Studio service and click Create open-live-studio.

Field Value
Name A name for this studio instance
OpenLiveUrl The Open Live backend URL from Step 1

When the instance status turns green, click on its card to open the production controller in your browser.

Using Open Live Studio

From the studio interface you can:

  • View and activate live productions
  • Switch video sources and control transitions (PGM/PVW bus, T-bar, FTB, DSK)
  • Mix and monitor audio with per-channel faders, aux sends, groups, and metering
  • Configure Picture-in-Picture (PiP) slots and zones
  • Set a program start time and monitor on-air elapsed time
  • Collaborate with other producers connected to the same backend

Production limits

Resource Maximum
Sources (video inputs) 16
Outputs 8
AUX buses 8
Group buses 8
PiP slots 4

All state is persisted via the Open Live backend API — the studio itself is stateless and multiple producers can connect simultaneously.

Troubleshooting

If you run into issues, the OSC AI assistant can help diagnose your instance — describe your problem and it will inspect your configuration and logs.

Resources