Eight of make_cabaret_vc.py's Can Patterns on the cans pads 1-8, in a Can patterns solo frame in place of the pads frame's empty Buttons 53-60: Theater, Rainbow, Odd Even, Left Right, Scanner (with a fading tail), Fill, Center and Pairs, laid out for the test show's cans and walking the ring round the room (scripts/shows/can_patterns.py). Collapse and Chase Out are left out. The masks show the Colour 1 colour; Odd Even (a checkerboard) and Left Right swap between Colour 1 and Colour 2 through four Matrix widgets in the Chase colours frame. All of them follow the cans' Speed dial (knob 1). Each pattern is RGB matrices running from start to stop (rgbscripts/steps.js and swap.js, linked into ~/.qlcplus/rgbscripts), so a chase started over one lands on top, and the pad controller restarts the pattern that is on just after a Colour 1 press so the new colour scene doesn't cover it. The row of 4 (#3-#6) never animates; CLAUDE.md now says so for whatever comes next. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
1.9 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.
Cans 3–6 are always static
The row of 4 (#3–#6, fixture IDs 2–5) never animates. Chases, patterns, loops,
strobes and side dimmer holds leave them out, so they keep the Colour 1 scene
and their own dimmer knob whatever else runs. Their colour stays HTP, unlike the
other cans. When adding an animation for the cans, build it on the other 11
(the groups Sides and Strobe cans in test.qxw already skip them) and don't
write any FixtureVal for IDs 2–5.
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.