Direct answer
Run ffprobe locally against an authorized camera, supply credentials through the safest mechanism the environment supports, and redact the input URL before sharing output. Start with TCP when a single predictable connection is useful for diagnosis.
Why this happens
ffprobe reads container and stream metadata without becoming a camera-management system. It can reveal whether the endpoint advertises video, audio, codec profiles and frame dimensions before a GUI viewer is involved.
Inspect the advertised tracks and codec parameters before assuming a viewer or network problem.
A controlled test
Use a synthetic example in documentation, run the real command only on a trusted machine, and limit the probe duration.
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 |
|---|---|---|
| Authorization | Confirm the camera and account are yours to test. | The probe is within the approved network scope. |
| Transport | Choose TCP or UDP explicitly for a reproducible run. | The output states the tested mode. |
| Fields | Capture codec, profile, resolution, frame rate and audio. | The relevant stream facts are present. |
| Redaction | Remove user information, host and sensitive paths as required. | The report contains no working credential or private endpoint. |
Evidence to keep
A minimal report can include tool version, transport, stream index, codec, profile, dimensions and the sanitized error line.
Boundary and safety note
Do not run broad scans, probe cameras you do not administer or paste live credentials into shared terminals and tickets.
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
Can ffprobe play the camera?
Its main job is inspection; use a player such as ffplay or a camera viewer for visual playback.
Why specify RTSP transport?
It makes the result reproducible and can separate UDP path loss from codec issues.
Is ffprobe output safe to share?
Only after removing credentials, private addresses and any device identifiers your policy treats as sensitive.
Primary references
- FFmpeg — ffprobe documentation
- FFmpeg — RTSP protocol options and examples
- IETF RFC 7826 — Real-Time Streaming Protocol 2.0
Related SmartRTSP guide
Open related guideA safe inspection workflow for codecs, tracks, resolution and transport with a redacted support output.