OPAL 2026 had NO metadata anywhere — content/lives/ carried 2024 and 2025
entries for the same festival and nothing for this one. Writing it by hand is
how wrong strings get copied between files (split_bandcamp.py's ALBUM already
did that once), so tools/gig-metadata.py reads every fact from whoever owns it:
backlog.md via tools/setlist.py --long -> membership, ORDER, name, bpm, section
the .tidal via tools/setlist_samples.py -> the sample packs actually referenced
--segments -> timecodes measured off the take
The timecodes pay for themselves twice. They came from aligning the gig log to
the audio by cross-correlation (r>=0.99 over 20 probes across 11 orbits, 0.00 ms
spread), and they let a visualist cut to the set without re-deriving boundaries
by ear — which is exactly what Slopmotion needs.
OPAL 2026: 15 tracks, 89-166 BPM, 60 sample packs, 1:20:09 — and the set was
played in the EXACT planned order, 15 for 15.
Also two pan TODOs, measured rather than felt: mafia_sans_serif is width 0.05
and ghosts_in_the_toilets 0.09 (side/mid RMS) against a set median of ~0.20 —
the two narrowest tracks of the night, and they played back to back. Both files
also carry PLN's own gig-day edits; both still pass silent-eval --seeded.
