fader_master/checklist.md

3.3 KiB
Raw Blame History

fader_master hands-on checklist (Arch + PipeWire)

Automated tests cover validation, buffering, IPC, rollback, rendering, and atomic persistence. This checklist is only for behavior requiring your real PipeWire session, APC MINI, applications, and terminal.

Setup

Use a disposable profile directory so editor Save does not modify tracked examples:

work=/tmp/fader-master-check
mkdir -p "$work"
cp examples/profiles/{arch-pipewire,desktop}.toml "$work/"
cargo run --locked -p fader_master -- serve \
  --config "$work/arch-pipewire.toml" --audio pulse

In another terminal:

cargo run --locked -p fader_master -- tui

Known mappings: Music CC48/Note64, Browser CC49/Note65, Media sync CC50/Note66, and Master CC56/Note98. The profile polling interval is 10 ms and accepts 1–100 ms.

Mixer smoke test

  • TUI shows Music, Browser, Media, Master, and the APC backend ID; startup does not change any live volume or mute.
  • CC48/49 control only their applications; CC50 sets both Media members to one absolute value; CC56/Note98 affect only the default output.
  • Pickup starts waiting, becomes tracking only after crossing the live value, and returns to waiting after an external volume change.
  • A rapid fader sweep stays responsive and converges to its last position; rapid double mute presses preserve both edges.
  • With Browser offline, its controls are nonfatal and are not replayed when Browser starts.

Profile switching and recovery

Both disposable profiles are siblings, so while the server is running:

cargo run --locked -p fader_master -- profile switch desktop
cargo run --locked -p fader_master -- profile switch arch-pipewire
  • Each successful switch changes the profile shown in Config, preserves observed live audio without a write, and requires pickup again.
  • A missing/invalid profile reports an error and leaves the old profile active. A switch attempted during pending fader work returns an actionable retry error instead of crossing generations.
  • Stop the server while TUI remains open: rows stay visible, the error is internal to the TUI, and restart reconnects without replaying input. local socket operation failed for /run/user/1000/fader_master/control.sock: Connection refused (os error 111) error is smooth but unhelpful, log the actual error and show a helpful one ?
  • Unplug/replug APC MINI: server/TUI stay alive, status changes to missing — connect device, and reconnection rearms pickup.
  • Start TUI before the server and confirm it recovers automatically when the socket appears.

Polling and report

  • Compare poll_interval_ms = 10, 5, and 2 (restart between values). Record responsiveness, CPU impact, and the lowest useful value. About the same, cpu usage a little on the higer end of what I would like tho
  • Run cargo run --locked -p fader_master -- status; confirm status=ready and expected final values.
  • Report any pre-pickup jump, wrong target, rough sweep, stale/pending value, lost mute edge, failed apply/save diagnostic, reconnect over one second, terminal corruption, or process exit.

Explicit profile switch --restore is automated but remains optional for manual testing until the MIDI output-feedback milestone is implemented.