# Playback & Triggering: On the output

> How a play reaches /view.

Glider documentation · Animation · Web page: https://cgglider.com/docs/playback/output/

Sections of this page: [In the editor](https://cgglider.com/docs/playback.md) · [The five ways to start one](https://cgglider.com/docs/playback/triggering.md) · [On the output](https://cgglider.com/docs/playback/output.md)

Plays travel as signals on the page's animation queue, each stamped with a time. The output consumes them, de-duplicating by stamp, and plays the same plan the canvas plays: the clip and everything chained to it, started together on one clock. The canvas, the monitors, the Output tab, /view and every output draw the graphic with the same render engine and the same scene tree.

- The Output tab and the rundown's PGM monitor use the same mechanism against their preview trees. PVW plays nothing: it shows the next take at rest.
- A stamp already handled is ignored, so an output that reconnects and receives recent state does not replay an old take.
- Elements that are not mounted yet get the six-attempt retry, which covers a scene taken in the same instant as its animation.

> **An output that reloads loses in-flight motion:** State is restored, but a clip that was mid-flight is not resumed. Re-take the element rather than waiting for it to settle.