Commit 99ec9556 by PLN (Algolia)

gig: liquid_nite does not compile, and it is track 3 of the set

The full gate caught what the fast one skips. An uncommitted edit to
liquid_nite.tidal left '$ midiOn "^58" (iter 4 . )' -- a dangling composition
operator, so the section types as a function-to-function instead of a
Pattern ValueMap endomorphism, and since it is one do block EVERY dN in the
track is dead. He played it fine at 00:19 (driver logged eval=cycle 0 four
times) and edited it after, so it is a thought left mid-air at bedtime.

Both fixes verified with silent-eval --seeded on COPIES, without touching his
file, because which one he wants is musical: dropping the dot keeps both of
tonight's additions and compiles; reverting the file also compiles but discards
them, and needs Pulsar closed on that buffer first.

Also triages the rest of the 43-check run, and says plainly which failures are
mine. preload-covers-set now FAILS because tonight's parser fix made five banks
visible that the generated preload was never built for -- the gate is right and
that file gets regenerated WITH him, not unilaterally. And the 379/hour xrun
warning is my own churn: every burst timestamps to a command I ran, while the
last five idle minutes are zero.
parent 42251f09
......@@ -876,3 +876,87 @@ trade, and no pick.
4. Plug the **Dell barrel charger**, re-assert the gear, read the cap. Decide (a)
or (d) above with the rehearsal's ears.
5. `systemctl --user start midiviz` if you want the lens.
## 🔴 Thu 24, 01:25 — READ FIRST: `liquid_nite` (track 3 of 17) DOES NOT COMPILE
The full gate found it. Your **uncommitted** edit to
`live/midi/nova/lounge/liquid_nite.tidal` left a dangling composition operator:
```
line 46: $ midiOn "^58" (iter 4 . )
^ nothing after the dot
```
```
liquid_nite.tidal:46:21: error:
• Couldn't match type: a0 -> Pattern c0 with: Pattern ValueMap
• In the second argument of 'midiOn', namely '(iter 4 .)'
```
`(iter 4 . )` is a section of `.`, so it types as a function-to-function rather
than a `Pattern ValueMap -> Pattern ValueMap`. It is one `do` block, so **every
`dN` in liquid_nite is dead**, not just d6. You played the track fine at 00:19
(the driver logged `track ~ liquid_nite … eval=cycle 0` four times) and edited it
after, so this is a mid-thought left on the desk when you folded — you were
clearly about to chain something onto that dot.
**Two fixes, BOTH verified by `silent-eval --seeded` on copies tonight — I did not
touch your file, the choice is musical:**
- **Finish the thought or drop the dot.** `$ midiOn "^58" (iter 4)` →
`liquid_nite: ok, every declared orbit emits`. Keeps both of tonight's
additions: the new `^58 iter 4`, and the `^90 (ply "4 <8 16>")` you
uncommented. **One character. This is almost certainly what you want.**
- **Or revert the file.** `git checkout -- live/midi/nova/lounge/liquid_nite.tidal`
→ also `ok`. But it throws away both of tonight's lines, and **close Pulsar on
that file first** — a checkout under a live editor buffer is how the editor
writes the old text back over it.
Re-run `python3.12 tools/silent-eval.py --seeded --setlist armada/setlist_thu24.txt`
after, and expect 17/17. The other 16 are `ok` right now.
### The rest of the gate, triaged — 01:25, full run, 43 checks
`31 ok · 6 fail · 5 warn · 1 skipped` — and here is what each failure actually is,
because three of them are consequences of tonight's work rather than new faults:
- ✗ **setlist compiles** — the `liquid_nite` dot, above. **The only one that can
silence a track on stage.**
- ✗ **preload covers set** — **caused by tonight's parser fix, and it is the fix
working.** `extract_names` now sees `808bd`, `808cy`, `808hc`, `808sd` and
`90s_synatm`, which the generated `preload.scd` was never built for because the
old parser read them as `bd`/`hc`/`sd`. So the gate is right and the preload is
genuinely short by five banks. `tools/check-preload.sh --fix` then an SC restart
— **do it WITH PLN**, per the standing rule about that generated, gitignored,
load-bearing file (it "debuted as a crackle at the venue"). I did not regenerate
it unilaterally.
- ✗ **fader baseline** + ✗ **ardour faders** — your desk, your hands. Raise the
Master, **Ctrl+S**, re-run. `check-mix` reads the SAVED session and `use-osc=0`,
so no tool can see the live desk. Already on the 5pm list.
- ✗ **cpu energy bias** + ✗ **clock ceiling** — `thermal-pilot` rung 1, explained
above. **Note the gate's suggested fixes for these two cannot work**: `echo 100 >
max_perf_pct` is reasserted in 6 s and `cpupower set --epp performance` likewise.
Post-gig, those two fix strings should name the pilot instead of handing you a
command that loses.
- ! **xrun rate 379/hour** — **contaminated by me, disregard it.** Every burst in
this session timestamps to a command I ran: 01:02 was the SuperDirt restart
storm, 01:12 the `thermal-mode-apply` probe, 01:16 the patch simulation and the
gate itself. With the rig merely sitting, the **last 5 minutes are 0 xruns**, and
the clean 14-minute window after demoting Ardour's threads was measured *at* the
65 % cap. Re-measure with your hands on the board and nothing else running.
- ! **SC un-killable** — that is `parvagues-protect` being off on purpose. Step 3
of the morning list closes it.
### Morning list, final order
0. **`liquid_nite` line 46** — one character. Everything else can wait; this cannot.
1. `sudo systemctl start thermald` — my bad call, 30 seconds.
2. `sudo tools/fix-ardour-rt.sh` → read the diff → `--apply` → the acceptance test
it prints (**launch Ardour from the DESKTOP ICON**; a terminal or Bridge launch
inherits `unlimited` and proves nothing).
3. `sudo systemctl start parvagues-protect` — only after step 2.
4. `tools/check-preload.sh --fix` **together**, then one SC restart (which also
warms `90s_synatm` and finally loads `s.latency 0.1` — watch the `late` count).
5. Plug the **Dell barrel charger**, re-assert the gear, read `max_perf_pct`. The
cap may close for a cable.
6. Master fader → **Ctrl+S** → re-run the gate. Target: only the cap items left.
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