fader_master/checklist.md

3.8 KiB

Functional Pulse milestone checklist (Arch Linux + PipeWire)

This checklist validates the first real-audio milestone against your Arch user audio session. The fixture uses Arch's libpulse client library to talk to PipeWire's pipewire-pulse compatibility service; it does not install or run the standalone PulseAudio server, and it does not parse or invoke pactl. It changes only the sink-input index you explicitly select and refuses amplification above unity.

Preparation

  • Install or confirm the Arch packages used by this milestone: sudo pacman -S --needed base-devel pkgconf libpulse pipewire-audio pipewire-pulse wireplumber. (libpulse is the Arch package name; there is no separate libpulse-dev.)
  • Run pactl info and confirm Server Name contains PulseAudio (on PipeWire ...) rather than reporting a connection error.
  • If that check fails, inspect the user units with systemctl --user status pipewire pipewire-pulse wireplumber --no-pager. PipeWire normally starts them through user socket activation, so do not enable or start the standalone pulseaudio service.
  • Start continuous playback in a disposable application or browser tab.
  • Record that application's current volume and mute state so you can restore them after testing.

Discovery and metadata

  • Run cargo run --locked -p volume_lib --example pulse_fixture -- list.
  • Confirm the playing application appears with a numeric index, useful application/binary metadata, one or more channel gains, mute state, and writable=true.
  • Note whether any native-only PipeWire playback nodes are absent. This milestone intentionally sees the streams exposed through pipewire-pulse; direct native-PipeWire discovery belongs to the later native adapter milestone.

Confirmed volume and mute control

Replace INDEX below with the selected sink-input index.

  • Run cargo run --locked -p volume_lib --example pulse_fixture -- volume INDEX 0.35.
  • Confirm the application audibly changes and the command prints a readback whose loudest channel is approximately 0.35.
  • If the stream has unequal left/right gains, confirm their balance remains unequal in the same proportion after the change.
  • Run cargo run --locked -p volume_lib --example pulse_fixture -- mute INDEX on and confirm audio is muted without changing its channel gains.
  • Run cargo run --locked -p volume_lib --example pulse_fixture -- mute INDEX off and confirm audio returns at the prior gain.

External changes and lifecycle

  • In one terminal run cargo run --locked -p volume_lib --example pulse_fixture -- watch 30.
  • During those 30 seconds, change the application's volume and mute state in your desktop mixer; confirm each change produces an updated fixture line.
  • Stop and restart playback; confirm the watcher reports removal and then a newly discovered sink input without crashing.
  • When interrupting audio is acceptable, run systemctl --user restart pipewire pipewire-pulse wireplumber, then repeat the watch. A clean connection error is acceptable for this bounded fixture; record it so reconnect behavior can be verified in the full worker integration.

Restore and report

  • Restore the application's original volume and mute state.
  • Run cargo test --workspace --all-targets --all-features --locked and confirm it passes with your native libpulse installation.
  • Report the Server Name shown by pactl info and any unchecked or failed item, including the fixture's exact error text.

The main TUI is still explicitly backed by demo state at this milestone. Passing this checklist validates the real Pulse control boundary that will feed the server and live multi-application/group TUI; it does not yet validate MIDI or the final TUI-to-server path.