Core concepts
The vocabulary you'll see throughout the rest of the docs — Outputs, Looks, Scenes, Playlists, Devices, and Actions.
Six concepts that form the rest of Lightpath. Skim them to build a mental model, or jump straight to the API reference if you already know the territory.
Outputs
The surfaces you control.
An Output is an independently controlled feature in your installation — a facade, a projection-mapped surface, an LED sculpture. Each output receives its own content and can be addressed individually or as part of a scene. Outputs are the foundation of your project: everything else exists to put visuals on them.
Each output is an independently controlled feature — a facade, a projection-mapped surface, an LED sculpture. Content is assigned per-output.
Looks
The core content type.
A Look is the fundamental unit of visual content. It combines three ingredients: a Source (the animated visual — a generative pattern, a video file, a camera feed), a Color Palette (the colors applied to the source), and Effects (transformations like blur, mirror, or speed). A single Look is applied to a single output.
A Look combines a visual source, color palette, and effects into a single piece of content for one output.
Scenes
The state of your project.
A Scene captures the entire state of your project — it assigns content to every output. Each output can have a Look or its own Playlist. When you activate a scene, all outputs change together. Think of it like a lighting cue: one button sets the mood across your whole installation.
A Scene assigns content to every output — each output can have a Look or its own Playlist. It defines the entire state of your project at a given moment.
Playlists
Content over time.
A Playlist sequences Scenes (or Looks for a single output) over time. Items can advance on a timer, be triggered manually, or follow a schedule. Playlists enable hands-free operation — set it up and your installation runs itself.
A Playlist sequences Scenes or Looks over time — step through them manually, or let them advance on a schedule.
Devices
Connected hardware and software.
Devices connect Lightpath to everything else in your install — projectors, smart relays, LED controllers, media servers, building automation systems, and any device or software reachable over HTTP, OSC, or other protocols. Monitor status, send commands, and include device control in your automation workflows.
Devices let Lightpath communicate with external hardware and software in your install — using their native protocols.
Actions
Automated behaviors.
An Action is a reusable sequence of steps that controls your install — toggling devices, adjusting TouchDesigner parameters, or changing output settings. Once created, an action can be triggered manually from the UI, scheduled on the calendar, or fired automatically when specific content becomes active.
An Action is a reusable sequence of steps — control devices, adjust TD parameters, or change output settings. Run it manually, from the calendar, or automatically when content activates.
Ready to control Lightpath from outside the app? Head to the HTTP API, OSC API, or TouchDesigner Python API reference.