vMix supports the triggers TransitionIn/TransitionsOut which allow you to perform actions when the input is coming into the Output or going from the Output. Unfortunately, it is missing triggers for the same type of actions which should be performed when the input is coming into Preview or is going out from Preview. Triggers for the latter are important because most prepare actions shoud be done BEFORE something is brought into Output.
Workaround: Use a VB.Net script which observes the API XML element /vmix/preview for changes and performs the actions. Unfortuntely, this way the actions are not really tight to the particular inputs but are kept separate.
Recommendation: The PreviewTransitionIn/PreviewTransitionOut triggers should be added to vMix inputs.
Vendor Response: "Essentially, automation features are only meant to execute on the Program Output so as not to overcomplicate things, as such, the Triggers Manager was added in vMix 25 to help with overseeing what Triggers have been applied and where."
vMix supports the triggers
TransitionIn/TransitionsOutwhich allow you to perform actions when the input is coming into the Output or going from the Output. Unfortunately, it is missing triggers for the same type of actions which should be performed when the input is coming into Preview or is going out from Preview. Triggers for the latter are important because most prepare actions shoud be done BEFORE something is brought into Output.Workaround: Use a VB.Net script which observes the API XML element
/vmix/previewfor changes and performs the actions. Unfortuntely, this way the actions are not really tight to the particular inputs but are kept separate.Recommendation: The
PreviewTransitionIn/PreviewTransitionOuttriggers should be added to vMix inputs.Vendor Response: "Essentially, automation features are only meant to execute on the Program Output so as not to overcomplicate things, as such, the Triggers Manager was added in vMix 25 to help with overseeing what Triggers have been applied and where."