4All Compatibility and Format Reference

Plan browser, desktop, audio, caption, export, graphics, and streaming compatibility.

Written By 4ALL.LIVE

Last updated About 1 month ago

Select interoperable formats and validate the exact sender/receiver chain instead of relying on assumptions.

Best for: Implementation engineers, operators, IT, and procurement.

Before you start

Supported features vary by product version, OS, plan, provider, and receiving platform.

  • Use the current production release and approved organizational policy.
  • Record resource IDs, exact time zone, and accountable owner.
  • Validate in a non-production environment when possible.
  • Collect exact browser/OS/app builds and destination specifications.
  • Identify live, recorded, graphics, and export consumers.
  • Create an acceptance test for every required format.

Reference

  1. Web: use a current supported browser with microphone, autoplay, storage, secure WebSocket, and download permissions as required.
  2. Desktop Operator: use the current signed 4All.Live build; repository baseline 0.1.32 declares macOS 13+ and bundles a forallcli sidecar.
  3. Audio: use stable production devices; local STT requests normally use 16 kHz input payload while Encoder audio output is fixed at 48 kHz.
  4. Captions: distinguish 4All realtime transcript/display captions from Encoder embedded CEA-608/708 services.
  5. Exports: validate plain text, subtitle/transcript formats, language, speaker labels, timecodes, and encoding in the target editor/player.
  6. XPression: choose WebSocket DataLinq, captioning TCP, RSS HTTP, or UDP with simple text, JSON, or XML.
  7. Encoder: H.264/H.265, AAC/Opus, RTMP/RTMPS, SRT, or RIST; verify receiver profile and CEA preservation.
  8. Languages/providers: verify recognition, translation, glossary, and TTS support for the exact locale and account configuration.

Use this reference to confirm: Every required browser, app, format, protocol, language, and receiver has a documented pass/fail acceptance result.

Validation checks

  • Exact versions are pinned.
  • Test files/streams open in target systems.
  • Captions survive the final chain.
  • Known limitations and fallback are recorded.

Compatibility notes

  • Works locally/not downstream: inspect receiver/container/transcode.
  • Locale not available: choose supported provider/locale or approved workaround.
  • Old browser/app: update in maintenance window.
  • Format accepted but metadata lost: configure exporter/receiver mapping.

Limits and cautions

Important: This draft is not a permanent support matrix. Confirm current release notes and contractual support before procurement or compliance decisions.