RTMP remains one of the most widely supported ingest protocols across streaming platforms and CDNs worldwide. YouTube Live, Facebook Live, and most professional streaming platforms accept RTMP as their primary ingest protocol. For broadcasters distributing live content to online audiences, either as a primary distribution channel or alongside traditional linear broadcast, RTMP encoding is the standard workflow step that connects broadcast production to streaming platform delivery.
BridgeWIZ is Tricube's GPU-accelerated RTMP encoder software. It accepts SDI, HDMI, NDI, ST2110, SRT, HLS, YouTube Live, and screen capture sources and encodes them to RTMP in real time through a full GPU processing pipeline. RTMP is one of several simultaneous outputs: the same source can be delivered to RTMP, NDI, SRT, SDI, UDP, and local ISO recording at the same time from one encoding pass.
What is RTMP and why it matters for broadcast streaming
Real-Time Messaging Protocol was originally developed by Macromedia, later Adobe, for streaming audio, video, and data over the internet. Although it is decades old, RTMP remains the dominant ingest protocol for live streaming platforms because of its low latency, wide platform support, and reliable delivery of live content.
RTMP key characteristics:
Universal platform support
YouTube, Facebook, and most professional streaming platforms and CDNs accept RTMP as their primary live ingest protocol. Few other ingest protocols have comparable platform coverage.
Low latency for live ingest
RTMP delivers video to streaming platform ingest points with latency typically under five seconds, lower than HLS and other protocols used for viewer-facing distribution. This makes RTMP the appropriate protocol for the contribution leg of a streaming workflow, from the broadcast facility to the platform.
Reliable live streaming delivery
RTMP's persistent connection model keeps a stable connection between the encoder and the streaming platform, and most implementations reconnect automatically when the connection is interrupted.
RTMPS: encrypted RTMP
RTMPS adds TLS encryption to RTMP. Some platforms, including Facebook, require it for secure stream ingest. BridgeWIZ supports both RTMP and RTMPS output.
Sources BridgeWIZ encodes to RTMP
BridgeWIZ accepts the following sources for RTMP encoding:
SDI and HDMI
From Blackmagic Design DeckLink, AJA, Magewell, Deltacast, and Bluefish444 professional capture hardware. Broadcast-quality SDI and HDMI sources are encoded to RTMP for streaming platform delivery.
NDI
Any NDI-compatible device or software source on the network, including production systems, cameras, software tools, and hardware NDI devices, can be encoded to RTMP for streaming.
SMPTE ST2110
ST2110 IP media sources are encoded to RTMP for streaming platform delivery, connecting IP media infrastructure directly to online distribution.
SRT
Incoming SRT contribution feeds are decoded and re-encoded to RTMP, so remote production contributions can be redistributed to streaming platforms at the same time.
HLS and RTSP
Network stream sources re-encoded to RTMP output.
YouTube Live
YouTube Live streams ingested and re-encoded to RTMP for redistribution to other platforms.
Screen capture
Full screen, window, and custom region capture can be encoded to RTMP, streaming computer display output directly to platforms.
RTMP encoding specifications
BridgeWIZ encodes RTMP output using NVIDIA NVENC, Intel QuickSync, or AMD hardware acceleration:
Video codecs:
- H.264 AVC, the standard codec for RTMP streaming, which RTMP-compatible platforms widely accept
Resolution:
- Source resolution output
- Resolution scaling, such as 4K to HD or HD to SD, configurable per output
- Platform-specific resolution presets configurable per destination
Frame rate:
- Source frame rate output
- Frame rate conversion configurable per output
Bitrate:
- Configurable per RTMP destination
- Variable bitrate for quality-optimised streaming
- Constant bitrate for bandwidth-controlled delivery
Connection:
- RTMP: standard unencrypted RTMP for platforms and CDNs that accept standard RTMP ingest
- RTMPS: TLS-encrypted RTMP for platforms that require secure ingest
Stream key:
- Configurable per RTMP destination
- Saved per project configuration for fast deployment
Multiple simultaneous RTMP destinations
BridgeWIZ supports multiple RTMP output destinations from a single source at the same time. The same input can stream to YouTube and Facebook together, each with its own RTMP destination URL, stream key, and encoding parameters.
This removes the need for a separate stream relay or multi-destination streaming service. BridgeWIZ encodes and delivers directly to multiple RTMP destinations from one GPU processing pass.
Simultaneous outputs alongside RTMP
BridgeWIZ encodes RTMP as one output among several simultaneous destinations. The same source delivers simultaneously to:
- RTMP: streaming to YouTube, Facebook, and other platforms
- NDI: full-bandwidth network output for production systems
- SRT: for contribution or distribution over IP
- SDI: physical output to broadcast infrastructure
- UDP: multicast or unicast network delivery
- Local ISO file: independent recorded file per source
One source feeds multiple simultaneous outputs from one GPU processing pass, without separate encoder appliances.
Live graphics on RTMP streaming
BridgeWIZ's built-in HTML graphics engine adds live broadcast graphics to the source during RTMP encoding. Graphics are rendered in the GPU pipeline and embedded in the RTMP output stream delivered to streaming platforms:
- Scrolling tickers and news banners
- Lower thirds and name straps
- Logo overlays and watermarks
- Date and time displays
- Live time counter and elapsed time
- Custom HTML templates
Add channel branding, live news tickers, sponsor overlays, and custom graphics to streaming platform output without a separate CG system. Graphics appear on the streamed output exactly as they appear on the broadcast signal.
RTMP streaming use cases in broadcast
Linear broadcast to streaming platform simulcast
Broadcasters simulcasting linear television content to YouTube Live or Facebook Live encode the broadcast programme feed, from SDI or NDI, to RTMP for streaming platform delivery alongside the traditional broadcast output.
Remote production to streaming
Outside broadcast locations encode programme feeds directly to RTMP for streaming platform delivery, using BridgeWIZ alongside SRT contribution to the base facility. The same source goes to base over SRT and to the platform over RTMP at the same time.
ST2110 facility to streaming platform
ST2110 signals from IP media infrastructure are encoded directly to RTMP, connecting professional broadcast facility infrastructure to streaming platform delivery without intermediate format conversion steps.
Multi-platform simultaneous streaming
Content is delivered to YouTube and Facebook at the same time from a single source and one BridgeWIZ instance. Each platform receives its own RTMP stream with its own stream key and encoding parameters.
Screen capture to streaming
Presentations, software demonstrations, and computer display content are captured and streamed directly to RTMP destinations, without dedicated streaming hardware or separate streaming software.
Multi-instance RTMP encoding
Run multiple independent BridgeWIZ instances on a single GPU server, each encoding a different source to RTMP at the same time. Each instance has its own input, its own RTMP destination configuration, and its own graphics setup.
Multi-channel streaming operations, teleports, and broadcast facilities with several channels going to streaming platforms often need multiple RTMP streams at once. Multiple instances on one GPU server can take the place of several dedicated hardware streaming encoders.
How BridgeWIZ differs from hardware RTMP encoders
Dedicated hardware RTMP encoder boxes perform one fixed encoding: one video input to one or two RTMP outputs. Each box handles one channel, so expanding to multiple channels means buying more boxes.
BridgeWIZ performs RTMP encoding in software on GPU-accelerated server hardware, with simultaneous additional outputs, live graphics, resolution scaling, and ISO recording included. Multiple instances on one server handle several RTMP encodings at once without additional encoder hardware.
FAQs
What is RTMP encoder software used for in broadcast?
RTMP encoder software converts video sources into Real-Time Messaging Protocol streams for delivery to streaming platforms and CDNs. It is the standard workflow step that connects broadcast production sources such as SDI, NDI, and ST2110 to online delivery via YouTube Live, Facebook Live, and other RTMP-compatible platforms.
What video sources can BridgeWIZ encode to RTMP?
BridgeWIZ encodes SDI, HDMI, NDI, ST2110, SRT, HLS, RTSP, YouTube Live, and screen capture to RTMP. Any professional video source accepted by BridgeWIZ can be encoded to RTMP output simultaneously alongside other output destinations.
Does BridgeWIZ support RTMPS for encrypted streaming?
Yes. BridgeWIZ supports both RTMP and RTMPS output, so it can stream securely to platforms such as Facebook Live that require TLS-encrypted RTMP ingest.
Can BridgeWIZ stream to multiple RTMP destinations simultaneously?
Yes. BridgeWIZ supports multiple simultaneous RTMP output destinations from a single source, such as YouTube and Facebook at the same time from one instance. Each has its own destination URL, stream key, and encoding parameters.
How many simultaneous RTMP streams can BridgeWIZ handle?
Multiple BridgeWIZ instances run independently on a single GPU server, each encoding a different source to RTMP. The number of streams depends on the GPU server specification, and adding instances does not require additional hardware RTMP encoder appliances.