-
Notifications
You must be signed in to change notification settings - Fork 112
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Added AJA Bridge Live documentation #743
Open
jyepe
wants to merge
3
commits into
SkylineCommunications:main
Choose a base branch
from
jyepe:main
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,56 @@ | ||
--- | ||
uid: Connector_help_AJA_Bridge_Live | ||
--- | ||
|
||
# AJA Bridge Live | ||
|
||
## About | ||
|
||
The AJA Bridge Live connector enables seamless integration with AJA Bridge Live, a high-performance turnkey solution for SDI video encoding, decoding, transcoding, and streaming. Designed for remote production, live contribution, and content delivery, this connector allows users to monitor and configure critical workflows while ensuring reliable, cost-effective video transport across networks. | ||
|
||
## Key Features | ||
|
||
**System monitoring**: Retrieve system details such as software versions and real-time GPU/CPU utilization for performance monitoring. | ||
|
||
**Network interface management**: Monitor network interfaces and bandwidth utilization, and ensure optimal connectivity for uninterrupted streaming. | ||
|
||
**Pipeline control & configuration**: Start, stop, and modify pipelines dynamically, adjusting video, audio, and caption settings as needed. | ||
|
||
**Input & output stream management**: Configure input and output streams with flexible encoding and transport options, including NDI, SRT, and RTMP. | ||
|
||
## Use Cases | ||
|
||
### Use Case 1: Replacing Satellite Uplink with IP Streaming | ||
|
||
**Challenge**: Traditional satellite uplink solutions are expensive and require extensive infrastructure, making them inefficient for modern live broadcasts. | ||
|
||
**Solution**: AJA Bridge Live allows broadcasters to replace satellite transponders with a simple ISP connection, leveraging bidirectional IP transport for reliable video streaming. | ||
|
||
**Benefit**: Significant cost savings, reduced complexity, and improved flexibility for remote productions and live events. | ||
|
||
### Use Case 2: Dynamic Multi-Codec Transcoding | ||
|
||
**Challenge**: Live production environments require real-time transcoding across multiple formats to ensure compatibility with different platforms. | ||
|
||
**Solution**: Bridge Live supports multiple codecs (H.264, HEVC, JPEG XS, MPEG-2) and can dynamically transcode streams to meet delivery requirements. | ||
|
||
**Benefit**: Enhanced compatibility with CDNs like YouTube, Twitch, and Facebook Live, enabling seamless content distribution. | ||
|
||
### Use Case 3: High-Redundancy Live Streaming | ||
|
||
**Challenge**: Live video streams are vulnerable to network issues such as packet loss, jitter, and latency fluctuations. | ||
|
||
**Solution**: With SMPTE 2022-7 hitless redundancy, AJA Bridge Live ensures seamless failover by transmitting identical streams across independent network paths. | ||
|
||
**Benefit**: Increased reliability, reduced risk of video interruptions, and optimized quality of experience for viewers. | ||
|
||
## Technical Reference | ||
|
||
### Prerequisites | ||
|
||
- Network access: AJA Bridge Live must be accessible over the network for API communication. | ||
- Authentication configuration: Basic authentication credentials (username and password) must be set up. | ||
- Pipeline configuration: Users should pre-define input and output settings for efficient stream management. | ||
|
||
> [!NOTE] | ||
> For detailed technical information, refer to our [technical documentation](xref:Connector_help_AJA_Bridge_Live_Technical). |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,37 @@ | ||
--- | ||
uid: Connector_help_AJA_Bridge_Live_Technical | ||
--- | ||
|
||
# AJA Bridge Live | ||
|
||
## About | ||
|
||
BRIDGE LIVE is the broadcast-quality, low-latency turnkey system for REMI, synchronous multi-channel video contribution, remote collaboration, direct-to-audience streaming, and multi bit rate/multi format delivery. | ||
|
||
## Configuration | ||
|
||
### Connections | ||
|
||
#### HTTP Connection - Main Connection | ||
|
||
This connector uses an HTTP connection and requires the following input during element creation: | ||
|
||
HTTP CONNECTION: | ||
|
||
- **IP address/host**: The polling IP or URL of the destination. | ||
- **IP port**: The IP port of the destination. | ||
- **Device address**: The bus address of the device. If the proxy server has to be bypassed, specify *BypassProxy*. | ||
|
||
### Initialization | ||
|
||
The **Configuration** subpage contains the **Username** and **Password** fields. These fields are used to authenticate the user to the device. These fields must be filled in for the connector to be able to retrieve information. | ||
|
||
## How to use | ||
|
||
REST API is used to retrieve the device information. The connector can be used to retrieve the device information and monitor the device status. | ||
|
||
The **Pipelines** page shows information about all available pipelines. You can also start and stop pipelines from this page. | ||
|
||
Pipelines can be edited from the **Inputs** and **Outputs** pages. | ||
|
||
All sets to the device can be found on the **Pipeline Sets** page. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These use cases seem related to the AJA Bridge Live itself, instead of to the connector. However, these should in fact illustrate the benefits of the connector. Could you adjust this?