| Name |
Last commit
|
Last update |
|---|---|---|
| .. | ||
| api | ||
| escales | ||
| manifeste | ||
| semaphore | ||
| tasks | ||
| tide-table | ||
| ui | ||
| .gitignore | ||
| DESIGN.md | ||
| PRODUCT.md | ||
| README.md | ||
| ardour_faders.json | ||
| serve.py | ||
| setlist_opal2026.txt |
Eight commits of rig work that had accumulated on the branch while the shared
checkout sat on it. Reviewed as a diff, not taken on faith:
perf.sh stop DWIM-launching Pulsar into /usr/local/sbin -- 183
SIGABRTs between 08-19 and 09-05 because BASH_SOURCE resolved
to the deploy path, and the perf watcher re-entered every 30s.
rig_units.py neither LCXL painter may be auto-started blind; gig-up.sh's
generation-aware chooser owns that decision.
midiviz its own Wayland app id (desktopFileName, not applicationName),
so focus and KWin rules can name this window and no other;
plus the CC readout PLN asked for while wiring.
logs 040/041 the phantom port, and the GIG UP rewire parked behind the
Ardour double-launch bug.
The four other branches were already upstream by patch-id.
# Conflicts:
# TASKS_DUMP.md
| Name |
Last commit
|
Last update |
|---|---|---|
| .. | ||
| api | Loading commit data... | |
| escales | Loading commit data... | |
| manifeste | Loading commit data... | |
| semaphore | Loading commit data... | |
| tasks | Loading commit data... | |
| tide-table | Loading commit data... | |
| ui | Loading commit data... | |
| .gitignore | Loading commit data... | |
| DESIGN.md | Loading commit data... | |
| PRODUCT.md | Loading commit data... | |
| README.md | Loading commit data... | |
| ardour_faders.json | Loading commit data... | |
| serve.py | Loading commit data... | |
| setlist_opal2026.txt | Loading commit data... |