Point Visuals and Nodes at the openflowfm/visuals wiki, where they live now
Add a page for mixing stems
mix[flow] had no page at all. This is the mixer: which lanes you get and why a
four-source model has no empty ones, what mute, solo and the faders do, the
zoom gestures and how far they go, and the one-time engine install the first
separation does.
Co-authored-by: Codex <noreply@openai.com>
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01DwCZhhdrJEPTXfXEgmHunc
Call the product open[flow], and the env vars OPENFLOW_
The suite was renamed; the manual follows. References to the legacy
bsv.json sidecar file stay, because that really was its name and the
import path from it still exists.
Co-authored-by: Codex <noreply@openai.com>
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01P5mLf7B2kE7jYXiNgihDWQ
Add the visuals page, and put it in the manual
The rig has had no user-facing page at all. This is the one a person reads before
touching it: looks are the unit, a stack of them is a composition, and the order
of work is **design first, bind after** — build a library with nothing playing,
then point the set at it.
Says out loud that it does not need Ableton running, because that is the thing
most likely to be assumed and it is the reason the designer exists.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01XgWVKDg9bAtZhhDoQjtqE4
Push: names read the way you typed them
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01XgWVKDg9bAtZhhDoQjtqE4
Update the set configuration manual
Co-authored-by: Codex <noreply@openai.com>
Document naming the artist
The optional artist behind " - ", why the spaces and the first separator
matter, and that it names the song rather than identifying it.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01NuDUtsHz4MdrtrvrjaawW4
Document meter controls and device connection status
Song tags, the sort hierarchy, and following Live
Brings the manual up to the 2026-08-07 work. Three of these were not
additions but corrections — the pages described behaviour the app no
longer has.
The convention lost its BPM. A scene name is `[ROLE] @{key} {SONG}
{TAG}`; the tempo lives on Scene.tempo, which is the one fact Live
already has a home for, and duplicating it into the name meant two
answers that could disagree. Naming is rewritten around that, with the
three readable legacy forms in a table so a half-converted set is
recognisable rather than mysterious.
Song tags are new and get a section rather than a page: an open,
optional, brace-delimited classification of what the song is. The braces
are the point — they make an arbitrary tag reversible without a fixed
vocabulary, which is what keeps the mapping derivable from the name
alone. Roles gets the tag-versus-role distinction, since one describes a
scene and the other a song, and they are deliberately different marks.
Roles and the chosen palette moved out of bsv.json and localStorage into
a hidden device parameter, so Live writes them into the .als. That is a
better story than the one it replaces and Installing, Roles and Color
each told the old one. Home gains a section saying it plainly: there is
no database, and the set is the storage.
The palette is now compiled in. Color and Troubleshooting documented a
Re-derive button that no longer exists — worse than incomplete, since
someone would have gone looking for it.
Following Live is documented with its failure mode stated out loud. It
watches the Session cursor and it is the least verified path in the app,
so "a clip drawn in two places means this got it wrong, press sync" is
in both Reading the grid and Troubleshooting. A manual that only
described the happy path would leave the one symptom worth reporting
looking like a bug in the reader's set.
The same commit records what following Live cost: a write no longer
re-reads the set, so it no longer quietly catches up on changes made in
Live as a side effect. That is a regression from the user's seat and it
says so.
Also: the sort hierarchy in the running order, per-scene slices in
folded song headers, ⌘A, and the bar.beat.sixteenth readout that has
been in the header since the branded transport and was never written up.
Some of this documents work that is still in the working tree, so the
manual is briefly ahead of the released device.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01MutvDXT74GQ57Jjztt21cz
Group tracks, dragging scenes and clips, meters
Catches the manual up with the grid.
Track groups were described as a header row spanning their members, with a
folded group standing in as a count column. They're columns now — a group is a
real track at the head of what it contains, with a launcher that fires the whole
group and a bar showing how far it reaches. Folding writes back to Live, so it
survives a snapshot.
New page for moving clips, since it overwrites and has no undo — that needs
saying somewhere it can't be missed rather than as a bullet on another page.
Dragging a single scene joins the running order, which is now three ways to
reorder rather than two.
Track headers carry each track's own color from Live, and the meter toggle is
mentioned where the header is described.
Dropped ⌥ from the mouse tables. It used to add to a selection and no longer
does anything; both pages that taught it now say so, since a shortcut people
learned going quiet is worse than one that never existed.