ScopeDock support / Knowledge base

Camera setup and troubleshooting.

Start with the failure you can observe: device detection, macOS camera permission, RTSP connection, ONVIF discovery, or local file handling.

Fast diagnostic

Separate a Camera permission issue from a camera-source issue.

Generate a private next-step checklist for USB UVC, RTSP, or ONVIF before sending a support report.

Check camera permission
Before troubleshooting

Turn the source you have into an ordered first-connection plan.

The browser planner separates USB UVC, manual RTSP, and ONVIF discovery prerequisites without collecting camera details.

Build a setup plan
Private compatibility report

Bring structured evidence to troubleshooting.

Use a print-ready report skeleton that keeps camera details and connection secrets off the website.

Open the report template
Quick start

Get to your first preview

Test one source first. If it still fails, send a short description of what happened.

  1. 01
    Step 1

    Re-check compatibility

    Confirm platform scope, protocol coverage, and known limits before assuming the product should match every camera path.

  2. 02
    Step 2

    Identify the source type

    Decide whether you are troubleshooting USB UVC, USB microscope, endoscope, RTSP preview or recording, ONVIF discovery, or local file and capture behavior.

  3. 03
    Step 3

    Review permissions and storage

    Camera permissions, local storage, and network reachability are common root causes in early evaluation workflows.

  4. 04
    Step 4

    Choose the feedback type before sending

    Use compatibility issue for device detection or protocol behavior, setup issue for macOS permission or first-preview blockers, and feature request when the current workflow works but needs a new capability.

  5. 05
    Step 5

    Escalate with context

    If the guides do not resolve the issue, use Contact and include camera type, protocol, Mac model or chip, macOS version, ScopeDock version, expected behavior, and actual behavior. Do not send passwords, private LAN details, or full RTSP URLs.

Troubleshooting

Common troubleshooting lanes

Use the lane that matches the failure first. If the documented path still does not match your device, send compatibility feedback with symptoms and source type, not private credentials.

  1. 01

    USB camera does not open

    Confirm the device is attached directly or through a reliable adapter, appears to macOS as a USB UVC camera, and is not locked by another app. This is the right lane for USB microscopes, endoscopes, otoscope-style cameras, and inspection cameras. If the vendor requires a private driver-only app, ScopeDock compatibility may be limited.

  2. 02

    Camera permission blocks preview

    Check macOS camera permission for ScopeDock, then quit and reopen the app before testing one source again. Permission problems are setup issues, not proof that every USB microscope, endoscope, or UVC camera is unsupported.

  3. 03

    RTSP URL, authentication, or timeout fails

    Confirm the full RTSP URL format, username and password if required, local network reachability from the Mac, and whether the device actually exposes a standard RTSP stream. Do not send full private URLs or passwords in feedback.

  4. 04

    ONVIF discovery does not find the camera

    ONVIF discovery depends on device support and local network visibility. If discovery fails, manual RTSP can still be the correct path when you already know the stream URL.

  5. 05

    Snapshots, recordings, or local files feel unclear

    Check local storage assumptions, file handling expectations, and whether the workflow needs more product guidance rather than protocol debugging.

  6. 06

    Platform expectation mismatch

    Confirm whether the question is really about current platform availability, especially if you need Windows or Linux.

  7. 07

    Compatibility feedback

    Send feedback when a USB microscope, endoscope, UVC camera, RTSP camera, or ONVIF device behaves differently from the documented path after these checks. Include source type, Mac model or chip, macOS version, ScopeDock version, expected behavior, and actual behavior; remove private credentials and internal addresses.

  8. 08

    Feature request

    Use Contact when the current path works but you need a different capture, layout, onboarding, or device workflow. Keep feature requests separate from compatibility feedback so follow-up stays clearer.

FAQ

ScopeDock essentials

Answers about camera sources, captures, and privacy.

Does ScopeDock upload my video by default?

No default cloud upload flow is part of the product positioning. ScopeDock is presented as a local-first tool. It does not automatically upload videos, images, full RTSP URLs, LAN IP addresses, or media paths, and the website keeps feedback separate from anonymous usage measurement.

What cameras are supported?

The current site explains support around USB UVC devices, improved RTSP manual input, and ONVIF discovery workflows. Exact compatibility can still vary by device implementation, especially for network cameras.

Does ScopeDock support RTSP?

Yes. ScopeDock 1.1.1 continues to include the 1.1 series RTSP preview and recording improvements, including continuous video stream preview, preview resolution and frame rate choices after connection, improved RTSP recording save behavior, better thumbnails, and clearer connection, authentication, and timeout error messages. Network camera compatibility can still vary by device implementation.

How many sources can I connect at once?

The website currently describes ScopeDock as supporting up to four sources in a lightweight multi-source layout. That limit is part of keeping the product focused on practical inspection work rather than dense surveillance-style grids.

Is ScopeDock available on Windows?

Not yet. ScopeDock is currently available on macOS, and Windows availability will be published when it is ready.

Next step

Still blocked?

Tell us which ScopeDock version and camera source you are using, what you expected, and what happened. Remove passwords, private URLs, local paths, and sensitive content before sending.