Skip to content

Run and watch

Play, pause and stop a project in Tato Studio, watch any node's output in the Node visualizer, follow every edit in History, and see why something failed.

A project plays as a whole: every stream in it starts, pauses and stops together.

Play (F5) Starts the project. A closed project is opened first, a paused one resumes, and a stream that failed is loaded again and retried.
Pause Holds every stream where it is, its nodes keeping their state, until you play again. Edits you make meanwhile are kept, and take effect when it resumes.
Stop (Shift-F5) Ends playback. The graph stays open to read and edit, and the next Play starts every stream fresh.

They’re in the Run menu, and on the Play button at the top of the window, whose arrow holds the others. The graph is there to edit whatever the project is doing: building a stream while it plays is the usual way to work.

Select a node in the graph and the Node visualizer shows what it outputs, live, as it runs:

  • Pictures are shown straight from the GPU, with no copy and no encoding.
  • Audio shows each channel’s waveform and level.
  • Encoded media shows its bitrate, the time between keyframes, and the last five seconds of units by size, keyframes marked.
  • Records show their fields, and tensors and arrays their attributes.

When nothing is arriving, it says why: the project is stopped or paused, the node has failed, or nothing has reached that output yet. Expand to fill the window gives it the whole window; Esc puts the layout back.

The History view lists every edit to the project as it lands, newest first, with who made it: You for edits in Studio, an agent by its name, and Runtime for the runtime’s own. Adding a node, connecting two pins, setting a value, importing an asset, adding a module and saving a file are each one edit.

  • Edit › Undo (⌘Z) and Redo (⇧⌘Z) take back and reapply your own edits, never anyone else’s.
  • In History, choose Undo back to this edit on any row of yours to take back everything since, or Redo up to this edit to bring it back.

The history lives in the project’s .tatolab/ folder, so it survives restarts, and works the same from the command line and for agents: each one undoes only its own. With Developer turned on in Settings, the Transactions view lists every change exactly as the runtime recorded it, with its author, its operations and its result.

  • A stream that fails to start shows why, in the runtime’s words, in place of its graph. Fix what it names and press Play. With notifications on in Settings, Studio tells you when a stream fails, even while it’s in the background.
  • A node that fails, or whose code keeps raising, says so on its card and in Properties. The runtime starts a crashed node again on its own; one that keeps crashing is left stopped, with the reason. Fix it, save, and it runs again.
  • A node that isn’t ready, such as one with a setting left empty, says what it needs. Everything else keeps running.
  • A wire that can’t carry data shows as an error, naming both ends.

The project’s log, under the Code view, has the rest. Troubleshooting covers the common problems.

The status bar at the bottom of the window shows the runtime Studio is connected to. Studio starts the runtime when it opens and stops it when it quits, or uses one that’s already running on the machine, such as a service. Settings › Runtime shows its version, how long it’s been up and where it writes its log.