Skip to content

Chart SYSTEM1/2.RC0 in the atlas: a 716-byte pair, not an empty file - #150

Merged
AliceLafox merged 2 commits into
mainfrom
docs/system-atlas
Oct 17, 2026
Merged

AliceLafox merged 2 commits into
mainfrom
docs/system-atlas

Conversation

@AliceLafox

Copy link
Copy Markdown
Member

Closes #148.

docs/pedal-settings.md claimed SYSTEM1/2.RC0 were zero bytes and uncharted. On a working card both files are 716 bytes and carry the same pair-and-counter mechanism as MEMORY1/2; the code has known this since SystemFile.hpp and Controls.hpp landed, the atlas had not caught up.

  • The stale paragraph becomes a SYSTEM section in the atlas's own shape: the pair rule (which file wins), the observation that switching the current memory is a SYSTEM write, and one table per section (SETUP, MIDI, CTL) with the file's confidence marks. Field names, presence, MemoryNumber's meaning and zero base are [V]; CTL names are [M] from the lists Controls.hpp already cites (reference manual pp. 13-14); SETUP and MIDI meanings beyond the tag names are [?] until read off the screen.
  • A short subsection records that nothing in SYSTEM is an auto-save setting (the question behind research: can the pedal be told to save a loop over MIDI? (AutoSave spike) #23).
  • Correction to the issue text: the counters 53/54 quoted there were the MEMORY pair's; SYSTEM stood at 8/7, then 10/11 in the next reading.

Docs only; no code changes.

The atlas said the pedal's settings files were zero bytes and uncharted.
On a working card both carry a <sys> document with SETUP, MIDI and CTL,
and the same pair-and-counter mechanism as MEMORY1/2 — which the core
has read by since SystemFile.hpp. Replace the paragraph with one section
in the atlas's own shape: the pair and which file wins, a table per
section with the observed values, and the confidence each fact earned.
MemoryNumber is the pedal's selected memory, zero-based, and the pedal
rewrites the pair when that changes; the CTL names follow the manual's
lists as Controls.hpp decodes them; the SETUP and MIDI meanings stay
unknown until read off the screen.
…overed

Testers keep asking whether the pedal can save a memory by itself. The
settings file is now charted, and nothing in its three sections names a
save, a write-on-change or a confirmation. Write that down next to the
tables; whether the pedal behaves that way with no stored setting behind
it is still a question for the manual or the hardware.
@AliceLafox
AliceLafox merged commit 3bc0c0d into main Oct 17, 2026
5 checks passed
AliceLafox added a commit that referenced this pull request Oct 17, 2026
0.9.6: merge #150-#159 in stack order, with the integration fixes
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

docs: SYSTEM1/2.RC0 are not empty — chart what a working card carries

1 participant