Hey, I'd love to use some more very specific and niche activators. But instead of requesting every single activator that someone, somewhere, might need sometimes, I'd prefer a more general, open and flexible activator.

I'd suggest an activator based on xpaths of the already existing API.XML, so activators are only limited by the information provides by the XML.
Adding more activators would be done by appending additional information to the XML. This would also extend the capabilities of scripting and API-access at the same time. So all parties would benefit.
I just made 4 quick examples of what I think would be a good implementation.


xpath_activator_example1.png (8kb) downloaded 3 time(s).
In this case the activator would be active, if Input1 is in loop-mode.


xpath_activator_example2.png (13kb) downloaded 3 time(s).
Here its activated, if a specific file is selected in a list with the name "MyList".


xpath_activator_example3.png (11kb) downloaded 3 time(s).
An activator for a particular vMix-Preset being loaded.


xpath_activator_example4.png (12kb) downloaded 2 time(s).
And finally an activator for an input being on MultiViewOverlay1 of the input named "MyMultiview".


As you can see, such an activator would open up so many doors.
Not for everyone, I get it - handling an activator like this is far from being "easy to use".
But for all the scripting enthusiasts this would be totally doable and even for a non scripter easy to learn in a short time.

+1