feat(gig): 1-click ordered launcher — SuperDirt-first, then Ardour, killing the MIDI dance
Start-of-gig pain: whichever of SuperDirt or Ardour opens the LaunchControl XL first wins it, and when Ardour wins, sclang can't get the controller → the manual "disconnect MIDI / reconnect MIDI" dance mid-setup. The fix is ordering + a real readiness gate. gig-up.sh (repo root): brings SuperDirt up FIRST and WAITS until it has actually claimed the controller, then launches Ardour + Pulsar. Readiness = three unambiguous signals, all of which appear during main_fairbanks.scd's boot: scsynth alive + UDP :57120 listening (SuperDirt.start) + a "SuperCollider" ALSA-seq client present (MIDIClient.init has run). 120s timeout (sample loads can be slow) → proceeds with a clear warning rather than hanging. Best-effort throughout: terminal auto-detected (konsole/kitty/…, background-log fallback), Ardour/Pulsar binaries probed by name, skips SuperDirt if scsynth is already up. gig-boot.scd: one eval that runs the real boot (main_fairbanks.scd) + the LaunchControl CC->OSC bridge (start_and_midi.scd) so the rig comes up fully armed in a single file; loaded by relative path to stay portable. Validated offline: bash -n clean; the three probes correctly read 'down' with SuperDirt dead; ardour9 + pulsar resolve; the Tidal Multi session path exists. End-to-end (the live MIDI gate) to be confirmed on the next real boot.
Showing
gig-boot.scd
0 → 100644
gig-up.sh
0 → 100644
Please
register
or
sign in
to comment