Skip to main content

Share One Camera Across Applications

Keep using your preferred recording, annotation, or reporting tool while Vidsy Pipes performs real-time analysis on the same live video source.

If you also want Vidsy Pipes to send detected observations into that external tool, pair this setup with App Control.

Why this setup is useful​

Most camera drivers only allow one application to open a physical camera at a time. That blocks you from recording in one tool while Vidsy Pipes analyzes the same feed.

Two options solve this:

  1. OBS Studio — opens the camera once and shares it as a Windows virtual camera device or preview window.
  2. MediaMTX — runs as a background server that reads your IP camera and re-publishes it over RTSP/WebRTC.

Which option to choose​

Use OBS when:

  • you have a local USB webcam
  • other tools expect a normal Windows webcam device
  • you want a visible app to preview, crop, or overlay the feed
tip

OBS is the simplest choice for local cameras. It exposes the feed as a Windows virtual camera that any app can select — no network streams needed.

Use MediaMTX when:

  • you have an IP/RTSP camera
  • you want a background service without a visible window
  • multiple apps need the same network stream
  • your apps are running on different machines

Finding your RTSP camera URL​

Needed for IP cameras and the MediaMTX option.

  1. Find the IP address — use Advanced IP Scanner to scan your network. Your camera appears with its IP and manufacturer name.
  2. Find the URL — check your camera's documentation. Most vendors publish the RTSP URL format. A typical URL looks like:
rtsp://username:password@192.168.1.173:554/stream1
  1. Test the URL — use ffplay (included with FFmpeg):
ffplay rtsp://username:password@192.168.1.173:554/stream1

If video appears, the URL and credentials are correct.

Option 1: MediaMTX​

MediaMTX reads your IP camera's RTSP stream and re-publishes it so multiple tools can connect.

Step 1: Install and configure​

  1. Download MediaMTX from the official GitHub releases page and extract to a folder.
  2. Open mediamtx.yml in a text editor.
  3. Add your camera under the paths section:
paths:
  front_cam:
    source: rtsp://username:password@xxx.xxx.xxx.xxx:554/stream1

Replace front_cam with any short name — it becomes the path used in all URLs. Don't forget to replace source as well with the actual url to your camera.

  1. Save the file and start MediaMTX from a command line in the same folder:
mediamtx.exe

Keep the console window open. MediaMTX connects to the camera automatically.

Step 2: Connect Vidsy Pipes​

  1. In Vidsy Pipes, add a WebRTC Camera source.
  2. Enter the URL using your path name:
http://localhost:8889/front_cam
  1. Confirm the preview and start analysis.

Step 3: Connect other applications​

Any RTSP-capable app can read the same stream:

rtsp://127.0.0.1:8554/front_cam

Option 2: OBS Studio​

OBS Studio opens the camera once and shares it as a virtual camera, preview window, or both.

Step 1: Install OBS​

Download and install from the official website.

Step 2: Add the camera source​

  1. Create a new scene, for example Shared Camera.
  2. In Sources, add:
    • Video Capture Device — for a local USB webcam
    • Media Source — for an RTSP IP camera: click Add, choose Media Source, uncheck Local File, paste the RTSP URL
  3. Set resolution and frame rate as needed.
  4. Confirm the preview looks correct.

OBS now owns the camera. Other apps should use the OBS output, not open the camera directly.

Step 3: Share the feed​

As a virtual camera (simplest for local webcams):

  1. Click Start Virtual Camera in OBS.
  2. In other apps, select the OBS virtual camera as the video source.
  3. In Vidsy Pipes, select the OBS virtual camera or use window capture.

As a window (simplest desktop setup):

  1. Keep the OBS preview window open.
  2. In Vidsy Pipes, add a Window input and select the OBS preview window.

Troubleshooting​

Camera is busy​

Don't open the physical camera in multiple apps. Open it once in OBS or let MediaMTX read it, then feed everything else from that output.

No picture in Vidsy Pipes from MediaMTX​

  • Confirm mediamtx.exe is running.
  • Check the URL and path name match what's in mediamtx.yml.
  • Test with ffplay first.

Too much delay​

  • Lower resolution or frame rate.
  • Keep all apps on the same machine or LAN.

Poor window capture quality​

  • Make the preview window larger before capturing.
  • Use RTSP or virtual camera instead for better fidelity.

Summary​

  • Local USB webcam → OBS virtual camera.
  • IP/RTSP camera, multiple consumers → MediaMTX.
  • Quickest setup → capture your existing preview window in Vidsy Pipes as a Window input.

When you want Vidsy Pipes to trigger updates inside the reporting application, continue with App Control.