# Atem-scopes

Atem-scopes is a browser-based video scope tool that captures a Blackmagic ATEM multiview over USB and overlays waveform, vectorscope, histogram, false colour, zebras, or focus peaking on individual program and preview. It is open source and self-hosted, installable on Unraid.

Canonical page: https://ourlocalhost.com/app/2626/atem-scopes

## Description

Atem-scopes is a browser-based video scope tool that captures a Blackmagic ATEM multiview over USB and overlays waveform, vectorscope, histogram, false colour, zebras, or focus peaking on individual program and preview windows, with all analysis performed client-side so the video stream never leaves the browser.

## Platform availability

Available on 4 of 10 platforms: Unraid, Mac, Windows, Linux.

## Desktop and other devices

Mac, Windows, Linux.

## Health score

62/100 (Good), based on 3 of 4 factors.
- Maintained: 100 (last commit 11 days ago)
- Popular: 0 (0 GitHub stars)
- Easy to install: 65 (4 install platforms, install notes, Docker image)

## Links

- desktop: https://github.com/stoatworks-labs/atem-scopes/releases/latest
- Unraid: https://ca.unraid.net/apps/atem-scopes-1pfz0gi1nkymqe?q=atem-scopes

## Common questions

### Why doesn't the hosted or browser build show live source names from the ATEM?

The ATEM control protocol uses UDP on port 9910, and browser pages have no UDP API. The hosted build therefore uses region names typed when drawing them, while the desktop build can use the switcher's multiviewer configuration.

### Can the browser build capture a PCIe DeckLink card directly?

No, a PCIe DeckLink card is accessed through Blackmagic's SDK and a kernel driver, so it does not enumerate as a webcam for getUserMedia. UVC Blackmagic boxes such as the UltraStudio Recorder 3G or Web Presenter family work like ordinary cameras.

### What capture-path choices can make the scopes look correct but actually be wrong?

The scopes only see the RGB handed to the browser, not the original video signal. The capture path may use either BT.601 or BT.709 matrixing and may or may not expand studio-range levels to full range. If either choice is wrong, the scopes can be plausibly wrong rather than obviously wrong.

### What build command should a containerized self-hosted build use?

The container build command should be static:build, not build. Running npm run build produces the Electron desktop app in out/ instead of the static site in dist/, which can cause the image to fail to copy or serve a stale build.

---
Source: Our Local Host (https://ourlocalhost.com/app/2626/atem-scopes), the self-hosted and open-source app directory.
