SRT, RTMP and camera addresses: which setting goes where?
Distinguish camera inputs from publishing outputs and verify the assigned destination.
Input and output are different
A camera input brings media into the production system. A publishing destination receives the outgoing broadcast. Similar-looking SRT or RTMP addresses can appear in either role; entering an output server as a camera input will not establish the intended production.
Verify the event output
For a Hub-paired truck or camera kiosk, inspect the event/station publishing assignment in Hub. Local Production Truck productions can configure their supported SRT or RTMP/RTMPS destination while off air. Do not assume changing a local field overrides a paired Hub assignment.
Check the connection details
- Obtain the exact address and any stream key from the destination configuration.
- Confirm whether the address belongs to an input or output, the expected protocol, and caller/listener behavior where applicable.
- Use the intended secure transport supported by the destination. Do not paste a stream key into a public event description or screenshot.
- Apply through the app's output controls with the required outputs stopped.
- Make a test broadcast and verify reception at the destination, including audio and latency. A local Program picture only confirms local composition.
If it fails
Record whether the failure happens when saving, connecting or receiving media. Check network reachability and the exact server/key pairing. Keep stream credentials private. When working with a remote server administrator, describe the protocol and failure without sending passwords in public reports.
Need more help with this?
Search a specific symptom, review related guides below, or prepare a report with the app version, operating system and exact error. Guides describe the documented release; installed versions and subscription access can differ.
Prepare a support report