> For the complete documentation index, see [llms.txt](https://unknown-56-works.gitbook.io/luigiscreen/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://unknown-56-works.gitbook.io/luigiscreen/control-studio/screens-live-control.md).

# Screens and Live Control

## Screen overview

Each screen icon represents its current state:

* live direct source
* playlist
* event
* paused
* stopped
* waiting or reconnecting
* source error

Its lore shows the current item, next queued or automatic item, controlling playlist/event, remaining time, viewers and effective/target FPS.

Click behavior:

| Click      | Action                          |
| ---------- | ------------------------------- |
| Left       | Open screen detail              |
| Right      | Start or stop the screen        |
| Shift-left | Select it and open Live Control |

## Screen detail

### Playback

* **Hold/Resume** freezes or resumes automation.
* **Skip** advances to the next event, queue or playlist decision.
* **Repeat** locks the current source until repeat is disabled.
* **Return to Automation** clears event control, queue, hold and repeat.
* **Content Queue** opens the queue editor.

### Why is this playing?

This item explains the current decision. Examples:

```
Selected by playlist spawn_rotation with weight 10.
All configured conditions passed.
```

```
Event update_reveal took control with priority 80.
```

```
This item was manually queued by an administrator.
```

Playback History stores the latest 20 runtime decisions for the screen.

### Location

* **Teleport** moves the admin three blocks in front of the display.
* **Highlight Bounds** draws temporary particles around both screen corners.
* **Repair and Resync** respawns the virtual MapEngine frames for viewers and forces a full map resend.

Repair does not change the saved location or dimensions.

### Visibility

The visibility button toggles `permission-required`.

When enabled, viewers need:

```
luigiscreen.see.<screen>
```

### Health

Health shows:

* source state and last error
* age of the latest frame
* reconnect count
* received, rendered and replaced frame counts
* effective and target FPS
* last and average render time
* viewers and shared-screen count

Usage Statistics shows plays, planned playback time, viewer-time, average viewers, skips and failures. Statistics are aggregate; no personal viewing history is stored.

## Queue editor

Every screen has its own queue.

| Click       | Queue action              |
| ----------- | ------------------------- |
| Left        | Play this queued item now |
| Right       | Remove it                 |
| Shift-left  | Move it one position up   |
| Clear Queue | Remove all waiting items  |

An active event has priority over the manual queue. After the event ends, the queue continues before normal playlist selection.

## Live Control Room

Live Control is for operating an event without opening configuration:

* **Preview/Media Library** chooses a source.
* Left-click media to take it now.
* Right-click media to cue it as Next.
* **Take Live/Next** advances to the first queued source.
* **Hold/Resume** freezes or resumes the current item.
* **Events** opens available timelines for the selected screen.
* **End Event** returns from an active event.
* **Return** clears temporary control and restores normal automation.
* **Audience Vote** starts or ends a vote.
* **Emergency** opens a separate confirmation page.

There is no invisible second decoder for Preview. In this alpha, preview means validating and cueing the source before Take Live. A staff-only preview screen can be created as a normal permission-protected screen.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://unknown-56-works.gitbook.io/luigiscreen/control-studio/screens-live-control.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.