Install and Update 4All Encoder

Install Encoder, its GStreamer media runtime, capture drivers, and production updates safely.

Written By 4ALL.LIVE

Last updated 12 days ago

Prepare a supported Windows or macOS workstation to capture video/audio, receive 4All transcript v3 captions, and transmit caption-embedded contribution streams.

Best for: Broadcast engineers, streaming technicians, and system administrators.

Before you start

A 4All account with desktop access is required; licensed desktop capacity may be governed by your agreement.

  • 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.
  • Use a 64-bit workstation with administrator access and a reliable production network.
  • Obtain the approved signed installer.
  • Install the vendor driver before connecting SDI/HDMI hardware.

Installation and updates

  1. Close older Encoder instances and active production pipelines.
  2. Run the signed installer and keep the default local authentication callback port 5051 unless IT approved another value.
  3. Install the packaged GStreamer runtime. Packaged production builds should prefer their bundled runtime; compatible PATH runtimes are primarily for development.
  4. Install Blackmagic Desktop Video before commissioning DeckLink hardware, then restart the workstation.
  5. Open Encoder and complete browser authorization. Allow the localhost callback through endpoint security.
  6. Open Diagnostics and confirm GStreamer, capture plugins, caption elements, output sinks, devices, and hardware encoding.
  7. Use the approved stable update channel. Update only during a maintenance window.
  8. Restart and perform a complete start, receive, stop, and relaunch test.

What success looks like: Encoder opens without a media-runtime error, authentication completes, and a test-pattern pipeline starts and stops cleanly.

Check your setup

  • The intended build/channel are displayed.
  • gst-launch-1.0 resolves from the expected runtime.
  • Test input and the intended device are visible.
  • No orphan pipeline remains after Stop.

Troubleshooting

  • Installer blocked: verify publisher trust and follow the IT allow-list process.
  • Callback fails: allow local TCP 5051, close stale instances, and authorize again.
  • GStreamer unavailable: repair the bundled runtime.
  • Device absent: repair the driver, power-cycle, and rescan.

Security and operational notes

Important: Treat app, GStreamer, GPU, and capture-driver updates as production changes. Validate the exact combination off air.