AJA 1072859 Video IO and Streaming Appliance Installation Guide
- June 16, 2024
- AJA
Table of Contents
AJA 1072859 Video IO and Streaming Appliance
Product Information
Specifications
- Version: 1.14
- Published: June 27, 2023
Overview
The BRIDGE LIVE Video I/O and Streaming Appliance is a powerful device
designed for video input/output and streaming capabilities.
It provides advanced features and supports various encoding and decoding
protocols.
AJA and Comprimato
The BRIDGE LIVE is a collaboration between AJA and Comprimato, combining their expertise to deliver a high-quality and efficient streaming solution.
Features
The BRIDGE LIVE offers the following features:
- Video input and output
- Streaming capabilities
- Metadata support
- Encoding and decoding protocols
Metadata
The BRIDGE LIVE supports metadata, allowing users to embed additional information into their video streams.
Encoding and Decoding Protocols Supported
The BRIDGE LIVE supports a wide range of encoding and decoding protocols, ensuring compatibility with various streaming platforms and devices.
Hardware Description
Chassis Front
The front of the BRIDGE LIVE chassis features various ports and indicators for easy access and monitoring.
Chassis Rear
The rear of the BRIDGE LIVE chassis provides additional ports for connectivity and expansion options.
Product Usage Instructions
What’s In the Box?
When you receive your BRIDGE LIVE Video I/O and Streaming Appliance, make sure the package contains the following items:
- BRIDGE LIVE device
- Power adapter
- Ethernet cable
- User manual
Quick Start Guide Login Credentials
Before you begin using the BRIDGE LIVE, you need to log in using the provided credentials. Please refer to the Quick Start Guide for the login information.
Installation Summary
The installation process of the BRIDGE LIVE involves the following steps:
- Unpacking the device
- Mounting the chassis
- Connecting AC power
- Setting up initial system access via the local kiosk interface
- Accepting the End User License Agreement (EULA)
- Configuring basic information, network connectivity, and GPU/CPU acceleration
Initial Hardware Installation
Unpacking
Start by unpacking the BRIDGE LIVE device and ensuring all the included items are present.
Mounting the Chassis
Next, securely mount the chassis in a suitable location, following the instructions provided in the user manual.
Connect AC Power
Connect the provided power adapter to the BRIDGE LIVE and plug it into a power outlet.
Initial System Access via Local Kiosk Interface
EULA
Upon powering on the BRIDGE LIVE, you will be prompted to accept the End User License Agreement (EULA) displayed on the local kiosk interface.
Initial System Setup Process
Basic Information
During the initial setup process, you will be required to enter basic information such as system name, date, and time.
Network Connectivity
Configure the network settings of the BRIDGE LIVE, including IP address, subnet mask, gateway, and DNS servers, to ensure proper connectivity.
GPU and CPU Acceleration
If your system supports GPU and CPU acceleration, you can enable these features to enhance the performance of the BRIDGE LIVE.
Configuration Summary
Review the configuration summary to ensure all the settings are correct before finalizing the setup process.
FAQs
Q: How can I contact AJA support for assistance?
A: You can contact AJA support through telephone at +1.530.271.3190 or via their support website at https://www.aja.com/support/contact. You can also reach out to them through email at support@aja.com.
Q: Where is the shipping address for AJA Video Systems?
A: The shipping address for AJA Video Systems is 180 Litton
Drive, Grass Valley, CA 95945, USA.
BRIDGE LIVE
Video I/O and Streaming Appliance
Installation and Operation Guide
Version 1.14 Published June 27, 2023
Notices
Trademarks
AJA® and Because it matters.® are registered trademarks of AJA Video Systems,
Inc. for use with most AJA products. AJATM is a trademark of AJA Video
Systems, Inc. for use with recorder, router, software and camera products.
Because it matters.TM is a trademark of AJA Video Systems, Inc. for use with
camera products. Corvid Ultra®, lo®, Ki Pro®, KONA®, KUMO®, ROI® and T-Tap®
are registered trademarks of AJA Video Systems, Inc. AJA Control RoomTM,
KiStorTM, Science of the BeautifulTM, TruScaleTM, V2AnalogTM and V2DigitalTM
are trademarks of AJA Video Systems, Inc. All other trademarks are the
property of their respective owners.
Copyright
Copyright © 2023 AJA Video Systems, Inc. All rights reserved. All information
in this manual is subject to change without notice. No part of the document
may be reproduced or transmitted in any form, or by any means, electronic or
mechanical, including photocopying or recording, without the express written
permission of AJA Video Systems, Inc.
Contacting AJA Support
When calling for support, have all information at hand prior to calling. To
contact AJA for sales or support, use any of the following methods:
Telephone: +1.530.271.3190 Support Website:
https://www.aja.com/support/contact
Support Email: support@aja.com Sales Email:
sales@aja.com
Shipping Address: AJA Video Systems 180 Litton Drive Grass Valley, CA 95945,
USA
BRIDGE LIVE Video I/O and Streaming Appliance v1.14
www.aja.com
Introduction
Overview
BRIDGE LIVE is a broadcast quality, low latency turnkey system for REMI,
Synchronous Multi-Channel Video Contribution, Remote Collaboration, Direct to
Audience Streaming, and Multi Bit Rate/Format Delivery.
NOTE: REMI is an acronym used in the broadcast industry for Remote Model
Integration and is sometimes called “at home” production.
Equipped with 12G-SDI I/O plus the power and flexibility to enable real time
bidirectional encoding, decoding, and transcoding for critical UltraHD and HD
workflows, BRIDGE LIVE is an essential part of any modern live video
production toolkit. A compact and robust 1RU form factor with redundant power
supplies and a 3 year warranty means peace of mind even when dealing with the
most demanding applications.
Whether facilitating remote production, two-way interviews, live event
streaming, synchronous multi-cam backhaul with HDR, cloud contribution,
program return, confidence monitoring, collaborative production, ABR ladder
profiles to hand-off for OTT packaging, BRIDGE LIVE ensures simultaneous,
secure, and stable workflows whether over private lines or the public
internet.
AJA and Comprimato
BRIDGE LIVE represents an exciting partnership between AJA and Comprimato,
both long standing industry innovators. The merging of AJA’s hardware
development and video I/O expertise with Comprimato’s transcoding and internet
transport know-how means customers can expect the versatility, speed, and
quality needed for that competitive edge. The unique fusion of company talent
between AJA and Comprimato ensures that BRIDGE LIVE delivers the performance,
reliability, and ease of use needed for critical live encode, decode, or
transcode needs.
Features
· 12G-SDI/3G-SDI I/O supports Multi-Channel HD or UltraHD as standard ·
Bidirectional Encode/Decode/Transcode; NDI, H.265 (HEVC), H.264 (AVC,
MPEG-4), H.262 (MPEG-2), and with optional licenses JPEG 2000 (TR-01), and
JPEG XS (TR-07) · Synchronous Multi-Channel / Multi-System Transport for SDI
backhaul or Cloud Delivery · Protocols; SRT, UDP, HLS, RTP, RTMP/S (output),
MPTS (input) · Transports; MPEG-TS, NDI, AVC-TS, Fragmented MP4 (input) · NDI
Discovery Server support · Supports NDI Groups · Multi bit rate/format
distribution, ABR Ladder Profiles for OTT hand-off. · Selectable profiles for
10-bit and 8-bit, 4:2:2 and 4:2:0 · Unmatched Metadata capabilities including
MPEG-2 ANC, SMPTE 2038, Ad insertion markers (SCTE-35/SCTE-104), CC/Subtitles
(EIA-608/708, Line 21, H.264 SEI) · HDR/SDR from SDI source to SDI destination
in BRIDGE LIVE end-to-end configurations
BRIDGE LIVE Video I/O and Streaming Appliance v1.14
6
www.aja.com
· Remote WebUI or local GUI for easy administration, control, and operation. · Monitoring, Control, and Automation supported via REST API or SNMP · Turnkey 1RU rack-mountable, enterprise-class form factor · Dual 10GbE interface for control and transport · Dual power supplies for critical application redundancy · Three year warranty
Metadata
BRIDGE LIVE allows the pass through of metadata, and supports various codecs,
protocols,and transports: · Generic SDI VANC metadata via SMPTE 2038 ANC
(MPEG-2 ANC) · Closed Captioning (EIA-608/708 including conversion) ·
CC/Subtitles embedding into H.264 SEI messages · SDR/HDR Transfer
Characteristics, Colorimetry + Luminance · Timecode · Ad insertion markers
(SCTE-35/SCTE-104) pass through · Line 21 captions · Electronic program guide
(EPG) on input
NOTE: “End-to-End SDI Transport” refers specifically to workflows where the
first BRIDGE LIVE is receiving SDI and sending IP video to a second BRIDGE
LIVE, which is receiving IP video and outputting SDI.
NOTE:
End-to-End SDI workflows support HDR transport (SDI to IP to SDI), but this is only possible when the IP Video format supports 4:2:2, 10-bit and as such, is a function of using either H.264 (AVC) 4:2:2, 10-bit (HQ), or JPEG2K TR-01 4:2:2 and JPEG XS TR-07, 10-bit.
Encoding and Decoding Protocols Supported
BRIDGE LIVE supports encoding from SDI to Stream, and decoding from Stream to
SDI. Encoding and decoding between SDI, JPEG 2K and JPEG XS streams is also
fully supported (watermark removed), with installation of optional licenses.
Transcoding between any Stream input and Stream output is also supported.
See Table 1 “SDI to Stream Encoding” on page 8 and Table 2 “Stream to SDI
Decoding” on page 9 for detailed signal specifications. The table values are
recommendations only. You can use lower values if you need to, and if you have
good enough network throughput you can use higher bit rates.
BRIDGE LIVE Video I/O and Streaming Appliance v1.14
7
Table 1. SDI to Stream Encoding
Codec/Quality
NDI UYVY 4:2:2, 8-bit P216 4:2:2, 16-bit H.265 (HEVC) 4:2:0, 8/10-bit
HD (1080p) 4x up to 60p 105-165 Mbps
4x up to 60p 5-12 Mbps
H.264 (AVC) 4:2:0, 8-bit
4x up to 60p 8-15 Mbps
H.264 (AVC) 4:2:2, 10-bit (HQ)
4x up to 30p 2x up to 60p 50-75 Mbps
H.262 (MPEG2) 4:2:0, 8-bit
H.262 (MPEG2) 4:2:2, 8-bit (HQ)
JPEG2K TR-01 4:2:2, 10-bit
4x up to 30p/60i 8-15 Mbps
4x up to 30p/60i 10-20 Mbps
4x up to 60p 80-220 Mbps
JPEG XS 4:2:2 10-bit
4x up to 60p.
Possible to increase count, depending on remaining resources
180-400Mbps
UltraHD 1x up to 60p 2x up to 30p 150-312 Mbps 1x up to 60p 2x up to 30p
35-110 Mbps 1x up to 60p 2x up to 30p 40-75 Mbps
1x up to 30p 80-120 Mbps
1x up to 60p 2x up to 30p 200-800 Mbps
1x up to 60p 2x up to 30p 360-1600 Mbps
Protocol NDI
HLS RTP SRT UDP HLS RTP RTMP/S SRT UDP HLS RTP RTMP/S SRT UDP
RTP SRT UDP RTP SRT UDP RTP SRT UDP
RTP SRT UDP
Transport Metadata NDI
AVC-TS MPEG-TS MPEG-TS MPEG-TS AVC-TS MPEG-TS MPEG-TS MPEG-TS MPEG-TS AVC-TS
MPEG-TS MPEG-TS MPEG-TS MPEG-TS
MPEG-TS MPEG-TS MPEG-TS MPEG-TS MPEG-TS MPEG-TS MPEG-TS MPEG-TS MPEG-TS
MPEG-TS MPEG-TS MPEG-TS
End-to-End: Generic SDI VANC metadata via SMPTE 2038 ANC (MPEG-2 ANC)
Encoding: SCTE-104 to SCTE-35 conversion
End-to-End: Generic SDI VANC metadata via SMPTE 2038 ANC (MPEG-2 ANC)
Encoding: SCTE-104 to SCTE-35 conversion Subtitles embedded within H.264 SEI
messages
End-to-End: Generic SDI VANC metadata via SMPTE 2038 ANC (MPEG2 ANC).
Supporting SDR/HDR Transfer Characteristics, Colorimetry and Luminance
Encoding: SCTE-104 to SCTE-35 conversion Subtitles embedded within H.264 SEI
messages
End-to-End: Generic SDI VANC metadata via SMPTE 2038 ANC (MPEG-2 ANC)
Encoding: SCTE-104 to SCTE-35 conversion
End-to-End: Generic SDI VANC metadata via SMPTE 2038 ANC (MPEG-2 ANC)
Encoding: SCTE-104 to SCTE-35 conversion
End-to-End: Generic SDI VANC metadata via SMPTE 2038 ANC (MPEG2 ANC).
Supporting SDR/HDR Transfer Characteristics, Colorimetry and Luminance
Encoding: SCTE-104 to SCTE-35 conversion
End-to-End: Generic SDI VANC metadata via SMPTE 2038 ANC (MPEG2 ANC).
Supporting SDR/HDR Transfer Characteristics, Colorimetry and Luminance
Encoding: SCTE-104 to SCTE-35 conversion
BRIDGE LIVE Video I/O and Streaming Appliance v1.14
8
www.aja.com
Table 2. Stream to SDI Decoding
Codec/Quality NDI UYVY 4:2:2, 8-bit P216 4:2:2, 16-bit NDI HX (1, 2, 3) 4:2:0,
8-bit
H.265 (HEVC) 4:2:0, 8/10-bit
H.264 (AVC) 4:2:0, 8-bit
H.264 (AVC) 4:2:2, 10-bit (HQ)
H.262 (MPEG2) 4:2:0, 8-bit
H.262 (MPEG2) 4:2:2, 8-bit (HQ)
JPEG2K TR-01 4:2:2, 10-bit
JPEG XS 4:2:2 10-bit
HD (1080p) 4x up to 60p 105-165 Mbps
4x up to 60p 9-16 Mbps
4x up to 60p 5-12 Mbps
4x up to 60p 8-15 Mbps
4x up to 30p 2x up to 60p 50-75 Mbps
4x up to 30p/60i 8-15 Mbps
4x up to 30p/60i 10-20 Mbps
4x up to 60p 80-220 Mbps
4x up to 60p. Possible to increase count, depending on remaining resources
180-400Mbps
UltraHD 1x up to 60p 2x up to 30p 150-312 Mbps 1x up to 60p 2x up to 30p 19-30
Mbps 1x up to 60p 2x up to 30p 35-110 Mbps
1x up to 60p 2x up to 30p 40-75 Mbps
1x up to 30p 80-120 Mbps
1x up to 60p 2x up to 30p 200-800 Mbps 1x up to 60p 2x up to 30p 360-1600 Mbps
Protocol NDI
NDI HX
HLS RTP SRT UDP
HLS RTP SRT UDP
HLS RTP SRT UDP
RTP SRT UDP RTP SRT UDP RTP SRT UDP
RTP SRT UDP
Transport NDI
Metadata
NDI
Fragmented End-to-End: Generic SDI VANC metadata MP4, AVC-TS via SMPTE 2038 ANC (MPEG-2 ANC)
MPEG-TS
MPEG-TS
MPEG-TS
Fragmented End-to-End: Generic SDI VANC metadata MP4, AVC-TS via SMPTE 2038 ANC (MPEG-2 ANC)
MPEG-TS
MPEG-TS
MPEG-TS
Fragmented MP4, AVC-TS
MPEG-TS
MPEG-TS
MPEG-TS
End-to-End: Generic SDI VANC metadata via SMPTE 2038 ANC (MPEG2 ANC), supporting SDR/HDR Transfer Characteristics, Colorimetry and Luminance
MPEG-TS MPEG-TS
End-to-End: Generic SDI VANC metadata via SMPTE 2038 ANC (MPEG-2 ANC)
MPEG-TS
MPEG-TS MPEG-TS
End-to-End: Generic SDI VANC metadata via SMPTE 2038 ANC (MPEG-2 ANC)
MPEG-TS
MPEG-TS MPEG-TS MPEG-TS
End-to-End: Generic SDI VANC metadata via SMPTE 2038 ANC (MPEG2 ANC), supporting SDR/HDR Transfer Characteristics, Colorimetry and Luminance
MPEG-TS MPEG-TS MPEG-TS
End-to-End: Generic SDI VANC metadata via SMPTE 2038 ANC (MPEG2 ANC). Supporting SDR/HDR Transfer Characteristics, Colorimetry and Luminance
Encoding: SCTE-104 to SCTE-35 conversion
BRIDGE LIVE Video I/O and Streaming Appliance v1.14
9
Table 3. JPEG XS (TR-07) Encoding Efficiency Mbp
Format 720p 59.94 720p 50 1080i 29.97 1080i 25 1080p 59.94 1080p 50 2160p 59.94 2160p 50
Minimum 92 77 104 86 207 173 829 691
Maximum 221 184 249 207 497 415 1989 1659
Hardware Description
Chassis Front
Figure 1. BRIDGE LIVE Chassis Front View
Power Status
Chassis Power Button
The main power switch is used to apply or remove power from the power supply
to the system. Turning off system power with this button removes the main
power but keeps standby power supplied to the system. Therefore, you must
unplug all system power cords before servicing.
Chassis Rear
Figure 2. BRIDGE LIVE Chassis Rear View
USB Ports (4)
Redundant Power Supplies
IPMI Unused
Unused
Display Port
Dual 10Gig Ethernet Streaming Video I/O
BRIDGE LIVE Video I/O and Streaming Appliance v1.14
10
SDI Ch 4 SDI Ch 2 Reference SDI Ch 3 SDI Ch 1
Baseband Video I/O
www.aja.com
BRIDGE LIVE is equipped with: · Two Redundant Power Supplies (IEC connectors)
· Two USB 3.0 (blue) connectors · Two USB 2.0 (black) connectors · Two 10Gb
RJ-45 Ethernet connectors · Three Display Ports for use with monitors · One
IPMI (Intelligent Platform Management Interface) RJ-45 connector · Four bi-
directional 12G-SDI connectors · One Video Reference input port
Rear Panel Power Supply LEDs
On the rear of each power supply module an LED indicates its status as
follows. · Solid Green: When illuminated, indicates that the power supply is
on. · Solid Amber: When illuminated, indicates the power supply is plugged in
and
turned off, or the system is off but in an abnormal state. · Blinking Amber:
When blinking, this system power supply temperature has
reached 63°C. The system will automatically power-down when the power supply
temperature reaches 70°C and restarts when the power supply temperature goes
below 60°C.
Workflow Examples
REMI (Remote Production)
Since BRIDGE LIVE can be used as an encoder, decoder and transcoder, there are
many advantages to its use in REMI workflows. Additionally, BRIDGE LIVE can
take independent SDI source inputs, and maintain their synchronous
relationship while transporting the content to end-point destinations. This
functionality can take place between a pair of BRIDGE LIVE units for a
synchronous end-to-end SDI workflow, often referred to as SDI backhaul, or
siteto-site SDI workflows. BRIDGE LIVE’s synchronous multi-channel capability
is also supported for cloud contribution, whereby a BRIDGE LIVE system can
send to a cloud instance of Comprimato Live transcoder software, for delivery
to various platforms / cloud services as IP video.
Simultaneous Bidirectional Encoding and Decoding
BRIDGE LIVE supports simultaneous bidirectional encoding and decoding with
UltraHD, HD, and SD sources. For example, with a pair of BRIDGE LIVE systems,
a broadcast facility can receive three incoming encoded HD camera sources from
a remote location and decode them back into SDI for editing and production
while simultaneously providing an HD program return to the remote location.
BRIDGE LIVE Video I/O and Streaming Appliance v1.14
11
www.aja.com
Figure 3. Multi-Channel Synchronous Transport for Backhaul
Synchronous Multi-Channel Transport for Backhaul
For SDI backhaul or other site-to-site SDI workflows, BRIDGE LIVE’s bi-
directional functionality means BRIDGE LIVE can act as an encoder or a
decoder, and do so simultaneously. As such, references to BRIDGE LIVE Tx or
BRIDGE LIVE Rx are only descriptions of how the unit is currently configured.
A single BRIDGE LIVE unit can be configured for encode only, decode only, or a
combination of both.
BRIDGE LIVE Synchronous Multi-Channel Transport functionality provides an easy
and repeatable way to ensure synchronous SDI video sources can be fed to an
encoding BRIDGE LIVE (Tx), then be timestamped, transported, and ultimately
output from the decoding BRIDGE LIVE (Rx) with each SDI signal in lock step
with each other.
Furthermore, Synchronous Multi-Channel Transport can be scaled up from a
single BRIDGE LIVE pair to additional BRIDGE LIVE pairs, to enable workflows
where multiple BRIDGE LIVE systems can be receiving SDI and sending to
multiple BRIDGE LIVE systems outputting SDI, all in synchronicity.
For end-to-end SDI workflows, HDR is also supported.
BRIDGE LIVE Video I/O and Streaming Appliance v1.14
12
Figure 4. Multi-Channel Synchronous Transport for Backhaul
Synchronous Multi-Channel Transport for Cloud Contribution
When using individual or multiple BRIDGE LIVE systems for contribution to
cloud platforms/services, the receiving side is supported by single or
multiple instances of Comprimato Live Transcoder software. From Live
Transcoder, Synchronous Multi Channel IP Video can be handed off to 3rd party
services.
NOTE: AWS references are examples. Comprimato Live Transcoder can be used as
the receiver with other cloud providers/services.
BRIDGE LIVE Video I/O and Streaming Appliance v1.14
13
Figure 5. Multi-Channel Synchronous Transport for Cloud
BRIDGE LIVE as a Receiving Hub
BRIDGE LIVE supports workflows where it is necessary to receive contribution
streams coming from various 3rd party encoders, IP cameras, or AJA products
such as HELO Plus, for conversion back/to SDI at a production facility.
For example, BRIDGE LIVE could be receiving UDP or HLS from AJA HELO Plus, SRT
from a Panasonic camera (e.g. AW-UE150, AW-UE100, AG-CX350, AJ-CX4000), SRT
from a Haivision encoder (e.g. Makito X4), and NDI from AJA Bridge NDI,
software such as NLE or Gaming PC, NDI cameras, or hardware based encoders
such as Birdog (e.g. Studio NDI) and Magewell (e.g. ProConvert).
BRIDGE LIVE Video I/O and Streaming Appliance v1.14
14
www.aja.com
Figure 6. BRIDGE LIVE as a Receiving Hub
Contribution
Remote Video Transport
For Broadcast, BRIDGE LIVE provides an efficient mechanism for backhauling
remote live SDI camera sources to the media production facility, in order to
be converted back to SDI and made available on the internal facility SDI
router for ongoing production/transmission.
Traditional secure lines for remote production can be very expensive, with
additional fees being levied for time before and after a production starts and
ends. BRIDGE LIVE allows source cameras and local program out to be
transported using publicly available Internet, with no penalty for early or
extended use during a production. BRIDGE LIVE also offers lower latency than
traditional secure lines for time critical productions.
BRIDGE LIVE Video I/O and Streaming Appliance v1.14
15
www.aja.com
Figure 7. Remote Video Transport and Contribution
Collaboration
Reference Video for Remote Creatives
Production and Post: Connecting remote artists and clients using reference
quality video, or providing a high quality window into production for those
who cannot be on-set.
BRIDGE LIVE means the flexibility to leave media and equipment at the secure,
managed facility, and have creative talent work together remotely with
reference quality video.
BRIDGE LIVE compliments existing GUI driving technologies (e.g. RDP, Teradici)
by layering on the reference quality video needed for creative confidence and
client/ executive sign-off. Choices between H.265 (4:2:0, 10-bit), H.264
(4:2:2, 10-bit) with turnkey BRIDGE LIVE, or via optional license JPEG 2000
(4:2:2, 10-bit), mean there is choice and flexibility in how to approach your
needs in terms of quality and latency.
BRIDGE LIVE Video I/O and Streaming Appliance v1.14
16
www.aja.com
Figure 8. BRIDGE LIVE for Facility HD Streaming to Creatives and Clients
Secure Window into the Remote Set or Studio
BRIDGE LIVE also offers the flexibility to tap video from on-set recording
devices and stream the output of cameras (over a secure private line with
encryption) providing a high quality window into production for those who
cannot be on-set.
BRIDGE LIVE Video I/O and Streaming Appliance v1.14
17
www.aja.com
Figure 9. Encoding for Remote Production UltraHD to H.265
Connecting Remote NDI Production Teams
BRIDGE LIVE can be used to connect two geographically separated NDI production
teams via Public Internet.
For example, a studio or event location could be sending the feeds from 3 NDI
cameras to an NDI production or post facility, which can distribute those
sources as both NDI and SDI, while also returning a program feed back to the
studio location.
BRIDGE LIVE Video I/O and Streaming Appliance v1.14
18
www.aja.com
Figure 10. Connecting Remote NDI Production Teams
Streaming
Direct-to-Audience Streaming
BRIDGE LIVE offers a comprehensive platform for live video streaming.
Streaming support includes SRT, HLS, RTMP/S, RTP, UDP, and MPEG-TS. Using
these standard protocols provides wide support for streaming services such as
Twitch, YouTube Live and Facebook Live. BRIDGE LIVE builds upon the tried and
tested approach of AJA’s HELO Plus streaming device, while including
flexibility for multiple bi-directional transport, broad format and bit-rate
support, as well as metadata and redundancy. And, while streaming to CDNs for
a direct-to-audience delivery, BRIDGE LIVE can simultaneously deliver
different stream types to partners to re-transmit, transcode, or store.
BRIDGE LIVE Video I/O and Streaming Appliance v1.14
19
Figure 11. Direct to Audience Streaming for UltraHD Workflows
Delivery
Encoding For Content Distribution
For Studios and Broadcast applications BRIDGE LIVE facilitates primary
distribution of finished and mastered content to partners for subsequent
streaming to audiences.
BRIDGE LIVE can provide ABR ladder profiles or hand-off for OTT packaging. For
example, encoding to H.264 or H.265 for hand-off with ABR ladder profiles,
including pointing the ladder profile directly to a local packager or CDN.
BRIDGE LIVE can also provide multi-format/rate/bit-rate material via HLS. The
combined outputs within the HLS stream are presented as a “playlist”, meaning
that devices (e.g. phones or tablet) or software (e.g. web browser) can pull a
particular format, frame rate and bit-rate based on the device characteristics
and the current connectivity. Note that this is not a Push model. If
conditions change (e.g. available bit rate) then the receiving device can
elect to consume a different format / frame rate / bit-rate. However, multi
variants are chunked, so if a player switches to a different resolution, it
must start downloading a new chunk and this may result in a spinning wheel
since chunks are 10 seconds in length.
The best way to deliver HLS with BRIDGE LIVE is to provide the pre-packed
video to a CDN. This means many end-point-devices can utilize the content
simultaneously.
HLS could be sent to a local network in a studio or on set, to enable iPad and
iPhone to receive and monitor (provided the devices have network access to
BRIDGE LIVE). However, in this situation the number of simultaneous consumers
will need to be kept low (under 10) to avoid over-taxing BRIDGE LIVE.
BRIDGE LIVE Video I/O and Streaming Appliance v1.14
20
Figure 12. Encoding for Content Distribution
Live Production Encoding
Telcos, IPTV and cable operators are often presented with an SDI source or a
live event or live production, which is needed as a simple MPEG-Transport
Stream with H.264/H.262 encode. The delivered stream may be required for
further processing (storage, production), or else be streamed directly to an
IPTV/Cable network.
BRIDGE LIVE Video I/O and Streaming Appliance v1.14
21
www.aja.com
Figure 13. Live Production Encoding for Telco, IPTV and Cable
Synchronous Multi-Channel Transport
NOTE:
Bi-directional functionality means that BRIDGE LIVE can act as an encoder or a decoder, and can do so simultaneously. As such, references to BRIDGE LIVE Tx or BRIDGE LIVE Rx are only descriptions of what the unit is currently deployed to do, rather than references to an encode-only or decode-only model of the product.
BRIDGE LIVE can take independent SDI source inputs and maintain their
synchronous relationship while transporting the content to end-point
destinations.
This functionality can take place between a pair of BRIDGE LIVE units for a
synchronous end-to-end SDI workflow, often referred to as SDI backhaul, REMI,
or site-to-site SDI workflows.
BRIDGE LIVE’s synchronous multi-channel capability is also supported for cloud
contribution, whereby a BRIDGE LIVE system can send to a cloud instance of
Comprimato Live transcoder software for delivery to various platforms or cloud
services as IP video.
Synchronous Multi-Channel Transport for Backhaul
BRIDGE LIVE Synchronous Multi-Channel Transport functionality provides an easy
and repeatable way to ensure synchronous SDI video sources can be fed to an
encoding BRIDGE LIVE (Tx), then be timestamped, transported, and ultimately
output from the decoding BRIDGE LIVE (Rx) with each SDI signal in lock step
with each other.
Furthermore, Synchronous Multi-Channel Transport can be scaled up from a
single BRIDGE LIVE pair to additional BRIDGE LIVE pairs, to enable workflows
where multiple BRIDGE LIVE systems can be receiving SDI and sending to
multiple BRIDGE LIVE systems outputting SDI, all in synchronicity.
BRIDGE LIVE Video I/O and Streaming Appliance v1.14
22
www.aja.com
Synchronous multi-channel transport is necessary when the SDI sources being
decoded by the BRIDGE LIVE Rx are required for uses such as live production
switching, multicam recording or other live multichannel workflows.
NOTE: For end-to-end SDI workflows, HDR is also supported.
In most situations BRIDGE LIVE will yield perfect sync between sources. In
some cases a transport may occasionally drift by a maximum of 1 frame late.
Figure 14. Multi-Channel Synchronous Transport for Backhaul
Remote Sources
Reference
Reference
SDI Source 1 SDI
SDI Source 2 SDI
Genlock
Reference
Reference
SDI Source 3 SDI
SDI Source 4 SDI
Public Internet Stream or Private Line (IP Video)
Stream (IP Video)
BRIDGE LIVE Tx
(Encode SDI) +
Write Timestamps
Stream (IP Video)
Stream (IP Video)
Media Facility or Data Center
SDI
SDI Dest 1 Reference
SDI
SDI Dest 2 Reference
BRIDGE LIVE Rx (Decode SDI) +
Read Timestamp
Genlock
SDI
SDI Dest 3 Reference
SDI
SDI Dest 4 Reference
Multi-Channel Synchronous Transport for Backhaul
Synchronous Multi-Channel Transport for Cloud Contribution
When using individual or multiple BRIDGE LIVE systems for contribution to
cloud platforms/services, the receiving side is supported by single or
multiple instances of Comprimato Live encoder software.
From Comprimato Live Encoder, Synchronous Multi Channel IP Video can be handed
off to 3rd party services.
NOTE: AWS references are examples. Comprimato Live Encoder can be used as the
receiver with other cloud providers/services.
BRIDGE LIVE Video I/O and Streaming Appliance v1.14
23
Figure 15. Multi-Channel Synchronous Transport for Cloud
Remote Sources
Reference
Reference
SDI Source 1 SDI
SDI Source 2 SDI
Genlock
Reference
Reference
SDI Source 3 SDI
SDI Source 4 SDI
Public Internet Stream or Private Line (IP Video)
Cloud or Data Center
IP
AWS Media Connect
IP
AWS Media Live
Stream (IP Video)
BRIDGE LIVE Tx
(Encode SDI) +
Write Timestamps
Stream (IP Video)
Comprimato Live Transcoder (Transcode) +
Read Timestamp
IP
AWS Media Connect
IP
AWS Media Live
IP
AWS Media Connect
IP
AWS Media Live
Stream (IP Video)
IP AWS Media
Connect IP
AWS Media Live
Multi-Channel Synchronous Transport for Cloud
Configuration Requirements
The default encoding configurations should be suitable for most use cases.
However, when configuring synchronous multi-channel transport, the following
four key areas warrant careful consideration: · Genlocking · Encoding
Guidelines · Decoding Guidelines · Audio Best Practices
Genlocking
Genlock on the SDI source side should be provided to the BRIDGE LIVE Tx system
and upstream SDI source devices, such as cameras.
Genlock on the SDI destination side should be provided to the BRIDGE LIVE Rx
system and downstream SDI devices, such as switchers.
Genlocking on both the source and destination sides should be of the same
frequency.
If delivering to Comprimato Live Transcoder, genlock on the destination side
is not required.
BRIDGE LIVE Video I/O and Streaming Appliance v1.14
24
www.aja.com
Encoding Guidelines
Encode the SDI inputs using MPEG-TS.
Use equal parameters for all SDI inputs. Do not modify any video parameters
such as scan type, resolution, or frame rate.
To simplify this process of using equal parameters, you can use the “Clone”
button to replicate the configuration on a single encoder. Use the “Download”
and “Upload a preset” buttons to replicate the configuration over multiple
encoders.
Use the RTP network protocol for transport on reliable networks such as within
a single facility. Use the SRT network protocol for transport over less
reliable networks when possible packet losses may be expected.
The output of every encoding pipeline must be routed to a unique address and
port destination.
You can tune the encoding configuration to achieve your desired quality. For
example, you could choose to encode using the visually lossless codec
JPEG2000.
Decoding Guidelines
Decoders are configured to receive traffic originating from encoders and to
straightforwardly decode it to your SDI feed without modifying any video
parameters such as scan type, resolution, or frame rate.
When decoding using the SRT network protocol, you may need to tune SRT latency
to meet the requirements of the network unreliability.
Configure all decoding pipelines to equal SRT latency. This field is present
in the BRIDGE LIVE User Interface on the main page. If you see packet drops,
there could be an issue with SRT. Increasing the latency should help. Be
careful to set up the same latency in each pipeline. Refer to the pipeline
configuration on the Source side.
Audio Best Practices
For Audio, best practice is to add primary audio via a single pipeline (up to
16 channels). This may require some routing or premixing upstream of BRIDGE
LIVE (Tx).
Audio can be carried via all pipelines. However, in some circumstances, it is
possible for one or more pipelines to get up to 1 frame late. In this
scenario, the audio transported across each pipeline remains good; however, if
switching live between the SDI outputs from the BRIDGE LIVE (Rx), then some
audio clicks and pops may occur.
BRIDGE LIVE Video I/O and Streaming Appliance v1.14
25
Installation
Overview
BRIDGE LIVE ships from the factory with the latest version of software
installed.
What’s In the Box?
· BRIDGE LIVE Quick Start Guide · BRIDGE LIVE appliance, including:
· pre-installed rack-ears · rack rails · two power cables
Quick Start Guide Login Credentials
BRIDGE LIVE ships with a Quick Start Guide when it comes from the factory.
This physical document contains the login information for accessing BRIDGE
LIVE for the first time. Do not discard the unique Quick Start Guide, as these
credentials will be required following any future Factory Reset. If you do not
have this Quick Start Guide, you will need to contact AJA tech support. If you
are receiving a system that has been used elsewhere and you do not have the
password that may have been applied, you can perform a Factory Reset and then
use the factory supplied password from the Quick Start Guide to regain access
to the system for set up.
Installation Summary
First time BRIDGE LIVE configuration involves the following steps. · Unpack
the shipping box, retaining the printed BRIDGE LIVE Quick Start Guide. · Mount
the BRIDGE LIVE chassis into a standard 19-inch wide equipment rack,
allowing space for cooling airflow. The chassis occupies only one vertical
rack unit. · Connect the two BRIDGE LIVE power cords to AC mains. · Perform
initial network configuration. This is accomplished via the Kiosk interface,
using a customer supplied Display Port monitor, keyboard, and mouse. · Access
the BRIDGE LIVE UI over your network, using the unique User and Password
information for your unit, included in the printed BRIDGE LIVE Quick Start
Guide provided. · Connect your SDI sources and/or destinations to your BRIDGE
LIVE. Which SDI connectors you use depends on your intended workflow. · Create
an initial BRIDGE LIVE workflow by creating the necessary BRIDGE LIVE
Pipelines, to ether encode SDI signals to the network, decode from the network
to SDI, or for encode/decode bi-directional operation.
BRIDGE LIVE Video I/O and Streaming Appliance v1.14
26
www.aja.com
Initial Hardware Installation
Unpacking
As you unpack the shipping box, carefully examine the contents. Retain the
Quick Start Guide, which has important information for that individual BRIDGE
LIVE unit. Make sure you received everything and that nothing was damaged
during shipment. If you find any damage, immediately notify the shipping
service and supply them with a description of the damage.
If you find shipping damage, contact your AJA dealer or distributor for
details on how to have your BRIDGE LIVE repaired or replaced.
NOTE: Save packing materials and the shipping box. If your BRIDGE LIVE ever
requires service or you move your system, use the packaging materials and box
for safe shipment.
Mounting the Chassis
Mount the BRIDGE LIVE chassis as desired into a standard 19-inch wide
equipment rack, using the provided sliding rails. The chassis occupies only
one vertical rack unit.
NOTE: Cooling airflow enters the chassis from the front, and exits from the
rear and top panels. Do not obstruct these air vents.
Two rack rail assemblies are included in the rack mounting kit. Each assembly
consists of two sections: an inner fixed chassis rail that secures directly to
the server chassis and an outer fixed rack rail that secures directly to the
rack itself.
The rail assemblies are shipped with rack adapters installed for use with IT
(square hole) style rack frames. For IT racks, simply slide the unit into
place, as the rails will lock automatically. For use with a standard round
hole rack frame, you will need to remove the adapters using a small Phillips
head screwdriver.
Connect AC Power
Connect the two BRIDGE LIVE power cords to AC mains. For redundancy, use both
power supplies and connect them to separate branch circuits. Then the BRIDGE
LIVE will continue to operate even if a circuit breaker opens on one branch.
For even greater reliability, connect one BRIDGE LIVE power supply to a UPS,
and leave the other connected directly to a live circuit (not through that
same UPS). This covers the situation where the UPS itself fails. For the
highest level of protection use two UPS units connected to two different
branch circuits.
You will power up the unit later, depending on which initial network
configuration procedure you decide to use.
Initial System Access via Local Kiosk Interface
1. Connect a computer monitor (user supplied) to one of the rear Display Port
connectors.
2. Connect a keyboard and mouse (user supplied) to available rear USB
connectors.
3. Power up the chassis. The system will boot up to the BRIDGE LIVE and
display a login splash screen. The same screen will appear when connecting
using a remote network connected computer’s web interface.
BRIDGE LIVE Video I/O and Streaming Appliance v1.14
27
www.aja.com
Figure 16. BRIDGE LIVE Kiosk View Login Splash Screen
4. At the login screen, enter the system’s specific Admin credentials as
shown below:
· Username: admin
· Password: See your BRIDGE LIVE Quick Start Guide for that units unique
default password.
EULA
When you login to the BRIDGE LIVE UI for the first time, you will be prompted
to read and accept the EULA. If you change the BRIDGE LIVE version using the
Version manager, you will be required to accept it again.
Figure 17. EULA
BRIDGE LIVE Video I/O and Streaming Appliance v1.14
28
Initial System Setup Process
BRIDGE LIVE has a menu driven initial setup process available for first time
installation. This allows you to easily set basic system operation parameters.
For an initial system setup, you can simply click on the Setup (wrench) icon
on top line of the screen. This action takes you directly to the first step of
the setup process. Figure 18. Top Line with Setup Icon
NOTE: The Licensing and API top line icons can also can be clicked on to
activate them. However, there is no need to access these functions during an
initial system setup.
Alternatively you can hover your cursor over the top line Setup Icon, and then
click on the Setup item in the opened Setup Menu dropdown. This is the method
used to access all the items in this dropdown menu. NOTE: This cursor hover
technique is also used with the Admin top line Icon. However,
there is no need to access the Admin functions during initial system setup.
Figure 19. Accessing the Setup menu
After selecting Setup, a series of screens will be displayed from which you
can select or enter the necessary information. Four screens will be opened in
sequence:
· Basic Information
· Network Connectivity
· GPU & CPU Acceleration
· Configuration Summary
BRIDGE LIVE Video I/O and Streaming Appliance v1.14
29
www.aja.com
Basic Information
Figure 20. Setting the System Hostname
A Welcome screen is displayed first, allowing you to identify that specific
BRIDGE LIVE system with a unique Hostname.
HostName
Enter a name in the Hostname field, then click Next step.
Network Connectivity
Figure 21. Configuring network connectivity
The Network Connectivity screen appears. Here you configure each of the two
10GbE interfaces.
Use For
Select one of the following from the pull-down menu: · Don’t Use ·
Administration
BRIDGE LIVE Video I/O and Streaming Appliance v1.14
30
www.aja.com
· Input/Output · Input/Output and Administration NOTE: Typically
Administration is applied to only one port. If applied to more than one
port, you will see a warning message (but not an error).
NOTE: With a dual NIC setup, you cannot have both NICs connected to the same
network.
Assign Address
Configure the following as appropriate for your network: · DHCP · Static
· IPv4 Address · Mask · Default gateway · Mask · Gateway After entering all
the information, click Next step.
GPU and CPU Acceleration
This screen is informational only. It reports detected GPUs and CPUs for
acceleration of video frame decoding and encoding. Figure 22. Informational
only Configuration of GPU & CPU acceleration
Click Next step.
Configuration Summary
A summary of the final configuration settings of your device, including
hostname, network connectivity, CPU and GPU acceleration, and DNS settings.
BRIDGE LIVE Video I/O and Streaming Appliance v1.14
31
www.aja.com
Figure 23. Configuration summary
Default Route
This is used for setting up the BRIDGE LIVE system so that it communicates
correctly within your network. The default route determines which interface is
used by BRIDGE LIVE for outbound communication. The Default route is also used
for internal communication. It is typically the address of another router,
which treats the packet the same way: if a route matches, the packet is
forwarded accordingly, otherwise the packet is forwarded to the default route
of that router. Click on the Default route circle of the desired NIC.
Set DNS Manually for Whole System
You can manually set which DNS server should be used for your BRIDGE LIVE
system. The BRIDGE LIVE server will send DNS requests to either the primary or
secondary DNS server. DNS is a protocol which allows you to translate domain
names (www.domainname.com) into IP addresses
Enter any desired Primary and Secondary DNS IP addresses, and then click on
the Save and proceed to stream setup button to complete your initial system
setup. After a short time you are returned to the BRIDGE LIVE Dashboard UI
(figure). Figure 24. BRIDGE LIVE Dashboard After System Setup
BRIDGE LIVE Video I/O and Streaming Appliance v1.14
32
Once your BRIDGE LIVE has completed its initial setup, you will be able to
make it fully operational by configuring pipelines that meet your
requirements. See “Pipeline Configuration” on page 63.
BRIDGE LIVE System Administration
Once a BRIDGE LIVE system has been setup with properly configured pipelines,
the unit can be routinely reconfigured by an end user to select different
signal Inputs and Outputs and adjust other pipeline features, using the
Dashboard UI. Other more complicated system updates and re-configurations are
generally performed by a BRIDGE LIVE system administrator using other UI
menus.
Admin Menu
Some basic functions can be performed via the Admin Menu. Hover your cursor
over the Admin icon and click on the desired function. Figure 25. Open Admin
Menu
Security
Used to manage password security. See “Password Administration” on page 35
Logout
Logs you out of that BRIDGE LIVE’s web interface. This will not affect any
currently running pipelines. You will need the user name and password for that
BRIDGE LIVE unit to log back in.
Restart Service
This function assists with restarting the BRIDGE LIVE software, useful if
unexpected transport problems are encountered. An “Do you really want to
restart…?” prompt appears. After answering Yes, all currently running
pipelines will be halted and will then restart. You will also be logged out.
You will need the user name and password for that BRIDGE LIVE unit to log back
in.
Reboot
This function performs a complete reboot of the hardware, useful if serious
unexplainable problems with signals or OS occur.
BRIDGE LIVE Video I/O and Streaming Appliance v1.14
33
www.aja.com
A “Do you really want to reboot…? prompt appears. After answering Yes, all
currently running pipelines will be halted, the BRIDGE LIVE chassis will power
cycle, the BRIDGE LIVE application will reload, and all the previously active
pipelines will be restarted. You will also be logged out. You will need the
user name and password for that BRIDGE LIVE unit to log back in after the unit
has completed its reboot.
Shutdown
A “Do you really want to shutdown…? prompt appears. After answering Yes, all
currently running pipelines will be halted and the BRIDGE LIVE chassis will
power down. To regain operation, the front panel Power button will need to be
pressed, and you will need the user name and password for that BRIDGE LIVE
unit to log back in after the unit has completed its bootup.
Factory Reset
NOTE: BRIDGE LIVE factory reset can only be performed locally using the Kiosk
UI, not with a web interface.
Performing a factory reset will restore BRIDGE LIVE to its factory settings.
All pipelines and settings, including network setup and passwords, will revert
to default factory settings. Only your current licenses will be preserved.
Once changes are applied, the server will restart itself and boot into the
factory state. The process takes approximately one minute.
WARNING: Before performing a factory reset, be sure to backup your pipeline
configurations. See “Verifying Pipeline Configurations” on page 94 for more
information.
CAUTION: A factory reset will revert the login credentials back to how they
were set at the time of shipment from the factory. You will need to reference
your Quick Start Guide for these original login credentials; otherwise you
will need to contact AJA Tech Support.
Different methods exist for performing a Factory Reset to BRIDGE LIVE. · One
method is to continuously press and hold any key on the keyboard while
booting or rebooting the device, then selecting from a list of menu options. ·
Another method is to use a command line interface (CLI).
Keyboard Method
To perform a factory reset using the keyboard: 1. While booting or rebooting
the BRIDGE LIVE device, continuously press
and hold any key on the local keyboard that is connected to the unit. The
following list of menu options displays: · Continue booting with the existing
version · Boot using previous software version · Perform a factory reset 2.
Select “Perform a factory reset.” 3. You will need the original Admin
credentials indicated in the Quick Start Guide in order to login following the
factory reset.
Command Line Interface Method
NOTE: SSH needs to be enabled under the Admin>Security menu before you can
perform any function via the command line.
BRIDGE LIVE Video I/O and Streaming Appliance v1.14
34
To perform a Factory Reset Locally Using the Command Line Interface 1. Press
CTL+ALT+T to switch to the terminal application so that you can use a
command prompt. 2. From the command line interface, enter the following
command:
sudo ostree-factory-reset 3. You will need the original Admin credentials
indicated in the Quick Start
Guide in order to login following the factory reset.
To Perform a Factory Reset Remotely Using the Command Line Interface
1. Launch a command prompt for Mac or Windows. · Terminal application on a
Mac · Command Prompt on Windows 2. Login to your BRIDGE LIVE device as a
transcoder user. WARNING: When using SSH to access the BRIDGE LIVE system and
run commands
as a root (sudo) user, please exercise caution. It is possible to severely or
irreparably damage the system if you are not clear on what you are doing.
Please seek appropriate guidance if you are uncertain about how to proceed.
3. From the command line interface, enter the following command:
sudo ostree-factory-reset 4. You will need the original Admin credentials
indicated in the Quick Start
Guide in order to login following the factory reset.
Password Administration
User Types
Two user types exist for a BRIDGE LIVE System: · Admin Username (“admin”) is
used for local login, browser login and REST API
access. This is the user type we are going to be using in the examples below.
· Transcoder Username (“transcoder”) is used for CLI/SSH (CLI stands for
Command Line Interface, SSH for Secure Shell). Changing passwords for the two
user types is done through the Password management page, accessed through the
Admin > Security menu. Figure 26. Accessing Password Management
BRIDGE LIVE Video I/O and Streaming Appliance v1.14
35
www.aja.com
Setting Remote Shell Access
From the Password management page, you can enable or disable SSH access to
BRIDGE LIVE altogether by clicking the Enable button (if currently disabled)
or the Disable button (if currently enabled) underneath the Secure Shell (SSH)
heading. Remote secure shell (SSH) access is intended only for the transcoder
user (console user).
Password Management
Manage passwords for the admin user (web application user) and the transcoder
user (console user) by entering the current password, then setting the new
password.
Licensing
Licenses that are ordered at the time of purchasing the BRIDGE LIVE unit will
be pre-installed prior to shipment. At a later date, if you want to order an
additional license, you will need to get the unique Installation ID number,
found on the System Information page, and contact your AJA Distributor or
Regional Sales representative. If you do not know who that is, you can contact
AJA Sales directly. To access the System Information page, select System
Information from the Setup menu in the upper right area of Dashboard. The
System Information page displays.
Figure 27. Accessing the System Information page from the Setup menu
From the System Information page, the Installation ID is found a few lines
below
Installing a New License Package
Typically, new BRIDGE LIVE License Packages are delivered as a zip file. If
zipped, please unzip the delivered package.
Remote Installation
Accessing BRIDGE LIVE through a browser requires that you are using a machine
that has network connectivity to the BRIDGE LIVE device.
Steps for Installing a New License
1. From the BRIDGE LIVE interface, select the Licensing menu in the upper
right area.
Figure 28. The Licensing menu
The Licenses page displays.
BRIDGE LIVE Video I/O and Streaming Appliance v1.14
36
www.aja.com
Figure 29. The Licenses page
2. Click the downward pointing disclosure triangle to display your License
Package details for your previously installed License Package.
Figure 30. The Licenses page displaying previously installed License Package
3. Click the red “X” icon to the right of the currently installed License
Package to remove it.
4. Next, with no License Package present, click Load license file. A
navigation window opens.
5. Navigate to your new License Package location, choose the file, and select
Open. The new License Package will install.
6. Next, navigate to the License page by clicking Licensing in the upper
right area of Dashboard.
Figure 31. Accessing the Licenses page
7. From the Licenses page, select Load license file. Navigate to the license
file, select it, then click Upload.
Upon completion of the license upload, the license will immediately be
available for use.
License Status
If a license is granted, the status shows “Unlimited time” or the time for
which the stream is allowed to produce an output, according to loaded license
files. The status will be, for example: · License: Unlimited time a stream
may produce an output for an unlimited
period of time · License: Till 2021-02-21 23:59:59 a stream will produce an
output until the
displayed time point is passed.
BRIDGE LIVE Video I/O and Streaming Appliance v1.14
37
www.aja.com
NOTE:
For your convenience, the status shows the time and date according to your computer’s time setting, not the BRIDGE LIVE system time, which may be different. For example, during installation, the automatic installer sets the timezone to America/Los Angeles, but you may be located in a different time zone. Also, you might have offices in different time-zones and would prefer the servers to have the same system time, potentially for monitoring purposes.
If a stream is not allowed to produce an output, the license status reads
“Blocked” or “Unavailable” and is shown red. BRIDGE LIVE will process the
stream as usual, the only difference is that the output will not be sent to
defined output sinks. This feature will help you verify your environment
abilities, such as system load limits, input stream compliance, and other
factors, even if you don’t have enough licenses yet. For that reason, the
input and output stream status indicator may be green even if the license
status is not valid.
Possible invalid license statuses are:
· License: Blocked there are licenses for the stream loaded in the system,
but the count of streams exceed the licensed number (other streams have
exhausted the available licenses)
· License: Unavailable the stream needs a license which is not loaded (the
stream contains a feature of newer version of BRIDGE LIVE which isn’t included
in any loaded license)
BRIDGE LIVE Software Update
To check for updates for BRIDGE LIVE software: 1. Go to the AJA website and
view/download the package for your particular
BRIDGE model: https://www.aja.com/products/bridge-live#support After
unzipping the file, the download will be a .tgz file. NOTE: MacOS with Safari
has a setting that can cause the browser to incorrectly unzip the .tgz file
into it’s elementary components, making it unusable. To prevent this turn off
“Open safe files after downloading” via Safari>Preferences>General.
2. Stage the downloaded update on an accessible network location. 3. From
within BRIDGE LIVE, navigate to Setup > Version management.
Figure 32. Accessing the Version management page from the Setup menu
The Version Management Upgrading page displays.
BRIDGE LIVE Video I/O and Streaming Appliance v1.14
38
www.aja.com
Figure 33. Version management Upgrading page
4. Select Upload upgrade file and browse to the downloaded update. 5. Select
Perform upgrade. BRIDGE LIVE will upload and install the update.
You will need to reboot the system via the dialog after the update completes.
Following the upgrade, you can verify the version installed if you like by
navigating to Setup > System information. Figure 34. Accessing the System
information page from the Setup menu
The System Information page displays, indicating the version number currently
installed and running. Figure 35. System Information page indicating the
version number
BRIDGE LIVE Video I/O and Streaming Appliance v1.14
39
In the event that there is an issue or failure during the update process,
BRIDGE LIVE will automatically retry the upgrade process and reboot up to
three times.
If the upgrade is unsuccessful, even after the automatic retries, the UI shows
a warning statement at the top of the page with a link to the Version
Management page. From the Version Management page, you can retry the upgrade
process manually.
Upgrading BRIDGE LIVE from USB Flash Drive
If your work environment is such that you cannot access your BRIDGE LIVE
remotely through a browser interface, you can upgrade firmware or load a
license file from a USB flash drive connected directly to one of the USB ports
on the rear panel of the BRIDGE LIVE device.
To Upgrade Remotely from a USB Flash Drive Attached Locally
1. Place a copy of the upgrade package onto a USB flash drive.
2. Insert the USB flash drive into one of the USB ports on the rear panel of
your BRIDGE LIVE device.
3. Mount the USB flash drive using the following steps and commands:
A. Launch a terminal application so that you can use a command prompt.
B. Login to your BRIDGE LIVE device as a transcoder user. For more information
about logging in as a transcoder user, please see: · “User Types” on page 35 ·
“Default Accounts” on page 48 · “Setting Remote Shell Access” on page 36
WARNING: When using SSH to access the BRIDGE LIVE system and run commands as a
root (sudo) user, please exercise caution. It is possible to severely or
irreparably damage the system if you are not clear on what you are doing.
Please seek appropriate guidance if you are uncertain about how to proceed.
C. From the command prompt, enter the command: lsblk This command returns a
list of all connected drives. The output in a terminal window will display
something like the following: sda, sda1, sdb, sdb1 D. Identify the correct USB
flash drive by checking that its storage capacity
matches the one you have inserted. For example, let’s assume that the USB
flash drive is sdb1. E. For this example, you would enter the following
command:
sudo mount /dev/sdb1 /mnt/
NOTE: If the output from the lsblk command shows that your USB flash drive has
a different name, use that instead. Please be careful to use the correct name
for your USB flash drive.
F. Close the terminal application.
4. From within BRIDGE LIVE, navigate to Setup > Version management.
BRIDGE LIVE Video I/O and Streaming Appliance v1.14
40
www.aja.com
Figure 36. Accessing the Version management page from the Setup menu
The Version Management Upgrading page displays. Figure 37. Version management
Upgrading page
5. Select Upload upgrade file and navigate to the /mnt folder where the
upgrade file is located.
6. Select the upgrade file, then click Perform upgrade. BRIDGE LIVE will
upload and install the update. This may take several minutes.
Your BRIDGE LIVE unit will be upgraded to the version that you just uploaded.
Following the upgrade, you can verify the version installed if you like by
navigating to Setup > System information. Figure 38. Accessing the System
information page from the Setup menu
The System Information page displays, indicating the version number currently
installed and running (see Figure 39 on page 42).
BRIDGE LIVE Video I/O and Streaming Appliance v1.14
41
www.aja.com
Figure 39. System Information page indicating the version number
To Upgrade Locally from a USB Flash Drive
This scenario is for upgrading locally, using a keyboard and monitor attached
directly to the BRIDGE LIVE device.
1. Place a copy of the upgrade package onto a USB flash drive.
2. Insert the USB flash drive into one of the USB ports on the rear panel of
your BRIDGE LIVE device.
3. Log in as “admin” on BRIDGE LIVE.
4. Mount the USB flash drive using the following steps and commands:
A. Press CTL+ALT+T to switch to the terminal application so that you can use a
command prompt.
B. Login to your BRIDGE LIVE device as a transcoder user. For more information
about logging in as a transcoder user, please see: · “User Types” on page 35 ·
“Setting Remote Shell Access” on page 36
BRIDGE LIVE Video I/O and Streaming Appliance v1.14
42
WARNING: When using SSH to access the BRIDGE LIVE system and run commands as a
root (sudo) user, please exercise caution. It is possible to severely or
irreparably damage the system if you are not clear on what you are doing.
Please seek appropriate guidance if you are uncertain about how to proceed.
C. From the command prompt, enter the command: lsblk. This command returns a
list of all connected drives. The output in a terminal window will display
something like the following:
sda, sda1, sdb, sdb1
D. Identify the correct USB flash drive by checking that its storage capacity
matches the one you have inserted. For example, let’s assume that the USB
flash drive is sdb1.
E. For this example, you would enter the following command:
sudo mount /dev/sdb1 /mnt/
NOTE: If the output from the lsblk command shows that your USB flash drive has
a different name, use that instead. Please be careful to use the correct name
for your USB flash drive.
5. Press ALT+F4 to toggle out of terminal mode and back to the BRIDGE LIVE
UI.
6. From within BRIDGE LIVE, navigate to Setup > Version management.
Figure 40. Accessing the Version management page from the Setup menu
The Version Management Upgrading page displays. Figure 41. Version management Upgrading page
7. Select Upload upgrade file and navigate to the /mnt folder on the USB
stick where the upgrade file is located.
8. Select the upgrade file, then click Perform upgrade. BRIDGE LIVE will
upload and install the update. This may take several minutes.
Your BRIDGE LIVE unit will be upgraded to the version that you just uploaded.
Following the upgrade, you can verify the version installed if you like by
navigating to Setup > System information.
BRIDGE LIVE Video I/O and Streaming Appliance v1.14
43
www.aja.com
Figure 42. Accessing the System information page from the Setup menu
The System Information page displays, indicating the version number currently
installed and running. 9. You will also be prompted to select which network
interface’s default
gateway will be used as a default route (likewise for every interface).
Low Latency Operation
Introduction
The best practice to achieve the lowest BRIDGE LIVE processing latency is to
configure low latency preset all the BRIDGE LIVE pipelines have been set up.
If all the formats, rates and settings are the same across all pipelines, then
the low latency.ini file can be used (variable bit rate (VBR) mode) for low
latency operation. This is the default setting. If different settings are used
across pipelines, then a constant bit rate (CBR) *.ini file can be adjusted
manually to achieve the desired results. Please follow the appropriate
procedure below for your workflow.
Low Latency Using VBR
If all the formats, rates and settings are the same across all pipelines, then
the low latency.ini file can be used. 1. In the BRIDGE LIVE Dashboard
screen, hover your cursor over the Setup item
at the top right and click on “Advanced setup”.
BRIDGE LIVE Video I/O and Streaming Appliance v1.14
44
www.aja.com
Figure 43. BRIDGE LIVE Dashboard
2. Inside the Advanced setup window that opens, open the drop-down menu of
“Available Settings” and choose “Low Latency.”
Figure 44. Selecting Low Latency from Available Settings
3. You will be prompted with a verifying message asking if you want the Low
Latency settings file to be used. Click “Next.”
4. In the additional pop-up that appears, click “Restart now!”
5. BRIDGE LIVE will restart and activate the Low Latency Preset.
BRIDGE LIVE Video I/O and Streaming Appliance v1.14
45
www.aja.com
Low Latency Using CBR
If the formats, rates and settings are the same across all pipelines are
different, a constant bit rate (CBR) .ini file can be adjusted manually to
achieve the desired results.
Within the CBR .ini file (default _ settings.ini), there are two attributes
that need to be edited manually. They are: · LATENCY_ADDITION (value in
milliseconds). The default value is “2000”. This
attribute can be a common cause for synchronization to fail. Every pipeline
has a different latency. If you don’t want latency to be dynamic, use “0” (or
a different specific value) in milliseconds. · FULLSPEED_MUXING. Indicates
either CBR (value of “0”) or VBR (value of “1”).
1. From the Setup menu, select Advanced Setup. The Advanced Setup page
displays.
Figure 45. The Advanced Setup page displaying the default_settings.ini file
2. Select the file you want to edit from the Available Settings drop-down list. Figure 46. Selecting latency .ini file presets
3. Click Download. The file you selected downloads to your computer.
BRIDGE LIVE Video I/O and Streaming Appliance v1.14
46
4. Make any needed edits to the file using your preferred text editor.
5. Once finished, select Upload. Navigate to the file you want to upload,
select it, then click Open. The file will upload and it will display in the
Settings Preview area.
6. Click Apply. A confirmation message displays. Click Next. Another
confirmation displays. Select Restart later or Restart now.
The currently selected .ini file is indicated in the Current settings field.
You can select a different .ini file from the Available settings drop-down
menu.
NDI Discovery Server
NDI supports the idea of a discovery server. This server can act as a central
resource which detects the presence of all of the NDI streams on the network.
The NDI discovery service is designed to allow you to replace the automatic
discovery NDI uses with a server that operates as a centralized registry of
NDI sources.
This can be very helpful for installations where you wish to avoid having
significant mDNS traffic for a large number of sources. It can also be useful
in situation where multicast is not possible or desirable; it is very common
for cloud computing services not to allow multicast traffic.
When using the discovery service, NDI can operate entirely in unicast mode and
thus in almost any installation. The discovery server supports all NDI
functionality including NDI groups.
Using NDI Discovery with BRIDGE LIVE
To send the NDI output of BRIDGE LIVE to the NDI discovery server, it is
necessary to change a parameter via the Advanced setup tab. With the Advanced
Setup dialog opened, locate the line which contains “NDI_DISCOVERY=” and add
the IP address of your discovery server to that line (e.g.
NDI_DISCOVERY=10.3.60.2).
If your preset doesn’t contain a “NDI_DISCOVERY=” line, simply add it to the
.ini file (along with the required IP address) and click Apply. While that new
line can be located anywhere, appending it to the end of the file makes it
easy to find should it require a change (Figure 47 on page 48).
BRIDGE LIVE Video I/O and Streaming Appliance v1.14
47
www.aja.com
Figure 47. Advanced Setup, NDI Discovery
OS and Network Administration
Console Administration
If you want to administer the BRIDGE LIVE locally, it is highly recommended
that you boot it with the monitor already connected. You can unplug the
monitor later, but if you want to use it again, you should re-connect it to
the previously used port.
The default user environment is the aforementioned web-based console. However,
for advanced administrative tasks, it is possible to switch to the system
console. The background OS is CentOS 7. The standard shortcut Ctrl+Alt+T will
take you to the graphical terminal application (not meant for long-term use,
only for a quick configuration or diagnostic).
Default Accounts
Admin User
Admin Username: admin · Used for local login, browser login and REST API
Admin Password: · See the Quick Start Guide that was originally delivered with
your unit for your
factory-provided unique password.
Transcoder User
Transcoder Username: transcoder · Used for CLI/SSH Transcoder Password:
BRIDGE LIVE Video I/O and Streaming Appliance v1.14
48
www.aja.com
· See the Quick Start Guide that was originally delivered with your unit for
your factory-provided unique password.
NOTE: Due to security reasons, it is not possible to connect using SSH as a
root user.
BRIDGE LIVE Files Location
Most of the important files are located in /opt/transcoder/ folder including
the binaries or configuration files as well.
System Services
All BRIDGE LIVE components run as a system service. You can use the standard
OS’s interface systemctl to manage those services.
transcoder-base
Starts the BRIDGE LIVE and the web server with web UI at system start.
transcoder-x
Starts graphical window system with lightweight desktop manager OpenBox.
transcoder-browser
Starts chromium browser in kiosk mode and restarts it in case it detects that
chromium stops running.
transcoder license
Starts the license server with its web UI at system start.
System Security
The security of the system is provided by a built-in firewall. The setup is
available in the UI’s setup wizard. Each network interface needs to be marked
with an attribute whether its intent is to be used for: · Administration
SSH, HTTP(S), SNMP protocols ports allowed · Incoming/outgoing streams
1024-65535 ports allowed · Both · Unused All of the remaining ports are
blocked. In a situation when an interface is marked either Administration or
Unused, it will not show in the stream configuration dialogue; therefore, it
cannot be selected there.
Manual Network Interface Configuration
BRIDGE LIVE UI offers a somewhat limited set of possibilities to configure the
network interface. In the event that you need to set it more precisely, CentOS
7 has three main options for how to configure network interfaces. · ifcfg
files It uses ifcfg network configuration script files placed in `/etc/
sysconfig/network-scripts’. It is used internally in BRIDGE LIVE. You can
BRIDGE LIVE Video I/O and Streaming Appliance v1.14
49
manually adjust some parameters when needed. Preferred and the only supported
way of manual network setup in BRIDGE LIVE OS.
· NetworkManager NM uses its nm* commands to configure network interfaces;
however, it conflicts with BRIDGE LIVE setting up the network in its own way.
Therefore, BRIDGE LIVE setup interfaces are not to be managed by NM. Please do
not use it.
· ip command some changes made by ip command are only temporal and are not
guaranteed to survive system restart. We recommend exercising caution in
making use of this functionality.
Virtual Interfaces
BRIDGE LIVE currently doesn’t support creating new virtual interfaces in the
web UI. These interfaces need to be added using system console using ifcfg
scripts. Currently BRIDGE LIVE recognizes bond, bridge and vlan interfaces.
Adding New Virtual Interface
For example, to add vlan 100 to existing Ethernet interface enp4s0: With sudo
add new file ifcfg-enp4s0.100 to directory /etc/sysconfig/networkscripts/ (for
example with nano or vim) cd /etc/sysconfig/network-scripts/ sudo vim ifcfg-
enp4s0.100 DEVICE=enp4s0.100 TYPE=Vlan VLAN=yes VLAN_ID=100 ONBOOT=yes
BOOTPROTO=none NM_CONTROLLED=no IPV6INIT=no ZONE=trc-admin-data Next start the
interface sudo ifdown ifcfg-enp4s0.100 sudo ifup ifcfg-enp4s0.100 Restart
BRIDGE LIVE service sudo systemctl restart transcoder-base Wait until BRIDGE
LIVE starts and in BRIDGE LIVE Dashboard run Setup where you can find your new
vlan interface. Configure usage and complete setup.
IPMI
You can use IPMI to remotely reboot or shutdown BRIDGE LIVE.
CAUTION: Use of IPMI can introduce possible security implications for your
network. AJA can not be responsible for issues that arise from making use of
the IPMI functionality.
To access the IPMI of a Supermicro server, you need to know the IP address to
which you want to connect. With BRIDGE LIVE, you do not need to have the
dedicated IPMI interface plugged in, since IPMI shares an interface with the
OS while having its own IP address. You can find the IP address using an app
on your phone (Android/iOS), PC (IPMIView), or you can memorize the IP address
that you can see during the boot process as “BMC IP:”.
BRIDGE LIVE Video I/O and Streaming Appliance v1.14
50
www.aja.com
If IPMI has no IP address assigned (for example, if there is no DHCP server in
the subnet), you can configure it in BIOS. When you start the server, press
the DEL key repeatedly until you are in BIOS. From there, navigate to the IPMI
tab. Select BMC network config and fill in the parameters you require.
The current list of IPMI features can be found here. As of now, we do not
support out of the box the following items: · Keyboard, Video & Mouse (KVM)
Console Redirection with multi-language
support, · HTML5 web Console Redirection, · Serial over LAN (SOL) – this can
be enabled from the OS.
You can find the complete Supermicro IPMI user guide here.
BRIDGE LIVE Video I/O and Streaming Appliance v1.14
51
Operation
Overview
BRIDGE LIVE is designed as a network appliance, such that once configured it
will transport signals across the network without requiring direct user
interaction. After initial configuration of the unit for network operation,
most of BRIDGE LIVE end-user operating procedures involve creating or
modifying pipelines, which can be as simple as selecting different available
input or output signals.
Browser Types
Once BRIDGE LIVE has been configured, it can be accessed with a network
connected computer running a supported browser (Chrome, Firefox, Edge,
Safari).
Unsupported Browsers
Browsers change over time as new functionality is added. In some cases, using
an older browser may cause some issues. If that happens, you will be notified
that you are using an old or unsupported browser, as pictured in Figure 48.
Figure 48. Example of an Unsupported Browser Message
Logging in Remotely with a Browser
Once BRIDGE LIVE has been configured, it can be accessed with a network
connected computer running a browser. You login by entering the IP address of
that BRIDGE LIVE into the browser. The following login prompt appears: Figure
49. BRIDGE LIVE Initial Login Prompt via Browser
BRIDGE LIVE Video I/O and Streaming Appliance v1.14
52
www.aja.com
The Username is “admin”, and the default password that is unique to that
BRIDGE LIVE unit is included in the Quick Start Guide provided with shipment.
If the password has been changed, contact your system administrator for the
new password.
After entering the username and password, click Login. You will go to the
BRIDGE LIVE Dashboard displays showing the general user interface (see “BRIDGE
LIVE Dashboard Home View” on page 53).
BRIDGE LIVE User Interface Description
Dashboard Interface Basics
Click to Return to Home View
Figure 50. BRIDGE LIVE Dashboard Home View
Home View Upper Left Quadrant
Home View Upper Right Quadrant
Administration Menu Buttons
Pipelines Status
Pipelines
Chart Color IDs
GPU/CPU Utilization
Chart
System Memory
Chart
Add New Pipeline Button
Home View Lower Left Quadrant
Home View Lower Right Quadrant
The BRIDGE LIVE UI has two basic layouts, Home View and Pipeline View. Both
views share the same left column, which displays system status and is also
used for pipeline operation and selecting a pipeline for configuration.
Home view is the default display when the BRIDGE LIVE application is first
launched (Figure 50). You can return to Home view at any time by clicking on
the BRIDGE LIVE logo at the upper left corner of the screen.
Clicking on a pipeline in the left column displays the Pipeline view, showing
video configuration information for that pipeline on the right side of the
screen (Figure 51).
Home View Lower Panel
BRIDGE LIVE Video I/O and Streaming Appliance v1.14
53
www.aja.com
Home View
Home View provides an overview of system status. It also shows an overview of
performance and of the utilization of the system through the following
interface elements:
Left Column – Shared with Pipeline View. Pipeline status, pipeline selection
for configuration, and controls for starting, stopping, and deleting
pipelines.
Upper Left Quadrant – Reports the data throughput transmitted (Tx) and
received (Rx) for the selected interface. For SDI, it reports what is detected
and if it is used for output streaming.
Upper Right Quadrant – GPU utilization/CPU utilization
Lower Left Quadrant – Services and devices status
Lower Right Quadrant – Memory GPU/System RAM
Lower Panel – Stream statistics including stream latency, FPS and FPS drops.
Pipeline View
Figure 51. BRIDGE LIVE Dashboard Pipeline View
Click to Return to Home View
Pipeline Name (editable)
Input Stream
Output Stream
Configuration Pane Configuration Pane
Selected Pipeline
Option Menu Access
Selected Output Stream
Add New Pipeline Button
Delete Pipeline Button
Add Output Output Stream Stream Button Selection Pane
Save Buttons
Left Column – Shared with Home View. Pipeline status, pipeline selection for
configuration, and controls for starting, stopping, and deleting pipelines.
Input Stream Configuration Pane – Input stream configuration parameters, which
will vary depending on type of input stream.
Output Stream Selection Pane – Output stream addition and selection, used for
pipelines that support multiple output streams.
BRIDGE LIVE Video I/O and Streaming Appliance v1.14
54
Output Stream Configuration Pane – Output stream configuration parameters,
which will vary depending on type of input stream.
Pipeline Control Buttons – Located at the bottom of the screen, these buttons
affect the currently selected pipeline or output stream, allowing you to
Delete and Save pipelines. Different button functions are displayed, depending
on the current pipeline configuration step.
The Left Column (Pipelines)
Beneath the AJA and Comprimato logos, in the top left of the interface, is a
summary of the number of running pipelines, beneath which are flags for Errors
(Red) or Warnings (Yellow).
Flags, Warnings and Errors
The Pipeline status indicators shown in Figure 52 below show the number and
types of errors, along with indicators for configured and applied Pipelines.
Hover the mouse over a half circle to see specific error messages for a
Pipeline.
Figure 52. Pipeline status indicators
Pipelines
Below the errors and warning flags the currently configured pipelines are
displayed. Clicking on a pipeline displays information for that selected
pipeline. On the left side, each pipeline has a circular status icon. The left
half of the colored circle provides feedback on the incoming part of the
pipeline, while the right side indicates the status of the outgoing part of
the pipeline. Immediately to the right of the circular icon is the name of the
pipeline. An asterisk (*) in front of the name indicates changes have been
made to that pipeline’s configuration that have not been saved. Further to the
right, when hovering the mouse over the pipeline, there is also a toggle
pipeline stop and start button. Figure 53. Pipeline Stop Button
Figure 54. Pipeline Play Button
BRIDGE LIVE Video I/O and Streaming Appliance v1.14
55
When hovering the mouse, along the right edge of each pipeline is a vertical
row of three dots. Clicking on the three dots will toggle the button to
display the following three options: Figure 55. Pipeline Delete, Clone,
Download Buttons
Use these buttons to delete, clone or download a pipeline.
Backing Up Pipelines
Once you have created all the pipelines you need, you can create a backup of
them. From the lower left corner, click the column of three vertical dots next
to “Add new pipeline” to open the Pipelines Management pop-up menu. Figure 56.
Pipelines Management Menu
Select “Download all as a preset.” All of your pipeline configuration settings
will download as a “pipelines.json” file.
You can upload this file in the future to upload your pipeline preset using
the “Upload a preset” menu. If the name of an uploaded pipeline is identical
to an existing pipeline, the name will be appended with #1, #2, etc.
Additionally, you can delete all pipelines by selecting the “Delete all” menu.
Output Streams and Licenses
Beneath the name of the pipeline is an indication of the number of output
streams associated with the pipeline. For every stream, there is also
information on license status. Streams need to be licensed in order to run.
For H.265, H.264 and H.262, BRIDGE LIVE will come with perpetual licenses.
Meaning of Color Statuses
Both sides Grey – No pipeline has been created (new system or all pipelines
deleted). The pipeline has been stopped.
Right side Grey – The output is not configured
Red – There is an error causing the pipeline not to work correctly. Left side
for input, right side for output.
Yellow – Standby mode. This can occur, for example, when a pipeline is in SRT
mode and the stream does not have a subscriber. In that case, the stream is
not being sunk. In this case when a subscriber is actively receiving the
stream, the signal turns green. Another example is HLS buffering.
Green – The stream is working correctly (and in the case of SRT, is being
subscribed to).
BRIDGE LIVE Video I/O and Streaming Appliance v1.14
56
www.aja.com
Add New Pipeline Button
The bottom left corner of the Dashboard has an Add new pipeline button for
adding a new pipeline. Selecting it directs you to the pipeline window. This
is the same window accessed when you want to change the configuration of an
existing pipeline.
Returning to Dashboard Home View
At any time, to return to the main Dashboard home view, click the AJA/
Comprimato logos in the top left area of the Dashboard interface.
Upper Left Quadrant Interfaces
The first quadrant (upper left) displays information for the BRIDGE LIVE’s I/O
signals. When the AJA Corvid is selected, the configuration status and format
of that incoming signals are displayed (Figure 57). Figure 57. Interfaces
Panel of Dashboard, Corvid 44 Selection
Clicking on the Interfaces box presents a dropdown menu (Figure 58). Figure
58. Interfaces Panel Drop-down Menu
Selecting an Ethernet Card displays a chart over time of data transfer (Figure
59). The Loopback setting is used for system testing purposes.
BRIDGE LIVE Video I/O and Streaming Appliance v1.14
57
Figure 59. Interfaces panel Ethernet Selection
Upper Right Quadrant GPU/CPU Utilization
The second quadrant (upper right) shows GPU/CPU utilization hardware
components. The GPU has three statistics. The blue line shows the level of GPU
utilization. NvEnc and NvDec represents the workload of the NVIDIA hardware
encoder decoder respectively. Hover the mouse over a line to see the
percentage of utilization of that component at that point in time on the
graph. Figure 60. GPU utilization/CPU utilization panel of Dashboard
NOTE: When working with JPEG 2000, the CPU chart may go to 100% utilization. Generally, however, the CPU is not expected to go over 65%.
Lower Left Quadrant Services and Devices Status
The lower left quadrant, Services and devices status, reports statistics for
services that are running. It reports what is running, and it also displays
the status of the License server. In the example shown below, the License
server is initialized. Hardware temperatures are also reported.
BRIDGE LIVE Video I/O and Streaming Appliance v1.14
58
www.aja.com
Figure 61. Services and devices status panel of Dashboard
Lower Right Quadrant Memory GPU/System RAM
The lower right quadrant, Memory GPU/System RAM, reports memory consumption.
When you hover the mouse over the line in the graph, a mouseover message
reports the amount of memory used at that point in time, followed by the
amount of memory that was available. Figure 62. Memory GPU/System RAM panel of
Dashboard
Lower Panel
In the lower panel of Dashboard, you can see a list of all currently running
streams, both input and output. Use the Stream statistics radio buttons to
filter by All, Input stream only, or Output stream only. Clicking on a column
name on the top gray line sorts the list by that category. You can also search
for a particular stream using the search tab in the upper right section of the
panel.
If an error occurs, the relevant lines will turn red. When you hover the
cursor over a red line, a brief description of that error will be displayed.
BRIDGE LIVE Video I/O and Streaming Appliance v1.14
59
www.aja.com
Figure 63. Dashboard Stream Statistics
NOTE: Inactive pipelines still being configured will not be displayed on the
stream statistics list.
Setup Menu
Additional setup and information screens can be accessed by hovering your
cursor over the Setup top menu button, and then click on the desired menu
item.
Setup
Initiates an initial system setup procedure (see “Initial System Setup
Process” on page 29). If you do not want to run this procedure, click on
Cancel Setup.
System Information
To view system information, click System information. System information
reports various aspects of the system including software version, OS version,
Installation ID, Memory statistics, drivers, hardware and network information.
Figure 64. Selecting System information from the Setup menu
BRIDGE LIVE Video I/O and Streaming Appliance v1.14
60
www.aja.com
Figure 65. System Information
Advanced Setup
Figure 66. Setup Mouse-over
Access Advanced setup by clicking the Advanced setup option under the Setup mouse-over. You can select between saved configuration under Available settings drop-down menu, download them, upload new ones and delete custom configuration files. Click the Apply button in order to set the chosen settings configuration. After that, you will be prompted to restart the BRIDGE LIVE service in order to apply changes. This configuration allows you to edit parameters, which adjust the transcoding process, such as GPU memory distribution, encoding presets, and other settings.
BRIDGE LIVE Video I/O and Streaming Appliance v1.14
61
www.aja.com
The suffix “preset” means that the file is the pre-configured one, which in
general should work best with a particular use case. The suffix “custom”
points out the fact that this settings file was uploaded to BRIDGE LIVE by the
end user. It is advised to consult the configuration adjustments with your
support team.
Figure 67. Advanced Settings Management
See “Low Latency Operation” on page 44 for an example using Advanced Setup.
Version Management
See “BRIDGE LIVE Software Update” on page 38 for information.
Diagnostics & Support
The Diagnostics and Support page lets you create a BRIDGE LIVE log file, which
can be useful for troubleshooting by AJA support staff. The report contains
system information, pipeline configuration information, pipeline error
messages, and system logs. To access the page, select Diagnostics & Support
from the Setup menu in the upper right area of Dashboard. An informational
screen will be displayed.
BRIDGE LIVE Video I/O and Streaming Appliance v1.14
62
www.aja.com
Figure 68. Diagnostics and Support Screen
To create a log file, Click Create and download diagnostic report. The
diagnostic report will download to your computer. You can see logs in the
folder:
/opt/transcoder/transcoder/logs/ If you need to send logs to AJA Support,
please copy the contents of the folder, archive them and share.
Admin Menu
Functions available in the Admin Menu can be used for system management
functions, including restarting all pipelines, and rebooting or shutting down
the BRIDGE LIVE unit. See “Admin Menu” on page 33 for more information.
Pipeline Configuration
About Pipelines
A pipeline is a configured network communications path defining necessary
signal stream information. Each pipeline has an Input Stream and at least one
Output Stream, which specify various parameters that are configured to define
the functionality of that pipeline. Each Output Stream also has an Output
Stream Sink, which further defines that Output Stream target and capabilities.
Each Pipeline also employs a Codec, used to encode and decode the data sent
over the network. Various parameters are available, depending on the choice of
Input Stream, Output Stream, Sink, and Codec. During the pipeline
configuration process the BRIDGE LIVE UI displays only the parameters
applicable to the options that you have selected. Because of the progressive
definition of a pipeline, the order of the configuration steps you perform is
important. For example, some pipeline settings can be set automatically when a
pipeline is first created, but only if an active source is already present and
detected. If that source is not available, additional manual configuration
settings, subject to human error, will be required. Following the general
procedure described here can help you efficiently and successfully configure
your BRIDGE LIVE with the pipelines needed for your workflows.
BRIDGE LIVE Video I/O and Streaming Appliance v1.14
63
Saving, Starting, and Stopping Pipelines
Once created, each pipeline must be saved before it can be used. When a
pipeline is started, it activates that network signal path, transporting video
from the selected source to the desired destination. Pipelines continue to
operate as long as the input source and output sink(s) are present and valid.
Currently active pipelines will be automatically restored to operation when
the BRIDGE LIVE unit is reset, rebooted, or power cycled. All pipeline
configurations are also retained, but inactive pipelines are not automatically
re-activated under those circumstances.
General Procedure for Creating a Pipeline
Overview
The following procedures describe the basic steps required to create an
entirely new pipeline. You will make choices regarding transport streams,
protocols, and codecs to meet your encoding requirements. These choices
dynamically affect which sets of configuration options become available as you
build your pipeline. NOTE: Because different parameter settings are required
depending on the type
of pipeline being created, cross references are provide to manual locations
explaining specific settings.
Identifying Your Encoding Requirements
Before you begin, consider which of the following components match your
requirements. See “SDI to Stream Encoding” on page 8 and “Stream to SDI
Decoding” on page 9 for available options.
Add New Pipeline
1. From the BRIDGE LIVE Dashboard, click Add new pipeline at the bottom of
the Pipeline pane in the lower left corner.
BRIDGE LIVE Video I/O and Streaming Appliance v1.14
64
www.aja.com
Figure 69. Add New Pipeline Button
2. Dashboard will display a page with Input stream configuration options. Figure 70. Input Stream Options
BRIDGE LIVE Video I/O and Streaming Appliance v1.14
65
www.aja.com
Naming the Pipeline
3. From the top of the Input stream configuration options column, click [edit
name], found immediately to the right of the text “Name your pipeline.”
Figure 71. Edit Name Button
4. The Edit Pipeline Name pop-up window displays. The default name is
“Pipeline”.
Figure 72. Edit Pipeline Name Pop-up Window
5. Click in the box and enter a name for your new pipeline. Use a simple name
that will be easy to understand.
NOTE: Pipeline names are limited to 128 characters. An error message is
displayed If you try to enter too many characters, and you will not be able to
save the name.
6. After clicking OK, the new pipeline will be shown in the left column of
Dashboard. Both half circles are gray indicating that the pipeline is not
configured or active yet.
Figure 73. Newly Named Pipeline
BRIDGE LIVE Video I/O and Streaming Appliance v1.14
66
www.aja.com
Selecting Input Stream Type
Figure 74. Input Steam Type Selection
7. The rest of the configuration procedure depends on the Type of Input
stream you select. Click on the Type box, and select your desired Input stream
type. Example procedures are included for the following types:
· SDI (see “Configuring an SDI Input Stream” on page 67) · NDI (see
“Configuring an NDI Input Stream” on page 70) · RTMP (see “Configuring an RTMP
Input Stream” on page 71)
Configure Input Stream Options
Bridge Live now supports automatic population of the input codec and signal
format when receiving MPEG-TS streams. Once the Input Stream Source is
configured, select ‘Start Detecting Input’. Once the signal is detected, the
‘Auto Detected Video streams’ section will show a summary of the incoming
signal. Select ‘Set as Input’. The detected input will now automatically
populate the codec and all associated formats. There should be no need to
further configure the incoming signal. The manual steps to configure MPEG-TS
Input streams are still included in the manual.
Configuring an SDI Input Stream
NOTE: Procedure continued from the conclusion of “Selecting Input Stream Type”
on page 67.
After selecting the pipeline’s input stream type, you now need to configure
the input stream’s parameters. NOTE: The SDI CORVID card installed in the
BRIDGE LIVE unit will need to have an
active input SDI signal connected to the desired BNC port to continue with
this procedure.
BRIDGE LIVE Video I/O and Streaming Appliance v1.14
67
www.aja.com
Figure 75. SDI Input Stream Example
1. Click on Select SDI device. Select the only choice, which is the AJA
Corvid card installed in your BRIDGE LIVE chassis.
2. Select the input SDI port with the desired SDI input signal. Figure 76.
SDI Input Stream, Device and Port Selected
Start Detecting Video Input Properties
3. To prompt BRIDGE LIVE to detect the incoming SDI signal, click Start
Detecting Input located above the video preview window. A preview image of the
input will be displayed, with the left half circle colored green, indicating
an input source is present. A new heading called “Auto-detected video streams
is also displayed.
NOTE: If no image displays, check that an SDI signal is actively being output
from that device’s selected port.
BRIDGE LIVE Video I/O and Streaming Appliance v1.14
68
www.aja.com
Figure 77. SDI Input Stream, Detected Input with Preview
NOTE: If you require reference-quality video image monitoring, we recommend
that you use either an SDI monitor and/or a receiving client (host system)
with a highquality GPU and Monitor.
4. Under the “Auto-detected video streams” heading, click on Set as input
(Figure 78). The heading immediately above expands and displays autopopulated
characteristics of the detected video signal.
IMPORTANT: Both the Start Detecting Input and Set As Input buttons need to be
clicked if you want to use the automatically detected source video format for
the output stream.
Figure 78. Auto-populated Characteristics of the SDI Input signal
5. This completes the pipeline’s Input stream configuration.
Go to “Add New Output Stream to Pipeline” on page 74 to continue this
procedure.
BRIDGE LIVE Video I/O and Streaming Appliance v1.14
69
Configuring an NDI Input Stream
NOTE: Procedure continued from the conclusion of “Selecting Input Stream Type”
on page 67.
NOTE: This procedure assumes an NDI system is already present and operating on
the network, using standard NDI auto-discovery. See “NDI Discovery Server” on
page 47 for information about using an NDI Discovery server instead.
After selecting the pipeline’s input stream type, you now need to configure
the input stream’s parameters.
Figure 79. NDI Input Stream Example
1. Click on Select NDI Source in the “Detected sources” box. A list of the
discovered NDI sources will be displayed.
NOTE: Only the names of currently active NDI sources will be available for
selection.
Figure 80. NDI Detected Sources
2. Click on the desired NDI source. That source name will be displayed in the
“Detected sources” and “Selected source” boxes.
3. Click on the Start Detecting Input button. An “Auto-detected video
streams” heading appears displaying the detected NDI video format. The left
half of that pipeline’s status will also be colored green.
BRIDGE LIVE Video I/O and Streaming Appliance v1.14
70
www.aja.com
Figure 81. NDI Detected Video Format
4. Click on the Set As Input button. Additional information about that NDI
source will be displayed in the “Input stream video configuration options”
pane.
IMPORTANT: Both the Start Detecting Input and Set As Input buttons need to be
clicked if you want to use the automatically detected source video format for
the output stream.
Figure 82. Auto-populated Characteristics of the NDI Input signal
5. This completes the pipeline’s Input stream configuration. Go to “Add New
Output Stream to Pipeline” on page 74 to continue this procedure.
Configuring an RTMP Input Stream
NOTE: Procedure continued from the conclusion of “Selecting Input Stream Type”
on page 67.
BRIDGE LIVE Video I/O and Streaming Appliance v1.14
71
IMPORTANT: RTMP source clients must be configured with a video format
compatible with BRIDGE LIVE. For example, 720p 30 is not a SMPTE standard and
is not supported by BRIDGE LIVE. See “Appendix A Specifications” for a listing
of supported video formats.
About RTMP Streaming
Configuring an RTMP input on BRIDGE LIVE differs somewhat from configuring
other IP video stream inputs because RTMP requires a stream key. Typically the
stream key follows the / after the IP address.:
rtmp://
The BRIDGE LIVE pipeline’s RTMP input (sink) must be configured with a stream
key, and also be running, before the external RTMP client (source) that has
been configured with that same stream key is started. When that source stream
starts, it finds the matching key for that BRIDGE LIVE’s running RTMP
pipeline’s input stream, and can then complete the streaming connection. With
that connection established, you can then set the video settings for that
BRIDGE LIVE pipeline, and continue configuring that pipeline’s output
stream(s). BRIDGE LIVE actually provides three methods of stream key
configuration (see “RTMP (Input and Output)” on page 99).
This example procedure assumes an external RTMP source device is available on
the network, you can change the configuration settings for that RTMP source,
and you can turn that external source stream off and on.
1. After selecting the pipeline’s input stream type, you now need to
configure the input stream’s parameters.
Figure 83. RTMP Input Stream Example
2. Click on the Generate Random button to create a unique stream key.
BRIDGE LIVE Video I/O and Streaming Appliance v1.14
72
www.aja.com
Figure 84. RTMP Input Stream Key Generated
. 3. Click on the Copy button of the RTMP stream URL you wish to use. 4. Go to
the RTMP source stream configuration application and paste in that
URL and stream key, as required for that application. NOTE: Do not turn on the
external RTMP source stream yet.
5. Click on the Start button at the bottom left of the BRIDGE LIVE UI. Figure
85.
6. Now start the external RTMP source stream. The left side of the status
circle for that pipeline will be colored green.
Figure 86. RTMP Stream Connection Initiated
7. Click on the Start Detecting Input button. An “Auto-detected video
streams” heading appears displaying the detected video format. The left half
of that pipeline’s status will remain colored green.
8. Click on the Set As Input button. Additional information about that source
will be displayed in the “Input stream video configuration options” pane.
BRIDGE LIVE Video I/O and Streaming Appliance v1.14
73
www.aja.com
Figure 87. RTMP Input Stream Key Generated
.
IMPORTANT: Both the Start Detecting Input and Set As Input buttons need to be
clicked if you want to use the automatically detected source video format for
the output stream.
9. This completes the pipeline’s Input stream configuration. Go to “Add New
Output Stream to Pipeline” on page 74 to continue this procedure
Add New Output Stream to Pipeline
NOTE: Procedure continued from the conclusion of “Configure Input Stream
Options” on page 67 for your selected Input Stream Type.
After you have configured your pipeline’s Input stream, and a valid signal has
been detected, you now can now easily configure your pipeline’s Output
stream(s). During initial pipeline configuration the Dashboard will indicate
that the currently selected pipeline lacks any output streams.
BRIDGE LIVE Video I/O and Streaming Appliance v1.14
74
www.aja.com
Figure 88. Pipeline Without Output Stream
Adding an Output Stream
1. Click on Add output stream at the bottom of the Output Stream Mapping
pane. New fields display in the Output stream column on the right side of
Dashboard for naming and configuring your new output stream. Some of the
fields of the Output stream column are auto-populated, matching the detected
Input stream
Figure 89. Output Stream Added with an Input Stream Source Detected
BRIDGE LIVE Video I/O and Streaming Appliance v1.14
75
NOTE:
If no valid Input stream is detected, you can manually enter data into empty fields, but will need to know exactly what that pipeline’s input values will be when that input is activated. Having an already active input stream greatly simplifies the initial configuration process.
Naming the Output Stream
2. Under Output stream options, enter a name in the Name field. Create a name
will be descriptive to your users for this specific output stream.
Figure 90. Output Stream Named
NOTE:
The name of the Output Stream is intended for user convenience and does not affect signal transport operation. However, it is important Input and Output Stream names be descriptive enough so users can distinguish between them, especially when multiple streams are being configured for simultaneous operation.
Selecting Output Stream Type
1. Click on the Stream Type box and select your desired Output stream type.
Figure 91. Output Stream Type Selection
2. After creating, naming, and selecting the pipeline’s Output Stream type,
you can configure the audio (if any) to be included in the output stream.
Configure Audio Mapping
By default a newly created pipeline will not include any audio in the output
stream. You must manually map incoming audio channels to the output stream.
NOTE: Some RTMP streaming services will not accept streams without audio. 3.
Click on Change Audio Mapping near the bottom of the Output Stream
pane.
BRIDGE LIVE Video I/O and Streaming Appliance v1.14
76
www.aja.com
Figure 92. Change Audio Mapping Button
4. A screen will appear displaying the available incoming source audio.
Figure 93. Audio Mapping Window, No Output Stream Audio
5. In order to add the incoming audio to the output, select a desired audio
pair to send to the output. Then select Add all channels. This will add the
two channels in the selected pair to the output section of the Audio channel
selector. The audio channels can then be inserted into the desired output
audio pairs. If more than 1 pair of audio mapping is needed, repeat the above
procedure for each needed pair.
Figure 94. Output Stream with 2 Channels
6. You can name that audio output stream, and adjust other audio related
settings for conversion.
7. Click on the Save Setup button. The window closes.
8. You can now configure additional Output Stream Options. Different options
are available, depending on the Output Stream Type. Follow the link below to
the appropriate sub-procedure for your Output Stream Type:
· NDI (go to “Configuring an NDI Output Stream” on page 78) · MPEG-TS (go to
“Configuring an MPEG-TS Output Stream” on page 78)
BRIDGE LIVE Video I/O and Streaming Appliance v1.14
77
www.aja.com
Configuring an NDI Output Stream
NOTE: Procedure continued from the conclusion of “Selecting Output Stream
Type” on page 76.
1. After selecting NDI as the output stream type with a valid Input stream
source detected, the following parameters are displayed by default. It will be
auto-populated with the incoming signal video format.
Figure 95. Output Stream, NDI Defaults
2. Enter a descriptive name for the NDI Output stream. 3. Click on Save and Restart at the bottom of the screen. Figure 96. Save & Restart button
4. The NDI output stream will be activated, and both circles for that
pipeline status will be colored green.
Figure 97. Pipeline Status
5. This completes the procedure for creating an NDI pipeline.
NOTE:
When this NDI Output stream is active, its name will appear all other pipeline NDI Input stream Detected Sources lists, becoming available for selection. When that NDI Output stream is stopped, its name will be removed from all pipeline selection lists.
Configuring an MPEG-TS Output Stream
NOTE: Procedure continued from the conclusion of “Selecting Output Stream
Type” on page 76
BRIDGE LIVE Video I/O and Streaming Appliance v1.14
78
www.aja.com
About Port Numbers
Ethernet port numbers can be used to direct network communications to a
specific application associated with a destination Network Interface Card
(NIC). Specifying a port number is required for network communications, and
default port numbers are often used.
A NIC configured with a specific IP address may communicate with multiple
applications at the same time. Because each NIC has only one IP address,
defining a unique port number in the sent message packets can direct the
communications to the correct receiving application using that port number.
Numbering conventions exist defining ranges of port numbers, but generally all
that is required is to have the port numbers of the sending and receiving
message packets match each other.
About Loopback
Loopback is a special Ethernet configuration used for internal network
traffic, and is commonly used for pre-testing network settings. Loopback can
be useful to protect the network from excessive or inappropriate data traffic
during network configuration. The localhost (127.0. 0.1) IP address can be
used to communicate only with your local computer.
1. After selecting MPEG-TS as the Stream type with a valid Input stream
source detected, the following parameters are displayed by default. It will be
autopopulated with the detected incoming signal video format.
Figure 98. Output Stream, MPEG-TS Defaults
BRIDGE LIVE Video I/O and Streaming Appliance v1.14
79
www.aja.com
Select Output Stream Sink Type
2. Select the Output Stream Sink Type. Choose from: · RTP or UDP- see “RTP or
UDP Output Stream Sink” on page 80 · SRT – see “SRT Output Stream Sink” on
page 82
RTP or UDP Output Stream Sink
NOTE: Procedure continued from the conclusion of “Select Output Stream Sink
Type” on page 80.
The BRIDGE LIVE’s RTP and UDP Output Stream sink parameters are identical.
This sub-procedure demonstrates using Loopback to internally test the
pipeline’s network settings, using default settings. 1. Enter the desired IP
address for your Output stream sink. In this example the
default 127.0.0.1 (localhost) IP address is used for testing. 2. Enter the
desired port number. In this example use the default port 5050. 3. Select the
Ethernet card or Loopback. In this example use the default
Loopback I/O Connected setting for testing. The remaining default settings can
be used for this test only pipeline configuration. 4. Click on Save and
Restart at the bottom of the screen.
BRIDGE LIVE Video I/O and Streaming Appliance v1.14
80
Figure 99. Loopback Example, Default Settings
5. The pipeline will be activated and loopback the signal through only the
NIC card. When the path is complete and active, both halves of the Status
circle for that pipeline will go green.
Figure 100. Pipeline Status
6. This completes the procedure for creating a pipeline that demonstrates
Loopback operation for testing.
BRIDGE LIVE Video I/O and Streaming Appliance v1.14
81
www.aja.com
Stream to the Network Instead of Loopback
To configure and run an actual network stream, instead of loopback, select an
Output Stream Ethernet Card, enter the desired IP address and Port number, and
click Save & Restart.
SRT Output Stream Sink
NOTE: Procedure continued from the conclusion of “Select Output Stream Sink
Type” on page 80.
About SRT Operating Modes
NOTE: SRT is only available with MPEG-TS and MPEG-TS PCR stream types.
BRIDGE LIVE supports two SRT stream modes of operation, Listener and Caller (a
clientserver model).
Listener – The Listener unit is configured with a pipeline that always waits/
listens for a connection from an external Caller unit. After the connection is
established, if the Listener is output, it will start sending the streaming
data. If the Listener is input, it starts receiving the streaming data.
Caller – The Caller unit is configured with a pipeline that first seeks a
connection with an external Listener unit, and when that is achieved the
Caller receives streaming data from the Listener. The Caller pipeline is
configured with the remote Listener unit’s IP address and port.
This method works as long as each stream has one Listener and one Caller that
use matching IP and port numbers, regardless of which unit is actually sending
or receiving data. BRIDGE LIVE can even act as the Listener for one pipeline,
and simultaneously act as the Caller for a different pipeline.
NOTE:
SRT is a one-to-one connection scheme and cannot be used in a one-to-many workflow. If multiple SRT destinations are needed, simply add additional output streams following the above procedure. Each output stream will need its own unique port number.
This example procedure demonstrates methods for sending the identical or related SRT streams to multiple clients using a single pipeline.
Configuring Output Side of SRT Transmission
1. After selecting SRT as the type of output stream, the following default
screen will be shown.
BRIDGE LIVE Video I/O and Streaming Appliance v1.14
82
Figure 101. SRT Output Default Settings
2. For the SRT mode, select either Listener or Caller. Choose the mode
opposite to that configured for the other end of the stream.
DNS Resolution of Hostname for SRT Caller Output
3. When using SRT output with Caller mode, you can use either an IP address
or a web URL name. This can be useful when a URL points to multiple IP
addresses for distribution.
Figure 102. SRT Caller Mode
BRIDGE LIVE Video I/O and Streaming Appliance v1.14
83
www.aja.com
4. Enter the IP Address to which you want to send the stream. · For Caller
mode, enter the address which is being called (sending to). · For Listener
mode, enter the address which is being called (receiving a request
from said address to which the stream will be sent).
Port
5. Port 5050, 5051, 5052 and 5053 are all viable. It usually does not matter
which port is used, it just needs to match on both ends.
Ethernet Card
6. Because this example does not use loopback, select a BRIDGE LIVE Ethernet
card.
SRT Overhead
7. In addition, you should define the SRT overhead parameter a percentage
amount over Total Bit Rate that can be surpassed in order to achieve the lost
data recovery. As a result, the maximum used connection bit rate is equal to
the configured Total Bit Rate + SRT overhead. In general, this is the upper
limit and the connection does not require it for normal operation.
Select Video Codec
8. Next, under the heading Output stream video configuration options, for
Video codec, select H.264.
Figure 103. Multiple video codec selections available
9. The Frame size is auto-populated to reflect the detected input signal. The Scan rate and other properties are also auto-populated. Leave the remaining fields with their default values.
BRIDGE LIVE Video I/O and Streaming Appliance v1.14
84
www.aja.com
Figure 104. Output stream video configuration options
10. Click Save & Restart. Figure 105. Save & Restart button
11. BRIDGE LIVE takes just a few moments to process the settings. Once
finished, the left column updates to show your newly created pipeline. The two
green circle halves indicate that both the input and output sides of the
pipeline are running with no errors.
Figure 106. The newly created Pipeline displaying in the left column
One SRT Output Stream, Multiple Clients Example
If you have 10 remote clients who all want to view the same SRT stream, you
can Configure Sinks to add 10 new sinks and increment the IP, port number or a
combination of both, as long as each is unique. In this example only the port
numbers are incremented. For example, client 1 is assigned port 5051, client 2
is assigned port 5052, client 3 is assigned port 5053, and so on.
BRIDGE LIVE Video I/O and Streaming Appliance v1.14
85
www.aja.com
Figure 107. The Configure sinks link
1. To Add a New Sink with a New Port Number, From the Output stream sink
panel, click Configure sinks. The Output stream sinks window displays.
Figure 108. Adding port numbers
2. Click Add new sink. A new row is added for the new stream sink.
3. Edit the port number to match your port configuration plan.
4. Repeat as needed, then click Save changes. The new stream sinks are added
to the pipeline. This is an efficient approach since it requires only one
output stream and BRIDGE LIVE does not need to do any extra encoding.
Two SRT Output Streams, Multiple Clients Example
If you have 10 remote clients who all want to view the same SRT stream, but 5
of them require 15Mbps and the other 5 require 8Mbps, you would need to create
two separate output streams–one for 15Mbps and another for 8Mbps.
1. For each output stream, configure five sinks, each with a unique IP and
port number, to correspond to the 5 remote receiving clients.
NOTE: Encoding two output streams rather than one is more demanding on the
BRIDGE LIVE system. However, it meets the needs of the two sets of remote
clients with varying bit rate requirements.
BRIDGE LIVE Video I/O and Streaming Appliance v1.14
86
www.aja.com
Managing Pipelines
When to Reduce the CPU/GPU Load
Users are advised to look out for errors, alarms, drop frames, etc. If the
BRIDGE LIVE is consistently dropping frames, chances are you have pushed the
BRIDGE LIVE over the limit. Please consider reducing the CPU/GPU load by
either reducing channel count, output numbers, 4:2:2 10-bit to 4:2:0 8-bit
encoding, lower frame rate, etc.
Clearly Naming Multiple Output Streams
Figure 109 depicts the dialogue window for output streams settings. It also
shows the situation where there are multiple output streams already
configured. When adding an output stream, it is important to name it clearly
to eliminate any potential confusion as to what it is. Besides the mandatory
options to direct the output to a specific network interface and a receiving
device, these settings have more attributes that impact the quality of the
resulting stream.
Figure 109. Additional Output Stream Configuration
Cloning an Output Stream
If you need multiple similar output streams within one pipeline, you can clone
an output stream that you have created earlier.
1. Hover your mouse over the output stream that you want to clone. A clone
button displays.
BRIDGE LIVE Video I/O and Streaming Appliance v1.14
87
Figure 110. Hovering mouse over output stream shows cloning button
2. Click the clone button. A copy of the output stream displays beneath the
original.
3. Make any modifications you need to the copy of the original output stream.
Figure 111. The cloned output stream (copy #1)
Output Stream Audio Configuration Options
While configuring the output stream, you can choose which transmitted audio or
metadata channels you wish to include (Figure 112). Figure 112. Audio Mapping
Cloning Output Audio Streams
If you need multiple similar output audio streams within one Audio Mapping,
you can clone an output audio stream that you have created earlier.
BRIDGE LIVE Video I/O and Streaming Appliance v1.14
88
www.aja.com
To Clone an Output Audio Stream
1. Hover your mouse over the output audio stream that you want to clone. A
double page clone button displays.
Figure 113. Hovering mouse over output audio stream shows cloning button
2. Click the clone button. A copy of the output audio stream displays beneath
the original.
Figure 114. The cloned output audio stream (copy #1)
3. Make any modifications you need to the copy of the original output audio
stream.
Creating and Loading Preset Stream Configurations
In order to avoid manually configuring Pipelines, you can save configuration
settings to a file. You can then load the saved configuration settings from
the file and instantly populate all the settings, saving time and potential
configuration errors. Presets can also serve as a way to backup, clone or
restore pipeline configuration settings. These configuration files are stored
in the .json structured file format.
BRIDGE LIVE Video I/O and Streaming Appliance v1.14
89
www.aja.com
To save as a preset
1. From the left column of Dashboard, click on the configured stream that you
want to save as a preset. The window opens showing the Input stream
configuration options and the Output stream mapping.
2. With the stream selected, or while hovering the mouse over the stream, a
vertical row of three dots displays along the right edge.
Figure 115. Initial display of vertical row of three dots
3. Click on the vertical row of three dots. Three buttons display, giving you
the choice of Deleting, Cloning, or Downloading the Pipeline.
Figure 116. Delete, Clone, and Download buttons
4. Select Download. A JSON file downloads to your computer that contains all
of the configuration settings. If your pipeline is named “SDI to H264,” the
downloaded file will be named “SDI to H264.json.” This is the Preset file. You
can view or edit it using a text editor.
To load a preset configuration
1. From Dashboard, hover your mouse over Add new pipeline from the lower left
area.
Figure 117. Add new pipeline
2. Click on the vertical row of three dots. Three buttons display, giving you
the choice of Delete all, Upload a preset, or Download all as a preset.
Figure 118. Three buttons displaying after clicking the vertical row of three
dots
3. Select Upload a preset. A navigation window displays.
4. Navigate to the .json file that you want to upload, select it, then click
Open. Dashboard refreshes to display the pipeline populated with all the
configuration settings that were stored in the JSON preset configuration file.
Alternatively, if you have previously created a pipeline and saved it, you can
drag and drop its .json file onto the left column as another method of adding
a pipeline.
BRIDGE LIVE Video I/O and Streaming Appliance v1.14
90
www.aja.com
Figure 119. Adding New Pipeline by Dragging a .json File
JSON Created Pipelines
If you have previously created a pipeline and downloaded it, you can drag and
drop its .json file onto the left column as another method of adding a
pipeline. This new pipeline will have the previously selected parameters, but
can be a good starting point for creating a new variation of that pipeline.
Figure 120. Adding pipeline with a .json file
When a .json file is loaded, the pipeline will have the original name of the downloaded pipeline. If you modify the settings to create a pipeline with different functionality, you should rename it.
BRIDGE LIVE Video I/O and Streaming Appliance v1.14
91
Additional BRIDGE LIVE Features
Output Stream Cropping and Padding
In order to address how you want BRIDGE LIVE to handle resolution change, use
the Cropping/Padding configuration window to adjust settings for the input
video and output video. Click Configure cropping and padding in the Output
stream video configuration options area to access the configuration window.
Figure 121. The Cropping/Padding configuration window
For the input video, you can adjust frame size, left/top cropping and right/
bottom cropping.
Cropping Example
As an example, let’s consider a case in which you want to crop an image with a
frame size of 1920 x 1080. You want to crop 30 pixels off of the left side, 30
pixels off of the right side, 20 pixels off of the top, and 20 pixels off of
the bottom. In that case, you would enter the numbers as shown below. Select
Scale for Resize method. Figure 122. Example of entering numbers into Crop
number fields
BRIDGE LIVE Video I/O and Streaming Appliance v1.14
92
www.aja.com
· In the above example, the number “30” is being used to crop the left side.
“30” indicates the horizontal offset of the first pixel to be used from the
input video (0 by default). Use a negative value to create explicit padding.
· The number “20” is being used to crop the top. “20” indicates the vertical
offset of the first pixel to be used from the input video (0 by default). Use
a negative value to create explicit padding.
· The number “1890” is being used to crop the right side. “1890” indicates the
horizontal offset after the last pixel to be used from the input video (frame
width by default). Use a value greater than the width to create explicit
padding.
· The number “1060” is being used to crop the bottom. “1060” indicates the
vertical offset after the last pixel to be used from the input video (frame
height by default). Use a value greater than the height to create explicit
padding.
For the output video, you can adjust the output frame size and resize method.
Resize Method
From the Resize method pull-down menu, available selections are: · Scale:
Resizes the configured input frame to the configured output frame and
changes the aspect ratio when it differs. · Crop: Resizes the configured input
frame to the configured output frame, but
keeps the input frame aspect ratio. The input will be automatically cropped
horizontally or vertically. · Pad: Resizes the configured input frame to the
configured output frame, but keeps the input frame aspect ratio. The input
will be automatically expanded with horizontal or vertical black bars.
Logo Insertion
You can insert a logo into the stream. You can configure it in the “Output
stream video configuration options” section by clicking the “Output stream
video configuration options” button. Figure 123. Logo Insertion Button
Upon clicking it, we are presented with another pop-up window, in which the
user can set up.
BRIDGE LIVE Video I/O and Streaming Appliance v1.14
93
Figure 124. Logo Insertion Configuration
First, a logo file in the .png format must be uploaded and selected. After
that, the user can choose to position the logo either in pixels, or set its
positions using percent. If for some reason a logo has to have adjusted scale,
it’s possible to do it using the Logo scaling option. If you save a pipeline
that uses the Logo insertion function and has some logo uploaded as a preset,
it will be saved with the logo file, too.
Verifying Pipeline Configurations
You can use a variety of methods to verify your pipeline configurations. For
an encoded stream using stream type MPEG-TS, you can use RTP, UDP, or SRT to
send the stream to an output stream sink device. For RTP or UDP, BRIDGE LIVE
needs to be able to send the stream directly to the target location. If the
target location is behind a router that blocks it, or if the target location
is in a network behind NAT (network address translation), your target location
will not be able to receive the stream. For an encoded stream using stream
type RTMP(S), the stream cannot do pointto-point. It has to bounce off of a
server first. See “Alternative Methods for Verifying Pipeline Configuration”
on page 110 for more advanced methods of testing pipelines.
Verifying the Configuration of Your Pipeline Remotely
When an SRT output pipeline is configured on BRIDGE LIVE, you can verify it is
functioning correctly by accessing the stream with off-the-software for
monitoring. Besides the BRIDGE LIVE itself, the following external devices or
applications can be used to monitor an SRT stream for testing purposes: · VLC
– (see https://www.videolan.or
References
- Example Domain
- GitHub - sallar/mac-local-rtmp-server: Local RTMP Streaming Server
- Open Broadcaster Software | OBS
- BRIDGE LIVE is a broadcast-quality, low-latency turnkey system
- HELO Plus Advanced H.264 Streaming and Recording
- AJA Product Support Downloads
- SRT Alliance - Open-source SRT - Secure Reliable Transport
- VLC: Official site - Free multimedia solutions for all OS! - VideoLAN
- The Embedded Video Platform for Solution Builders | Wowza
Read User Manual Online (PDF format)
Read User Manual Online (PDF format) >>