| Name |
Last commit
|
Last update |
|---|---|---|
| .. | ||
| api | ||
| escales | ||
| manifeste | ||
| semaphore | ||
| tasks | ||
| tide-table | ||
| ui | ||
| .gitignore | ||
| DESIGN.md | ||
| PRODUCT.md | ||
| README.md | ||
| ardour_faders.json | ||
| serve.py | ||
| setlist_opal2026.txt |
build_release_joins hardcoded its first closing clip as CLOSE · DRY, "what ships today". That was true exactly once — before any reverb was chosen. The clip is cut from the RENDERED last track, so the moment PLN picked a preset the file he auditioned had the echo baked in and the label said it did not. An audition UI that misdescribes what ships is the one bug this tool cannot have: its entire job is to let the ear check the actual artefact, and a wrong label turns a passed listen into a false clearance. Same family as the earlier allow-list that silently dropped reverb_preset — the output looked clean and was clean, of the wrong thing. Now the first entry is CLOSE · SHIPPED and reads the preset out of the release segments, so it renders as "SHIPPED · MORE tail baked in". Names the artefact from the data that produced it rather than from an assumption frozen at the time the code was written. Wrapped in try/except: a missing segments file drops the suffix rather than blocking the audition. The A/B variants are unchanged and still opt-in behind --close-ab.
| Name |
Last commit
|
Last update |
|---|---|---|
| .. | ||
| api | Loading commit data... | |
| escales | Loading commit data... | |
| manifeste | Loading commit data... | |
| semaphore | Loading commit data... | |
| tasks | Loading commit data... | |
| tide-table | Loading commit data... | |
| ui | Loading commit data... | |
| .gitignore | Loading commit data... | |
| DESIGN.md | Loading commit data... | |
| PRODUCT.md | Loading commit data... | |
| README.md | Loading commit data... | |
| ardour_faders.json | Loading commit data... | |
| serve.py | Loading commit data... | |
| setlist_opal2026.txt | Loading commit data... |