media server logo
PricingAPI docsLaunch SRT for vMix
For teams already running vMix

Turn one vMix output into a stable live workflow.

Keep vMix as the live production surface your team already trusts. Use Callaba to add cleaner SRT ingest, browser playback for viewers, one-to-many distribution, live monitoring, and recording around the same output.

Built for broadcast teams first, with API and vMix Script available when you want automation.

Launch SRT for vMixGet self-hosted
See operator control + APISee the vMix SRT workflow
Signal invMix output in via SRT

Accept a cleaner contribution path before the network gets noisy.

Signal outBrowser playback + multi-destination out

Publish to viewers, social platforms, and archive paths without rewiring the source.

Operator trustLive RTT and bitrate monitoring

See delivery health while the stream is still recoverable.

“Easy to organize SRT broadcasts and monitor them live.”

Andy SmithVerified AWS customer
What your team getsBroadcast teams first

Callaba wraps a vMix output in a controlled transport and delivery layer.

The production switcher stays where it is. Callaba adds stable ingest, runtime visibility, and viewer-facing surfaces around the same live signal.

InputvMix program output

Keep the familiar production workflow, but move it into a cleaner contribution boundary.

ControlSRT ingest + monitoring

Watch RTT, bitrate, and stream state while the session is still recoverable.

OutputsBrowser playback, social delivery, and recording
YouTube
Twitch
Facebook
Instagram Live
TikTok
X Live
LinkedIn Live
Kick
Vimeo
Dailymotion
Bilibili
Douyin
Kuaishou
WeChat Channels
XiaoHongShu
Niconico
LINE VOOM
Trovo

Publish the same live output to viewers and downstream destinations without rebuilding the source path.

Dashboard for operatorsAPI and vMix Script when automation mattersCloud or self-hosted
Iurii Pakholkov, founder of Callaba

Written by Iurii Pakholkov

Founder of Callaba · LinkedIn · Published · Last updated

vMix is live video production and live streaming software for Windows. It works like a software video switcher: you add cameras, files, graphics, audio, remote guests, NDI sources, SRT streams and other inputs, then mix them into a live program output.

Callaba does not replace vMix. Callaba adds the cloud and transport layer around it: SRT ingest, routing, browser monitoring, recording, restreaming, playback and API control.

vMix production map Inputs are mixed in vMix, then outputs are sent to recording, SRT, RTMP, NDI or external displays. Inputs cameras vMix production Record Stream NDI SRT
vMix is the production surface: inputs go in, the operator builds the show, then outputs leave the system.

What is vMix?

vMix is a live production tool for Windows. It lets one production computer do many jobs that used to require separate hardware: video switching, audio mixing, titles, overlays, recording, streaming, replay, remote guests and external outputs.

The main idea is simple: vMix is where the live show is built. Operators use it to choose what goes on air, mix sound, add graphics, prepare the program output and send that output to another system or platform.

What vMix is used for

vMix is used when a team needs more control than a webcam or meeting tool can give. It is common in live events, sports production, church broadcasting, webinars, conferences, education streams, corporate broadcasts, remote interviews, online shows and small studios.

If the job is only a simple webcam stream, vMix may be more than you need. If the job includes many sources, graphics, overlays, recording, replay, remote contribution and managed outputs, vMix becomes useful.

How vMix works

A vMix workflow usually has three parts: inputs, production and outputs.

  • Inputs: cameras, capture cards, files, graphics, audio, NDI, SRT, remote guests, screen captures and stream inputs.
  • Production: switching, mixing, audio control, titles, overlays, picture-in-picture, replay and program output.
  • Outputs: recording, streaming, external display, NDI, SRT, RTMP or another workflow.

Where Callaba fits with vMix

vMix is strongest inside the production machine. Callaba is strongest around the production machine: contribution, cloud routing, browser monitoring, recording, restreaming, playback, failover and API control.

For example, vMix can send one SRT or RTMP program feed to Callaba. Callaba can then preview it, record it, send it to multiple destinations, expose it as browser playback or route it into another production workflow.

vMix and Callaba roles vMix builds the show while Callaba handles transport, monitoring, recording and routing around it. vMix show Callaba cloud layer Restream Record Callaba extends the workflow.
Callaba does not replace vMix. It adds transport, cloud routing, monitoring, recording and playback around the vMix production.

vMix SRT output to Callaba

Use this workflow when vMix is the local production system and Callaba is the cloud SRT server. vMix sends the program output over SRT. Callaba receives it and becomes the control point for monitoring, recording, restreaming, playback or API routing.

vMix SRT output to Callaba vMix can send the program output to a Callaba SRT server for routing and monitoring. vMix program SRT caller Callaba listenerUse matching latency, stream ID and passphrase when enabled.
A common workflow is vMix program output to a Callaba SRT server, then Callaba handles routing, recording or delivery.

Receive SRT from Callaba into vMix

Use this workflow when a remote source arrives in Callaba first and then needs to become a vMix input. In vMix, use Add Input → Stream / SRT and choose the SRT mode required by the receiver-side workflow.

Callaba SRT feed into vMix vMix can receive an SRT feed from Callaba as a production input. Callaba receiver SRT caller vMix inputUse Add Input → Stream / SRT for incoming feeds.
vMix can also receive remote feeds from Callaba as SRT inputs for production.

