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…

  • Media Applications
  • Monitoring & Logging
  • Tools & Utilities
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
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac
  • Windows
  • Linux
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

62/100 Good

Maintained
100last commit 11 days ago
Popular
00 GitHub stars
Easy to install
654 install platforms, install notes, Docker image
Light to run
No data

Based on 3 of 4 factors.

Availability: platform listings confirmed today, links checked 23 days ago

GitHub stars
0
Open issues
0
Last commit
2026-11-10
Latest release
v0.2.4
License
MIT
Activity
steady

Checked 8 days ago - source: GitHub (stoatworks-labs/atem-scopes)

Resources & Compatibility

Requirements not published yet.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Build command The container buildCmd is `static:build`, not `build`. Running `npm run build` invokes `electron-vite build`, which produces the desktop app into `out/` rather than the static site into `dist/`, causing the image to either fail to copy or silently serve a stale build. source

Fetched 47 days ago - each note links to its source

Alternatives

No alternatives collected yet.

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.

Answers sourced from github.com

Community

Collected 53 days ago - public community threads