This is a personal effort as I've found it challenging to coordinate non-technical guests joining vMix Calls, but developed it so anyone can use it. Throwing it out here in case it's useful for anyone else.

Problems:

- It's been a lot of trouble/effort to establish a vMix Call for each remote guest, keep track of their vmix.at URL, and text it to each guest individually
- When calls / inputs change, it's difficult to get the remote guest to switch to a new call code, and they start to feel that it's too complicated or get frustrated

So I put together an experience that seeks to make this better:

- Creates 1 link that can be shared with all guests at once
- Assigns guests to the next available vMix Call input
- Holds guests in a "waiting" state if vMix is not running yet or if there are not enough available inputs
- Asks only for their name and doesn't confuse them with a password/call code

This is accomplished by running a "vMix Remote Agent" app that talks to vMix via the local API, and keeps the cloud side updated with the current inputs available in vMix.

Available here: https://vmix.brandonpotter.com

Hey, just installed your software and I am getting "Error: Error communicating with vMix (may not be started". vMix is started. Any tips for troubleshooting? Looks like it could be super cool, thanks for sharing!

-Aaron

API is enabled on port 8088. I can access it via a browser.

Yep, no issues getting to that address, or localhost.

System.InvalidOperationException There is an error in XML document (1, 1246).

Using vMix 23.0.0.50. No proxies. When I access in browser the response starts with the version #, then show name, then shortcuts<--I lied, inputs, not shortcuts.

Ah! I'm on 49, you might be right - maybe there's an API change in 50. Will try 50 later and see what happens...

Same problem on .50 unfortunately.

I haven't specifically checked, but there were some vmix call changes made in the most recent versions. For instance, the peer-to-peer only option.

Not sure if that's exposing itself via API. If so, .50 may be presenting some new data via API that your app is unprepared for?

Anyhow, very curious to check this out once you get it resolved.

Thanks!

.50 should be fixed now (requires re-downloading the remote agent)

Some types in the XML weren't mapped correctly that I guess .50 started using.

Just tried it and i'm impressed!

The only thing that i see as a problem is the timeout of a ended call. But probably that's a internal vmix problem.

Really nice job! Also wiling to see a package for deploying your own customized instance!