Teradek Prism Flex
Teradek Prism Flex: remote contribution, return, and venues
Prepare an inter-venue video link with defined encoder, decoder, and network. Evaluate integration, compatibility, and reception testing with GLMedia.
Model and application
Identify Prism Flex generation and role: Mk I distinguishes encoder 855 and decoder 875; Mk II distinguishes encoder 856 and decoder 858. Do not assume every unit encodes and decodes simultaneously or has identical outputs.
Connections and limits
- Signal
- The encoder receives HDMI or SDI according to variant; the decoder delivers video to the destination. Tables include formats up to UHD60, but standard, interface, and configuration must match at both ends.
- Transport
- Choose SRT or other protocols according to generation, firmware, and receiver. Prepare network, addresses, ports, caller/listener role, and private parameters; a shared protocol does not guarantee every codec/audio profile.
- Options and support
- Bidirectional operation on the Mk II encoder is listed with an additional license; Core and cloud services require scope confirmation. Use specified power, ventilated installation, and recording media only where documented.
Preparation and troubleshooting
- Record label, firmware, licenses, and role at each venue. Check local source and receiver output before investigating Internet; save approved settings.
- Coordinate settings and connectivity with the network owner. Test the agreed link under controlled conditions, then on real networks; do not modify others’ firewalls or expose keys.
- Measure end-to-end delay with visible and audible references, plus loss, stability, and recovery. Rehearse remote participation and return using agreed content and duration.
Show use and alternatives
We can evaluate contribution from another venue into show production: source, encoder, compatible reception, audio, monitoring, and operation at both ends. Quote any return route explicitly.
For a simple call, compare computer and meeting platform; for production reception, a contribution link may fit better. Start with venues, use, date, and live conversation needs; format and network design follow.
Frequently asked questions
Does Prism Flex alone identify encoder versus decoder?
No. Check generation, unit code, connectors, and licenses. Mk II lists bidirectional encoding/decoding on the encoder as an option; do not transfer this to every historical unit.
Does SRT guarantee fixed delay or uninterrupted video?
No. Actual delay depends on encoding, buffers, network, receiver, and display. Measure and approve it for the use; nominal figures do not validate conversation or show return.
Can any SRT device receive the signal?
Compare roles, address, port, encryption, codec, profile, resolution, and audio. Test both real endpoints; reception on another computer does not replace that test.
Is return video included in the main send?
Do not assume so. Define returning picture/audio, destinations, compatible hardware, and activation. Confirm licenses and version before offering bidirectional operation.
Do all links need Core?
There is no universal requirement asserted. The guide describes direct routes and Core services; choose architecture for network, distribution, and operation. Bonding and cloud are not assumed included or free.
Why is there picture without expected audio or captions?
Check channels, codec, and receiver/firmware support for auxiliary data. Test end to end; another revision’s experience does not establish event-unit support.
Manufacturer documentation
Documentation reviewed: October 23, 2026