# making-music
Tooling for writing and editing music together with an LLM.
LLMs can't read MIDI, and the text formats that do exist either quantize (ABC) or speak
in ticks and note numbers (midicsv). The tool here is **duet**. Its first format,
**notefmt**, turns a MIDI file into one readable note per line, in bars, beats and note
names, and turns it back into MIDI without losing a tick. Its second, the **drum grid**,
writes a drum part as one row per drum and one column per step. It also reads and writes
**ABC**, the shared score format, through the part of ABC a song can hold exactly, and
refuses the rest by name.
The workspace is split by domain:
| `duet-core` | the `Song` every format converts through, quantizing, and the notefmt text |
| `duet-midi` | reading and writing Standard MIDI Files |
| `duet-drums` | the drum grid, its lane maps, and grid ⇄ `Song` |
| `duet-abc` | a subset of ABC 2.1 ⇄ `Song`, and the corpus that checks it against abc2midi |
| `duet-cli` | the `duet` binary |
## How the formats fit together
**ABC is a score, and notefmt is a performance.** They are different kinds of text, and the
`Song` sits between them. Every format converts through one in-memory `Song`: notes at
bar.beat.tick positions with exact tick lengths, velocities, channels, programs, controls,
and tempo, meter and key changes. notefmt is the text form that shows a `Song` exactly. The
drum grid and ABC are readable, grid-shaped views of part of one, for discussing it.
```mermaid
flowchart LR
MIDI["MIDI (.mid)"] <-->|lossless| Song(("Song"))
Song <-->|lossless| TXT["notefmt (.txt)<br/>a performance, exact"]
Song <-->|lossless| JT["JSON / TOML<br/>the Song through serde"]
Song <-->|"a drum track on its grid"| DRUMS[".drums<br/>a drum part"]
Song <-->|"a score-shaped song"| ABC[".abc<br/>a melodic score"]
Q["duet song quantize<br/>(an explicit step)"] -.->|"makes a played take score-shaped"| Song
```
- **notefmt holds whatever MIDI holds that duet keeps.** A note can start 10 ticks late, last
0.98 of a beat, have velocity 103, or overlap another note; a track can sit on channel 10,
with sustain pedal and pitch bend. Nothing has to fit a grid. That is what a sung or tapped
idea looks like after capture, and what a take from a DAW looks like. MIDI ⇄ notefmt never
loses anything duet keeps.
- **ABC holds a score.** Lengths are fractions of a unit note, bars are full, pitches are
spelled against a key, and velocity is one of eight dynamics. ABC also carries notation a
performance has no use for: repeats, slurs, beaming, annotations. It is the format people
and LLMs already read and talk about as music. ABC → `Song` → ABC keeps every note of the
subset duet reads; notation-only marks are listed and dropped, and repeats come back written
out.
- **Writing ABC works only for a song that is already score-shaped.** A played take is
refused by name, naming the note, and never snapped quietly. Quantizing is a step you
choose: `duet song quantize`, then `duet abc write`.
- **The drum grid is the same idea for drums**, which ABC refuses. ABC covers pitched lines.
| What it is | a performance, exact | a drum part on a step grid | a melodic score |
| Unit | ticks | steps | fractions of a note |
| Velocity | any, 1 to 127 | three levels as text (exact in `.drums.json`) | eight dynamics |
| Lossless with `Song` | yes | for what fits the grid | for the subset |
| For | capture, DAWs, exact edits, diffs | discussing a groove | discussing and sharing a tune |
notefmt is also where anything is checked exactly. The ABC tests compare in it: abc2midi's
reading of each corpus tune is committed as notefmt text. That is how abc2midi's
undocumented habit shows: every note one tick late and one tick short (`1.1.1 C4 0.998`),
which ABC itself could not express.
## notefmt
```
# notefmt v1: positions are bar.beat.tick, lengths are quarter notes
title "Sketch in D minor"
tpq 480
tempo 92
time 4/4
key D minor
[track "Piano" ch1 prog0]
1.1.0 cc64 127
1.1.0 D4 1 80
1.2.0 F4 0.5 72
1.2.240 A4 0.5 75
3.1.0 D4 0.333 80
3.1.160 E4 0.333 76
[track "Bass" ch2 prog33]
1.1.0 D2 2 90
1.3.0 A1 2 84
```
The full example is [samples/sketch.txt](samples/sketch.txt).
### Install and run
```sh
cargo install --path crates/duet-cli
duet convert take.mid take.txt # MIDI to text
duet convert take.txt take.mid # text back to MIDI
duet convert take.mid take.json # or JSON, or .toml
duet song show take.mid # print as text
duet song show take.mid --to json
duet song quantize take.mid take-q.mid --grid 1/16 # a copy snapped to sixteenths
```
Formats come from the file name (`.mid`/`.midi`, `.json`, `.toml`, the drum grid forms
`.drums`, `.drums.json` and `.drums.toml`, anything else is text). Use `-` for standard
input or output, with `--from` and `--to` to name the format: `midi`, `text`, `json`,
`toml`, or `drums`, `drums-json` and `drums-toml` for a grid. `convert` reads and writes
[drum grids](#drum-grids) too; writing one needs `--grid`.
### The text format
**Header**, before the first track. Every line is optional; the defaults are 480 ticks
per quarter, 120 bpm and 4/4. A header line after a `[track]` line is an error: tempo, meter and
key are the whole song's, so they are never written inside a track.
| `title "Name"` | Song name: the MIDI sequence name (see below) |
| `tpq 480` | Ticks per quarter note: the file's resolution |
| `tempo 92` | Tempo at the start, in quarter notes per minute |
| `time 6/8` | Time signature at the start |
| `key D minor` | Key at the start (`Dm`, `Bb major`, `Bb` also work), or a mode: `key D dorian` |
| `tempo 96 at 9.1.0` | Tempo change |
| `time 3/4 at 17.1.0` | Time signature change |
| `key A minor at 33.1.0` | Key change |
| `end 41.1.0` | Where the song ends, when it says (see below) |
**Tracks** start with `[track "Name" ch1 prog0]`: a name, a MIDI channel from 1 to 16 and
optionally the General MIDI program (0 to 127) at the start. Then one event per line:
| `3.2.240 F#4 0.5 80` | Note: position, pitch, length, velocity (1 to 127) |
| `5.1.0 cc64 127` | Controller: number and value (64 is sustain, 1 the mod wheel) |
| `5.3.0 bend -2048` | Pitch bend, -8192 to 8191, 0 is none |
| `9.1.0 prog 5` | Program change later in the track |
- **Positions** are `bar.beat.tick`, as a DAW shows them. Bars and beats count from 1. A
beat is the time signature's denominator (a quarter in 4/4, an eighth in 6/8), and the
tick is the offset into the beat in the file's own ticks: at 480 tpq, `1.2.240` is an
eighth note after beat 2. `1.2` means `1.2.0`, and offsets past the end of a beat carry
on (`1.1.960` in 4/4 is read as `1.3.0`).
- **Pitches** are scientific pitch names with middle C (MIDI 60) as `C4`. Sharps and flats
both work (`F#3`, `Bb2`). When reading MIDI, black keys are spelled the way the scale of
the key in force where the note starts spells them, so D minor gives `Bb` and `C#`, and
after `key A major at 9.1.0` the same keys are `A#` and `C#`.
- **Lengths** are in quarter notes, whatever the time signature: `1`, `0.5`, `1.5`, or a
fraction like `1/3` for a triplet.
- Lines starting with `#` are comments, and so is anything after a word that starts with `#`.
### Where a song ends
A song names its end with `end`, a position like any other: `end 9.1.0` is the bar line
before bar 9, and `end 8.3.0` stops halfway through bar 8, for a pickup ending. Every format
keeps it: the header line in text and drum grids, `end` in JSON and TOML, and MIDI's end of
track, where every track ends.
**Every file `duet` writes states its end**, so a file shared between people means the same
on every machine, whatever defaults each has set.
- A note may end exactly on the end. Anything past it is refused, naming it and the end:
`track 'Piano': the D4 at 8.4.0, which ends at 9.1.240, lies past the song's end at 9.1.0`.
That goes for notes, controls and tempo, meter or key changes, when reading, writing MIDI
and quantizing. Nothing is cut to fit.
- A song that names no end gets the default: the bar line after the last bar holding a
note or control, and never before a tempo, meter or key change. `duet.toml` can change
the default (see [Configuration](#configuration)). A file written from it states that
end, so it reads the same wherever it goes.
- Reading MIDI, the file's end (its latest end of track) becomes the song's when some
track's end of track comes after the event before it, or when it lies past every event
kept. A file whose tracks each end exactly at their last event cannot say whether it means
an end there or none, so it reads as naming none and the default applies; the music is
the same either way.
### Exact round-trips
Reading a MIDI file and writing it back keeps every note to the tick: start, length, pitch,
channel and velocity. Lengths and tempos are written as the shortest decimal that converts
back to exactly the same ticks and microseconds (a triplet eighth at 480 tpq is 160 ticks,
written `0.333`), so nothing drifts however many times a file goes through text.
Kept: notes, tempo changes, time signature changes, key signatures, track names, program
changes, controllers, pitch bend, and the file's end (above). A key in a mode other than
major or minor (dorian, phrygian, lydian, mixolydian, locrian) is written as its key
signature plus a `duet:key D dorian` text event, which is read back; other programs see the
signature.
Dropped: aftertouch, SysEx, markers, lyrics and other text events, and note-off velocity.
A MIDI track that mixes channels (as format 0 files do) becomes one track per channel, and
files are always written as format 1, with the title, tempo, meter and key in the first track.
The title is the sequence name, which MIDI keeps as a track name: the name of a format 1
file's first track when that track holds no notes, or of the only track in a format 0 file.
A format 0 file's tracks have no names of their own, so they are named `Channel 1`,
`Channel 10` and so on.
Names are text. A track name or title whose bytes are not UTF-8 (an old file written in
Latin-1, say) is read with each invalid byte replaced by `�` (U+FFFD), so that name is not
written back byte for byte. Notes and everything else above are unaffected.
One thing MIDI cannot hold: a note that starts after another note of the same pitch and
channel and ends before it. MIDI has no note ids, so its note-off would end the outer note
instead. Converting such a song to MIDI is an error that names both notes. Notes that only
overlap, or that start together, are kept exactly.
Nothing is quantized unless you ask: played timing comes through as it was played.
### Quantizing
`duet song quantize` (or `Song::quantized` in the library) writes a copy with every note's
start and end moved to the nearest point of a grid. The input is never changed.
- The grid is written `1/16` for sixteenths or `1/8t` for triplet eighths. A grid whose step
is not a whole number of the file's ticks is refused, naming the grid and the resolution.
- The grid restarts at every bar line, so bar lines are always on it. In a bar cut short by
a time signature change, the last step before the bar line is short.
- A tick exactly halfway between two grid points goes to the later one.
- A note that would collapse to zero length gets one step instead, so no played note
disappears. A note that was already zero length stays that way.
- Pitch, velocity, track and note order are kept. Controls, tempo, key and time signature
changes are not moved.
- Two notes of the same pitch can end up one inside the other. Writing those to MIDI is
refused by name, as above; quantize to text to see and fix them.
### As a library
```rust
use duet_core::Song;
use duet_midi::Midi; // adds Song::from_midi and Song::to_midi
let song = Song::from_midi(&std::fs::read("take.mid")?)?;
let text = song.to_text();
let json = serde_json::to_string_pretty(&song)?;
let back = Song::from_text(&text)?.to_midi()?;
```
`Song`, `Track`, `Note` and `Control` derive serde's `Serialize` and `Deserialize`, so any
serde format works. Positions, pitches, keys and time signatures serialize as the same
strings the text format uses.
## Drum grids
```
# notefmt drums v1: one row per lane, one column per step, | at bar lines
title "Groove in D"
tpq 480
tempo 96
time 4/4
grid 1/16
map gm
[bars 1-2]
# 1 . . . 2 . . . 3 . . . 4 . . . 1 . . . 2 . . . 3 . . . 4 . . .
hh-open | . . . . . . . . . . . . . . . . | . . . . . . . . . . . . . . x . |
snare | . . . . X . . . . . . g X . . . | . . . . X . . . . . . . X . g . |
kick | X . . . . . . X . . X . . . . . | X . . . . . . X . . X . . X . . |
```
That is [samples/groove.drums](samples/groove.drums). A drum grid is a matrix: for each
bar, one velocity per lane and step, 0 for no hit. `.drums` files are its text form, and
`.drums.json` and `.drums.toml` its exact form, the matrix itself.
```sh
duet drums render groove.drums groove.mid # to MIDI (or .txt, .json, .toml)
duet drums read take.mid take.drums --grid 1/16 # a song's drum track to a grid
duet drums read take.mid take.drums.json --grid 1/16 # keeping every velocity
duet drums snap take.drums.json take.drums # velocities snapped to g, x and X
duet drums lanes # the lanes and their keys
```
`duet convert` goes between grids and every other format as well, by the same code:
reading a grid it writes what `duet drums render` writes, and writing one from a song it
takes `duet drums read`'s `--grid`, `--track`, `--bars` and `--snap-levels`, and writes and
refuses what `duet drums read` does.
```sh
duet convert groove.drums groove.mid # the same as drums render
duet convert take.mid take.drums --grid 1/16 # the same as drums read
duet convert groove.drums groove.drums.json # a straight copy to the exact form
duet convert groove.drums sixteenths.drums --grid 1/16 # re-stepped through a song
```
Writing a grid from a song without `--grid` is refused, naming it: the step is never
guessed. From a grid to a grid, with no `--grid`, the grid is copied as it is, read and
written as `drums snap` does but without snapping: a lane with no hits, the grid's own
`vel` levels and, in the exact forms, any velocity all survive. A velocity off the levels
is refused as text unless `--snap-levels` is given. With `--grid`, the grid goes through a
song at that step, as `drums render` then `drums read` would, so lanes with no hits are
dropped. A grid flag that would do nothing (`--track` or `--bars` without `--grid` from a
grid, or any grid flag for an output that is not a grid) is refused too, so no flag is
silently ignored.
**A name means the same to every command.** `.drums`, `.drums.json` and `.drums.toml` are
grids, and every other name is a song's, even when the file holds the other: a song saved
as `x.drums.json` is read as a grid. So a command that reads or writes a song (`drums
render`'s output, `drums read`'s input, `song show`, `song quantize`) refuses a grid's name,
and one that reads or writes a grid (`drums render`'s input, `drums read`'s output, `drums
snap`) refuses a song's, rather than misreading the file. `--from` and `--to` say what a
name does not, and `-` is .drums text on a grid's side.
**Header.** The notefmt header lines (title, tpq, tempo, time, key and their `at`
changes) mean what they mean in notefmt, plus:
| `grid 1/16` | One step (required): `1/16`, `1/8`, `1/8t` for triplet eighths, and so on |
| `map gm` | The lane map the rows are named from; `gm` is the default and the only one |
| `lane shaker-2 82` | Adds a lane, or moves a map lane to another key |
| `channel 10` | The MIDI channel, when it is not the map's (10) |
| `vel g 40 x 90 X 120` | The velocities the cells stand for, when they are not these |
| `end 3.1.0` | Where the grid stops: the bar line after its last bar, or a step inside that bar |
The writer always states the end. An `end` inside the last bar must be on a step, and the
cells from that step on must be rests. An `end` that contradicts the bars, before the last
bar or past it, is refused by name, and so is a tempo, meter or key change past the end.
**Blocks.** `[bars 1-4]` holds rows for those bars. Blocks cover every bar in order from
bar 1, so an empty bar is written as rests, and every block lists the same lanes in the
same order. A row is a lane name, then each bar's cells between `|`s. A cell is `.` (no
hit), `g` (ghost), `x` (hit) or `X` (accent), separated by single spaces. Each bar's cell
count is checked against its meter, and a wrong count names the line, lane and bar:
`line 14: snare, bar 2 has 15 steps; 4/4 at 1/16 needs 16`. The `#` row counting beats is
a comment, written to help find "the and of 3".
**Every bar must be a whole number of steps**, so 7/8 needs a grid of `1/8` or finer, and
a grid that does not fit is refused by name.
**Lanes.** The `gm` map has a lane for every General MIDI Level 1 percussion key, 35 to
81, on channel 10, with names that are never note names: `kick` 36, `sidestick` 37,
`snare` 38, `clap` 39, `rimshot` 40, `hh` 42, `hh-pedal` 44, `hh-open` 46, `crash` 49,
`ride` 51, the toms from `tom-high` 50 down to `tom-floor` 41, and so on. `duet drums
lanes` lists them all with their aliases (`bd` for `kick`, `oh` for `hh-open`); a file may
use an alias, and the grid then uses the lane's own name. Rows are written cymbals first,
then hats, toms, snare, kick and percussion. A user's or project's `duet.toml` can add lanes, move them and give them aliases (see
[Configuration](#configuration)).
**To and from a song.** Rendering gives one track named `Drums` on the grid's channel:
each hit is a note on its lane's key, one step long, with its velocity. Reading a song
takes its drum track (the one on channel 10, or the one `--track` names) and keeps only
note starts and velocities: lengths, controls and other tracks are left out, and `duet`
says how many. Nothing is moved to fit. A note off the grid (quantize it first, with
`duet song quantize`), on a key no lane plays, or on the same lane and step as another is
refused by name. The grid runs to `--bars` when it is given, or else to the song's end, the
one it names or its default (a mid-bar end, which must be on a step, becomes the grid's
`end`). `--bars` never cuts anything: a hit or a tempo, meter or key change past it is
refused by name.
Rendering gives the song the grid's end, so trailing empty bars and a mid-bar end survive.
Grid → song → grid gives back the same grid, through MIDI too, with no bar count asked for,
trailing empty bars and a mid-bar end included, when its lanes are in the map's row order
and each is played at least once, as the writer leaves them.
**Velocities.** The text holds three levels. Writing a velocity that is not one of them as
text is refused, naming the lane, bar and step; keep it in `.drums.json`, or snap it to the
nearest level with `duet drums snap` (or `--snap-levels` when reading). A velocity exactly
halfway between two levels goes to the louder one. Nothing snaps unless you ask.
## ABC
```sh
duet abc check tunes.abc # what each tune holds that a song does not carry
duet abc render tunes.abc tune.mid --tune 2 # one tune as MIDI (or .txt, .json, .toml)
duet abc write take.txt take.abc --unit 1/4 # a song as ABC, X:1
duet convert tune.abc tune.mid # .abc works both ways, for a file of one tune
```
`duet-abc` reads a subset of [ABC 2.1](https://abcnotation.com/wiki/abc:standard:v2.1):
header fields, notes, octaves, accidentals, lengths, rests and multi-bar rests, bar lines,
ties, broken rhythm, tuplets up to `(9`, chords, repeats and endings (unfolded), inline
`[M:]`, `[L:]`, `[Q:]` and `[K:]`, keys with a mode, voices, `%%MIDI program` and
`%%MIDI channel`, the dynamics `!ppp!` to `!fff!`, and several tunes per file. A pickup is
a short first bar of its own time signature, so its notes keep abc2midi's ticks exactly.
**Notation only.** Slurs, annotations, information fields such as `C:` and `N:`, voice
properties other than the name, other `%%` directives and the spacer `y` are read and not
carried into the song. `duet abc check` lists each with its line, and `render` says how many
there were.
**Refused by name.** Everything else is refused with its line and column and the name of
the construct: grace notes, decorations other than dynamics, chord symbols, lyrics, parts,
`K:none`, clefs and transposition, `%%MIDI` commands other than program and channel, and
the rest of the table in `duet_abc::REFUSED`. Two constructs are refused because the
standard and abc2midi read them differently: a bare `Q:120`, which the standard reads as
unit lengths per minute and abc2midi as quarters (write `Q:1/4=120`), and a tune with no
`M:`, which is free meter in the standard and 4/4 in abc2midi. A bar of the wrong length is
an error naming the bar; abc2midi plays it as written, without a warning.
**One place duet parts from both.** A `:|` with no `|:` goes back to the start of the tune,
in the standard and in abc2midi, so a pickup is replayed there (abc2midi warns of the short
bar). A song cannot hold a short bar in its middle, so duet goes back to the first full bar
after the pickup instead. Write `|:` after the pickup and all three agree.
**Writing.** Nothing is quantized. A note off the 1/64-note grid that is not in a triplet
group (three equal slots filling whole beats, each note one or two of them) is refused,
naming its track and position (quantize it first with `duet song quantize`). So are a velocity that is not a dynamic's level
(`--dynamics nearest` snaps it, and the ABC says so in a comment), a tempo that is not a
whole bpm, a track on channel 10 (drums are the drum grid's), and notes that overlap
without starting and ending together. ABC needs a key, so a song with none is written in C
major. The ABC written is canonical: reading it and writing it again gives the same text.
**Where it comes from.** `duet-abc` was written from the ABC 2.1 standard and from
abcMIDI's documentation of how abc2midi plays what the standard leaves open. No abcMIDI
source file was opened, and none is copied. abc2midi is only ever run as a separate
program, on a developer's machine, to check this crate's reading (see Development).
## Configuration
`duet` reads `duet.toml` and `duet.local.toml` from two places, each file over the ones
before it:
1. the user config directory: `~/.config/duet` on macOS and Linux (or `$XDG_CONFIG_HOME/duet`),
`%APPDATA%\duet\config` on Windows, or whatever `DUET_CONFIG_DIR` names
2. a project's `.duet/` directory: the nearest one from the working directory up
```toml
[song]
end = { round-up = 4 } # or "last-bar", the built-in
[lanes.shaker-2] # a new lane: it needs a key; it goes in the "other" group
key = 82
aliases = ["sh2"]
[lanes.kick] # a gm lane: only the fields given change
aliases = ["bd", "boom"]
```
- **`[song] end`** is the end a song that names none gets when a file is written.
`"last-bar"` is the bar line after the last bar holding a note or control. `{ round-up = 4 }`
carries that on to the next multiple of 4 bars. The end is always written into the file, so
someone with other defaults reads the same song.
- **`[lanes.<name>]`** adds a lane to the `gm` map, or changes one. The fields are `key`,
`group` (one of the map's groups, or `other`) and `aliases`. A file never removes a
built-in lane, so one that would put two lanes on one key is refused: move the other lane
too. Each file must leave a valid map.
- **Config lanes are for reading.** A `.drums` row may use a lane or alias config adds, and
`duet drums read` names notes by the configured keys. Written `.drums` files never depend on
config: they say `map gm` and carry a `lane` line for every lane the built-in map does not
name on that key, so they read the same with no config at all.
- **`map gm` is General MIDI on every machine.** When reading `.drums` text, a config that
moves a gm lane's key or group does not apply: `kick` is still 36 there. The move still
applies to `duet drums read`, where it describes your kit. `duet` says on standard error
when a moved key doesn't apply, and `duet config show` lists it. A file's own `lane` line
still moves a lane.
- A file that breaks a rule (bad TOML, a field `duet` does not know, two lanes on one key)
is refused, naming the file and the rule.
```sh
duet config path # the directories, and each file in the order it is read
duet config show # the merged config as a duet.toml, each value with where it came from
```
## Development
Builds on the latest stable Rust (1.100 or later, edition 2024).
```sh
cargo test --locked
cargo clippy --locked --all-targets --all-features -- -D warnings
cargo fmt --all --check
```
CI also runs `cargo deny`, `cargo audit`, rustdoc with `-D warnings`, a build on the declared
`rust-version`, and the checks for the tasker-systems
[conventions](https://github.com/tasker-systems/conventions) baseline this repository is pinned to
(see [CLAUDE.md](CLAUDE.md) and `.conventions/`).
The round-trip tests in `crates/duet-midi/tests` generate MIDI files with humanized timing,
sustain pedal, pitch bend, tempo and meter changes (including one in the middle of a bar),
overlapping notes, and a format 0 file with several channels, at 96, 384, 480 and 960 ticks
per quarter, and check every kept event survives MIDI to text to MIDI unchanged. Those in
`crates/duet-drums/tests` generate drum grids in several meters (with a change of meter),
grids and resolutions, with any velocity, ending in empty bars or inside a bar, and check
grid → song → grid, through MIDI, JSON and TOML, and the text form all round-trip unchanged.
`crates/duet-abc/corpus` holds our own ABC tunes, MIT, one per construct the subset reads
plus six whole tunes, each with committed recordings of abc2midi's reading of it and of the
ABC our writer makes from it. CI compares our reading with those recordings
(`crates/duet-abc/tests/oracle.rs`). It never runs abc2midi. On a developer's machine, the
`oracle` feature also runs abc2midi and checks the recordings still match it:
```sh
brew install abcmidi # the version in corpus/manifest.toml
cargo test -p duet-abc --features oracle # fails on any other abc2midi version
DUET_ABC_RECORD=1 cargo test -p duet-abc --features oracle recordings_match_live_abc2midi
```
The last line re-records, for a new corpus tune or a writer change; review its diff. When
our reading disagrees with a recording, re-recording is not the fix: either our reading of
the standard is wrong and is fixed, or abc2midi differs from the standard and the
difference is listed in the manifest with its reason. mise cannot pin abcmidi (no registry
entry, and the project publishes no release binaries), so Homebrew installs it and the
oracle checks its version against the manifest.
`crates/duet-e2e` holds the tests that drive the `duet` binary end to end. It is never
published. Each test run builds the binary with `cargo build -p duet-cli --bin duet` and runs
what that build reports, so a test never runs a stale binary (set `DUET_E2E_BIN` to run
another, such as one built from `main`). Its `golden/` holds what `duet` wrote from the
samples before a song could name an end, and a test checks that every file written now holds
the same music, event for event, and differs only by stating its end. CI runs it again, with
duet-cli's tests, under the hostile config in `crates/duet-e2e/hostile`, so no test reads a
developer's own config.