|
|
@@ -249,13 +249,23 @@ Four projects written by the Go writer (`tools/checkpoint-a`, built from commit
|
|
|
|
|
|
Every item on the original 0.5.0 list (project name, pad sample assignment, sequence name, BPM, bar length, adding a sequence) plus pad tuning has now been written by these recipes and accepted by the device.
|
|
|
|
|
|
+### Checkpoint B (2026-11-11)
|
|
|
+
|
|
|
+Five projects made from DemoFile in the app, exported, and loaded on the device (details and results in `docs/checkpoint-b.md`). All loaded and worked:
|
|
|
+
|
|
|
+- **Unchanged round trip** (B1): plays as DemoFile.
|
|
|
+- **Moving a pad with notes** (B2): the sample plays from its new pad; the notes stay on the old slot, as expected.
|
|
|
+- **Copy across banks, swap pads with notes** (B3): as expected.
|
|
|
+- **Remove the current sequence, add one in bank B** (B4): works; Sequence 02 is selected on open (see open question 7).
|
|
|
+- **Shorten a sequence with notes** (B5): the notes past the new end are kept and play again once the sequence is lengthened (open question 4).
|
|
|
+
|
|
|
## 8. Open questions
|
|
|
|
|
|
1. Device-test a moved and a copied pad.
|
|
|
1a. ~~Confirm the tuning limits on the device.~~ Confirmed 2026-11-10 (checkpoint A): -24 to +24 semitones and -90 to +90 cents.
|
|
|
2. Level and pan have not been seen changed; confirm they are written to `pad[n].mixable`.
|
|
|
3. `triggerMode` values (0 and 3 seen) and how they pair with `loopMode`.
|
|
|
-4. When a sequence with notes is shortened, are notes past the new end kept or removed?
|
|
|
+4. ~~When a sequence with notes is shortened, are notes past the new end kept or removed?~~ Answered 2026-11-11 (checkpoint B5): kept. They don't play while the sequence is shorter, and play again when it is lengthened on the device.
|
|
|
5. Sample rates outside 22.05-96 kHz and 64-bit float are untested. (The extensible header was confirmed in checkpoint A; other WAV bit depths and sample rates are confirmed; non-WAV formats are out of 0.5.0.)
|
|
|
6. What key and tempo to write for a sample mpckit imports (the device detects them; mpckit cannot yet).
|
|
|
-7. Is `currentSequence` a slot number or an index into `sequences[]`? Every file seen has 0, and slot 0 is stored second, so the files cannot tell. mpckit treats it as a slot (build plan 4.3); checkpoint B4 should remove the current sequence and check which one the device opens.
|
|
|
+7. Is `currentSequence` a slot number or an index into `sequences[]`? Every file seen has 0, and slot 0 is stored second, so the files cannot tell. mpckit treats it as a slot (build plan 4.3). Checkpoint B4 (removing the current sequence) worked, with Sequence 02 selected on open, but in that file slot 1 and list position 1 are the same sequence, so it does not tell them apart. Still open.
|