Choose the Right 4All Workflow

A decision guide for mobile captions, venue screens, broadcast graphics, translated experiences, ASL, and embedded captions.

Written By 4ALL.LIVE

Last updated 12 days ago

Turn production requirements into a specific 4All workflow, destination set, operator model, and validation plan.

Best for: Producers, accessibility coordinators, broadcast engineers, event planners, and organization administrators.

Before you start

Some workflows require plan entitlements such as translation capacity, ASL, Remote Control, Extended Screen, Closed Captions, custom branding, exports, or desktop licenses.

  • List audience locations and devices.
  • List the required source and target languages.
  • State whether captions must be personal, projected, keyed into video, rendered by XPression, or embedded as CEA-608/708.
  • Identify audio and network owners.

How to choose

  1. Use the viewer for personal web or mobile captions. Choose this when each attendee needs personal language, text size, colors, spoken captions, or mobile controls. Share the viewer URL or QR code and configure the lobby and privacy policy.
  2. Use Program Display for a shared venue screen. Choose this for projection, confidence displays, digital signage, or a dedicated caption monitor. Configure layout, background, speaker pills, typography, language, and TAKE behavior.
  3. Use Closed Captions for a transparent browser overlay. Choose this for OBS, a switcher browser layer, or a compositing system that can capture a browser source. Verify alpha behavior, resolution, safe areas, text position, and speaker treatment.
  4. Use Extended Screen for an independent paired output. Choose this when another screen needs a different language, style, sponsor treatment, or operator HUD. Pair it, lock its intended settings, and test reconnect behavior.
  5. Use XPression Bridge for Ross graphics workflows. Choose this when captions must populate XPression scene fields through supported data protocols. Specify caption line behavior, payload format, port, DataLinq mapping, scene control, and firewall path.
  6. Use 4All Encoder for encoded contribution or embedded CEA. Choose this when captions must travel inside a video stream or when 4All will encode video/audio to RTMP, SRT, or RIST. Define input hardware, codec, bitrate, latency, service mapping, and receiver validation.
  7. Add translation, Spoken Captions, or ASL as separate accessibility layers. Select target languages and provider settings, verify terminology with a glossary, choose supported voices, and design interpreter private-stage and public-output responsibilities.
  8. Add Remote Control only when operationally useful. Remote Control is for authorized production control while the host keeps device ownership. Define scopes, permissions, and takeover policy; do not distribute it like a viewer URL.
  9. Document the fallback. For every selected path, define an alternate audio input, replacement operator, backup display or receiver, and a rule for continuing safely when a provider or destination fails.

What this unlocks: The event plan names one primary workflow, optional secondary outputs, required entitlements, responsible operators, and end-to-end acceptance tests.

Check your understanding

  • A test phrase appears on every required destination.
  • Language and speaker identity are correct.
  • The final downstream screen or decoder—not just 4All preview—has been inspected.
  • Fallback instructions are accessible to the production team.

Common misconceptions

Selecting an output by name alone

Validate the destination’s actual production behavior: transparency, latency, control, authentication, language independence, caption transport, and reconnect.

Combining too many unowned outputs

Every enabled destination needs an owner and monitoring point; disable unused outputs to reduce ambiguity.

Choosing embedded captions without a decoder test

CEA carriage is not proven until a compatible downstream decoder exposes the intended service.

Good to know

  • Plan and usage availability should be verified before committing accessibility deliverables to a client.
  • Public browser outputs and authenticated production controls have different security expectations.
  • Do not make material workflow changes after Go Live without a communication and rollback plan.
  • 📲 Mobile and Web Caption Workflow
  • 🎭 Venue and Stage Display Workflow
  • 🎬 Broadcast Graphics with XPression
  • 📡 Embedded Captions with 4All Encoder