Say that the bpm can be made to move the tempo on rename
Song start tempo, in Set configuration. The page already described the bpm as a
label and the tempo as its own button; this is the switch that joins them for a
set that always wants both, and why it is off to begin with.
Co-authored-by: Codex <noreply@openai.com>
Say the bpm field holds Live's own 20-999 range
Co-authored-by: Codex <noreply@openai.com>
Rename the tempo button and say what it writes
The button is now Apply tempo to song start: the song's first scene gets
Scene.tempo and the rest of the song gives it up. That is also how a set
written the every-scene way converts, so the page says so, and
Troubleshooting gains the symptom that sends you there — firing a scene
mid-song snapping the whole set.
Co-authored-by: Codex <noreply@openai.com>
Say that the bpm lives in the name and does nothing on its own
The scene name format grows a bpm slot, and the page has to show it. The
reason is the mixing problem: Scene.tempo on every scene of a song meant
that song could only be entered at its own tempo.
Co-authored-by: Codex <noreply@openai.com>
Describe the Master section, and roles as filled cells
The left edge is one region with one heading now, not a column plus a
column: the Songs label and the song-workflow buttons span the metadata
and Master columns together, filled with Live's Master colour the way
every track header is filled with its own. Nothing spells out that Master
is in there, so the page doesn't either — the launchers down the column
and the strip at its foot are what say so.
A role is no longer a pill beside a launcher. It fills its cell edge to
edge the way a clip's colour fills a slot, with the launcher recessed on
top, so a tagged scene reads as a slot with something in it; an untagged
one is a dim cell reading NONE, and a role nobody has coloured takes a
dashed outline. Roles.md, Color.md, Naming.md and the keyboard reference
all described the old pill.
Song headers split at the same boundary every other row does rather than
running the full width, and their identity is two lines: the name with
the artist beside it, then bpm, key, tag and 2/2 underneath. Open and
folded headers are the same shape now, which is worth saying plainly
because the folded one used to be a different layout — and because it is
why a folded song's name is readable rather than a strip left over after
the facts.
Both ASCII diagrams redrawn and re-aligned, and The-running-order stops
telling you to drag the header marked "part 2 of 2", which now reads 2/2
with the words in its tooltip.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01JcqKqi7azGSadYatDcsyGD
Document the split left columns and the continuous song header
The grid's left edge is two columns now, not one. The metadata column
holds a scene's number, BPM and key and nothing else; the Master column
beside it is Live's Master track at the head of a column of its own,
carrying each scene's launcher and role above, and Stop All Clips and
Master's strip below. Both stay pinned while you scroll across the
tracks.
What that changes for a reader: the ▶ is in the Master column rather than
a gutter of the scene's own, the role chip sits beside it, the Songs
heading is no longer tinted with Live's Master color — that color went
with the Master column — and Master's strip is the same size as every
other strip rather than a wider one centred in an oversized cell.
An open song header is one continuous bar across the whole grid, with its
name, artist, facts, tag and flags pinned to the left edge so scrolling
out to track 30 still says which song those clips belong to. The song tag
is gone from the scene rows: every scene of a song carries the same one,
so a column of them said nothing the header hadn't.
Both ASCII diagrams are redrawn and re-aligned. The width table's track
counts are recomputed for the narrower left edge — Narrow fits about 11
tracks now, Wide about 7 — and the 8/16 note says that Master takes a
track's worth of width without being one of the eight.
Two things were stale before this and are fixed with it: "click a scene
name" described a gesture whose target shows no name, and Troubleshooting
still recommended the S column width, which was removed some time ago.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01JcqKqi7azGSadYatDcsyGD
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
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