Skip to main content

Advanced Troubleshooting: Camera & Switcher Setups

Troubleshoot DSLR, ATEM, and capture card connection issues. Covers browser handshakes, resolution mismatches, background app conflicts, and cabling. Use this 5-step checklist to fix your setup and get your pro gear working fast.

Updated over a week ago

You hooked up a DSLR, ATEM switcher, or capture card. It looks fine in the test window, but when you enter the room, the screen goes black or MarketScale reverts to your basic webcam. High-end gear requires a precise setup. If the browser hits a snag (bandwidth limits, a "busy" signal, or a format mismatch) it cuts the feed. Here is the checklist to get your signal back online.


Force the Browser Handshake (Most Common)

If the browser panicked on the first try, a simple refresh won't fix it. You need to force a re-check.

  • Click the Lock/Settings icon in your URL bar.

  • Toggle Camera permissions to Block, then immediately back to Allow.

  • This forces the browser to drop the cheap webcam and re-negotiate with your capture card. You may need to refresh your page for this setting to take effect.


Kill the Background Apps

Cameras can usually only serve one application at a time. If Zoom, Teams, or FaceTime is running in the background, it might be hogging the video feed.

  • Close every other video app completely.

  • Refresh MarketScale.


Check Your Output Settings

Browsers like standard formats. If you feed them a weird signal, they will reject it to save bandwidth.

  • Resolution: Set your switcher/camera to 1080p.

  • Frame Rate: Stick to 30fps.

Pro tip: MarketScale standardizes all output to 1080p at 30fps (approx. 8 Mbps). Don't burn bandwidth sending us a 4K feed; we automatically downscale it anyway. Match our settings for the smoothest connection.


Swap the Cable

It sounds too simple, but cheap HDMI or USB cables are the #1 cause of signal drops.

  • If you are pushing 1080p video, make sure you are using a high-speed cable. If the data transfer is too slow, the browser assumes the device is broken.

Did this answer your question?