BRIDGE LIVE Video I/O and Streaming Appliance v1.12 74 www.aja.com
Stream Type
NDI
SDI Inputs can be encoded to NDI for output to the network.
NDI Inputs can be received, decoded and output as SDI.
IP Video Stream inputs can be transcoded to NDI for output to the network.
NDI Inputs can be received, transcoded and output as IP Video Streams.
NOTE: NDI HX is unsupported at this time.
HLS (Input)
HLS sources can be input to BRIDGE LIVE, and then decoded to SDI for output.
HLS Input supports AVC TS segments and fragmented MP4.
HLS (Output)
HLS Output supports AVC TS segments.
SDI sources can be input to BRIDGE LIVE, and then encoded for sharing via HLS.
IP Video Stream sources can be input to BRIDGE LIVE, and then encoded for
sharing via HLS.
MPEG-TS
BRIDGE LIVE supports data transmission using MPEG-TS (MPEG Transport Stream)
container format. The transport stream is used in broadcast systems and is
designed to be used in terrestrial or satellite broadcast, for example. It can carry
multiple programs. Each program contains packets of video stream, audio stream
and metadata (if present).
BRIDGE LIVE supports receiving and processing the MPEG-TS streams, detects all
programs, and allows its users to choose them easily.
RTMP(S)
BRIDGE LIVE supports RTMP streaming (output only). RTMP output in BRIDGE LIVE
supports both streams with and without authentication. The protocol is used for
video, audio and data streaming over the Internet and serves as a bridge between
Flash player and a server.
BRIDGE LIVE supports RTMP (output only) in the H.264 video codec and the
AAC audio codec. Some services, such as YouTube, do not accept RTMP streams
without audio.
To set up an RTMP output stream, select Output stream options, Stream type as
RTMP and just beneath it, fill out the URL address. An example URL of a stream
with authentication is the following:
rtmp://user:pass@IPADDRESS/application/stream-key
If you have provided a valid URL, BRIDGE LIVE will produce an output stream
upon starting the configured pipeline using RTMP.
You can see how the UI looks without a configured URL address in Figure 120.