feat(cosmicfest): the first stemless gig reaches segments — 14 tracks, 63.0 min
R-0 and C-0, the two moves the release board put ahead of everything else. R-0. The CosmicFest master existed in exactly one place: ~/Downloads. It is now in Prod/Cosmic26_master/ and mirrored to the freebox, sha256 7a197589…d671b identical on both, and the Downloads original was removed only after both copies were verified — a move, not a hopeful mv. feedback_freebox_ssot names the freebox as the SSOT for audio, and an irreplaceable 63-minute gig in a scratch directory was the cheapest large risk on the board. The spec records the naming trap that nearly cost an hour: Prod/cosmicfest/ and Prod/cosmicfestv0.live1.* are the 2025 edition, files dated 2025-06-27/28, and nothing in them belongs to this release. C-0. POSTPROD.md's rule is that a new gig is a copy of judge_specs/<gig>.json and never a copy of a script — so the question was whether a gig with NO stems can use the pipeline at all. Answered by reading the code, not by trying it and hoping: apply_boundaries and render_release touch no stem key whatsoever, only segments/master/variants/releaseRoot/releaseTag. The single tool that genuinely needs stems is build_judge_set, which derives nominal segments from per-orbit activity. That is the one hole, and setlist_to_segments.py fills it. The converter turns judge_specs/<gig>_setlist_ear.json into the two inputs apply_boundaries wants, and its real job is keeping two grades of truth apart. The setlist silently mixes them: some starts are playhead calls PLN made while listening, others were reconstructed from his notes on boundaries he SKIPPED. Only the former go into `verified`, so apply_boundaries prints ear or nominal per row and asserts every playhead call reached the output. An inferred edge can therefore never be mistaken later for one he actually heard. That distinction immediately corrected the board. It had named #10 and #12 as the soft edges, taken from the recovered tracklist's unresolved list. The setlist ear file supersedes that: ten starts (#2-#11) are playhead calls, #1 is the origin, and the inferred ones are #12 LiveCode Parade, #13 Vague de CRIME and #14 Outro: La Dub Sirène. #10 PunkAChien was ear-called all along — "perfect cut at 48:27.4 into PunkAChien!". Three tracks to audition, not two, and a different three. The board also claimed 11 decided boundaries; there are 10. Titles resolve authored -> OPAL-release -> catalog -> NEEDS_PLN, and never by title-casing a slug. The authoritative source for a shared track is what actually SHIPPED: OPAL-26's ear-signed segments_v4.json joined to that gig's tracks.json on performance order, since neither file alone holds both the score path and the released title. Four tracks were in no shipped release and no catalog entry, so the first run emitted them as NEEDS_PLN rather than inventing anything; PLN then gave all four, and they live in judge_specs/cosmicfest-2026_titles.json with value+source+locator+date per feedback_metadata_provenance. The same file carries a `score` alias, because the gig slug "mafia" is mafia_sans_serif.tidal — and that alias then cross-checked itself, yielding a declared 160 BPM that matches OPAL's Mafia exactly. Outro: La Dub Sirène has no .tidal at all, being a played outro rather than a composed track, which is also why the catalog can never hold its title: the catalog is keyed by score path. `album` is deliberately absent from the spec. CosmicFest 2026 has no page under content/lives/2026/, so there is no canonical set title to copy, and inventing one would be exactly what feedback_metadata_vs_mastering forbids. The source measures better than "raw stage mic with FOH effects" suggests: I = -25.2 LUFS, true peak -5.1 dBFS, LRA 11.1 LU over the full 62:59. Not clipped, not crushed, just quiet — reaching -14 LUFS needs about +11 dB and therefore limiting, but that is a gain problem rather than a repair job. Recorded in the spec's sourceProvenance so the next pass starts from the number. apply_boundaries output: 14 tracks, 63.0 min kept of a 63.0 min master, zero gaps, all assertions green. variants still point at mastered files that do not exist; the mix is the next step and render_release will say MISSING until it runs.
Showing
armada/tide-table/setlist_to_segments.py
0 → 100644
Please
register
or
sign in
to comment