Blackmagic SRT Gateway Workflows with Callaba
More live video workflow notes and product updates.
Blackmagic streaming processors
Encoder and Decoder are opposite edges of the path—not two names for the same gateway
A Blackmagic Streaming Encoder takes a local program toward a network destination. A Streaming Decoder receives a supported network stream and returns it to a production output. Callaba can sit between those roles as the named receiving, monitoring, recording and routing point, but it does not erase the direction of either appliance.
This distinction matters during troubleshooting: a successful Encoder-to-Callaba contribution does not prove that a later Callaba-to-Decoder return is compatible or reachable.
Read the workflow from left to right
If the event needs only contribution, stop the design at Callaba and its downstream destinations. Add the Decoder only when a real baseband return is required. Use different operational names, ports and evidence for the forward and return legs.
Select hardware by direction and media envelope
Originating the program
- Streaming Encoder workflow for the family-level contribution path.
- Encoder HD guide when the required program is within the documented HD envelope.
- Encoder 4K guide only after source, encode, network and downstream support have all been checked for the selected Ultra HD profile.
Returning to production output
- Streaming Decoder workflow for a network-to-baseband path.
- Confirm the Decoder accepts the codec, raster, frame rate and audio emitted by the chosen Callaba route.
- Do not describe the Decoder as the origin of an incoming contribution merely because it appears in the same product family.
Run two acceptance tests when both directions matter
Test A — contribution
- Lock the actual SDI or HDMI source on the Encoder.
- Load a configuration built for that processor and software version.
- Confirm the named Callaba input connects and holds the expected bitrate.
- Decode motion and every audio channel, then make a short recording.
Test B — return decode
- Create one explicit Callaba output from the already accepted source.
- Configure the Decoder as the opposite SRT peer where supported.
- Verify the baseband output on the intended monitor, router or switcher.
- Interrupt only the return leg and document its reconnect behavior.
Treat configuration as production material
Configuration record
Store a short, redacted record another operator can understand:
- exact processor and installed software;
- send or receive direction;
- source, codec, raster and audio;
- named Callaba endpoint and production role.
- Use current Blackmagic developer resources for the exact processor instead of copying an XML example from another model.
- Keep passphrases, public addresses and stream identities out of screenshots and shared repositories.
- Revalidate after any processor or supporting-software update.
- For simultaneous jobs, test the complete codec and channel mix at production rates.
- Keep local recording proof separate from network-output proof where both are required.
Trace a failure in the direction it travels
If the Encoder has no input lock or encode output, keep Callaba and the Decoder out of that diagnosis. If the Encoder reports an active output but Callaba has no session, compare the two SRT roles, address, UDP port, firewall, Stream ID, latency and encryption. If Callaba receives transport but cannot decode useful media, compare codec, raster and audio before rebuilding the network.
On the return leg, first prove that the accepted Callaba source is routed to the intended output. Then inspect session arrival and the Blackmagic Decoder’s physical output. A working contribution leg is valuable evidence, but it must remain untouched while the independent return leg is repaired.
Check the current Blackmagic resources before airtime
Consult Blackmagic’s streaming developer resources and current Streaming Processor pages. Supported protocols, configuration fields and media limits must be checked against the exact model and installed software.
