AFAIK there is no way within vMix to set something like this. However vMix relies on your host routing table where you can set which route/gateway to use per destination.

Alternatively you can use NDI to another encoder (like OBS) or Fullscreen HDMI OUT to a hardware encoder.

It can be done. At least I’ve done it with one system that runs vmix.
But I will not say that it is easy..
you need to have knowledge of routing tables on computers and persistent routes.
Also the destination service need to be in a fixed IP space.

???
Funny statement... If you want to deal with routing and networking, I think you should go back to the basics of how the internet works...


I'm sorry but no, this is very simple if you understand what we're talking about.

The way you're thinking this backup/failover situation is not the way to go. It's not vMix's job or a computer's job to manage routing !
If you want an easiest solution just use the equipment that is designed to do it : a multi wan router !

don't assume if you want to be taken seriously

try to play with "nslookup" or "dig" commands and when you find a domain or host name which does not resolve to an ip address on the internet we can carry on talking.



a good combination of cache and timeout on failover will do the job

You're quite right - the streaming address is normally a domain name, and it would be very bad practice to replace this with an IP address in general, since the streaming provider probably uses multiple servers around the world and frequently changes the IP address - there is no guarantee that any particular address will always be available. Unfortunately easily managed URL based routing is generally only available in high-end firewalls, so you're not going to be able to do this on your PC running vMix. If you want to risk using IP addresses, you can do this by having the two independent routers for main and backup connections connected to the same switch as the vMix PC (just remember to turn off DHCP on one of them!)

Unfortunately this will not work for Facebook - the main and backup streams both go to rtmps://live-api-s.facebook.com:443/rtmp/ - the "backup" here is not achieved by having two routes on one computer - it's achieved by having two separate machines both sending out the same stream (i.e. you're providing a backup in case your streaming machine fails - not in case your internet connection fails).

You could potentially provide a solution by having a second computer running OBS (or if you want, the single input license for vMix), which is on a separate logical network, using a separate router and internet connection. The easy but expensive way of connecting them is using SDI (you now need to buy a capture card for the second computer). The cheap (free!) method is to put two addresses on the computers and use NDI to transfer the programme output between the two computers. (so for example, the main PC is 192.168.1.2 and has gateway 192.168.1.1. It also has a secondary address 192.168.2.100. The other PC has 192.168.2.2 as it's address and gateway 192.168.2.1, and has a secondary address 192.168.1.100. For computer 2, the source of NDI is 192.168.2.100).

If you really wanted to do it in one machine, you could run OBS on a Virtual PC, which has a different gateway from the host machine, but I wouldn't recommend that for a whole host of reasons! :)

For YouTube the URLs are rtmp://a.rtmp.youtube.com/live2 and rtmp://b.rtmp.youtube.com/live2?backup=1 and since the a and b URLs resolve to different addresses, you could do it all in one machine using static routes, but for the reasons given above, I wouldn't try it.

If you want to give it a try though, let's say you have your two internet routers, one on 192.168.1.0 and the other on 192.168.2.0, both using the .1 as their gateway address.
If your computer primary address is manually set to 192.168.1.2 with gateway 192.168.1.1, and the secondary to 192.168.2.2 (there should NOT be a gateway address for the second LAN in WIndows, even if you have two network cards).

Then at an elevated command prompt you do -
ROUTE ADD 173.194.190.137 MASK 255.255.255.255 192.168.2.1 -P
where 173.194.190.137 is the address of the backup streaming server. The -P means "persistent" and keeps the route in place across restarts. If you're just experimenting, leave it off!

If I understand correct you want to do
Stream1 - Nic1 - WAN1 - Primary
Stream2 - Nic2 - WAN2 - Backup

For this scenario you would need to create routes. Either in windows or in the router. This depends a bit on how you wire everything.

start with a command prompt and view the windows routes first
cmd route print
You will see the different routes that your computer has. If there are two routes for 0.0.0.0 for example then the lowest metric takes precedence
Usually for one stream you have to do nothing as it would use the default.
For the second you have to resolve the backup server IP and add a new route to the NIC2 gateway. Then traffic to x.x.x.x (backup server ip) takes NIC2 gateway and thus a different route.
Done, hope that the streaming server seamlessly switches. Once switched it might be problematic to switch a second time but you will find out while testing.


If you need help I can assist with a teamviewer session. We should be similar timezones.

Just to get things right. The complete internet is based on IP's. DNS ist purely made for humans to better remember and read. No matter what webside you open it's using IP addresses and not names.

OK, anyway. In your case it seems too complicated to get all this running for non IT guys. And it is problematic with dynamic IP address targets, absolutely true.

The only way in this case I see is to harden your internet connection with a bonding device. From Peplink over Teradek, Mushroom .... You coud even do it in software. Speedify as an example.