Automation rules
A rule belongs to a source, and says: when something happens to it, after an optional wait, do one or more things. It runs the same 34 actions a hotkey or a Stream Deck button can, so anything you can press, a rule can trigger for you.
Add one
On a source’s Automations, press Add Rule. Choose When it fires — a source reaching or leaving Program, its overlay going on or off air, an item, a playlist or a carousel finishing, or a replay finishing playing — and, if you want, a Wait in seconds before it acts.
What it can do
Then the first action runs, and And adds more after it: switching, putting something in Preview or as an overlay, playback (play, pause, restart, go to an item), replay (play a bucket or a clip, capture one, move the selection), muting or setting gain, moving through a data source’s rows, or starting and stopping an output.
Loops are refused, not run
A rule cannot trigger itself, however many other rules sit in between: InterDirector tracks the whole chain an action came from, not just what triggered it directly, so a cycle nobody meant to build simply cannot fire. Its own row explains why, in one of three ways:
- “This rule was reached by something it started, so it did not run again.” — a genuine loop.
- “Too many rules ran one after another, so this one did not run.” — more than four rules deep in one chain.
- “Its wait finished after the thing it was about had already ended.” — a delayed action whose moment has passed, such as one tied to an overlay that came back down before the wait was over.
Next
The auto director, for switching between cameras on a timer instead of on an event.