Commit 39ca4def by PLN (Algolia)

docs(board): the two-set release board — and CosmicFest is a better tape than we thought

PLN reframed the north star: not one release but four deliverables — {OPAL,
COSMIC} x {continuous club mix, per-track album split}. The board only tracked
OPAL, so this amendment measures both sets against the same scorecard instead
of recalling their state.

The four questions he asked, answered from the filesystem rather than memory:
boundaries are DONE for BOTH sets (OPAL ear-signed 2026-08-16, CosmicFest
2026-08-29 — 11 playhead calls plus 8 skip notes). The mix is done and
ear-reviewed for OPAL only. CosmicFest has had zero mastering: its ear pass
settled WHERE the cuts are, never HOW it sounds — there is no mix to review.

Two findings worth more than the status table.

The CosmicFest master has exactly ONE copy, and it is in ~/Downloads. 151 MB,
not on the freebox, not in Prod/. feedback_freebox_ssot says the freebox is the
SSOT for audio; an irreplaceable gig recording in a scratch directory is the
highest-risk, cheapest-to-fix item on the whole board. Filed as R-0, ahead of
all processing. Adjacent trap recorded too: Prod/cosmicfest/ and
Prod/cosmicfestv0.live1.* are the 2025 edition (files dated 2025-06-27/28) —
nothing there belongs to this release, and the names invite exactly that error.

And the tape is far better than "raw stage mic with FOH effects" implies.
Measured with ebur128 over the full 62:59: I = -25.2 LUFS, true peak -5.1 dBFS,
LRA 11.1 LU. The peak says it was recorded conservatively and is NOT clipped;
the 11.1 LU range says the desk did NOT crush the dynamics (a mangled feed lands
under 6). It is simply quiet — reaching -14 LUFS needs ~+11 dB and therefore
limiting, but that is a gain problem, not a repair job. PLN's "80/20 likely" is
reachable; what is genuinely impossible is a premix, because one stereo file has
no stems and none of OPAL's per-orbit surgery has an analogue.

The keystone follows from POSTPROD.md's own rule — "a new gig is a copy of
judge_specs/<gig>.json, never a copy of a script". That file does not exist for
CosmicFest, and BOTH of its deliverables sit downstream of it. One wrinkle to
settle while writing it: OPAL's spec assumes stems (stemsDir, stemmap, keeps,
clipsDir) and CosmicFest has none, so the stemless path must be verified rather
than assumed.

