Interactive RTSP URL Builder
Select your camera brand and generate live URLSame NVR IP — differentiate cameras via Ch 1, 2, 3...
Dahua Ready RTSP URLRECOMMENDED FOR AI
rtsp://admin:admin1122@192.168.100.33:554/cam/realmonitor?channel=1&subtype=1
•⚠️ CRITICAL: In Dahua NVR settings, go to Camera ➔ Encode and change compression from H.265 to standard H.264. Turn "Smart Codec" (H.264+/H.265+) OFF.
•If camera is connected to the PoE ports on the rear of the NVR, use the NVR IP with channel=X. Direct camera IP is isolated by the NVR switch.
•Recommended for AI: Use subtype=1 (Sub Stream) for high-FPS, low-latency multi-camera face tracking.
Why "Test" is Green but Stream is Black?
Top Dahua & NVR onboarding errors & fixes1. Camera Video Compression is Set to H.265
Dahua cameras ship with H.265 or Smart Codec (H.264+/H.265+) enabled by default. FFMPEG and OpenCV cannot decode Dahua proprietary Smart Codecs in real time, causing a blank screen with 0 FPS.
Fix: In Dahua NVR Web Portal ➔ Setting ➔ Camera ➔ Encode ➔ Set Compression to H.264 and turn Smart Codec OFF.
2. Direct Camera IP Plugged into Rear NVR PoE Ports
If your camera is plugged into the back of an NVR, the NVR isolates that camera on an internal virtual subnet. The PC on your office Wi-Fi/LAN cannot reach the camera IP directly.
Fix: Connect via the NVR IP with
channel=1 (or 2, 3), OR plug the camera into an external Gigabit switch on the same LAN as the PC.3. Using Wrong Path syntax (e.g. /unicast/c1/s0/live)
/unicast/c1/s0/live is Uniview syntax. Dahua accepts port 554 connection (causing the green "Ping" badge), but rejects the stream with 404 Not Found.
Fix: Use Dahua syntax:
/cam/realmonitor?channel=1&subtype=0.Multi-Camera & NVR Architecture: One NVR IP vs. Multiple Cameras
How multiple cameras connected to the same NVR are addressed, managed, and routed to TrackingFace Gate UnitsCORE RULE
"If two cameras are plugged into the same NVR, do they get two separate IP addresses on the network?"
No. The NVR has only ONE IP address on the school/office LAN (e.g.
Instead, the NVR acts as a single gateway multiplexing and streaming all camera feeds over its single IP address. You differentiate Camera 1 and Camera 2 by changing the Channel Number in the RTSP path (not the IP address).
192.168.1.100). Cameras plugged into the PoE ports on the rear of the NVR live on the NVR's private, internal virtual switch (e.g. 10.1.1.X), which is isolated and cannot be reached directly from your Gate PC.Instead, the NVR acts as a single gateway multiplexing and streaming all camera feeds over its single IP address. You differentiate Camera 1 and Camera 2 by changing the Channel Number in the RTSP path (not the IP address).
Multi-Camera Channel Syntax Matrix (Example NVR IP: 192.168.1.100)
| Brand / System | Camera 1 (Entrance Gate) | Camera 2 (Exit Gate) | Channel Syntax Rule |
|---|---|---|---|
| Hikvision / HiLook | .../Streaming/Channels/102 | .../Streaming/Channels/202 | Channel * 100 + Stream (101=Ch1 Main, 102=Ch1 Sub, 202=Ch2 Sub) |
| Dahua / Amcrest / CP PLUS | .../cam/realmonitor?channel=1&subtype=1 | .../cam/realmonitor?channel=2&subtype=1 | channel=X&subtype=1 (subtype=0 Main, 1 Sub) |
| Uniview (UNV) | .../unicast/c1/s1/live | .../unicast/c2/s1/live | c{channel}/s1 (s0 Main, s1 Sub) |
| Tiandy / TVT / Sunell | .../live/sub_ch0 | .../live/sub_ch1 | Zero-indexed: sub_ch{channel-1} |
Comparing the Two Physical Wiring Topologies
Topology A: Shared NVR (Built-in PoE Ports)Single NVR IP
Both cameras plug directly into the PoE ports on the back of the NVR. Only the NVR connects to the school router/switch.
- IP Scheme: 1 IP address on LAN (e.g.
192.168.1.100). - Gate PC Config: Gate 1 connects to Channel 1, Gate 2 connects to Channel 2.
- Pros: Zero extra network switches needed; NVR records 24/7 uninterrupted.
- Requirement: Must use Sub-Stream (subtype=1) to prevent overloading the NVR processor.
Topology B: External Gigabit PoE SwitchIndependent IPs
Cameras plug into an external PoE switch connected to the school LAN. NVR also connects to the same switch to record over LAN.
- IP Scheme: Each camera gets its own unique IP (e.g.
192.168.1.51,192.168.1.52). - Gate PC Config: Each Gate PC connects directly to its assigned camera IP on Channel 1.
- Pros: Direct camera feed with zero latency; no load on the NVR; maximum scaling.
- Requirement: Requires a dedicated PoE Gigabit switch.
🎯 Best Practice: Multi-Gate Deployment with One NVR
If you have two physical gates (e.g. Entrance Gate & Exit Gate) running on two computers, run
TrackingFaceGate.exe on PC 1 configured with Channel 1 Sub-stream, and run TrackingFaceGate.exe on PC 2 configured with Channel 2 Sub-stream. Both units operate concurrently in real time without interfering with each other or the NVR storage!Recommended Gate Computer Specifications
Benchmark standards to avoid frame dropping and multi-camera lagProcessor (CPU)
Intel Core i5 (8th Gen+)
⚠️ Core i3 dual-core systems suffer lag with 2+ cameras.
System Memory (RAM)
8 GB RAM Minimum
16 GB recommended for 3–4 high-resolution cameras.
Storage Drive
Fast SSD (Solid State)
Ensures instant offline queue syncing and fast AI model loading.
Operating System
Windows 10 / 11 (64-bit)
Universal single-file executable (TrackingFaceGate.exe).
The Golden Verification Rule: Test in VLC Media Player First
Open VLC on the gate PC ➔ Press Ctrl + N ➔ Paste your RTSP URL ➔ Click Play. If it plays in VLC, it will work 100% in TrackingFace.
Need help with Gate Activation or School Firewall Blocks?
If your gate software shows an "HTTP 403 / HTML page" error, expand ⚙️ Advanced: Cloud Server URL on the setup screen and set the endpoint to https://trackingface.vercel.app/api.