vMix VirtualSets are based on 1-5 input elements and 1-4 pre-defined zooms. The input elements can be configured under the input "Setup" tab and there under "Layer". Internally, they are actually mapped onto the standard layers 1-4 of the available 1-10 standard layers, which can be seen when opening the input "Settings" / "Layers". Each of the 1-4 VirtualSet input elements can be assigned/unassigned via "Setup" / "Input" set to an input or "None" and enabled/disabled through the toggle "Setup" / "Visible". Each of the 1-10 standard layers can be assigned/unassigned via "Settings" / "Layers" / Column-3 (Name) set to an input or "None" and enabled/disabled through "Settings" / "Layers" / Column-2 (Enable Toggle).

Unfortunately, the two mechanisms are not 100% in sync. Unselecting "Setup" / "Visible" does not toggle "Settings" / "Layers" / Column-2 (Enable Toggle), but sets "Settings" / "Layers" / Column-3 (Name) to "None" instead. Manually setting "Settings" / "Layers" / Column-3 (Name) to "None" on the other hand keeps "Setup" / "Visible" enabled and instead sets "Setup" / "Input" to "None". It becomes even worse when you disable a layer with "Settings" / "Layers" / Column-2 (Enable Toggle) it is visually gone although the "Setup" / "Visible" still shows it is "Visible".

This weak data-binding is rather confusing and the user has to remember that for VirtualSets one usually never should touch "Settings" / "Layers" at all, as a VirtualSet has its own idea of layer state and implicitly maps onto "Settings" / "Layers".

My request is to either disable "Settings" / "Layers" on VirtualSets at all or realize a true bi-directional data-binding to longer confuse the user. I really stumbled over this now the Nth time and wondered why the layers do not work as expected.