How ONVIF discovery differs from manual RTSP in ScopeDock

ONVIF discovery and manual RTSP solve different setup problems. ONVIF can make camera onboarding lighter when the device supports standards-based discovery, while RTSP is the direct path when you already know the stream endpoint and only need to add the source. Treating them as the same thing usually makes troubleshooting slower.

What ONVIF discovery is good at

ONVIF discovery helps when the device exposes discovery capabilities that reduce setup friction. In a lightweight local-first tool, that is valuable because it keeps the workflow practical without pretending to be a full surveillance platform.

What manual RTSP is good at

Manual RTSP input is the more literal path. It matters when you already know the source details and want direct access to a network camera stream without waiting for discovery behavior to cooperate.

Why the distinction matters during evaluation

Many compatibility questions are really setup-path questions. A device can support RTSP and still offer a weak or nonexistent ONVIF experience. A discovery problem does not automatically mean the RTSP path is impossible, and a working stream does not automatically mean discovery will be elegant.

A practical decision rule

• Prefer ONVIF discovery when it works reliably and saves setup effort.
• Use manual RTSP when you already know the stream path or discovery support is unclear.
• Use support when your device behaves differently from the common standards-based path described on the site.

Not every IP camera behaves like the happy path

Some network devices technically expose a stream but still behave inconsistently in discovery, authentication, or endpoint handling. That is why the site keeps compatibility, support, and troubleshooting close to RTSP and ONVIF messaging.

The practical next step

If your workflow depends on network cameras, compare the download page, support page, and product page together instead of expecting one sentence to answer every device-specific case.