Commit 5b0ad50d by PLN (Algolia)

docs(gig): green gate, and the rehearsal is the whole remainder

0 fail / 3 warn / 39 ok with the rig warm, 132/132 banks, 0 xruns per hour —
the 457/hour this morning was the dead NVIDIA sink, not the CPU.

Five learnings archived from the morning, all one shape: a check that asks the
wrong question reports success. A resolver matching hardware by product name
outlived the hardware in three files at once; a capability check that asked
'is the tool installed' wrote midi:true over nine empty sessions; a probe
gated on a precondition it did not need skipped the entire setup window; an
availability flag structurally incapable of being false hid a disconnected
cable for months; and a unit's start time is the only thing that distinguishes
running code from readable code.
parent a606d992
...@@ -460,3 +460,39 @@ correct whether or not the driver runs. ...@@ -460,3 +460,39 @@ correct whether or not the driver runs.
- [ ] **YOU: the 2h run with Ardour recording.** Unmoved since Sunday. It is the - [ ] **YOU: the 2h run with Ardour recording.** Unmoved since Sunday. It is the
only check that has never been run, and the only one that can still only check that has never been run, and the only one that can still
surprise you. surprise you.
## Wed 23, 10:40 — the rig is green and the rehearsal is the whole remainder
`check-gig`: **0 fail, 3 warn, 39 ok, 1 skipped.** `xrun rate 0/hour` — the
457/hour reading this morning was the dead NVIDIA sink, not a perf problem.
SuperDirt: `PRELOAD: 132/132 banks OK in 6.8 s`, server ready.
Fixed today, all pushed (a606d99): the audio (laptop card back on HiFi, NVIDIA
pin retired), the LCXL3 driver (started; its 1077 failures were a resolver
looking for the ORIGINAL board's name), midiviz (v3 map moved into the grid, so
any reader of the board is right), the gate's painter probe (was skipping every
cold run), gig-log's MIDI leg (had never bound a port in nine sessions), and a
stale-build detector.
### The three remaining warns, none blocking
- **audio profiles** — `50-alsa-config.conf` is 0.5 format on an 0.4.17
install, so it is dead config that looks like protection. Post-gig.
- **cpu governor** — daytime mode on a work laptop. `gig-up` does the perf pass.
- **monitor path** — headphones fold shows 2/28 links, d2-d14 unreachable
without Ardour. Expected with Ardour closed; the rig routes through it.
### YOURS, and it is the only thing left
- [ ] **The 2h arc, with Ardour recording.** This afternoon, or tonight after
the speaker dinner. Never once run. Everything else is green.
- [ ] **Plug the UMC202HD for the last stretch** and run
`tools/check-audio-graph.sh` with it present. Thursday's output path, and
the only one nobody has tested — the same UCM failure that ate the sof
card's HiFi can hit the UMC's when it enumerates.
- [ ] **Master fader**: `check-mix` reads the SAVED session, and Ardour OSC is
still off, so Ctrl+S before trusting a green fader line.
- [ ] After the run: the MIDI log is now real. `~/.local/share/parvagues/gig-log/`
carries `cc` records with `n / v0 / v1 / lo / hi` per control per second,
in corpus numbering — so "minute 23:30 the bass is too saturated" is
answerable from the file afterwards.
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