1.5 KiB
CLAUDE.md
Before working on the rig
At the start of a session, and before testing anything that needs the pad or the stage view, make sure the MIDI controller is working and the simulator is on:
-
Both user services are running:
systemctl --user is-active padcontroller simulatorIf either is not
active, start it withsystemctl --user start <name>. If the unit is missing, install it withpadcontroller/systemd/install.shorsimulator/systemd/install.sh. Checkjournalctl --user -u <name> -n 50if it won't stay up. -
The MIDI controller is connected and passed through:
aconnect -lIt should list the
SMC-PADclient (USBSINCO SMC-PAD-MasterorSMC-PAD Bluetooth) and thepadcontrollervirtual port. A service that is active with noSMC-PADclient means the pad is off or not paired: ask the user to switch it on rather than carrying on without it. -
The simulator answers on http://127.0.0.1:8765:
curl -sf -o /dev/null http://127.0.0.1:8765 && echo ok
shows/test.show.json (and the shows/test.qxw built from it) sends Art-Net
to 127.0.0.1 only, so testing drives the simulator and never the real rig. Keep
it that way; don't point it at a 192.168.1.x node.
Tell the user what was down and what you did about it. The preview
configurations in .claude/launch.json run separate copies on other ports
(8770, 8766) and don't count as the services being up.