Six decisions are logged as PLN's, not the tooling's: the still-unreviewed merge
2f947c2c; whether the A2 REVOLUTION fix is worth invalidating the A1.7 signoff it
would force a re-render of; whether "Outro Dub Siren" is an album track or
mix-only; the two soft CosmicFest edges (#10, #12) inferred from skip notes
rather than called on the playhead; the rights ledger re-measured at 103 banks
(43 third_party, 31 unknown, 19 dirt_samples, 10 cleared), which gates the split
but not the mix; and artwork, still unchosen for both.

Also traced the collab thread: piment_bresilien is in BOTH sets — OPAL track 07,
already on SoundCloud, and CosmicFest #7 at 2145.6-2525.4 on a playhead call.
Its score carries one uncommitted edit, line 33, |+ note 12 becoming |- note 12.
parent 2f947c2c
...@@ -1128,3 +1128,107 @@ words where they exist. IDs are stable; reference them in commits. ...@@ -1128,3 +1128,107 @@ words where they exist. IDs are stable; reference them in commits.
paint-reset culprit; that mystery is REOPENED with no suspect. paint-reset culprit; that mystery is REOPENED with no suspect.
- Midi-Thru→SC re-add explained: SuperCollider's own `MIDIIn.connectAll`. - Midi-Thru→SC re-add explained: SuperCollider's own `MIDIIn.connectAll`.
- A1 label off-by-one DISPROVEN ("d9 level [ard]" is correct). - A1 label off-by-one DISPROVEN ("d9 level [ard]" is correct).
---
## AMENDMENT — 2026-09-01, the two-set release board *(session-planning)*
PLN's declared goal, verbatim: *"release the tracks finish both Opal set and Cosmic
set release of both 1. their one live club mix, and 2. the album split"* — plus an
acknowledgement that sets the CosmicFest bar: *"i ack cosmicset is a raw record from
stage with effects, we can only do our best, 80/20 likely"*.
So the north star is now **four deliverables, not one**: {OPAL, COSMIC} x {continuous
club mix, per-track album split}.
### The scorecard (measured this session, not recalled)
| | OPAL-26 "Sunset Forest" | COSMICFEST-26 |
|---|---|---|
| source | 12 orbit stems + master, 48 k/24-bit | **ONE stage mic MP3**, 320 k/44.1, 62:59 |
| source location | `Prod/Opal26_master/` | **`~/Downloads/ZOOM0067.MP3` — single copy** |
| boundaries | ✅ ear-signed 2026-08-16 | ✅ ear pass 2026-08-29 (11 decided + 8 skipped) |
| setlist | 14 tracks (Desire cut) | 14 tracks, `cosmicfest-2026_setlist_ear.json` |
| gig spec | ✅ `judge_specs/opal26.json` | 🔴 **DOES NOT EXIST** |
| segments | ✅ `segments_v4.json` | 🔴 none |
| mix / master | ✅ v4 premix, streaming + club | 🔴 nothing rendered |
| album split | ✅ 14 x 2 variants | 🔴 none |
| club mix | ✅ 2 x `*_nodrop.flac`, 72.7 min | 🔴 none |
| ear review of the MIX | ✅ A1.7, on the rendered files | ⛔ impossible — no mix to review |
| published | 🟡 8/15 SC, private, 2 defects | 🔴 nothing, and no www page |
**Answering the four questions directly:** boundaries are DONE for *both* sets. The
mix is done and ear-reviewed for OPAL *only*. CosmicFest has had zero mastering work —
its ear pass covered *where the cuts are*, never *how it sounds*.
### 🔴 R-0 · The CosmicFest master has exactly one copy, in Downloads
`~/Downloads/ZOOM0067.MP3`, 151 MB, 2026-08-28. Not on the freebox, not in `Prod/`.
Per `feedback_freebox_ssot` the freebox is the SSOT for audio; an irreplaceable gig
recording sitting in a scratch directory is the single highest-risk item on this
board and the cheapest to fix. **Do this before any processing.**
(Note the naming trap: `Prod/cosmicfest/` and `Prod/cosmicfestv0.live1.*` are the
**2025** edition — files dated 2025-06-27/28. Nothing there belongs to this release.)
### 📏 The CosmicFest source is far better than "raw stage mic" implies
Measured with `ebur128` on the full 62:59: **I = −25.2 LUFS · true peak −5.1 dBFS ·
LRA 11.1 LU**. Read that as three pieces of good news:
- **−5.1 dBFS peak** = it was recorded conservatively and is **not clipped**. There is
real headroom to work with, not a squashed brick.
- **LRA 11.1 LU** = the FOH chain did **not** crush the dynamics. A mangled desk feed
typically lands under 6 LU.
- **−25.2 LUFS** = it is simply *quiet*. Reaching −14 LUFS streaming needs ~+11 dB,
which will demand limiting, but that is a normal gain problem, not a repair job.
The 80/20 is therefore genuinely reachable: gain-stage, broadband/room EQ,
harshness control, limit. **No premix is possible** — one stereo file, no stems, so
none of OPAL's per-orbit surgery (the d4 trim, the d5 cut) has an analogue here.
### 🔑 KEYSTONE · C-0 — write `judge_specs/cosmicfest-2026.json`
`POSTPROD.md` is explicit: *"A new gig is a copy of `judge_specs/<gig>.json` — never a
copy of a script."* That file is the **only** thing standing between CosmicFest and
the entire existing pipeline (`apply_boundaries``render_release`
`build_release_joins``build_release_plan` → the SC/YT/BC adapters). Both CosmicFest
deliverables sit downstream of this one file.
One known wrinkle to resolve while writing it: OPAL's spec assumes stems
(`stemsDir`, `stemmap`, `keeps`, `clipsDir`). CosmicFest has none. Either the spec
grows a stemless mode or the tools must tolerate absent stem fields — **verify, do
not assume**, per `feedback_verify_the_plumbing`.
### Open decisions that need PLN, not code
- **D-1 · the unreviewed merge `2f947c2`.** Still standing on master. PLN's own plan:
*"ill review migration diff and midiviz tomorrow"*. Nothing else should touch master
until this lands.
- **D-2 · A2 REVOLUTION mix fix vs the A1.7 signoff.** Cutting d5 requires a re-render,
and the board states plainly that any re-render **invalidates the ear signoff**.
Ship OPAL as signed, or re-cut REVOLUTION and re-get the ear on that one track?
- **D-3 · Is "Outro Dub Siren" (#14, 103 s) an album track?** PLN's note was a laugh —
*"pure dubsiren noise and fun ahahah it could be called 'Outro Dub Siren'"*. It
clearly belongs in the club mix. Whether it ships as a numbered track is a call.
- **D-4 · Soft edges.** CosmicFest #10 `punkachien` and #12 `livecode_parade` were
inferred from adjacent skip notes, not called on the playhead. They are the two
boundaries most likely to need an ear before rendering.
- **D-5 · Rights gate the album split, not the club mix.** `rights_ledger.json`
re-measured: **103 banks — 43 third_party, 31 unknown, 19 dirt_samples, 10 cleared**.
PLN's rule stands: *"cant push the single tracks when samples hit, but full mix might
well pass!"* This is the argument for shipping **club mix first, split second** on
every public platform.
- **D-6 · Artwork.** Still none chosen for OPAL; the `output/*.jpg` set was rejected as
GenAI of unknown provenance. CosmicFest has none either.
### Collab thread — piment_bresilien
PLN: *"my friend wants to collab on one of the cosmicfest lineup tracks, i think
piment bres."* Confirmed present in **both** sets — OPAL track 07 (rendered, and
already uploaded to SC as `/piment-bresilien`) and CosmicFest #7 (2145.6→2525.4,
379.8 s, an ear-called playhead boundary: *"starting at 35:45.6 i hear proper only
piment start sound"*). Score lives at `live/collab/raph/piment_bresilien.tidal`
(103 lines, 12 orbits) and carries **one uncommitted edit** — line 33,
`-- |+ note 12.``|- note 12`, i.e. the melodic layer transposed down an octave
instead of up. Decide whether that edit is the collab's starting point before
branching.
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment