> For the complete documentation index, see [llms.txt](https://docs.cstplus.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cstplus.org/documentation/guides/live-playout-linear-tv-control-room.md).

# Live Playout (Linear TV control room)

Live Playout is the real-time control room. Where a normal channel renders a fixed 24/7 loop, Live Playout lets you run a channel like a broadcast gallery: cut between clips, take graphics to air, pause, and switch sources live, all without restarting the stream.

Use it for shows that need a human in the loop: live events, manual playout, breaking-news overlays, or a channel where you want to change graphics on the fly.

***

### Where to find it

Open **Linear TV** in the sidebar and pick a channel. You get a control room with a preview, a playlist, the on-air state, and a row of graphics templates from CG Studio.

***

### How it works

Live Playout keeps one continuous output running. Underneath, a base video plays from your playlist while a real-time compositor draws CG graphics on top of it. Because the output never stops, every action (cut, take graphic, pause) happens seamlessly, with no black frame and no player reconnect.

| Action                   | What happens                                               |
| ------------------------ | ---------------------------------------------------------- |
| Go live                  | Starts the continuous playout + compositor for the channel |
| Cut to clip              | Switches the base video to the selected clip               |
| Take graphic (CG to air) | Composites a saved graphic over the live picture           |
| Apply                    | Updates the on-air graphic seamlessly (no restart)         |
| Pause / Play             | Freezes or resumes the live programme                      |
| Stop                     | Ends the live session                                      |

***

### Going live

**Step 1: Build the playlist**

Add clips to the channel's playlist. Each entry is a file that plays as the base video.

**Step 2: Choose the source**

Play from the playlist, from a live input (an incoming stream URL), or mirror another channel's output.

**Step 3: Go live**

Click **Go Live**. The channel starts its continuous playout and the preview shows what is on air.

**Step 4: Take graphics**

Select a template from the graphics row and take it to air. Change or clear it at any time; the picture never drops.

{% hint style="info" %}
Graphics come from CG Studio. Design and save them there first, then take them to air here.
{% endhint %}

***

### Bindings and hotkeys

The control room supports keyboard shortcuts and MIDI bindings so you can operate it like a hardware panel: bind a key or a MIDI pad to cut, take a graphic, pause, or clip-cut. This keeps your hands off the mouse during a live show.

***

### Live text

A graphic's text can update while it is on air. Type new text and apply it, or let an EPG-driven plate fill itself from the channel's programme guide. Nothing about the update interrupts the stream.

{% hint style="warning" %}
Live Playout runs a real-time compositor per channel, which is more CPU-intensive than a plain rendered loop. Size your server for the number of channels you intend to run live at once. See System requirements.
{% endhint %}

***


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.cstplus.org/documentation/guides/live-playout-linear-tv-control-room.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.