-
feat: cosmicfest prep · eb9221de
PLN's set work for CosmicFest, plus one new track and three mechanical fixes found by the pre-gig gate. His edits, across 23 tracks: the ^43/^44 -> ^41 control migration continued by hand (37857225 retired gMask and freed ^41 for d1's gate), and real musical work alongside it — a `resetCycles` head on rose_rouge, new `octersubbus` and `squizbus` sends, a `slow 2 $ ply 2` rework of rose_rouge's ^54 line, gain/lpf/room adjustments, and sample swaps (`n "74"` -> `n "25"` on the Savoy break). New track: live/midi/nova/techno/livecode_parade.tidal. Three fixes from the gate, none of which move a control number, so nothing changes under his hands: * mute map — d10 in something_about_drums declared gM2; the authored map (tools/lcxl_grid.py) puts d4-d12 on gM3. fix-mute-roles.py --apply, then re-run to confirm it converged to 0. * crushbus 101 in ouais_je_funk was shared by d9 and d10, with DIFFERENT ranges (16->1.5 and 16->6) landing on one bus instance — last event wins, so the knob turned for one orbit was heard on the other. d9 moved to its own 91 per the <orbit><slot> convention. * crushbus 41 in ghosts_in_the_toilets was shared by d4 and d7 the same way. d7 moved to 71. pvlint goes 4 errors -> 0 on the setlist. NOT included, deliberately: the remaining 20 column moves (ghosts 10, something_about_drums 7, perfect 2, the_revolution 1). PLN: "migration i unfinishe dgrrr lets not finish it before set for now." Renumbering which physical knob does what in four tracks he plays tomorrow is a muscle-memory change, not a safety fix, and two of the moves cannot resolve mechanically anyway (one overflow -> gSel, one FIXME with no slot). gig-up stays honestly red on `surface grid intact` until it is finished after the gig.
PLN (Algolia) authoredeb9221de
| Name |
Last commit
|
Last update |
|---|---|---|
| .. | ||
| gimme_acid.tidal | Loading commit data... | |
| la_dub_sour.tidal | Loading commit data... | |
| la_porte_de_leternite.tidal | Loading commit data... |