media server logo
PricingAPI docsLaunch SRT server

Blackmagic Web Presenter SRT setup with Callaba Gateway

May 21, 2026
Iurii Pakholkov, founder of Callaba

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 · Last updated: May 21, 2026

Blackmagic Web Presenter and ATEM Mini Pro workflows can send a live SRT feed into Callaba, but the cleanest Callaba setup is not always a direct device-to-server connection. If the Blackmagic device has trouble with a complex Stream ID or special characters, create an SRT Route in Callaba first, then route that input to your Callaba SRT server.

This guide shows the practical path: create the final Callaba SRT server, create a route with a simple device-side Stream ID, copy the route Input URL into Blackmagic Web Presenter, then monitor, record, restream or play back the received feed in Callaba.

Quick answer: how do you stream SRT from Blackmagic Web Presenter to Callaba?

Create a Callaba SRT server first and copy its Publisher URL. Then create a Callaba SRT Route with Input type: Listen SRT port, set a simple Stream ID such as stream1, and set the route destination to the SRT server Publisher URL. Finally, copy the route Input URL into Blackmagic Web Presenter: put the srt://host:port value in the Server field and the simple Stream ID in the Key field.

Blackmagic Web Presenter SRT to Callaba Gateway Indexable cover diagram showing Blackmagic Web Presenter or ATEM Mini Pro sending SRT to a Callaba SRT route, then Callaba routing the stream to an SRT server, monitoring, recording, restreaming and playback. Blackmagic Web Presenter SRT Web Presenter / ATEM Mini Pro → Callaba SRT route → SRT server Blackmagic Web Presenter 4K or ATEM Mini Pro simple SRT URL server field + key field Callaba SRT route accepts simple Stream ID SRT server record restream Stream ID fix SRT ingest UDP monitor · record · route
Use a Callaba SRT Route when the Blackmagic device needs simple stream values, then let Callaba forward the stream to the final SRT server.

What this setup does

The workflow takes a live SRT stream from Blackmagic Web Presenter or ATEM Mini Pro and brings it into Callaba Gateway. Once the feed arrives, Callaba can monitor the transport, route the stream, record it, restream it, create playback, or pass it into a larger live production workflow.

The important detail is that we build the destination first. That gives the Blackmagic device a simple input address and Stream ID, while Callaba handles the internal route to the final SRT server.

Why use SRT Route for Blackmagic?

Some Blackmagic workflows are easier when the device-side values are simple. For example, a Blackmagic setup screen may separate Server and Key. If your full Callaba SRT URL uses a Stream ID format that is difficult to enter on the device, create a Callaba SRT Route and give the device a simple key such as stream1.

Blackmagic Stream ID workaround with Callaba SRT Route Indexable diagram explaining why Callaba SRT Route helps Blackmagic Web Presenter or ATEM Mini Pro when Stream ID values with special characters are difficult to enter. Why use an SRT Route? Keep Blackmagic values simple, then let Callaba route to the full SRT destination. Direct SRT can be hard to enter Complex Stream ID Special characters Device field limits Callaba Route simple input side Port: 5000 Stream ID: stream1 Output: SRT server URL Stable result clear routing Callaba receives feed SRT server gets output Monitoring stays central Blackmagic sends simple values. Callaba handles the route.
The route acts as a clean adapter between the Blackmagic device fields and the full Callaba SRT server destination.

Before you start

Callaba access You need a Callaba instance where you can create SRT servers and SRT routes.
Blackmagic device Use Blackmagic Web Presenter, ATEM Mini Pro, or a compatible Blackmagic sender that exposes SRT streaming settings.
Video source Confirm that the SDI or HDMI source is active before debugging SRT.
UDP ports SRT uses UDP. Open the route input port and any SRT server ports in the cloud security group or host firewall.
Simple Stream ID Start with a simple key such as stream1. Avoid slashes and special characters on the device side.
Codec first test Use H.264 for the first test. Add H.265 only after the basic route is stable.
Video standard Confirm the SDI/HDMI input is stable and detected by Blackmagic Web Presenter before debugging SRT. A mismatched format such as 1080i vs 1080p can look like a streaming problem.

Workflow overview

The workflow is intentionally built backwards: final receiver first, device sender last. This avoids guessing the destination fields in Blackmagic Web Presenter.

Blackmagic Web Presenter to Callaba SRT workflow Indexable workflow diagram showing how to set up the destination first: Callaba SRT Server, SRT Route, route Input URL, Blackmagic Web Presenter settings, monitoring and output workflows. Set up the destination first Build the Callaba receive path, then copy the final route Input URL into Blackmagic Web Presenter. 1. Server SRT receiver 2. Route Listen SRT port 3. Input URL copy route URL 4. Device Web Presenter 5. monitor recording multiview restream playback
Create the Callaba receive path first, then paste the route input into Blackmagic Web Presenter.

Step 1: create an SRT server in Callaba

Go to SRT Servers and click Add New. Name the server, set the publisher and receiver ports, and save it. Then open the server Info window and copy the SRT Publisher URL.

