Actions Fabl can send
- Load and background-load clips
- Play, pause, stop, and seek
- Add, remove, and clear layers and clips
- Run server-side macros
- Send raw AMCP commands
A documented path from rundown to device
Roll playout
with the cue.
Keep video and graphics playout tied to the rundown, from loading a clip to clearing its layer when the item ends. Fabl sends the documented actions to CasparCG over AMCP and TCP.
Integration profilePublic setup guide
Open source
CasparCG
Broadcast graphics and playout server
Fabl rundown→Studio Agent→CasparCG
Playback / media serversConnection state
Integration modeProtocol integration
ConnectionAMCP over TCP · Port 5250
FeedbackConnection state
What you can run from the rundownCheck the current scope
Check the current scope
for CasparCG.
Use this as the current integration scope. Confirm device model, version, and site-specific behaviour before rollout.
Available state and signals
- Connection state
- Connected server version
Example cue sequenceFrom rundown event.
From rundown event.
To CasparCG.
Rundown event→Local execution→CasparCG
Cue
Background-load a clip on the required channel and layer.
Take
Play the prepared clip when the rundown item goes live.
Complete
Stop playback and clear the layer at the end of the item.
Check the room before productionPlan the
Plan the
connection.
Fabl Studio Agent runs on premises and needs network or file-system access to the integration endpoint.
- 01
Run Fabl Studio Agent on a machine that can reach the CasparCG server.
- 02
Enter the server host and AMCP port, commonly 5250.
- 03
Prepare the target channel, layer, and media references used by the rundown.
Fit the device into the live planConnect the room.
Connect the room.
Run the story.
Explore the complete workflow, create your account, or let us map how CasparCG fits your studio.
Explore the product tour Create an account Request a tailored walkthrough