ActiveInput

Ah! That solved it. Thanks!

However, there are a few important things to note:

1) The duration listed in the image is meaningless for this function. Which is why the trigger below image works. vMix doesn't use the duration for all functions which is why one can't edit that field in this function. Ideally, vMix should not display the duration on functions not using it to be more clear on this.

2) The delay does need to be longer than any transition in by other means. In this case, the shortcut I use does a 400 ms fade transition. Thus, the 405 ms delay.

3) There is still a bug in the vMix code as an insufficient delay on this function should just not do anything, rather than get confused an put the input in the Output Window (as the request is to change the Preview Window). Likely not handling an overflow condition as a result of the insufficient delay. Of course, there is no fundamental reason the Preview Window couldn't change before the Output Window completed a fade transition, but this specific case would probably require a good deal of additional programming if I am guessing correctly on how the loop of code is being implemented for these trigger functions.

Trigger 3.png (6kb) downloaded 0 time(s).