Hi,

Triggers are quite simple in concept, hence the small amount of information in the manual, but all the functionality is covered on that page believe it or not.

Two key steps form a trigger:

1. An event takes place for that input specifically.
(that input is transitioned in or out, or turned on or off in the 1-4 main overlays, or it is a video that has completed, or a countdown that has reached zero)

2. Any functions in the list that match the event are run one by one, top to bottom, with an optional delay between each item.

The only limitations are that the trigger will only occur if that input is used directly and not as part of a multiview of another input,
and that any tasks that could cause a loop, (such as transitioning from within a trigger) will not work, to prevent loops.

Example: This will run triggers: Transition Camera Input 1 to Output that has some triggers.
Example 2: This will not: Transition Virtual Set 2 to Output, that has the camera input 1 assigned as a layer/multiview, but has no triggers of its own.

Regards,

Martin
vMix

I think there may have been some confusion there, as there are no undocumented limitations of triggers that we are aware of.

You can transition to a camera (or any input) at the end of a video, simply setup an OnCompletion trigger
on the video and set it to Fade/Cut/etc to the camera of choice.
This is one of the examples in the Triggers tutorial video:


You can also turn off/on audio if you like, though do remember that vMix
also has automatic on/off/play/pause options you might need to turn off to prevent overriding behaviour.
This is found in the General tab in input settings and is also described in the documentation:

https://www.vmix.com/hel...nputSettingsGeneral.html


Regards,

Martin
vMix

for instance -- I wanted a video to play... have a trigger turn auto audio mix off.

then transition to a camera about 30 seconds into the video - - - so that the audio of the video would still be playing.

I was told this wasn't possible.

That the only way is via a countdown - that would have to be created separately

that timer would then have to be triggered on the video when it started.
the timer would then need a separate trigger that would switch to the camera at a certain time.

is this not correct?

That perhaps is the complicated way of doing things.

Instead, simply turn off audio auto mixing on the video input, and turn on the audio permanently, since you won't hear the audio
unless it is playing anyway. Might want to turn off auto pause so it doesn't pause when transitioning away.

Then no triggers should be needed, once the video starts playing the audio will remain until the video finishes, regardless of how much switching
is done in the middle.

I am not sure it is wise for most customers to delve into triggers, until they have become familiar with the other basics, such as how the audio mixer
works and how video playback is controlled by the General settings.

If you do want to automate at exactly the 30 second mark, have a look at the PlayList feature if you want
to build a rundown segment:

https://www.vmix.com/help21/Playlist.html

Or just setup a shortcut and press a button to do it when the time comes, gives more flexibility to jump back and forth between
the camera and video clip anyway.

What is more basic and simple than like Martin said " just setup a shortcut and press a button to do it when the time comes".
@ press button x then @ button Y and so on , following a "checklist"

The danger of making it "idiot proof for interns and new engineers." one can easely be the oneself being the *** by being stuck in the automation with no alternative to get out of.

I fully understand trying to automate things as we do it all the time due to lack of hands but ALWAYS it is based on individual elements that also can be controlled out of the automation cause there will always be a situation where one has to act out of the box manually especialy in fast pased situations.

Midi control boards or as we lately used a Stream Deck (with fancy easy understandable icons) helped tremendously even quickly adding/changing unforseen functions on the fly. Had to deal with 12 unfamiliar operators (12 productions simultaniously) each having to do the same procedures on their own and telling them to press a key or button at a certain time over and over was not an issue at all (pics say a thousand words :-) )

People are clever enough to understand KISS procedures. IMO the more one relies on an automation the less one pays attention too and for sure things go wrong then.