Before there’s a single line of animation code, a large-scale LED installation needs software that knows where every single light physically is. Chromatik is the tool a surprising amount of the field’s biggest work runs on — including Mark C. Slee’s own 60-foot, 68,000-LED Sonic Sphere at The Shed in New York (2023) and his 25,000-node Apotheneum, a 40-foot cube and 30-foot cylinder built with Anthony Fieldman for Burning Man’s Black Rock City (2025). Slee is also Chromatik’s lead developer — the software grew directly out of the installations it was built to run.
From LX Studio to Chromatik
Chromatik is the current, actively developed successor to LX Studio, the Processing-based tool that preceded it; LX Studio’s own project page describes itself as superseded, with Chromatik carrying the same underlying LX libraries forward under “a new, modern UI layer.” The practical difference for a newcomer: Chromatik runs as its own cross-platform application (macOS, Windows, and headless Linux setups for permanent installs) rather than inside the Processing IDE, and its implementation is mostly Java on a current Temurin 21 runtime rather than the older Processing stack.
Step one: define your model, not your animation
The first thing Chromatik asks for isn’t a pattern — it’s a model: the number, placement, and 3D orientation of every physical fixture in the installation, defined before any animation gets written. Chromatik uses a left-handed coordinate system with +Y pointing up, and that model becomes the coordinate space every subsequent animation pattern reads from. This ordering matters more than it would in screen-based creative coding: a pattern that looks right in the abstract can look completely wrong once it’s mapped onto real fixture positions that aren’t a flat grid, which is exactly the problem a model definition exists to solve up front.
Working directory and live reload
Chromatik keeps a ~/Chromatik/ working folder on disk, with content packages living in its Packages subfolder. Those packages can be reloaded without restarting the application, and Chromatik can watch that folder for changes and reload automatically — a workflow built for exactly the situation an installation artist is actually in: standing in front of the physical piece, tweaking a pattern, and wanting to see the change land in seconds, not after a restart cycle.
Pick your on-ramp
Chromatik’s own developer documentation lays out a deliberate learning sequence: try the JavaScript API first to get a feel for the environment, then read through “Coding in LX” to understand the underlying framework, and only then move on to building a full custom device. The built-in pattern library — chase, chevron, wave, swarm, and more, each with its own tunable parameters like speed, chunk size, and tempo sync — is the fastest way to get an installation animated before writing a single custom line, and most permanent large-scale pieces lean heavily on combining and layering those stock devices rather than hand-coding everything from zero. Each output in a Chromatik project is addressed by a KiNET port and a starting channel offset, with DMX channels numbered 0–511, so the underlying lighting-control concepts carry over directly from the DMX and Art-Net work this site has already covered — Chromatik is the layer that sits above that protocol work, turning raw channel addresses into a patchable, model-aware instrument.