Main-Stream and Sub-Stream NVR Software: Assign Clear Roles

Define the required outcome

A lower-bitrate stream handles overview or baseline recording while a higher-detail stream is reserved for focused viewing or events, without silent role changes.

Write the owner, cameras, stream roles, recording schedule, retention, storage location, users, review deadline, export method, and acceptable outage. A workflow cannot be tested while those responsibilities are implicit.

Describe a normal event and a failure event in plain language. The normal event proves the recorder creates useful history; the failure event proves the operator can recognize a gap, preserve what remains, and restore the path without changing unrelated settings.

Plan the complete media path

Trace camera power, LAN transport, authentication, RTSP or other media input, optional ONVIF discovery, recorder processing, storage writes, indexing, playback, and export. Each layer can fail independently.

Main and sub streams can have different clocks, codecs, audio, keyframes, authentication, and startup delay. Swapping them without testing can break timeline continuity.

Keep an installation record with camera model, firmware, address reservation, protocol setting, stream profile, codec, bitrate, time source, recorder account, storage destination, and retention. That record is more useful than guessing after a router, drive, or camera replacement.

Protect recording reliability

Use dedicated camera accounts where supported, avoid exposing camera services directly to the public internet, keep time consistent, reserve storage headroom, and make recorder health visible. Add cameras in stages.

Keep detection, notification, and remote access from becoming hidden dependencies for the basic recording path. An alert can fail while useful video continues, and the system should make that distinction clear.

Review health on a schedule instead of waiting for an incident. Check newest playable footage, free-space trend, disconnected cameras, clock drift, failed exports, pending updates, and who still has access. Assign the check to a named person.

Where OmniNVR fits

OmniNVR can use compatible camera streams in local recording workflows; available stream-role controls depend on the platform and released app version.

Current Apple-platform roles and availability are recorded on the platform facts page. Camera and workflow support still depends on the exact device, stream, codec, firmware, network, storage, app version, and purchase state.

Acceptance test

Record both profiles separately, compare timestamps and audio, trigger a high-detail event, restart the camera, and confirm the intended role returns.

Repeat the test after a camera update, app update, storage change, router replacement, or operating-system upgrade. Preserve the observed settings and a known-good exported clip so later troubleshooting starts from evidence.

Include a negative test: wrong credentials, unavailable storage, blocked network path, or unsupported profile. The app should expose a clear failure instead of presenting a frozen image or stale status as if recording were healthy. Record the recovery time, the exact action that restored service, and whether any footage or event context was lost.