Caspar AV

A live-events media server built on CasparCG that runs show control in the browser.

  • Media Applications
  • Media Servers
  • Tools & Utilities
A live-events media server built on CasparCG that runs show control in the browser. It lays out screens on a canvas, runs cue lists that can change several screens in a single frame, and adds a media library, graphics templates and a trigger grid, with AMCP (Automatic Media Control Protocol) bridging and OSC (Open Sound Control) for external control. Aimed at live-event and broadcast teams who want self-hosted, scriptable playout.

Platform availability

Available on 3 of 10 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac
  • Windows
  • Linux (not listed)
  • 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.

56/100 Fair

Maintained
100last commit 10 days ago
Popular
165 GitHub stars
Easy to install
553 install platforms, install notes, Docker image
Light to run
1016 GB minimum RAM

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

GitHub stars
5
Open issues
0
Last commit
2026-11-11
Latest release
v0.1.5
License
MIT
Activity
declining

Checked 8 days ago - source: GitHub (stoatworks-labs/caspar-av)

Resources & Compatibility

Minimum requirements: 16 GB RAM, 500 GB disk.

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

First-install notes

  • Building the Docker image (web console) The web/ console assets are not committed to the repo; they are built from console/ by Vite. When building the Docker image, include a Node build stage before the Rust stage, and pass the absolute path /app/web to the --web flag rather than the relative default so the browser console does not 404. source

Fetched 47 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Why would a Rust-only Docker image serve 404s for every web page?

The web/ directory is not tracked in git, and the console build writes to ../web, so the image needs a Node stage before the Rust build. The runtime should pass an absolute /app/web for --web because the default relative web path resolves against the working directory.

Is caspar-av ready to use in a live show?

No; the project says it has not been run on real output hardware or in a live show. Validate on your own rig before relying on it.

Which ports does caspar-av use to communicate with CasparCG?

It uses TCP 5250 for AMCP and listens for OSC telemetry over UDP.

What must be running for the Media and Templates pages to have content?

A media-scanner must be available on HTTP 8000.

Does the recorded console demo send commands to a real CasparCG server?

No. It replays a recording of caspar-avd running against scripts/fake-caspar.py, so nothing is driving a real server and nothing is saved.

Answers sourced from github.com, github.com, github.com

Community

Collected 53 days ago - public community threads