For Blackmagic Streaming Decoder 4K, check the protocol and codec together: the documented direct inputs are SRT/H.265 and RTMP/H.264. Support for a codec on the encoder does not automatically mean the decoder accepts that codec over the same protocol.
The device turns a compatible network stream into SDI or HDMI video. Before designing a return-feed route, establish that the actual source is supported, then check the output format required by the monitor or production equipment.
Match the source, protocol and codec
| Direct input | Documented codec | Source |
|---|---|---|
| SRT | H.265 | Blackmagic Streaming Encoder or a compatible Blackmagic camera |
| RTMP | H.264 | Blackmagic Streaming Encoder or a compatible Blackmagic camera |
This pairing comes from the decoder’s Direct Streaming specification. It does not establish compatibility with every third-party SRT sender. Use the decoder’s documentation for the installed firmware, rather than the specification for a similarly named encoder.
Prepare one known source before adding a route
- Identify both devices. Note the source model and the firmware installed on the source and decoder. Check that the source is covered by the documented direct-streaming path.
- Choose the required output. Record the destination’s connector, resolution and frame rate. This avoids debugging the network when the downstream monitor cannot accept the selected signal.
- Establish the direct connection. Follow the current Blackmagic Streaming manual for that source. Confirm moving video and audible sound at the decoder’s physical output.
- Keep the working setup. When you add another network segment or routing system, change one part at a time. If the result fails, return to the direct source to separate an interoperability issue from an output problem.
Connected, but no picture or sound?
The decoder’s 12G-SDI and 4K HDMI outputs can follow the incoming streaming standard or use a configured output conversion. For example, a destination expecting 1080p50 should be checked against that output timing, not merely against a generic “HD” label.
- No image at the monitor: check the selected connector, cable, monitor input and supported resolution/frame rate. If you can see a preview on the decoder, investigate this physical output path before changing the SRT settings.
- No decoded video: return to the source/protocol/codec pairing above and compare with the known working direct connection.
- Picture but no sound: confirm that the source carries audio, then check the destination’s audio selection and monitoring path.
- Intermittent output: note whether the interruption also occurs on the direct path. Compare source, network and output behavior over the same interval; one fixed loss or RTT threshold cannot diagnose every installation.
Adding Callaba to the path
The manufacturer specification reviewed here does not establish a Callaba-to-Decoder 4K integration or which endpoint initiates its connection. Do not copy a generic SRT URL into an assumed decoder field and treat it as a supported recipe.
If your project needs Callaba routing, evaluate that combination with the exact source and firmware first. Keep source compatibility separate from the Callaba SRT server configuration. For the opposite direction—sending video from a Blackmagic encoder into Callaba—use the dedicated Streaming Encoder guide.
FAQ
Does the decoder support H.264 over SRT?
The current direct-streaming specification lists H.265 for SRT and H.264 for RTMP. Do not transfer the encoder’s wider codec support to the decoder. Check the installed firmware documentation for any later change.
Can Blackmagic Streaming Decoder 4K receive a Callaba-routed stream?
The reviewed manufacturer documentation does not establish that combination or its caller/listener direction. This is an unverified route, not a statement that it cannot work. Test the intended source and route with the installed firmware before relying on it.
Next steps
Compare the device roles in the Blackmagic integration hub. For an already verified routing project, the SRT Servers API reference documents Callaba-side configuration; it does not configure or certify the decoder.
Ready to configure the Callaba side of a verified path? Open the SRT server guide →
