Osprey Talon UHD-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
For an Osprey Talon UHD-SC SRT setup, send the SDI source into the Talon UHD-SC, set the encoder to SRT caller mode, and point it to a cloud SRT listener in Callaba Gateway. Use this setup when Talon UHD-SC is at the venue and Callaba is the cloud SRT receiver for monitoring, recording, routing, multiview, or restreaming. The Talon UHD-SC is a hardware encoder, so the clean path is contribution ingest first; Callaba then handles downstream uses in parallel.
Quick answer
To use Osprey Talon UHD-SC with SRT, set Talon UHD-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 UHD-SC sends one contribution feed into Callaba. After ingest, Callaba can preview, record, route, restream, and feed multiview in parallel; these are not mandatory sequential setup steps.
- Talon UHD-SC12G-SDI in, SRT caller
- Callaba GatewaySRT listener and receiver
- Preview
- Record
- Route
- Multiview
- Restream
What this setup does
This workflow turns the Talon UHD-SC into the venue-side contribution encoder and Callaba into the Talon UHD-SC SRT gateway in the cloud. The encoder sends one SRT stream to Callaba. From there you can watch preview, build a multiview, record the input, route it to another endpoint, or restream to a public platform without changing the camera-side connection.
This is not a vendor receiver workflow. The Talon UHD-SC does not require an Osprey cloud receiver for this SRT path, and it is not a bonded cellular transmitter. Your network quality, uplink headroom, SRT latency, and codec choices still matter.
What this model can and cannot do in this workflow
- Confirmed for this model: Talon UHD-SC is a single-channel UHD60 encoder with 1x 12G-SDI input, embedded SDI audio up to 16 channels / 8 stereo pairs, and GigE IP streaming.
- Confirmed transports: Osprey lists RTMP(S), UDP, RTP, RTSP, Zixi, SRT, and WHIP for the Talon UHD-SC product family. This article uses SRT because it is the best fit for internet contribution to a receiver.
- SRT roles: the manual documents SRT caller and listener modes, SRT Destination Address in caller mode, SRT Port, SRT Stream ID, Latency, Encryption, Passphrase, and Video PID. I did not find official rendezvous mode for this model.
- Security detail: the manual describes 128-bit encryption and a 16-character alphanumeric passphrase for encrypted SRT transmission.
- Codec detail: H.264/AVC and H.265/HEVC are documented, with HEVC Main, Main 10, and Main 4:2:2 10 profiles. HEVC is useful, but UHDp60, 10-bit, and 4:2:2 can reduce compatibility with players and decoders.
- Do not plan Osprey Talon UHD-SC as a native NDI source. I did not find official NDI support for this exact model. If a production is NDI-based, use SDI or an external bridge path.
- RTMP/RTMPS difference: simulcast up to three destinations is documented for RTMP/RTMPS, not for SRT.
- Recording options: the Talon can save MP4 to USB 3.0 or network storage, while Callaba can record the received cloud feed as a separate downstream option.
Recommended workflow
Use this architecture: camera or switcher SDI output into the Talon UHD-SC 12G-SDI input, Talon UHD-SC SRT caller over the venue internet uplink, Callaba Gateway SRT listener in the cloud, and then Callaba outputs for preview, recording, routing, multiview, playback, or restreaming. Keep those Callaba outputs parallel. Do not treat preview, recording, and restreaming as a required chain.
For a Talon UHD-SC SRT to cloud setup, caller mode is usually easier because the venue device initiates the outbound UDP connection. Reversing the roles is possible only if the device side can accept inbound UDP: public IP, port forwarding, firewall rules, and a tested NAT plan.
When not to use this setup
If the encoder and production switcher are in the same rack, local SDI routing may be simpler than cloud contribution. If the only destination is YouTube or another public platform and you do not need cloud monitoring, recording, routing, or multiview, Talon RTMP/RTMPS may be enough. If you need NDI on the LAN, do not assume this model provides it; use SDI or an external NDI bridge. For local pull-style monitoring, RTSP can be useful on a controlled network, but I would not choose RTSP as the main internet contribution path.
Before you start
- Confirm the Talon UHD-SC firmware and update if required. Osprey lists production firmware for Talon UHD-SC Encoder on its firmware page.
- Decide the first-test format. For initial testing, H.264 is the safest codec choice. Start around 4-6 Mb/s for 1080p30 or 6-8 Mb/s for 1080p60, then adjust to the uplink and quality target.
- Use a stable wired network for the Talon. Leave room above the encoded bitrate for overhead and retransmits.
- Prepare a Stream ID and passphrase. Treat both as case-sensitive and whitespace-sensitive; a trailing space, copied newline, or changed capitalization can break the SRT handshake.
- If SRT handshakes fail in a way that does not match normal firewall or credential errors, confirm compatible SRT major versions from Osprey firmware notes or support information and from Callaba release or build information.
Create the Callaba SRT ingest
In Callaba, create an SRT server and choose listener mode for the public ingest address and UDP port. Add the Stream ID if your workflow uses one, set the passphrase to match the Talon, and keep encryption settings consistent on both sides. Success looks like an incoming connection, stable bitrate, uptime increasing, and a usable preview or audio meters after the Talon starts.
If the Talon is behind a normal venue firewall, do not open inbound ports to the Talon for this default design. The encoder should call out to the Callaba SRT listener.
Configure the Talon UHD-SC
Open the Talon web interface from the same network. Factory-default units use the documented admin login, but change production credentials before the event. In Channel Setup - Output, set the output protocol before finalizing video and audio settings because the manual states that protocol choice changes the available encode options.
In Channel Setup - Transport Protocols, select TS over SRT. Set SRT Mode to caller, enter the Callaba public address in SRT Destination Address, enter the Callaba UDP port in SRT Port, and match SRT Stream ID, encryption, and passphrase. The manual lists SRT port default 2088 and latency default 125 ms. For a first internet test, I usually start around 250-500 ms, then lower only after RTT, packet loss, and retransmits are stable. The manual also recommends latency at least 2.5 times RTT.
In video settings, use H.264 for the first pass unless you know every downstream decoder and player accepts your HEVC profile. If GOP controls are exposed, a two-second GOP is a practical starting point; on the Talon this usually means setting GOP Size to roughly twice the framerate, such as 60 frames for 29.97/30 fps or 120 frames for 59.94/60 fps.
Settings table
| Where | What to do / field to fill | First-test value | Why / check |
|---|---|---|---|
| Callaba | Create SRT server and choose UDP port | Use a known open UDP port | The Talon caller must reach this listener port. |
| Callaba | Stream ID | Use a short exact value | Must match the Talon SRT Stream ID exactly. |
| Callaba | Passphrase / encryption | Match Talon settings | Encryption mismatch or hidden whitespace can stop the handshake. |
| Talon UHD-SC | SRT Mode | caller | Venue encoder initiates outbound SRT to the cloud listener. |
| Talon UHD-SC | SRT Destination Address | Callaba ingest host/IP | This field is visible in caller mode. |
| Talon UHD-SC | SRT Port | Callaba UDP port | Do not assume the Talon default 2088 unless Callaba is listening there. |
| Talon UHD-SC | SRT Stream ID | Same as Callaba | Case and whitespace must be identical. |
| Talon UHD-SC | Passphrase | 16-character alphanumeric when encrypted | Use the exact value configured on the receiver side. |
Monitoring
After starting the encoder, check Callaba first: incoming bitrate, connection uptime, RTT, packet loss, retransmits, preview, and audio meters. Then check the Talon dashboard and front-panel status for SDI signal, channel encoding state, and network status. If preview is missing but bitrate is present, suspect codec, profile, resolution, or player compatibility before changing network settings.
Recording and playback
You can record in two places. The Talon UHD-SC can save MP4 locally to USB 3.0 or to a network share, which is useful for a venue-side archive. Callaba can also record the received SRT feed in the cloud. These are parallel choices: local Talon archive for on-site backup, Callaba recording for the received contribution feed, and Callaba playback or web player outputs for review and distribution.
Troubleshooting
| Symptom | Check in Callaba | Check on device | Likely fix |
|---|---|---|---|
| No SRT connection | Listener is running, UDP port is open, no wrong Stream ID rejection. | SRT Mode is caller, address and port are correct. | Fix firewall/NAT, port, or caller/listener direction. |
| Handshake starts then fails | Passphrase, encryption state, Stream ID, server logs. | Passphrase is exactly 16 alphanumeric characters when encryption is used. | Remove trailing spaces/newlines and match capitalization. |
| Connects but video is black | Incoming bitrate, preview decoder, codec warnings. | SDI signal, output resolution, codec/profile. | Test H.264 1080p first, then move to HEVC/UHD after preview is stable. |
| Audio missing | Audio meters and selected audio tracks. | Embedded SDI audio pair, audio enabled, AAC-LC or Opus selection. | Start with AAC-LC 48 kHz unless the endpoint requires Opus. |
| Stutters or drops | RTT, packet loss, retransmits, bitrate graph. | Target bitrate, rate control, GOP size, SRT latency. | Raise latency, lower bitrate, or use a cleaner uplink. |
| Hard-to-explain SRT failure | Callaba release/build support information. | Osprey firmware and support notes for SRT implementation details. | Confirm compatible SRT major versions and retest without encryption first. |
Official references
Vendor references
- Osprey Talon Encoders product page
- Osprey Talon Encoder manual
- Osprey Talon software and firmware
- Osprey user manuals
Protocol references
Callaba resources
FAQ
How do I use Osprey Talon UHD-SC with SRT?
Use the Talon UHD-SC as the SRT caller and Callaba as the SRT listener. Match address, UDP port, Stream ID, encryption, passphrase, latency, codec, and bitrate.
Should Talon UHD-SC be SRT caller or listener?
For internet contribution, caller is the normal first choice. Talon listener mode is an advanced fallback because the venue side must accept inbound UDP traffic.
Is Talon UHD-SC an SRT receiver or SRT server?
In this workflow, no. The Talon UHD-SC is the encoder. Callaba is the SRT receiver, listener, and gateway. Listener mode on the Talon does not make it the preferred cloud receiver.
What should I enter for Talon UHD-SC SRT Stream ID and passphrase?
Enter the exact Stream ID and passphrase configured in Callaba. Both are sensitive to case and hidden whitespace. For encrypted SRT, the Talon manual describes a 16-character alphanumeric passphrase.
Does Talon UHD-SC support NDI?
I did not find official NDI support for this exact model. Do not plan Osprey Talon UHD-SC as a native NDI source.
Can I use RTMP/RTMPS or RTSP instead?
Yes, RTMP/RTMPS and RTSP are documented. RTMP/RTMPS can be enough for a simple public platform ingest. RTSP is better kept to controlled local networks or bridge workflows.
Next steps
Build the first test with H.264, a conservative bitrate, Talon caller mode, and Callaba listener mode. Once the connection is stable, add recording, multiview, restreaming, or routing one at a time. Before the event, confirm firmware, SRT caller/listener direction, Stream ID, passphrase, latency, and codec settings in the official manual and on the installed firmware.
Try Callaba Gateway with Osprey Talon UHD-SC SRT setup
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.