Direct answer
Synchronize every camera, recorder, router and viewing host to a reliable time source, then verify timezone and daylight-saving settings separately. RTP timestamps order media; they do not replace accurate device wall clocks for incident comparison.
Why this happens
A camera can play smoothly while its overlay or recorded event time is minutes wrong. Mixed NTP sources, blocked time traffic, incorrect timezone rules and long device uptime are common causes.
Separate stream availability, media description, transport, decoding and timing before changing camera settings.
A controlled test
Compare each device against one reference clock, reboot only after recording the offset, and recheck drift over a full day.
Change one variable at a time. Keep the camera model, firmware, endpoint and account recorded; then test network reachability, protocol response, media transport and decoding as separate layers.
Use a dedicated view-only account and a trusted local diagnostic tool. Redact credentials, private addresses and identifying data before sharing output.
Diagnostic sequence
| Check | Action | Evidence of progress |
|---|---|---|
| NTP | Configure a reachable time source for every device. | Synchronization status is visible and stable. |
| Timezone | Set timezone and daylight-saving rules explicitly. | Displayed local time matches the reference. |
| Overlay | Compare burned-in camera time with recorder metadata. | Both represent the same instant. |
| Drift | Measure the offset now and after 24 hours. | The clock stays within the operational tolerance. |
Evidence to keep
Keep an offset table with device, source, timezone and measured drift. This helps explain why visually simultaneous events appear out of order.
Boundary and safety note
Video timing is not a substitute for a formal evidence-handling process; document clock accuracy requirements for the use case.
For remote viewing, use a managed VPN instead of exposing RTSP or camera administration ports directly to the public internet.
SmartRTSP
SmartRTSP is a camera-focused RTSP and ONVIF viewer for Apple devices, Windows and Android. It fits direct viewing, discovery and multi-camera checks; keep a dedicated NVR or VMS when continuous recording, evidence export or centralized enterprise controls are required.
Frequently asked questions
Are RTP timestamps the same as camera clock time?
No. RTP timestamps support media timing, while the camera clock and metadata provide wall-clock context.
Can the picture be smooth while time is wrong?
Yes. Playback continuity and device time synchronization are separate.
Why check timezone after NTP?
NTP can synchronize the instant correctly while a wrong timezone still displays the wrong local time.
Primary references
Related SmartRTSP guide
Open related guideSeparate camera wall-clock time, RTP media time and viewer display time so multi-camera events remain trustworthy.