Connecting to CasparCG
Control CasparCG playout and CG templates via AMCP through Helmo Middleware.
TutorialIntermediateUpdated
Connect CasparCG Server to Helmo Live for playout control, template management, and CG operations.
Prerequisites
- CasparCG Server running on your network (default AMCP port:
5250). - Helmo Middleware installed on the same machine or network as CasparCG. CasparCG uses the AMCP protocol over TCP, which requires a local bridge.
Why middleware is required
CasparCG uses a proprietary TCP-based protocol (AMCP) that cannot be reached directly from a browser. Helmo Middleware acts as a bridge: it receives commands from the cloud via Supabase Realtime and forwards them to CasparCG over the local network.
Connecting in Helmo
- Make sure your Helmo Middleware is running and connected (see What is Helmo Middleware? and Installing and configuring Helmo Middleware).
- Go to Connect and click + Add Integration.
- Select CasparCG as the type.
- Enter a name (for example, "CasparCG Playout").
- Select your Middleware instance from the dropdown.
- Enter the CasparCG host (for example,
localhostor the IP) and port (default:5250). - Click Save.
Available actions
| Action | Description |
|---|---|
| PLAY | Play a media file or template on a channel/layer. |
| STOP | Stop playback on a channel/layer. |
| LOAD | Load a clip into a channel/layer (paused, ready to play). |
| LOADBG | Load a clip in the background, ready for transition. |
| CLEAR | Clear a channel or specific layer. |
| CG ADD | Add a template (HTML or Flash) to the CG layer. |
| CG UPDATE | Update template data (for example, change text fields on a lower third). |
| CG PLAY | Play a loaded CG template. |
| CG STOP | Stop a CG template. |
| CG NEXT | Advance to the next step in a CG template. |
| CG CLEAR | Clear all CG templates from a layer. |
Tip
CasparCG actions use channel and layer numbers. Channel 1 Layer 10 is written as 1-10. Check your CasparCG config for available channels.
Watch out
Helmo Middleware must be running for CasparCG commands to work. If Helmo Middleware disconnects, commands will queue and fail after timeout.