Osprey Talon 4K-SC SRT setup: send SRT to Callaba Gateway
Written by Iurii Pakholkov
Founder of Callaba. Building cloud video tools for SRT, RTMP, WebRTC, NDI, live routing, monitoring, recording, and production workflows.
Release: Callaba 8.4
The Osprey Talon 4K-SC SRT setup is a direct encoder-to-cloud workflow: put the Talon 4K-SC in SRT Caller mode and send TS over SRT to a Callaba SRT Listener. Use this setup when Talon 4K-SC is at the venue and Callaba is the cloud SRT receiver for monitoring, recording, routing, multiview, or restreaming. The model is a single-channel 4K encoder with 12G-SDI and HDMI 2.0 inputs, so the practical work is matching Talon transport fields to the Callaba ingest.
Quick answer
To use Osprey Talon 4K-SC with SRT, set Talon 4K-SC as the SRT Caller and send the stream to a cloud SRT Listener. In this guide, Callaba works as the SRT gateway, receiver, monitor, recorder, and routing layer.
The Talon 4K-SC sends one SRT contribution feed into Callaba. After ingest, Callaba can preview, record, route, restream, and show the same source in multiview in parallel, not as mandatory sequential setup steps.
- Talon 4K-SCSRT caller encoder
- Callaba GatewaySRT listener receiver
- Preview
- Record
- Route
- Multiview
- Restream
What this setup does
This workflow sends the Talon 4K-SC program output over SRT to Callaba Gateway. Callaba listens on a UDP port in the cloud, receives the transport stream, and then makes that source available for monitoring, recording, routing, multiview, playback, and restreaming. The Talon stays at the venue as the encoder. Callaba is the Talon 4K-SC SRT gateway and receiver side of the workflow.
What this model can and cannot do in this workflow
- Confirmed: Talon 4K-SC is a single-channel hardware encoder with 1 x 12G-SDI input with loopout, 1 x HDMI 2.0 non-HDCP input, embedded SDI and HDMI audio, H.264/AVC, H.265/HEVC, and IP streaming transports including SRT, RTMP(S), RTSP, UDP, RTP, Zixi, and WHIP.
- SRT fields to match: the Talon manual documents SRT caller and listener modes, SRT Destination Address in caller mode, SRT Port, SRT Stream ID, Latency, 128-bit encryption, and a 16-character alphanumeric passphrase.
- Not a decoder: the 12G-SDI connector includes loopout of the SDI input. It is not a decoded return output from Callaba.
- Not native NDI: do not plan Osprey Talon 4K-SC as a native NDI source. Official Talon 4K-SC sources list SDI, HDMI, and IP streaming transports, not NDI for this model.
- Not ST 2110: SMPTE 2038 support is not the same as ST 2110 input or output.
- SRT rendezvous: caller and listener are documented. Rendezvous mode is not documented for this model, so I would not build an event plan around it without direct Osprey confirmation for the installed firmware.
Recommended workflow
For Talon 4K-SC SRT to cloud, I recommend using Callaba as the listener and the Talon as the caller. This avoids asking the venue encoder to accept unsolicited inbound traffic from the internet. It also fits the usual remote-production pattern: the venue sends one outbound UDP flow, and the cloud side handles monitoring and distribution.
Use H.264 first unless you control every downstream decoder and player. HEVC is confirmed on the Talon 4K-SC, but many browser, CDN, decoder, and monitoring paths still have stricter HEVC requirements. For first tests, start around 4-6 Mb/s for 1080p30, 6-8 Mb/s for 1080p60, and increase only after the uplink is stable. If the GOP or keyframe interval is exposed, 2 seconds is a practical starting point.
When not to use this setup
If the encoder and production switcher are in the same rack or on the same local SDI/HDMI path, a local baseband connection may be simpler. Do not substitute local NDI for this exact model unless you add a separate bridge device or software encoder, because native NDI is not listed for Talon 4K-SC.
If the only destination is a public platform and you do not need cloud monitoring, recording, routing, or multiview, the confirmed RTMP/RTMPS output may be enough. If you need a small local pull workflow, RTSP is also documented, but it is not the path I would choose for internet contribution when SRT is available.
Before you start
- Confirm the Talon firmware version and update plan. Osprey lists production firmware for the Talon 4K-SC encoder and recommends keeping Talon firmware current.
- Confirm the camera or switcher output format. For broad compatibility, test 1080p first before moving to UHD or DCI formats.
- Open the selected UDP port to the Callaba instance. SRT uses UDP, so TCP-only firewall rules will not help.
- Decide whether to use encryption. For an encrypted Talon test, prepare a 16-character alphanumeric passphrase that will be entered identically on both sides.
Create Callaba ingest
In Callaba, create an SRT server in listener mode and choose a UDP port. If you use Stream ID routing, create or copy the exact Stream ID that the Talon will send. If encryption is enabled, enter the same passphrase you will use on the Talon. Success looks like an active listener waiting for a source. If the listener cannot start, check port conflicts, cloud firewall rules, and whether another service already uses the same UDP port.
Configure the device
Open the Talon web interface from a browser on the management network. In the channel transport settings, choose TS over SRT. Set SRT Mode to caller, enter the Callaba public IP address or DNS name as the destination, and set the same SRT port. Enter the Stream ID exactly as configured on Callaba. Case, whitespace, copied newlines, and hidden trailing spaces matter.
Then set video and audio encoding. Start with H.264 and AAC-LC when compatibility is more important than compression efficiency. Use HEVC only after confirming the receiving, recording, playback, and restreaming path accepts it. Start the stream from the Talon Status or Dashboard area, then watch Callaba for incoming bitrate and preview.
Settings table
| Where | What to do / field to fill | First-test value | Why / check |
|---|---|---|---|
| Callaba | Create SRT server and choose UDP port | 2088 or another open UDP port | Use the same port on the Talon and open it in the cloud firewall. |
| Callaba | Stream ID | talon4ksc-main | Use a simple value first. It is case-sensitive and whitespace-sensitive. |
| Callaba | Passphrase / encryption | Off for first LAN test; on for production if required | When enabled, match the Talon 16-character alphanumeric passphrase exactly. |
| Talon Channel Setup - Transport Protocols - TS over SRT | SRT Mode | caller | The encoder initiates the outbound connection to the cloud listener. |
| Talon TS over SRT | SRT Destination Address | Callaba public IP or DNS name | This field is visible in caller mode and points to the receiver endpoint. |
| Talon TS over SRT | SRT Port | Same UDP port as Callaba | The manual lists 2088 as a default, but the two sides must match your deployment. |
| Talon TS over SRT | SRT Stream ID | Exact Callaba Stream ID | A changed capital letter, trailing space, or copied newline can break matching. |
| Talon TS over SRT | Latency | 250-500 ms for first internet test | The Talon manual lists 125 ms default and recommends at least 2.5 times RTT. Raise latency if retransmits or jitter appear. |
Monitoring
Once the Talon connects, check Callaba for connection uptime, incoming bitrate, packet loss, RTT, retransmits, preview, and audio meters. These are parallel checks: preview does not have to happen before recording, and recording does not have to happen before routing. If the stream looks stable for 10-15 minutes at the intended bitrate, test your real outputs next.
Recording and playback
After ingest is stable, enable recording in Callaba if the job requires a cloud archive. Then test playback or web player output separately from the contribution path. If the incoming stream is HEVC and a browser player does not show video, test H.264 from the Talon before assuming the SRT connection is at fault.
Troubleshooting
| Symptom | Check in Callaba | Check on device | Likely fix |
|---|---|---|---|
| No connection | SRT server active, UDP port open, no source connected | SRT Mode caller, destination address, port | Open the UDP port, correct the IP or DNS name, and restart the Talon stream. |
| Handshake rejected | Stream ID and passphrase values | SRT Stream ID, Encryption, Passphrase | Remove trailing spaces, match capitalization, and use the Talon 16-character alphanumeric passphrase limit. |
| Connects but freezes | RTT, packet loss, retransmits, incoming bitrate | Latency, bitrate, uplink capacity | Raise latency, reduce bitrate, or use a cleaner network path. |
| Preview works but downstream output fails | Codec shown on ingest and output compatibility | H.264 versus HEVC settings | Use H.264 for the first production path unless every downstream decoder supports HEVC. |
| Audio missing | Audio meters and selected audio track | Embedded SDI or HDMI audio pair and audio codec | Select the correct embedded pair and use AAC-LC for broad compatibility. |
| Hard-to-explain SRT failure | Callaba build, release notes, or support information | Talon firmware release notes or Osprey support information | Confirm compatible SRT major versions and passphrase behavior on both sides. |
Official references
Vendor references
- Osprey Video Talon Encoders product page
- Osprey Talon 4K-SC spec sheet
- Osprey Talon Encoder installation and operation guide
- Osprey Talon software and firmware
Protocol references
Callaba resources
FAQ
How do I use Osprey Talon 4K-SC with SRT?
Create a cloud SRT listener in Callaba, then configure the Talon 4K-SC TS over SRT output as caller. Match address, UDP port, Stream ID, latency, and optional encryption settings.
Is Talon 4K-SC the SRT caller, listener, receiver, or server?
For this setup, Talon 4K-SC is the SRT caller and Callaba is the listener or receiver. Talon listener mode is documented, but it is an advanced fallback because the venue side must accept inbound UDP traffic. The Talon is still an encoder, not a decoder return receiver.
What should I know about Talon 4K-SC SRT Stream ID and passphrase?
Stream ID should match exactly on both sides. The Talon manual documents a 16-character alphanumeric SRT passphrase for encrypted transmission. Treat Stream ID and passphrase as case-sensitive and whitespace-sensitive.
Does Osprey Talon 4K-SC support native NDI?
No official Talon 4K-SC sources used here list native NDI for this model. Use SDI, HDMI, or one of the documented IP streaming transports instead, or add a separate bridge if an NDI environment is required.
Can I use RTMP, RTMPS, or RTSP instead of SRT?
Yes, RTMP/RTMPS and RTSP are documented for the Talon encoder family. RTMP/RTMPS can be fine for a simple platform ingest. For remote contribution where you want monitoring, recording, and routing in Callaba, SRT is usually the better first choice.
Should I use H.264 or HEVC from Talon 4K-SC?
Use H.264 for the first test and for broad compatibility. HEVC is confirmed on the model, but every downstream decoder, player, CDN, and output path must also support it.
Next steps
Build the path in this order: confirm firmware and input format, start a Callaba SRT listener, send Talon 4K-SC as caller, verify incoming bitrate and preview, then test recording, routing, multiview, playback, or restreaming as separate downstream outputs. Before the event, confirm firmware, SRT caller/listener direction, Stream ID, passphrase, latency, codec, audio pair, and firewall rules with the actual network you will use.
Try Callaba Gateway with Osprey Talon 4K-SC SRT
Create an SRT server in Callaba, send the device feed to the gateway, and check the received stream. After ingest is stable, use Callaba outputs for preview, recording, restreaming, multiview, playback, routing, or API workflows as parallel downstream options.