Use Caller when vMix connects to a reachable Callaba endpoint. Use Listener only when another system must connect directly to the vMix machine. For production, avoid making the vMix machine responsible for public network exposure unless that is your intended design.

vMix, NDI and cloud workflows

NDI is useful inside a local production network. vMix can work well with NDI sources and outputs when the network is designed for video. Across public internet or cloud contribution paths, SRT is usually the safer transport layer.

NDI and cloud boundary NDI is useful inside a production network, while SRT is usually better across the public internet. NDI local LAN Bridge encode SRT cloud pathKeep NDI local unless the network is designed for it.
NDI is strong on a local production network. For cloud contribution, bridge or encode the feed into SRT.

vMix RTMP output through Callaba

RTMP is useful when you need a simple publishing path. Instead of pushing many outputs directly from vMix, you can send one controlled RTMP output to Callaba and let Callaba handle downstream routing, monitoring and recording.

vMix RTMP output and restreaming vMix can send one RTMP output to Callaba, then Callaba can fan out to other destinations. vMix RTMP Callaba ingest YouTube Player One output is easier to monitor.
When using RTMP, send one controlled output to Callaba and let the server handle the downstream workflow.

vMix and Callaba settings table

Workflow vMix side Callaba side Check first
vMix to cloud SRT output SRT server Incoming bitrate in Callaba
Cloud to vMix Stream / SRT input Receiver-side endpoint Mode, port and Stream ID
Simple publish RTMP output RTMP server RTMP URL and stream key
Local production NDI input/output Bridge when needed Network capacity
Important event Main program + backup Failover and monitoring Switching rehearsal

What to monitor in a vMix workflow

Monitor the vMix machine and the transport layer separately. vMix can be healthy while the network output is failing. The server can be running while the input has no real media. Look at both sides.

vMix workflow monitoring points Monitor both vMix and the cloud transport layer during a live event. vMix CPU Audio Inputs Output Bitrate SRT RTT Recording Route
Monitor both layers: the vMix machine and the transport/server layer around it.

Main and backup paths for vMix events

For important events, plan the backup path before the show. A backup can be a second vMix output, a hardware encoder, a second internet path, or a clean standby feed. Callaba can help keep the switching and monitoring outside the local production machine.

Main backup workflow around vMix Use a cloud layer to separate production switching from main and backup transport decisions. Main vMix Backup feed Callaba failover Output live
For important events, plan main and backup paths before the live window.

vMix vs OBS

OBS is a strong free tool for streaming and recording. vMix is more production-focused. It is usually a better fit when the event needs more controlled switching, audio routing, replay, professional outputs, NDI, SRT and operator workflows.

The practical difference is not “which one can stream.” Both can stream. The difference is the level of production control needed for the job.

Troubleshooting vMix with SRT, RTMP or NDI

Problem Likely cause Fix
No SRT connection Mode, port, firewall or Stream ID mismatch Match Caller/Listener direction, hostname, port, Stream ID and passphrase on both sides.
Connected but black Codec or source issue Test H.264 video and AAC audio first, then add HEVC only after the path works.
NDI source unstable Local network not sized for video Keep NDI on a controlled LAN and bridge to SRT for remote or cloud transport.
RTMP output fails Wrong URL, stream key or TCP port Re-copy the RTMP URL and stream key, then check incoming bitrate in Callaba.
High delay Buffering, SRT latency or player delay Measure each layer separately: vMix output, server receive, output route and viewer/player path.

Official references

FAQ

What is vMix?

vMix is live production and live streaming software for Windows. It lets you mix cameras, files, audio, graphics, remote guests, NDI, SRT and other sources into a live program output.

What is vMix used for?

vMix is used for live events, sports, churches, webinars, conferences, remote interviews, education streams, corporate broadcasts, studios, recording and multi-camera live production.

Does vMix support SRT?

Yes. vMix supports SRT input and output workflows, including Caller, Listener and Rendezvous modes. Use matching mode, latency, passphrase and Stream ID with the other side.

Does vMix support NDI?

Yes. vMix supports NDI workflows. NDI is usually best inside a local production network. For cloud or internet contribution, use a bridge or encode the feed to SRT.

Is vMix better than OBS?

vMix is usually a better fit for advanced production control, replay, multi-camera operation, external outputs, NDI and SRT workflows. OBS is a strong fit for simpler streaming and recording setups.

Can vMix send one output to several platforms?

Yes, but for important workflows it is often cleaner to send one controlled output from vMix to a server such as Callaba, then handle restreaming and routing from the server layer.

Can Callaba replace vMix?

No. Callaba is not a production switcher replacement. vMix builds and switches the show. Callaba adds the cloud, ingest, routing, monitoring, recording, playback and API layer around the show.

Can vMix receive streams from Callaba?

Yes. vMix can receive SRT and supported stream inputs. A common workflow is remote source to Callaba, then Callaba receiver-side feed into vMix as an input.

Next steps

Use Callaba with vMix live production

Send vMix output to Callaba over SRT or RTMP, confirm incoming bitrate, then add recording, restreaming, browser multiview, playback, failover, or API-controlled routing.