Today I stumbled upon one thing that for some strange reason I never noticed before.
The Input specified for a Trigger action is assigned to a specific Input number. So, if the Inputs are moved to another position, it is very likely that the wrong Input is used in the Trigger. Very bad, at least for me.

Therefore I request an option "Assign Trigger to Input Number", default enabled for backwards compatibility. Sort of the same option as already available for Shortcuts. (Although not for Input source to Fullscreen and External Outputs, but that's another old and neglected Feature request).

How would I do that? There is only a drop-down selection in the choice of Input when one is adding a Trigger.

That's why I suggested the option to use the input GUID rather than the input number.
I mean you would still select inputs by their names, but you could choose whether this particular trigger is effective for an input number (thus any input that has this position in the UI) OR a specific input no matter where it is in the input area...

We had the same problem when UTC was first released (only input number so as soon as you added an input in vMix, UTC was lost). I convinced Elgarf to use GUIDs instead so that we can move inputs as we want in vMix without breaking UTC's presets.

Here we would need a checkbox option to tick. For triggers, I think GUID should be the default behaviour but when ticking the checkbox we could define triggers on input numbers too.

Guillaume

PS : AFAIK, the input number = the input position