An input that uses any transport protocal you feel is best and an output so that the mix from a computer running vmix can be sent to another computer running vmix with the need for external software.

There are many uses for this.

For me I have two specfic reasons.

Scenario 1:

Vmix running a live channel 24/7 (it can be done, I've been doing it for three+ years now)
Computer A has Vmix running transmitting rtmp using stream 1 to Unreal media server on a remote server.
Input 1 is the channel logo
Input 2 is a now playing title
Input 3 is a next to play title
Input 4 is a few days of video list
Input 5 could be from another vmix running at remote plocation, like a live 1 hour show or something like that.

In this scenario we would also need the API to tell us that the vmix remote input is active so we can make a trigger automatically switch to it, or maybe an intro video input and then it or something along those lines. Powershell can be scripted to do those things fairly easily.


Scenario 2:

At a live video mix, you have 16 High Def cams, You could use 4 copies of vmix on 4 seperate computers to mix four cameras of different angles of similar stage or event locations and a fifth computer running vmix to mix the output from the other four. each having a live operator. Then that feed from the fifth computer could be sent to a 24/7 vmix computer (see above).

It acutually would make vmix less hardware dependant as workload could be spread out amoung multiple computers and operators and give alot more use to this awesome software package with zero extra cost, except for multiple licenses from people already using the software like me!

It can't be that difficult just basically add a stream and compatible input selection.. eh?

vMix call can be used to transmit over the public internet to another vMix. If set to 1080p, higher bitrate, it looks very good.

If on the same network, use NDI to get the signal in.