Create and Manage Multiple Encoder Outputs

Create, duplicate, enable, and monitor parallel RTMP, SRT, and RIST targets.

Written By 4ALL.LIVE

Last updated 12 days ago

Deliver one captured and captioned program to parallel or redundant destinations with explicit ownership.

Best for: Broadcast engineers and technical directors.

Before you start

Capacity depends on workstation resources, hardware-encoder sessions, bandwidth, and receiver limits.

  • Sign in with access to the correct organization, team, and event.
  • Record event, language, workstation, app build, OS, drivers, destination, and operator.
  • Commission with a test pattern and non-public receiver before program video.
  • Start with a stable single-output test.
  • Gather every URL, mode, port, key, and passphrase.
  • Create a capacity plan with CPU/GPU/uplink headroom.

Steps

  1. Rename the default target for its destination and purpose.
  2. Add RTMP, SRT, or RIST targets; each has its own enabled flag and video/audio configuration.
  3. Use matching codec/timing for redundancy unless a documented receiver requirement differs.
  4. Enter credentials only in protected fields—never names or screenshots.
  5. Commission one target at a time and confirm receiver-side video, audio, and captions.
  6. Enable the complete set and monitor sessions, load, throughput, dropped frames, and reconnects.
  7. Disable placeholders and document owner/rollback for every target.

What success looks like: Every enabled target reaches connected and carries the intended program and caption service.

Check your setup

  • Each target maps to a receiver.
  • One target can fail without silently changing another.
  • Every receiver confirms captions.
  • Performance headroom remains.

Troubleshooting

  • Only one connects: validate the failing receiver independently.
  • Resource saturation: reduce encodes or move redundancy.
  • Wrong key: stop, replace, and rotate after exposure.
  • Caption difference: compare container and downstream processing.

Security and operational notes

Important: Multiple destinations sharing one workstation, input, uplink, or power source are not full redundancy.