Osprey Talon SRT setup hub: 4K-SC and UHD-SC
More live video workflow notes and product updates.
Talon model comparison hub
Talon 4K-SC and UHD-SC are both single-channel hardware encoders, but their source interfaces and maximum raster are not identical. The model decision belongs before the SRT configuration: first match the physical input and production format, then connect the chosen encoder to Callaba.
Written by Iurii Pakholkov, founder of Callaba. Materially reviewed on July 17, 2026 against the official sources listed below.
Choose the correct 4K-SC and UHD-SC
| Path | Operational role | When to choose it |
|---|---|---|
| Talon 4K-SC | One HDMI 2.0 or 12G-SDI input, with UHD and DCI 4K formats. | Choose when HDMI input or 4096-wide DCI production is part of the requirement. |
| Talon UHD-SC | One 12G-SDI input for formats up to 3840×2160p60. | Choose for a straightforward single-channel SDI UHD contribution path. |
| Callaba receiving layer | A common listener, monitoring, recording and routing boundary. | Use the same operational layer without flattening the two encoder models into one configuration. |
Keep the source, handoff and Callaba roles explicit
Source-side responsibility
Talon owns the physical HDMI or SDI input, hardware encoding, local stream creation and source-side transport settings.
Transport handoff
The contract is the exact Talon model, input format, H.264 or H.265 profile, audio, SRT mode, port, security and recovery budget.
Callaba responsibility
Callaba owns public or private receiver reachability, live transport inspection, Multiview, recording, route fan-out and web playback.
Select Talon by input and production raster
- 1. Read the chassis label and confirm whether the unit is 4K-SC or UHD-SC. Similar web interfaces do not remove the hardware input difference.
- 2. Match SDI or HDMI source format, frame rate, color and audio to the exact product specification. Resolve HDCP and source timing before testing the network.
- 3. Install a reviewed production firmware and export the current configuration. Osprey publishes separate firmware entries and change logs for these models.
- 4. Configure Talon as the agreed SRT peer and Callaba as the matching endpoint. Verify port, Stream ID, passphrase and codec support end to end.
- 5. Record a sample while viewing Multiview and the final destination. Inspect motion, audio, HDR expectations and recovery under the real network profile.
After preflight, use the SRT Gateway hub for architecture choices, the SRT Server guide for receiver concepts, Multiview for browser operations, and the SRT API documentation for automation. These shared resources do not replace the model-specific guide linked in the decision table.
Official references reviewed
Capabilities and menu fields can change with hardware revisions, firmware and account entitlements. Recheck the exact model before a production event.
- Osprey Talon encoder specifications — Official 4K-SC and UHD-SC inputs, formats, codecs and transports.
- Talon software and firmware — Official model-specific production releases and change logs.
- Osprey manuals directory — Current operating documentation for exact Talon hardware.
Frequently asked questions
What is the difference between Talon 4K-SC and UHD-SC?
The 4K-SC accepts 12G-SDI and HDMI 2.0 and lists DCI 4K formats up to 4096×2160. UHD-SC is a 12G-SDI model for formats up to 3840×2160. Confirm all details on the current official specification.
Should Talon use caller or listener mode with Callaba?
A source-side caller to a reachable Callaba listener is a practical default, but the deployed firmware and network policy must support the selected role. Configure the opposite role on each peer and test UDP reachability.
Which codecs are available?
The current Talon page lists H.264/AVC and H.265/HEVC for both models. Select a profile supported by every recorder, player and downstream destination, not only by the encoder.
Do both models expose the same SRT security controls?
Do not assume so across firmware versions. Review the exact manual and release notes, then verify Stream ID, passphrase length, encryption and latency controls on the installed unit.
How do I verify and record a Talon feed?
Confirm the input lock on Talon, connection and statistics in Callaba, audio in Multiview, a playable recording artifact and the real downstream output. Test all five before sign-off.
Move from device choice to a tested receiving path
Open the exact-model guide, validate one contribution feed in Callaba, then add recording, monitoring and downstream routes only after the ingest contract is stable.
