Live video gateway

SRT decoder software for broadcast

An SRT decoder receives a Secure Reliable Transport stream over an IP network and converts it in real time to one or more broadcast formats, such as SDI, NDI, RTMP, UDP, or local file recording, for use in downstream broadcast infrastructure and production workflows.

SRT has become one of the most widely used protocols for broadcast contribution over IP. Remote production locations, OB vehicles, satellite uplinks, streaming platforms, and distribution partners send video via SRT. At the receiving end, whether a broadcast facility, playout centre, or production hub, an SRT decoder converts the incoming stream into the formats that local infrastructure requires.

Without an SRT decoder, an SRT contribution feed cannot feed an SDI production switcher, an NDI production system, or a local recording workflow. The SRT decoder is the receiving endpoint of every SRT contribution workflow and is as essential as the SRT encoder at the sending end.

BridgeWIZ is Tricube's GPU-accelerated SRT decoder software. It receives SRT streams in caller, listener, or rendezvous mode, decodes them through a full GPU processing pipeline, and outputs simultaneously to SDI, NDI, RTMP, UDP, and local ISO file recording.

What SRT decoding is used for in broadcast

Remote production contribution receive

OB vehicles and remote production locations send programme feeds via SRT. At the base facility, an SRT decoder receives the contribution feed and converts it to SDI for the production switcher or NDI for the production network.

Multi-site signal receive

Broadcasters receiving signals from remote studios, affiliate stations, or distribution partners via SRT decode incoming streams to SDI or NDI for integration into local production and playout infrastructure.

Streaming platform ingest

Platforms and CDNs delivering content via SRT are decoded to NDI or SDI for local monitoring, recording, and distribution.

Contribution feed monitoring and recording

Incoming SRT contribution feeds are decoded and sent simultaneously to a monitor feed and a local ISO recording. This provides both confidence monitoring and an archive of received content.

ST2110 facility receive

SRT feeds received from outside the ST2110 IP media infrastructure are decoded and routed into the facility workflow alongside native ST2110 sources, without separate gateway equipment.

How SRT decoding works in BridgeWIZ

BridgeWIZ receives and decodes SRT streams through a five-stage GPU processing pipeline:

  1. Stage 1: SRT stream receive

    BridgeWIZ connects to the incoming SRT stream in the configured connection mode: listener mode waits for an incoming caller connection, caller mode connects to a remote listener, and rendezvous mode sets up a peer-to-peer connection. AES decryption is applied automatically if the stream is encrypted.

  2. Stage 2: GPU decoding

    The received SRT stream, encoded in H.264 or H.265 HEVC, is decoded on GPU hardware. NVIDIA, Intel, or AMD GPU decoding reduces CPU load and increases the number of simultaneous SRT streams that a single server can decode.

  3. Stage 3: GPU processing

    The decoded video passes through the GPU processing pipeline for format conversion, resolution scaling and frame rate conversion where required, and graphics overlay if configured. All processing runs on GPU hardware.

  4. Stage 4: Output encoding

    The processed video is encoded for each configured output: NDI for network distribution and H.264 or H.265 for RTMP or UDP output. For SDI, it is prepared for physical output.

  5. Stage 5: Simultaneous output delivery

    The encoded video is delivered to all configured destinations simultaneously, including SDI physical output, NDI network output, RTMP streaming, UDP multicast, and local ISO file recording. Every output comes from the same decoded SRT stream.

SRT connection modes supported

BridgeWIZ supports all three SRT connection modes for receiving incoming streams:

Listener mode

BridgeWIZ opens a port and waits for an incoming SRT caller connection. The remote SRT encoder connects to BridgeWIZ at the configured IP address and port. This is the standard mode for contribution receive at a fixed facility endpoint.

Caller mode

BridgeWIZ initiates a connection to a remote SRT listener. This mode is used when the receiving end needs to pull a stream from a remote server or platform that operates in listener mode.

Rendezvous mode

Both ends connect to each other simultaneously. This mode is used for peer-to-peer connections where neither end has a reliable fixed IP address, or where firewall traversal is needed without port forwarding.

Simultaneous outputs from one SRT stream

