feat(set): d10 is the riser — 7 tracks get PLN's safe idiom, and d5 stops flattening (#33, #99)
PLN: "can you add a safe riser on all set tracks that dont have one, and consider
moving the d10 to d9 (eg a synmenace iirc) to have d10 riser always?"
THE CONVENTION. d10 = riser, so the gesture lives on the same column in every track
and his hands stop having to remember per-track. It was already true in three tracks
without anyone naming it — do_it_right (mask "<f!4 t f!3>"), take_5_drops (the
"A FAIR RISER" comment on d10) and vague_de_crime, whose line #33 designates as THE
safe riser because a 1-in-8 mask cannot run away:
d10 $ gF1 $ gM3 $ mask "<t f!7>" $ "risers:8"
Copied verbatim into the 7 tracks where d10 was free: bombe_dj, wap, lime_tacos,
you_my_sunshine, mafia_sans_serif, desire, electric_hammer. Inserted contiguous with
the existing d-blocks, because all three pre-existing risers live inside the main
block rather than standalone — a riser in its own block would need a separate
ctrl+enter, which is not the gesture. 10 of 15 tracks now have it.
WHY THE RELOCATION IS NOT IN THIS COMMIT. "Consider" did real work here. The two
tracks PLN was remembering are piment_bresilien (d10 = Menace, d9 free) and
ouais_je_funk (d10 = SynMenace, only d12 free) — but moving an orbit is not a
one-line move, because orbit N is simultaneously the LCXL column, the Ardour track
and the cut/crushbus group:
piment's d10 block carries -- A6 = d10's effect on its crushbus CC ^18
d9's fx CC is ^17, d12's is ^20 -> the CC must move with the sound
Ardour Tidal 10 = -2.2 dB, Tidal 09 = +6.0 dB, Tidal 12 = +6.0 dB
-> the synth lands +8.2 dB louder
And the argument that settles it: perfect, gimme_acid and the_revolution declare all
12 orbits, so d10 is never free there and the convention caps at 12/15 no matter what.
Relocating buys 2 tracks for two CC remaps, a cut-group change and two synths jumping
+8.2 dB — on material PLN has not rehearsed since, 7 days out. Deferred by choice, not
forgotten; his call to overrule.
#99, d5 of take_5_drops: `>|` takes structure from the RIGHT, so `slow 4` note
patterns were REPLACING the slice rhythm with one event per four cycles — the
"steals structure" symptom, confirmed. Now `|>`, which keeps the left structure and
takes only the note value. Note line 35 immediately above was already doing it that
way, so this makes the block self-consistent rather than inventing an idiom. Marked
TODO @pln verify as asked.
Also ouais_je_funk d10 read `gF3 $ gF3` — the same helper twice, so the orbit had no
family mute and NOTHING on the surface could drop it (pvlint PV013). Now `gF3 $ gM3`.
Also TODO @pln verify.
VALIDATION: all 15 setlist tracks still compile (gig-up "setlist compiles" green,
silent-eval cold-queries every dN), preload still covers the set at 53/53 banks, and
pvlint added zero new findings — still the one pre-existing error, lime_tacos' ^44
driving both d3 and d6. That one is left alone deliberately: ^44 is neither orbit's
home gate (d3 = ^43, d6 = ^58/^90), so fixing it means rebinding a button PLN's hands
already know, which is a taste call and not lint's to make.
Showing
Please
register
or
sign in
to comment