Appearance
Triggers and events
A trigger is a moment the operator causes: take it in, take it out, next page. An event is a moment the graphic announces: took in, finished, goal. Triggers go into the graphic; events come out of it.
Triggers
A trigger is a property of type Trigger in the Data panel (T). It has no value. It fires, and a Animation States transition waiting for it moves on.
In the editor, Fire fires it in Animate mode, while the Animation States play. On air, the operator's controller fires it by name.
Taking a graphic in and out
The usual pair. The controller has no fixed names; it goes by the word out:
| Trigger | What the Animation States do | On the controller |
|---|---|---|
takeIn | Idle → In: the graphic animates on, then holds | Fires it, and marks the graphic on air |
takeOut | Hold → Out: it animates off | Fires it, and marks the graphic off air |
Every trigger of the graphic appears on its rundown card as a button with the trigger's name. Pressing any of them puts the graphic on air. A trigger whose name contains out — takeOut, out, animateOut — also takes it off air.
Keep "out" for the way out
The controller reads out anywhere in a trigger's name, in any case. A trigger called layout, timeout or shoutOut would take the graphic off air on the controller while the graphic itself carries on. Name those arrange, timer or highlight.
To build the Animation States, see Animate with Animation States.
A graphic with pages
For a graphic that steps through pages — a results table, one row after another — add a trigger named next to the view model, and have each transition from one page to the next wait for it. The playout server's Next command fires it.
Next looks for a view-model trigger next first, then for a trigger input next on the Animation States, so graphics built either way work.
Firing from data
A control system can fire a trigger with a value of true, along with other values in the same message: new names first, then the take. See Sending values from airZ Engine.
Waiting for the take
airZ Engine can load a graphic ready, showing nothing, and bring it on the moment its trigger fires. Design for it:
- The first state after Entry shows nothing: everything off-screen or transparent at the first frame of In, or an empty Idle state.
- A graphic made from a new document already starts this way: Entry leads to Timeline 1, which plays from its first frame when the graphic is played, and a graphic loaded ready shows nothing until it is taken.
- The take trigger's name is exactly the one the operator's rundown fires. A trigger name that matches nothing reveals nothing, so a typing mistake leaves the channel empty rather than showing a half-built graphic.
Events
An event is a named moment the graphic reports, with values if you give it some: tookIn, goal with the scorer's name. It is reported from a timeline key, when a state is entered, or by a listener.

Inside the graphic, a listener set to Listen to: Event reacts to it. This is how a component tells the artboard around it that something happened.
Outside the graphic, events are listed in the bindings.json written with the export, with their properties, for players that act on them. airZ Engine plays the graphic and does not send its events on to the controller. For a moment the operator must see — "the clock has stopped" — show it in the graphic itself. The three air state events are the exception: airZ Controller reads them from its own copy of the graphic.
Telling airZ Controller it is on air
A rundown row in airZ Controller shows ON AIR from the moment the operator takes the graphic. With air state events, the graphic tells it more: when it really starts to show, when it is leaving, and when nothing shows any more.
| Air state | Key it at | The rundown row shows |
|---|---|---|
| On air | the start of the in animation, as the graphic starts to show | ON AIR |
| Going off | the start of the out animation | OUT… |
| Off air | the end of the out animation, when nothing shows any more | OFF AIR · LOADED: nothing is visible, and the graphic stays loaded, so taking it again is instant |
Use all three, or none. A graphic with none shows ON AIR from the take until it is taken out or cleared. With them, the row follows the events. Either way, pressing one of the graphic's triggers, whatever its name, does not change the row by itself: a trigger called "out" may hide just one part of the graphic. The bundled News lower third and Football lower third templates come with all three already keyed.
To key one, open the animation in Animate mode: the in animation for On air, the out animation for Going off and Off air. Then open Air state in the timeline's toolbar, after Key. Move the playhead to where it should fire first: the menu's heading says where it will go, Add at frame N · <animation>. Then pick On air, Going off or Off air.
A tick marks one already keyed at that frame. While the graphic has some of them but not all, the menu says which it still needs. Each one is a single undo step.

The events are called airz_on_air, airz_going_off and airz_off_air. airZ Controller matches these exact names, so the editor keeps them fixed: the list shows them as On air · airz_on_air and so on, and they cannot be renamed there. Their inspector shows an Air state row saying what each does, in place of Type.

On air, airZ Controller follows the graphic in its Program Monitor: while the item is on air it plays its own copy there, given the same takes and triggers as airZ Engine, and when that copy reaches On air, Going off or Off air, the rundown row changes. A new take starts the row from ON AIR again.