Create SRT server in Callaba for Blackmagic Web Presenter SRT workflow
Create the final Callaba SRT server and define publisher and receiver ports.
Copy SRT Publisher URL from Callaba SRT server info window
Copy the SRT Publisher URL. The SRT Route will use this as the destination.

Firewall reminder: open the selected UDP ports in your cloud security group or host firewall. If UDP is blocked, the Blackmagic device will not reach Callaba even if the URL looks correct.

Step 2: create an SRT Route in Callaba

Go to SRT Routes and click Add New. Set Input type to Listen SRT port, then choose the input port that the Blackmagic device will send to.

Open Advanced input settings and set a simple Stream ID, for example stream1. This is the value you will paste into the Blackmagic Key field.

Callaba SRT Route advanced input settings with Stream ID for Blackmagic Web Presenter
Set a simple Stream ID on the route input side, such as stream1.

For the route destination, choose SRT Output URL and paste the SRT server Publisher URL you copied in the previous step. Then save the route.

Callaba SRT Route output URL pointing to the SRT server publisher URL
Set the route destination to the final SRT server Publisher URL.

After saving the route, open its Info window and copy the Input URL. This is the URL you will use in Blackmagic Web Presenter.

Copy Callaba SRT Route input URL for Blackmagic Web Presenter
Copy the route Input URL. This is the Blackmagic device destination.

Text example of the route Input URL that the Blackmagic device sends to:

Command 
srt://YOUR_CALLABA_IP:5000?streamid=stream1

Stream ID case note: the value in the Blackmagic Key field can be case-sensitive in real workflows. If the Callaba route expects stream1, enter exactly stream1, not Stream1 or STREAM1.

Step 3: configure Blackmagic Web Presenter

Open Blackmagic Web Presenter Setup and go to Live Stream. Choose a custom SRT profile if needed, then split the Callaba route Input URL into the fields the device expects.

  • Server: use the route input URL host and port, for example srt://75.98.2:5000.
  • Key: use the route Stream ID, for example stream1.
  • Passphrase: the Passphrase field is in the SRT profile settings, usually near Server and Key. Use the same value as Callaba only if encryption is enabled. If you are not using encryption, leave it empty on both sides.
  • Quality: start with a medium profile for first test, then tune bitrate after the route is stable.
Blackmagic Web Presenter SRT settings with server URL and stream key for Callaba route
Paste the Callaba route Server value and simple Stream ID into Blackmagic Web Presenter Setup.

Save the settings and click ON AIR. Then return to Callaba and confirm that the SRT Route and SRT Server show real incoming bitrate.

Blackmagic Web Presenter ON AIR while sending SRT to Callaba
Once ON AIR is active, verify the stream in Callaba instead of relying only on the device state.

Settings table

Blackmagic Web Presenter SRT settings checklist Indexable settings table for Blackmagic Web Presenter SRT setup with Callaba: server, key, passphrase, quality, route port, Stream ID, latency, codec and firewall. Settings that must match The Blackmagic device only needs the route input. Callaba routes that input to the SRT server. Setting Blackmagic Callaba Why it matters Serversrt://host:route-portRoute Input URLingest target Keystream1Route Stream IDidentity Passphrasesame if usedsame if usedencryption Route portport in Server URLListen SRT portentry point Output URLnot used directlySRT Publisher URLdestination CodecH.264 firstreceive/routecompatibility Qualitystart mediumwatch bitrateuplink headroom Latencydevice profileSRT route/serverrecovery UDP firewalloutbound pathopen route portreachability Audioembedded inputpreview/recordpayload
Keep the Blackmagic side simple. Put the more complex destination logic inside Callaba.
Setting Blackmagic Callaba Why it matters
Server srt://host:route-port Route Input URL Tells the device where to send SRT.
Key stream1 Route Stream ID Simple ID avoids device field problems.
Passphrase Same key if used Same key if used Encryption fails if values differ.
Latency Device profile / SRT setting SRT route/server Recovery time for jitter and packet loss.
Codec H.264 first Receive and route Best first diagnostic path.
UDP firewall Outbound allowed Route input port open SRT packets must reach Callaba.

After the stream reaches Callaba

Once Callaba receives the Blackmagic SRT feed, the source can become part of a larger workflow:

  • browser multiview for operator monitoring;
  • cloud-side recording;
  • restreaming to social platforms;
  • SRT output to another production system;
  • HLS or web player delivery for approved viewers;
  • API-controlled routing for event workflows.

Monitoring threshold: in good conditions, RTT is often around 20–60 ms. If RTT is consistently above 150 ms or keeps growing, check the network path. Packet loss above 1–2% usually means you should increase latency, lower bitrate, or improve the uplink before the event.

Interactive check: open the Callaba multiview demo to see how received sources can look after cloud ingest.

Troubleshooting

