+1

I like to send a few shortcuts when vMix starts.
(for example start vMix with another input category then the 'all inputs'one)

Using a script is not an elegant method because sometimes vMix starts quickly and sometimes it take almost a minute.
So the script always has to wait a minute.

Ian H. on FB came up with a neat solution:
Have a browserinput set to a httprequest function to start a shortcut or a script

Something like http://127.0.0.1:8088/api/?Function=ScriptStart&Value=scriptname as link

Will perform the function each time a preset containing such input is loaded!

+1

Bump. Again.

x10 because the browser input script command workaround no longer works.

Two triggers are needed:
Preset load started (before inputs are added / configured by the load process)
Preset load complete (after load is complete and the software is "ready for work")

+1 again!

Yes, but it's a bit kludgey for some things as the preset change trigger seems to happen with varying delay. Had to build in a long delay to accommodate varying preset load times for post-load work. It would be far better for vMix to generate it's own internal triggers as the first / last step in any preset loading sequence. Obviously if someone wanted a script to run before preset load it would need to be a global script, and the preset loading code would need to wait for the script execution to complete (or exit).