Video & projection · software
SVT CasparCG troubleshooting
The SVT CasparCG problems live-event techs bring to Ask Roadie most (also called Caspar, Caspar CG, CasparCG 2.4, CasparCG 2.5). Pick your symptom, or describe your own in plain words, and get the likeliest fix first, with the manual page when there is one.
Common CasparCG errors & problems
What techs run into most, and what's usually behind it. The step-by-step fix for your exact software is in Ask Roadie.
- Step-by-step fixGet the fix →
CasparCG 2.5 won't start / crashes on launch after upgrade
Likely cause: 2.5.0 was rebuilt with VS2022 and newer toolchains; an older runtime or missing CPU/GPU features stop it loading.
- Step-by-step fixGet the fix →
CasparCG client can't connect to server
Likely cause: The client talks AMCP over TCP; a blocked or mismatched port refuses the connection.
- Step-by-step fixGet the fix →
CasparCG dropped frames / stutter on playout
Likely cause: The diagnostics graphs show which stage misses its deadline; PCIe bandwidth between GPU, DeckLink and CPU is called out in the README.
- Step-by-step fixGet the fix →
CasparCG media not found / clips missing in client list
Likely cause: The client's media list comes from the scanner, not the server itself; a dead scanner or wrong path shows an empty or stale list.
- Step-by-step fixGet the fix →
CasparCG no DeckLink output / DeckLink not detected
Likely cause: Device numbers come from the order Caspar enumerates cards; wrong number, unsupported mode or an incompatible driver gives no output.
- Step-by-step fixGet the fix →
CasparCG server closes right away after editing casparcg.config
Likely cause: An invalid config stops the server during start-up.
- Step-by-step fixGet the fix →
which OS for CasparCG server
Likely cause: Stated in the server README.
Not on the list? Describe it your way, or paste the error code off the display. Ask Roadie works the problem with you until it's fixed or you have a clear next move.
How Ask Roadie helps with the CasparCG
- 1. Pick the SVT CasparCG. It's already in the list.
- 2. Describe what you're seeing. In your own words, or the error code off the screen.
- 3. Get the likeliest fix first. Steps in order, the manual page when there is one, and a note when other techs have confirmed it.
- 4. Still broken? Tap 👎 and it keeps going from where you left off.