The archive¶
A headend needs an archive not for the viewer's sake but as proof: what exactly did we send out at 03:40, was there a signal on the input at the moment of the complaint, what advertisement ran in the disputed hour. The recording happens on the same machine that receives and delivers.
The archive is a storage of its own: the stream is appended into hourly files, separately per track, across several disks at once. Reading the archive does not interfere with writing it.
The machine's disks¶
The disks are set once in the machine's settings, the DVR section. The panel warns right there: these settings change where the archive is written on the machine.
- Archive root — the mount point, the home of the catalog and the base for relative paths.
- Disk 1, Disk 2, … — with the Add disk button. A disk's path is the name of a subdirectory inside the root, not an absolute path.
- Catalog path — the service directory for archive metadata; an empty field means
<root>/catalog. This is not where the archive is stored. - Check the mount before writing — worth enabling always: without it a disk that fell off turns into an ordinary empty directory, and the station will write the archive into the root filesystem until that one runs out.
Without a single disk the settings will not save: DVR needs at least one.
Next to them live the cache disks — archive parts that were read settle there, whether from another machine or from local archive disks; live recording never picks them, and space is freed by how long ago a fragment was read. A headend rarely needs them — mostly when it serves the archive of neighbouring machines.
Recording a stream¶
Open the stream, the DVR tab, turn on Record to DVR and set Retention depth (hours) — how many hours to keep.
Cleanup runs once an hour and deletes only fully expired hours: the depth is the archive's only limit, and how much disk it takes follows from the bitrate.
The recording balances itself across the active disks: consecutive hours of one stream alternate between disks, neighbouring streams are spread evenly, the tracks of a multi-track stream are written in parallel. A disk moved to read-only is still read but takes no new data — that is how a disk is retired without losing the archive.
Archive backup¶
With recording enabled, open the stream's Layout tab, set DVR backup copies, and save. For each copy, the layouter selects another streamer to receive the processed stream and record it without transcoding it again.
For SRT publishing, the copy receives the stream from the processing streamer. The backup streamer must have archive storage configured and Accept publisher connections disabled. The backup role preserves the recorded archive but does not keep transcoding running if the processing streamer fails.
Check the dvr backup assignment on Layout. If no suitable streamer is available, an unmet demand appears there with the rejection reason.
Reading¶
The archive is read by absolute time and by an offset back from live. The addresses, window parameters, rewind and frame previews are on the Archive playback page, and how to take a segment of the recording as a single file is in Archive export.
If the stream has subtitle extraction on, the extracted tracks are written alongside the video.
Checking the recording¶
The state of the recording is visible on the same tab: the archive window, the hours with data and the gaps in them, the archive size, the fragment write rates. What the deviations mean:
| Sign | What it means |
|---|---|
| DVR configured but not recording | the stream is offline or the recording never started |
| the archive edge lags behind the current time | the recording has stopped |
| the lower boundary stopped moving forward | the cleanup is not running — a full disk is ahead |
| gaps: N h with a wide window | there are holes in the archive: the stream fell over or recording was off |
| Archive write errors — data is being lost | the archive is losing data right now, check the disk |
| Writing is degraded | fragments are written slowly, with delay or collapsed — the storage is degrading |
The last row is an early signal rather than a statement of loss: the share of slow writes grows before the errors appear.
What next¶
- Archive playback — rewind and a window by absolute time.
- Archive export — a segment of the recording as a single MP4 file.
- Monitoring — where the recording counters go.
- Subtitles and teletext — what lands in the archive together with the video.
Fast archive navigation index¶
On the DVR tab of a stream or template, enable Fast archive navigation forwards and backwards. DVR recording must be enabled. The index is built from snapshots obtained after enabling the option and is retained with the archive.
- Snapshot interval (seconds) — the minimum time between snapshots; the default is 60 seconds, with a range of 1–86400. When a frame is unavailable, the actual time of the snapshot obtained is retained.
- Frames per GOP — the number of snapshots in an independently playable group; the default is 30, with a range of 1–100. This setting does not change the snapshot interval.
- First index video — becomes available after a group has accumulated. At an hour boundary, the remaining snapshots form a shorter group so a partial hour can also be viewed.
With a one-minute interval, a full day without gaps produces 1440 frames: playing them at 25 fps takes 57.6 seconds. A longer interval reduces the frame count and event search precision; a smaller GOP makes the next complete group available sooner.
Template DVR settings follow the usual rules: a stream's own dvr section replaces the template section as a whole. Existing groups remain unchanged when parameters change; the new parameters apply to unconfirmed groups. Disabling the index stops generation; existing data is deleted with the corresponding archive according to its retention period.
The index is available for unencrypted streams.