No NDI output on a SRT connection
After a connection is created, there is no NDI output or very low frame rate on the RX endpoint. Please try to use NDI Time Stamps as Timecode handling.
Low frame rate could also indicate poor hardware performance.
If there is no FPS shown on the RX side of the connection (In the Connection details - Right click on the thumbnail and select "Show Details", it could be an indication of the NDI source not carrying any audio frames. In that case select the "No Audio" option when creating or editing the connection.
Related Articles
What is SRT Caller --> Listener?
SRT Caller-Listener is a mode of operation for the SRT (Secure Reliable Transport) protocol, which is a low-latency, high-performance video streaming protocol that is designed to deliver high-quality video content over unreliable networks such as the ...
Connection Subscriptions
Subscriptions BirdDog Cloud is licensed by Subscriptions. This allows access to the platform for a certain number of concurrent connections. For example, each live connection you have between two locations counts as a single connection. You can ...
Troubleshooting "Connection Timeout"
Connection Timeout is usually caused by the fact that the 2 EP cannot create the SRT connection on the selected UDP port. This can be caused either by a firewall configuration problem, or that the UDP port is currently being occupied. A previous ...
High latency on SRT connections
If you are experiencing high latency, first make sure that you are using correct Timecode Handling and change to another to see if this helps. There may be an issue with the NDI source not producing consistent NDI Time Codes. High latency may also ...
SRT Networking documentation
SRT Networking To access BirdDog Cloud networking document click on the link To access SRT Networking in the Haivision SRT Deployment guide click here