Where to start live preview, recording, and playback
Select an activated channel under Asset details first. Open preview for current video, or use Recording Center to save video. A live stream and a recording file are different things.
Choose what you want to do
| Goal | Page entry | Continue with |
|---|---|---|
| Watch one live channel | Asset details → select channel → Live preview | Live preview and playback protocols |
| Inspect or download a channel's recent image | Asset details → Channel overview → Periodic snapshots | Periodic channel snapshots |
| Watch multiple channels | Top navigation Video Wall | Display wall and program scheduling |
| Record manually or schedule automatic recording | Top navigation Recording Center | Manual recording and recording schedules |
| Find, play, download, or clip a file | Recording Center → Files | Search, playback, download, and clipping |
| Find a moment by its visual content | Recording Center → Image and text search | Recording semantic search |
| Use browser conferencing or low-latency publish/subscribe | Top navigation RTC | Browser RTC |
Relationship between a live stream and recording files
flowchart LR
C["Video channel"] --> S["Current online stream"]
S --> L["Live preview"]
S --> R["Recording session"]
R --> F["Recording file on disk"]
F --> I["Database index"]
I --> P["Search and playback"]
A stream does not mean recording is active. A successful recording session does not mean the file is searchable yet. Start troubleshooting at the first broken step in the diagram.
Correct order for the first verification
- Play one channel continuously in the browser for 5 minutes.
- Start one manual recording and wait longer than one segment period.
- Stop recording and wait for the session to finish.
- Find the file by channel and time in Recording Center.
- Play or download it and verify content and duration.
- Create an automatic schedule only after the manual route succeeds.
How to choose a playback protocol
- HLS: widest compatibility and usually higher latency; use it first to prove playback works.
- HTTP-FLV: lower latency in desktop browsers and suitable for daily monitoring.
- WebRTC/WHEP: lowest latency but requires HTTPS and ICE, and may need TURN on the Internet.
- RTSP: suitable for VLC, NVRs, and SDKs; browsers cannot play it directly.
Do not choose by protocol name alone. Confirm the real user network, browser, and proxy support before optimizing latency.
Success criteria
- Live preview plays continuously without repeated reconnects.
- Closing the page releases on-demand streams and viewers according to policy.
- Manual recording creates a playable file that Recording Center can find.
- Automatic schedules start and stop in a clear time window.
- Ordinary users cannot play or download unauthorized channels and files.
If something fails
Channel exists but has no video: see No video or playback failed.
Recording reports success but the file is missing: see Recording file is missing.
WebRTC connection fails: see RTC or browser connection failed.
Image/text model quality, performance and hardware selection