Camera setup
Amcrest NVR and Camera Setup: RTSP, ONVIF and Recording
Connect a compatible Amcrest camera or NVR channel through its documented RTSP or ONVIF profiles, then validate recording, playback, and recovery.
Compatibility is model- and firmware-specific. OmniNVR and TardisLabs are not affiliated with or endorsed by Amcrest.
Check compatibility before you start
Decide whether to connect directly to an Amcrest IP camera or to a channel exposed by an Amcrest DVR/NVR. A direct camera connection keeps the stream independent of the recorder; a recorder connection can be necessary when cameras sit behind its private camera network. Check the exact manual for local RTSP and ONVIF enablement, channel indexing, account permissions, and codec options.
Use a dedicated local viewing account and a stable LAN address. An Amcrest app preview is not proof that every product line exposes the same third-party stream, so verify the model before buying several cameras.
Add the camera or NVR channel
Amcrest's published IP-camera pattern is rtsp://CAMERA-IP:554/cam/realmonitor?channel=1&subtype=0 for a main stream, with subtype=1 commonly selecting the sub stream. Its DVR/NVR example uses rtsp://RECORDER-IP:554/h264Preview_01_main; change the channel and stream only as the exact recorder documents.
Enter credentials in OmniNVR's protected fields instead of embedding a real password in a copied URL. Test the intended channel, record for at least fifteen minutes, play across a segment boundary, and restart the camera or recorder once before enabling long retention.
Choose recording roles
Use the lower-bitrate sub stream for continuous history when it has enough detail, and reserve the main stream for focused live view or event clips. This reduces storage and decode load without giving up high-quality evidence around important moments.
Before scaling up, record one camera for at least fifteen minutes, play it from the timeline, disconnect the network briefly, and restart OmniNVR. A working live preview alone does not prove that timestamps, recovery, and storage are reliable.
Troubleshooting checklist
- Wrong stream opens: distinguish IP-camera
subtypenumbering from recorderh264Previewchannel names. - Authentication fails: confirm the local account has live-view permission and test it in the device interface.
- NVR channel is blank: verify the channel is online on the Amcrest recorder before changing OmniNVR.
- ONVIF finds the device but video fails: inspect the returned host, path, codec, and network reachability separately.
Frequently asked questions
What is the Amcrest NVR RTSP URL?
Amcrest's official recorder example uses an h264Preview channel path such as /h264Preview_01_main, while direct IP cameras use a /cam/realmonitor path. Confirm channel numbering, stream name, port, and firmware for the exact device.
Does every Amcrest camera work with OmniNVR?
No. The camera or recorder must expose a compatible RTSP, RTSPS, ONVIF, or HLS stream, and support varies by model, firmware, codec, power mode, and network topology.
Should I connect to the camera or the brand NVR?
Connect directly when the camera is reachable and you want independent streams. Connect to the NVR when cameras are isolated behind its PoE network or the recorder is the only endpoint that exposes each channel.
Can I expose the RTSP port to the internet?
Do not forward camera RTSP ports for long-term remote access. Keep cameras local and use a trusted VPN when remote viewing is required.
Sources and further reading
Record locally on the Apple device that fits the job.
Mac, iPhone, iPad, and Apple TV all support local recording. Recording modes and storage options can differ by platform and app version.