A standard RTSP path uses DESCRIBE, SETUP, and PLAY; SDP describes H.264 and RFC 6184 defines carriage over RTP. Hikvision's SDK is a separate acquisition path: its official structures distinguish private-protocol PS or RTP, standard RTSP, several container types, and “private 264” versus standard H.264. SlimNVR currently uses RTSP, does not load the native Hikvision SDK, and does not disguise an SDK PS/RTP path as ordinary RTSP.
H.264+ is a third layer: a vendor smart-compression strategy that can alter GOP and bitrate allocation. It is neither a PS container nor an RTP packetization mode. Disabling H.264+ and establishing a standard-H.264 baseline is a useful diagnostic step, but does not prove every observed failure came from H.264+.
On this DS-7104HC-E1 playback SDP advertises packetization-mode=0, while field captures commonly contain a single NAL payload of about 8 KiB in TCP-interleaved RTP. RFC 6184 mode 0 permits single-NAL packets and not FU-A. A large NAL may reach one client over the DVR's TCP connection yet fail at a relay with a standards-sized packet limit. This is an observation for this device and firmware, not a claim about all Hikvision products.
For A1, gortsplib requests an absolute Range: clock and creates a one-shot RTSP service on container loopback. Its downstream SDP advertises mode 1. NAL payloads above 1300 bytes are split into RFC 6184 FU-A packets while preserving timestamps, marker, NAL type, and start/end bits and assigning continuous sequence numbers. FFmpeg reads that local feed over TCP. The operation changes RTP boundaries, not H.264 picture semantics, and exposes no host port.
A2 takes a different transparent-control path. SlimNVR performs Digest authentication, URL rewriting, and absolute PLAY Range injection. After PLAY succeeds, it forwards the TCP-interleaved media bytes between DVR and local FFmpeg byte-for-byte, without depacketizing or repacketizing. This retains FFmpeg's verified native behavior for that legacy track instead of assuming A1's repair is universally correct.
The post-processing fallback is layered: capture over RTSP/TCP and stream-copy the source bitstream while generating timestamps and discarding explicitly corrupt packets; verify the event second with one OSD read; then decode only the short event window and produce a precise 352×288, CFR 25 fps, H.264 Baseline Level 3.0, two-second-GOP, AAC file. Remuxing, timestamp repair, and re-encoding solve different classes of failure.
With live555, VLC can use a larger receive frame buffer together with RTP reordering and TCP or transport fallback paths, so it may tolerate a legacy DVR better than a stricter default pipeline. Those are buffering and transport safeguards, not a secret Hikvision decoder.
No compatibility algorithm can reconstruct pixels when a packet, NAL slice, SPS/PPS, or reference picture was already lost upstream. SlimNVR validates duration, frame count, maximum frame gap, and OSD, rejecting a bad sequence instead of presenting interpolation or decoder concealment as original evidence.
- A1: mode-0 large NAL → loopback mode-1 FU-A repacketization.
- A2: proxy only the control plane; pass media bytes unchanged after PLAY.
- Both tracks use absolute DVR playback time and an OSD gate.
- Standards-conforming output cannot restore missing evidence.
HikvisionDS-7104HC-E1RTSPHik SDKPSRTPH.264+packetization-mode 0mode 1FU-A8 KiB NALTCP interleavedgortsplibFFmpegOSDVLClive555