Say that Live keeps drawing while the set is read
The first read no longer locks Live up: it runs in pieces with a pause
between each, so the progress bar means something now. Two consequences a
user can see and would otherwise misread — it finishes a little later than
it would if it hogged everything, and restructuring the set mid-read makes
it start over rather than show a half-and-half answer.
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_01XgWVKDg9bAtZhhDoQjtqE4
fad06a4
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
99ea03d
Say that the mixer grabs, since a click used to throw a fader
The volume, pan and send fields were browser range inputs, which jump to wherever
you click. Live grabs the control where it already is, and now so do these — so a
stray click on a 26px pan field can no longer send it to one end, and the field is
usable at that size rather than offering about four positions.
Two things come with it that are worth a user knowing: ⌘ while dragging is fine
adjustment, taking or releasing it mid-drag without the control moving; and a
focused field takes the arrow keys at the parameter's own step size.
That last one is why the keyboard page needed more than a row. Its rule is that ⌘
means "make Live respond", and in the mixer ⌘ means fine — Live's own meaning, in
Live's own place. Stated outright rather than left as a quiet exception, and the
arrow keys get their own section so it's clear a focused control keeps them from
the grid until you click away.
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_01CBNC3e13kZgJJ7bKvnTsm3
3368346
Say that only the first load reads the set
The device keeps track of the set now, so opening, refreshing or opening a second
window is instant however big it is — and a refresh that reads everything again is
a bug to report rather than something to work around. Also says the following
happens in the device, which is why closing every window doesn't stop it and how
the Push encoder stays right with no browser open.
Co-authored-by: Codex <noreply@openai.com>
de0d4b7
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>
f4bcbc2
Say the bpm field holds Live's own 20-999 range
Co-authored-by: Codex <noreply@openai.com>
4eebe77
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>
e5fd174
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>
8ede5ab
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
8dd8009
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
22ae400
Document the track status display
The stop row now carries Live's own Track Status Display beside each
track's stop button: the loop pie, a one-shot's countdown and the take
length while recording. Says what each form means, that the countdown is
time left rather than time played, and which two of Live's forms are
missing so a blank cell isn't read as a bug.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01JcqKqi7azGSadYatDcsyGD
cc28ce2
Document the transport's Arrangement Record
The transport's third button is Live's Arrangement Record, and what it
does depends on when you arm it: before the song starts, the next start
records into the Arrangement; while the song is already rolling, the
take begins there. Nothing in the app arms it on your behalf.
The header's neutral-text rule needed the exception stated too. The
transport takes its colors from Live rather than from that rule — green
while the song rolls, red while Record is armed.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01JcqKqi7azGSadYatDcsyGD
0cc8957
Document that unity lands on the 0 dB line
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01JcqKqi7azGSadYatDcsyGD
9b0aca0
Document the button in every empty slot
Empty slots used to draw nothing, and the manual said so. They now carry
Live's own button at the left of the cell: a square that stops the track,
or — once the track is armed in Live — a red circle that records into
that slot.
Reading the grid gains the pair as part of what a cell can show, and says
that a column of circles is how the grid reports an armed track. Playing
things gains a recording section, and its stopping section now leads with
the per-slot square rather than only the stop row. Both note that a
pending stop shows on the track's header and stop-row button instead of
on the square that was pressed: Live reports a pending stop against the
track, not the slot, so there is no way to know which one to blink.
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_01PxyrR7kVhUaShgE822g19V
58585bf
Remove the Master mixer label
Co-authored-by: Codex <noreply@openai.com>
3649208
Document contained Master mixer label
Co-authored-by: Codex <noreply@openai.com>
db57e6d
Document mixer footer controls
Co-authored-by: Codex <noreply@openai.com>
3450bd6
Document the thin mixer divider
Co-authored-by: Codex <noreply@openai.com>
5a53cdf
Document segmented mixer handle
Co-authored-by: Codex <noreply@openai.com>
cee6fe0
Document aligned Master mixer controls
Co-authored-by: Codex <noreply@openai.com>
a36f0df
Document aligned footer separators
Co-authored-by: Codex <noreply@openai.com>
7d7a147
Document track stop row
Co-authored-by: Codex <noreply@openai.com>
f17bb3a
Document unified Master fader
Co-authored-by: Codex <noreply@openai.com>
d9a999e
Document larger mixer controls
Co-authored-by: Codex <noreply@openai.com>
c824079
Document responsive mixer meters
Co-authored-by: Codex <noreply@openai.com>
37d51c1
Document mixer track dividers
Co-authored-by: Codex <noreply@openai.com>
0471049
Document mixer send controls
Co-authored-by: Codex <noreply@openai.com>
0ede142
Update the set configuration manual
Co-authored-by: Codex <noreply@openai.com>
05f4044
Document the 0 dB meter reference
Co-authored-by: Codex <noreply@openai.com>
0bfe61a
Clarify mixer rail alignment
Co-authored-by: Codex <noreply@openai.com>
fb984b2