Blackmagic Web Presenter SRT troubleshooting path Indexable troubleshooting diagram for Blackmagic Web Presenter SRT setup: check route input URL, Stream ID, UDP firewall, passphrase, codec, audio and destination output. Debug Blackmagic SRT in this order Most issues are URL split, Stream ID, UDP firewall, passphrase, codec or route destination. 1. Route URLserver field 2. KeyStream ID 3. UDProute port open? 4. Passphrasesame key 5. CodecH.264 first 6. Audioembedded source 7. OutputSRT server URL
Debug route input first, then Stream ID, UDP, encryption, codec and route destination.

Blackmagic is ON AIR, but Callaba receives nothing

Check that the Blackmagic Server field uses the route Input URL, not the final SRT server Publisher URL. Then check that the route input UDP port is open.

Connection appears, but there is no video

Switch to H.264 for the first test, check that the source video is active, and confirm that Callaba sees real incoming bitrate. Do not start troubleshooting H.265 until H.264 works.

Video standard check: before debugging the SRT route, confirm that Blackmagic Web Presenter detects a stable SDI/HDMI input signal and that the expected format is selected. A mismatch such as 1080i vs 1080p, PAL vs NTSC, or unsupported input timing can prevent a valid outgoing stream.

Stream ID does not work

Use a simple Stream ID such as stream1 in the Callaba SRT Route and paste the same value into the Blackmagic Key field. Avoid slashes and special characters on the device side.

Passphrase is enabled but the stream fails

Confirm that the Blackmagic passphrase and Callaba route/server passphrase match exactly. For first diagnostic test, temporarily disable encryption, prove the route, then re-enable passphrase.

Audio is missing

Verify that the SDI or HDMI input actually carries embedded audio. Then check Callaba preview or recording. If audio is not present at the source, the SRT workflow cannot create it later.

FAQ

Can Blackmagic Web Presenter stream SRT?

Yes. This workflow uses Blackmagic Web Presenter or ATEM Mini Pro as the SRT sender and Callaba as the SRT ingest and routing layer. The exact menu labels depend on the device and software version.

Why use an SRT Route instead of sending directly to the SRT server?

Use an SRT Route when the Blackmagic device has trouble with a complex Stream ID or special characters. The route can accept a simple input such as stream1 and then forward the stream to the SRT server Publisher URL.

What should I put in the Blackmagic Server field?

Use the Callaba SRT Route Input URL host and port, for example srt://YOUR_CALLABA_IP:5000. Do not paste the final SRT server output URL into the Blackmagic device unless you intentionally want to skip the route workaround.

What should I put in the Blackmagic Key field?

Use the simple Stream ID configured on the Callaba SRT Route, for example stream1. Keep it simple to avoid device-side character limitations.

Do I need to open UDP ports?

Yes. SRT uses UDP. Open the route input UDP port and any SRT server publish or receiver ports in your cloud security group, host firewall, router or network policy.

Should I use H.264 or H.265?

Use H.264 for the first test. If your exact Blackmagic device and Callaba workflow support H.265, test it after the H.264 path is stable.

Can I use a passphrase?

Yes, if the device and Callaba route/server are configured with matching passphrase settings. If the passphrase does not match, the SRT session will not connect correctly.

How do I confirm Callaba receives the Blackmagic stream?

Check the Callaba SRT Route and SRT Server for connection state, incoming bitrate and preview or downstream output. A green connection alone is not enough; verify that media is arriving.

Can Callaba record the Blackmagic Web Presenter SRT stream?

Yes. After the SRT feed is received by Callaba, it can be routed to recording, restreaming, browser multiview, web player delivery, API workflows or another SRT destination.

Can this work with ATEM Mini Pro?

Yes, the same SRT routing idea can be used with ATEM Mini Pro models that expose compatible SRT streaming settings. Use the same rule: simple device-side values, then route inside Callaba.

What if the stream connects but there is no picture?

Start by switching to H.264, checking the input video standard, confirming that the device is ON AIR, and verifying that Callaba sees real incoming bitrate.

What latency should I use?

Start with 300 to 500 ms for typical internet paths. Raise latency if you see packet loss, jitter or unstable bitrate. Lower it only after the feed is stable.

Is the Blackmagic Key field case-sensitive?

Treat it as case-sensitive. If the Callaba route expects stream1, type exactly stream1. Do not change it to Stream1 or STREAM1.

Where do I enter the SRT passphrase in Blackmagic Web Presenter?

Use the Passphrase field in the SRT profile settings, usually near Server and Key. If encryption is disabled in Callaba, leave Passphrase empty on the Blackmagic side as well.

What SRT stats should I watch after Blackmagic goes ON AIR?

Start with incoming bitrate, RTT, packet loss and retransmissions. In good conditions RTT is often around 20–60 ms. If RTT is above 150 ms or packet loss rises above 1–2%, increase latency, reduce bitrate or improve the uplink.

Next steps

Last updated: May 21, 2026

Try Callaba Gateway with Blackmagic SRT

Create an SRT route in Callaba, send your Blackmagic Web Presenter feed to the route, and monitor the received stream before routing it to recording, restreaming, multiview, playback, or another SRT destination.

See SRT server setup Open multiview demo Try on AWS Marketplace