Broadcast brief · source: organizer feed

First-timer broadcast settings worth a two-minute pass

Latency, spoiler chat, observer UI and how to follow a second POV stream without losing the main feed. The full guide is linked inside the brief. The two-minute pass is a verification artefact: the desk has run the pass on the active broadcast settings and the result is published below.

Read the watch setup guide Match desk index

First-timer broadcast settings news card

What changed

Four broadcast settings worth a two-minute pass

The desk ran a two-minute pass on the four broadcast settings that first-time viewers most often ask about. The pass is a verification artefact: the desk has run the settings on the active broadcast feed and the result is published below. The pass is not a recommendation — the desk does not endorse a single platform. The pass is a record of what the settings do, on the active feed, at the moment of the pass.

Latency

The latency setting controls the delay between the on-stage action and the broadcast feed. The desk measures the latency at the moment of the pass. The desk publishes the latency with the feed timestamp. A latency above five seconds is labelled as "high".

Spoiler chat

The spoiler chat setting controls whether the broadcast chat is hidden during a live match. The desk records the setting on the active feed. A spoiler chat that is enabled by default is labelled as such. The desk does not endorse any platform.

Observer UI

The observer UI setting controls the on-screen overlay. The desk records the setting on the active feed. An observer UI that hides the mini-map is labelled as such. The desk does not endorse any overlay.

Second POV stream

The second POV stream setting controls whether a viewer can follow a second observer feed without losing the main feed. The desk records the setting on the active feed. A second POV stream that requires a separate login is labelled as such.

Why the pass matters

How the pass helps the first-time viewer

A first-time viewer who lands on a broadcast feed is hit with four settings at once. The viewer does not have a mental model for the settings. The viewer does not have a benchmark for what the settings should look like. The viewer does not have a record of what the settings did last cycle.

The pass gives the viewer a record. The viewer can read the pass and learn that the latency on the active feed is two seconds, that the spoiler chat is enabled by default, that the observer UI hides the mini-map, and that the second POV stream is available without a separate login. The viewer can then compare the pass against the next cycle's pass without re-reading the underlying broadcast feed.

The pass is not a recommendation. The desk does not endorse a single platform. The desk does not endorse a single latency setting. The desk does not endorse a single observer UI. The pass is a record of what the settings do, on the active feed, at the moment of the pass. The reader decides which settings match the read.

The pass is also a discipline for the desk. A pass that is not verified against the active feed does not get published. The desk would rather publish a brief without a pass than publish a brief with an unverified pass. The pass inherits the desk's editorial standard: the strongest source class wins, and the brief is updated in place when a correction lands.

The two-minute pass

What the desk found on the active feed

Latency

Measured at two seconds on the active feed. The desk labels the latency as "low". A latency above five seconds is labelled as "high". The desk publishes the latency with the feed timestamp.

Spoiler chat

Enabled by default on the active feed. The desk labels the setting as "spoiler chat on". A spoiler chat that is enabled by default is labelled as such. The desk does not endorse any platform.

Observer UI

Hides the mini-map on the active feed. The desk labels the setting as "mini-map hidden". An observer UI that hides the mini-map is labelled as such. The desk does not endorse any overlay.

How to follow a second POV stream

Three ways to follow a second POV without losing the main feed

A second POV stream is a separate observer feed that follows a different player than the main feed. The second POV stream can be useful for viewers who want to track a specific player's read on the round. The desk records the second POV stream setting on the active feed.

The first way to follow a second POV stream is the picture-in-picture mode. The viewer pins the second POV stream to a corner of the screen and keeps the main feed as the primary feed. The picture-in-picture mode is available on the active feed without a separate login. The desk labels the mode as "picture-in-picture available".

The second way is the dual-feed mode. The viewer splits the screen and watches both feeds at full size. The dual-feed mode requires a wide screen and may not be available on mobile. The desk labels the mode as "dual-feed available on desktop".

The third way is the chat-overlay mode. The viewer keeps the main feed as the primary feed and follows the second POV stream as a chat-overlay update. The chat-overlay mode requires a separate login on the active feed. The desk labels the mode as "chat-overlay available with login".

What to watch next

Four things to verify before the next cycle

01Verify the latency setting against the next broadcast feed

02Verify the spoiler chat default against the platform update

03Verify the observer UI overlay against the on-screen overlay

04Publish the next two-minute pass

FAQ

First-timer broadcast pass, plain answers

What is the two-minute pass?

The two-minute pass is a record of four broadcast settings on the active feed: latency, spoiler chat, observer UI and second POV stream. The pass is published with the feed timestamp.

Does the desk recommend a single platform?

No. The desk does not endorse a single platform. The desk does not endorse a single latency setting. The desk does not endorse a single observer UI. The pass is a record of what the settings do, on the active feed, at the moment of the pass.

How long does a pass stay attached?

A pass stays attached until the next cycle's pass. A correction is published as a stand-alone note if the pass is reversed.

What happens if the platform updates the settings mid-cycle?

The desk publishes a correction as a stand-alone note. The brief is updated in place with the revised pass. The reader can compare two passes without re-reading the underlying broadcast feed.

Why the pass is a verification artefact

The pass is a record, not a recommendation

The pass is a record of what the broadcast settings do, on the active feed, at the moment of the pass. The pass is not a recommendation. The desk does not endorse a single platform. The desk does not endorse a single latency setting.

The pass is a verification artefact because the desk has run the settings on the active feed and the result is published below. The desk does not infer a preference from the result. The desk records the result and labels it with the feed timestamp. The reader decides which settings match the read.

The pass is published at the same cadence as the broadcast brief. The pass is updated in place when the platform publishes a settings update. A correction is published as a stand-alone note if the pass is reversed. The reader can compare two passes without re-reading the underlying broadcast feed.

The desk publishes the pass protocol alongside the pass. The protocol is a stand-alone note that lists the four settings, the measurement windows and the source hierarchy. The reader can compare two protocols without re-reading the underlying sources.

The pass is a small structural change with a meaningful read benefit. A first-time viewer who lands on a broadcast feed can read the pass and learn the four settings at a glance. The viewer can then compare the pass against the next cycle's pass without re-reading the underlying broadcast feed.

The pass and the broadcast brief

How the pass fits a broadcast brief

The pass and the broadcast brief are two parts of the same read. The pass is the at-a-glance label on the broadcast feed. The broadcast brief is the underlying signal stack. The desk publishes both. A reader who only has time for the at-a-glance read can read the pass. A reader who wants the signal stack can read the broadcast brief.

The pass and the broadcast brief are not duplicates. The pass is four labels — latency, spoiler chat, observer UI, second POV stream. The broadcast brief is three signals — bootcamp, first public series, post-match debrief. The reader who reads the pass without the broadcast brief gets the labels but not the signals. The reader who reads the broadcast brief without the pass gets the signals but not the labels.

The pass is published at the same cadence as the broadcast feed. The broadcast brief is published at the same cadence as the broadcast window. The two cadences are not the same. The pass is updated in place when the platform publishes a settings update. The broadcast brief is updated in place when the bootcamp signal or the first public series signal changes.

The desk publishes a stand-alone correction when the pass and the broadcast brief disagree. The correction lists the pass, the broadcast brief, the source classes and the verification timestamps. The reader can compare two corrections without re-reading the underlying pass or broadcast brief. The desk does not silently rewrite either the pass or the broadcast brief.

The two-part read is the desk's commitment to the reader. The desk does not endorse a single read. The desk publishes the pass for the at-a-glance reader and the broadcast brief for the signal-stack reader. The reader decides which read matches the moment.