Suggestion: control 2 vmixes at the same time

[fmjsky]

As usual，we only need to control 1 vmix.
In some situation，a redundancy vimx is inneed.

New feature:
We can now control 2 vmixes simultaneously with one button (redundancy)

[elgarf]

MultiState widget should do that, but I don't test it a lot.

[fmjsky]

MultiState widget should do that, but I don't test it a lot.
It seems that the vmix information cannot be obtained through the Multistate Widget.

[elgarf]

You should connect to the main state, then all commands to main state duplicates to secondary state, information from secondary state never read.

[fmjsky]

You should connect to the main state, then all commands to main state duplicates to secondary state, information from secondary state never read.

192.168.200.173 is the primary vmix
192.168.200.111 is the secondary vmix
clicking the button，only primary vmix can be controlled.

[elgarf]

You should use same preset on each PC. Most commands refer to input GUID, so if you made inputs A and B on one machine, then A nad B on another machine, then its not the same inputs, and vMix doesn't switch them.

[fmjsky]

You should use same preset on each PC. Most commands refer to input GUID, so if you made inputs A and B on one machine, then A nad B on another machine, then its not the same inputs, and vMix doesn't switch them.

If I use the same preset with MultiState, I can indeed synchronize control of two Vmixes, such as Cut and OverlaysIN. However, I've also encountered a situation where the UTC timer isn't sending time data to both Vmixes simultaneously, as shown in the image below.
I think the best way to control multiple Vmixes simultaneously is to read the data from each one, but of course this can be a significant programming effort.
Thanks for your help.

primary(192.168.200.111)
secondary（192.168.200.173）

[elgarf]

That's because of text widgets nature, I think. I'll look at it later.

[elgarf]

I looked, and all was ok 🤔

[fmjsky]

I looked, and all was ok 🤔

I ran a second test, and it worked fine.
Strangely, the timer data wasn't transmitted to the second Vmix during the first test.
Perhaps it was a network issue.
Thanks again for your help.