Create and Manage a Bridge Output
Create a named bridge instance with event, language, protocol, host, port, payload, caption behavior, and enabled state.
Written By 4ALL.LIVE
Last updated 4 months ago
Create a named bridge instance with event, language, protocol, host, port, payload, caption behavior, and enabled state.
Best for: XPression operators, graphics engineers, caption operators, broadcast engineers, production IT, and licensed desktop administrators.
Before you start
Requires an active 4All organization/event, authorized desktop account, eligible XPression Bridge license, supported app build, and a network path to 4All plus the selected XPression protocol.
- Document the 4All event/language and XPression scene/DataLinq design.
- Know the bridge/XPression machines, IP interfaces, protocol, direction, port, firewall owner, and final program return.
- Prepare a backup output and an off-air test scene.
Steps
- Select event/language. Verify with known caption.
- Choose Add/Create output. Give a clear destination and redundancy name.
- Choose protocol. WebSocket DataLinq, captioning TCP, RSS HTTP, or UDP.
- Set bind host/remote host and port. Follow same-machine or LAN design.
- Choose payload. Simple text, JSON, or XML where supported.
- Set caption behavior. Line count 1โ3, max characters, rolling/instant, partial/final-only, roll step/direction/speed, clear timeout.
- Save disabled first. Prevent accidental transmission.
- Start test captions. Validate XPression mapping.
- Enable/start live source. Verify final program.
- Duplicate/edit/delete only off air. Preserve logs/config before destructive change.
What success looks like: The Bridge transports the correct 4All caption state to the intended XPression scene with verified formatting, timing, monitoring, and recovery.
Check your setup
- Bridge instance reports running, cloud connected, intended XPression connections, and correct caption payload.
Troubleshooting
Port in use
Choose approved unique port or stop conflicting process.
Bind failure
Check address/interface/firewall.
No cloud captions
Check event live/language/auth/network.
Security and operational notes
- A saved enabled output may start later according to app settings.
- Ports can expose caption data on a LAN.
- Name outputs so operators cannot confuse primary/backup.
Related guides
- Install and Update 4All XPression Bridge
- XPression Bridge Protocol and Payload Reference
- Collect XPression Bridge Logs and Diagnostics
Documentation status: Draft based on XPression Bridge repository version 0.1.59. Validate the installed release, supported OS, license policy, and live graphics workflow before publishing.
Was this helpful?
Still need help? Ask the team