BridgeWIZ decodes an incoming SRT stream and delivers it simultaneously to multiple destinations:

  • SDI: physical output to a production switcher, router, or transmission equipment
  • NDI: full-bandwidth network output to production systems and software tools
  • RTMP: redistribution to streaming platforms
  • UDP: multicast or unicast distribution to local network destinations
  • Local ISO file: an independent recorded file of the received SRT stream

One incoming SRT stream feeds multiple simultaneous outputs in a single GPU processing pass, with no additional hardware.

Live graphics on SRT decoded output

BridgeWIZ's built-in HTML graphics engine adds live broadcast graphics to the decoded SRT stream before it is sent to downstream destinations. Graphics are rendered in the GPU pipeline and embedded in all output streams simultaneously:

  • Scrolling tickers and news banners
  • Lower thirds and name straps
  • Logo overlays and watermarks
  • Date and time displays
  • Custom HTML templates

Add channel identification, live news graphics, or branding overlays to incoming SRT contribution feeds without a separate CG system.

Resolution scaling during SRT decoding

BridgeWIZ performs resolution scaling and format conversion during SRT decoding, independently of the incoming stream parameters:

  • HD SRT stream decoded and upscaled to 4K for downstream infrastructure requiring 4K
  • HD SRT stream decoded and downscaled to SD for legacy SD infrastructure
  • Frame rate conversion where downstream equipment requires a different frame rate
  • Colour space conversion where required

The output format is fully independent of the incoming SRT stream format.

SRT decoding with encryption

BridgeWIZ supports AES-128 and AES-256 encrypted SRT streams and decrypts them automatically using the configured passphrase. Encrypted SRT contribution feeds from remote locations are decrypted and decoded in the same GPU pipeline as unencrypted streams, with no additional processing overhead visible to the operator.

Multi-instance SRT decoding

Run multiple independent BridgeWIZ instances on a single GPU server, each decoding a different incoming SRT stream at the same time. Each instance has its own SRT input configuration (connection mode, port, and encryption passphrase) and its own output destinations.

For facilities receiving several SRT contribution feeds at once, such as multi-channel contribution receive, teleports handling multiple incoming streams, and broadcast facilities with multiple remote production locations, multiple instances on one GPU server can take the place of several dedicated hardware SRT decoder appliances.

How BridgeWIZ differs from hardware SRT decoders

Dedicated hardware SRT decoder boxes typically receive and decode one SRT stream and deliver one or two fixed outputs. Each box handles one channel, so expanding to multiple channels means buying more boxes.

BridgeWIZ receives and decodes SRT streams in software on GPU-accelerated server hardware, delivering simultaneous SDI, NDI, RTMP, UDP, and local ISO recording outputs from each incoming stream. Multiple instances on one server handle several SRT streams at once without additional hardware.

FAQs

What is SRT decoder software used for in broadcast?

SRT decoder software receives incoming SRT contribution streams and converts them to broadcast formats such as SDI, NDI, RTMP, UDP, and local recording for use in downstream broadcast infrastructure. It is the receiving endpoint of every SRT contribution workflow, converting remote production feeds, multi-site signals, and streaming platform outputs into formats that local broadcast equipment can use.

What SRT connection modes does BridgeWIZ support for decoding?

BridgeWIZ supports SRT listener, caller, and rendezvous connection modes for receiving incoming SRT streams. Listener mode waits for incoming connections. Caller mode initiates a connection to a remote listener. Rendezvous mode enables peer-to-peer connection for firewall traversal.

Does BridgeWIZ support encrypted SRT streams?

Yes. BridgeWIZ automatically decodes AES-128 and AES-256 encrypted SRT streams, decrypting incoming contribution feeds with the configured passphrase and no additional processing overhead visible to the operator.

Can BridgeWIZ output to multiple destinations from one incoming SRT stream?

Yes. BridgeWIZ decodes an incoming SRT stream and delivers it simultaneously to SDI, NDI, RTMP, UDP, and local ISO file recording, all from the same decoded stream in one GPU processing pass.

How many simultaneous SRT streams can BridgeWIZ decode?

Multiple BridgeWIZ instances run independently on a single GPU server, each decoding a different incoming SRT stream. The number of streams scales with the GPU server specification, without buying additional hardware SRT decoder appliances.

Get started

See BridgeWIZ working with your sources

Book a demo and our broadcast engineers will demonstrate BridgeWIZ using your sources, destinations, and channel requirements.