Webcam & RTSP Live Blur

Live Camera mode keeps a webcam or RTSP capture open, processes frames locally, and shows the redacted stream in the monitor. You can tune detection and blur controls without reconnecting the source.

Never publish a real camera password in screenshots, support tickets, documentation, or shared presets. If a credential is exposed, rotate it on the camera.

Before you connect

• Confirm the camera works in its vendor app or another trusted player.
• Close software that may hold exclusive access to a webcam.
• For RTSP, use an address beginning with rtsp:// or rtsps://.
• Confirm the PC can reach the camera host and port on the same network or VPN.
• Prefer a dedicated read-only camera account. Avoid administrator credentials when the device supports a viewer account.
• Choose a recording folder before recording. The app records the processed live output there.

Connect a webcam

1. Select Live Camera in the Mode bar.
2. In Live Source, choose Webcam.
3. Click Test Connection.
4. Expect the button to become Stop Stream and processed frames to appear in the monitor.
5. If no frames arrive, close Teams, Zoom, browser camera tabs, OBS, or other software using the camera, then test again.

SmartBlur currently tests the default camera, shown as Webcam 0. Windows camera privacy permission must allow desktop apps to use the camera.

Connect an RTSP stream

1. Select Live Camera.
2. Choose RTSP Stream… under Source.
3. Enter the complete RTSP or RTSPS address. Example shape: rtsp://camera-host:8554/stream.
4. Click Test Connection.
5. Expect a live-session status followed by processed frames. Use Stop Stream to close the session.

SmartBlur validates the address before opening it. A blank value reports that an RTSP URL is required; an unsupported scheme reports that the address must start with rtsp:// or rtsps://.

What happens when you change settings live?

SmartBlur waits about 400 ms after the latest control movement before applying the newest live configuration. This prevents a flood of updates while you drag a slider. The status area shows Applying live settings, then confirms the model used. If an update fails, the session stays visible and the error is reported; correct the setting or stop and retest the source.

Accuracy tuning while watching the stream

Use a scene that represents the real camera: typical distance, lighting, crowding, motion, and angle.

1. Start with the appropriate preset—Default, Street Footage, or Office CCTV.
2. Enable only the targets required by your privacy policy.
3. If a face/body/plate is missed, lower that target’s confidence by about 0.05 and watch several seconds.
4. If ordinary objects are blurred, raise that target’s confidence by about 0.05.
5. Move from Standard to Ultra when misses remain in small, angled, crowded, or low-quality subjects.
6. Use Ultra Super when maximum coverage matters more than latency/frame rate.
7. Enable 360° for rotated, overhead, sideways, or unusual camera angles.
8. Increase padding when a moving subject escapes the blur edge.

Do not compensate for missed detections only by increasing blur intensity. Intensity changes how a detected box looks; confidence/model/360° determine whether a subject is detected, while padding determines how much area around it is covered.

Record processed live video

1. Click Change Folder and choose an access-controlled destination.
2. Start and verify the live session.
3. Start recording from the live controls.
4. SmartBlur writes processed frames to a video in the selected folder.
5. Stop recording before stopping the stream so the video can be finalized cleanly.
6. Review the saved recording before sharing it.

If no folder is selected, SmartBlur refuses to start recording and asks you to choose one. A recording error stops the recorder and is shown in the status/console instead of silently claiming success.

RTSP troubleshooting

“Waiting for live frames from the configured source”

The session opened but no usable frame reached the preview yet.

• Verify the full path/channel in a trusted RTSP player.
• Confirm the camera is online and the PC can reach its IP and port.
• Check username/password and URL-encode special characters used inside credentials.
• Try the camera’s main and sub-stream endpoints; unsupported codecs or very large streams may fail or perform poorly.
• Stop the session, wait a moment, and test again after correcting the URL.

Connection fails immediately

• The field must not be blank.
• The scheme must be rtsp:// or rtsps://.
• Firewall/VPN/VLAN rules must allow the PC to reach the camera port.
• Some cameras limit concurrent viewers; close another RTSP client.

Frames appear but are delayed or slow

• Try Standard before Ultra or Ultra Super.
• Enable only needed targets—Body and Plate add work.
• Turn off 360° unless the camera angle needs it.
• Use the camera sub-stream or a lower resolution/frame rate if available.
• Prefer a wired network for fixed cameras.

Settings appear unchanged

• Stop dragging the control and wait for Live settings applied.
• Check the target is enabled; its threshold has no visible effect when that target is off.
• A model change takes longer than padding, confidence, target, or style changes.
• Review the status/console for a settings failure. If necessary, stop and retest the source.

Security and privacy

• Processing is local to the SmartBlur desktop worker; the camera stream is not uploaded for AI processing.
• An RTSP URL may contain credentials. Treat logs, screenshots, and screen recordings that show the URL as secrets.
• Prefer RTSPS or an isolated trusted network when the camera supports it.
• Store recordings in a protected folder and define a retention/deletion policy.
• Use a human review step for high-risk publication, compliance, or safety workflows.