When the host writes the drive (SCSI Write sets a dirty flag) and the drive has been idle ~1.5s AND playback is stopped, the loop re-reads programs.json and rebuilds the set lists (reload_user) -> a dropped file applies without a reboot. Read-only path (split read_programs_json out of read_user_setlists; the format flash-write only happens at boot), so no FAT-corruption risk from dual access. Note on the recommended write path: the device deliberately does NOT write the shared FAT while the host has it mounted (that corrupts the host cache - same reason CircuitPython is one-direction-at-a-time). The practice log should instead go to the editor via LOGSYNC (0x45); settings.json *read* (device read-only) is a safe follow-up. Documented in docs/rust-port.md. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| assets/bravura | ||
| glyphgen | ||
| pm-grid | ||
| pm-kit | ||
| pm-ui | ||
| track-format | ||
| uisim | ||
| .gitignore | ||
| Cargo.toml | ||
| Containerfile | ||
| probe-flash.md | ||
| README.md | ||
| run.sh | ||
Rust port — track-format crate (Stage 1)
Pure parse/serialize codec for the track DSL, validated against the shared golden
vectors (tests/fixtures/track-format.json) — the third implementation alongside
engine.js and app.py. See docs/rust-port.md for the staged plan.
All tooling runs in a container (per the develop-in-container rule):
./rust/run.sh # cargo test — runs the conformance + idempotency suite
./rust/run.sh cargo build
./rust/run.sh bash # interactive shell in the crate