Actions Fabl can send
- Mute and unmute channels
- Set channel fader levels
- Recall mixer scenes
- Send raw OSC messages
A documented path from rundown to device
Tie audio moves
to the show.
Tie audio moves to the show by connecting scene recalls, channel mutes, and fader changes to rundown cues. Fabl sends the documented actions over OSC and UDP; the documented state and triggers are listed below.
Integration profilePublic setup guide
Behringer
Behringer X32
Digital audio mixer
Fabl rundown→Studio Agent→Behringer X32
AudioDocumented state + triggers
Integration modeOSC protocol integration
ConnectionOSC over UDP · Port 10023
FeedbackDocumented state + triggers
What you can run from the rundownCheck the current scope
Check the current scope
for Behringer X32.
Use this as the current integration scope. Confirm device model, version, and site-specific behaviour before rollout.
Available state and signals
- Connection changes
- Channel mute changes
- Channel fader changes
- Scene recalled
- Channel number and level trigger data
Example cue sequenceFrom rundown event.
From rundown event.
To Behringer X32.
Rundown event→Local execution→Behringer X32
Prepare
Recall the studio scene associated with the production.
Take
Unmute the presenter channel and set its required fader level.
Confirm
Use mute, fader, and scene triggers to keep subsequent actions aligned.
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 the same reachable network as the console.
- 02
Enter the console host and OSC port, commonly 10023.
- 03
Set the channel count, typically 32.
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 Behringer X32 fits your studio.
Explore the product tour Create an account Request a tailored walkthrough