Start, Preview, Monitor, and Stop an Encoder Stream

Operate preflight, on-air monitoring, target isolation, and clean shutdown.

Written By 4ALL.LIVE

Last updated 12 days ago

Use a repeatable procedure that validates preview, caption state, every receiver, and a clean stop.

Best for: Live-event operators.

Before you start

Requires a configured stream and at least one enabled target.

Sign in with access to the correct organization, team, and event.
Record event, language, workstation, app build, OS, drivers, destination, and operator.
Commission with test pattern and a non-public receiver before program video.
Complete input, video, audio, caption, and destination checks.
Arrange receiver-side monitoring.
Document rollback and backup paths.

Open preview with captions and safe area; confirm video, audio, and caption text.
Compare event, language, input, targets, codec, bitrate, and service to the runbook.
Start and watch stopped → starting → running.
Monitor every target's idle, connecting, connected, reconnecting, or failed state.
Confirm receiver-side program, captions, and health before Ready.
During air, watch caption sequence/latency, source final state, pipeline health, load, drops, and network.
If one target fails, isolate it where possible instead of restarting healthy paths.
At wrap, confirm with production, stop, wait for stopped, verify receivers end, and preserve logs.

What success looks like: The stream remains healthy locally and at receivers and stops without orphan processes.

Stuck starting: inspect the first failing pipeline element.
Repeated reconnect: test destination reachability and uplink.
Stale captions: verify event live state and transcript WebSocket.
Stuck stopping: allow cleanup, collect diagnostics, then use approved force-close.

Important: Maintain receiver-side confidence monitoring; local preview is only one observation point.