|
Rust CI fader_master passed CI.
MadGobblins/fader_master/pipeline/head This commit looks good
Details
Add adopt and ordered restore startup behavior, confirmed fake readback, unavailable and reconnect transitions, bounded exponential retry, disconnect invalidation, joined worker cancellation, and drain-before-checkpoint shutdown. Record the verified M3 hardware-free milestone. Tests: cargo fmt --all -- --check; cargo check --workspace --all-targets --all-features --locked; cargo test --workspace --all-targets --all-features --locked; cargo test --workspace --doc --all-features --locked; cargo clippy --workspace --all-targets --all-features --locked -- -D warnings; cargo build --workspace --release --all-features --locked; cargo check --workspace --all-targets --no-default-features --locked; cargo test --workspace --all-targets --no-default-features --locked (all pass) |
||
|---|---|---|
| config | ||
| core | ||
| docs | ||
| examples/profiles | ||
| fader_master | ||
| midi | ||
| scripts | ||
| sound | ||
| tui | ||
| .gitignore | ||
| AGENTS.md | ||
| Cargo.lock | ||
| Cargo.toml | ||
| Jenkinsfile | ||
| LICENSE | ||
| README.md | ||
| architecture.md | ||
| rust-toolchain.toml | ||
| task.md | ||
README.md
fader_master
Linux application volume and mute control from one or more USB MIDI surfaces.
This repository currently contains tested domain and configuration libraries plus an interactive TUI shell. The domain layer supports matching, routing, balanced group volume plans, and mute intent. Atomic TOML persistence and checkpointing are implemented; the server, audio adapters, persistent bindings, and configuration editor remain planned in the following documents:
- Architecture and library research
- Implementation tasks and acceptance tests
- Project-agent instructions and test/commit workflow
- Build prerequisites and MSRV
- CI coverage and badge lifecycle
Run the TUI
cargo run --locked -p fader_master
Use the arrow keys to move the demo fader, Home/End for its endpoints, and Q or Escape to quit. The screen currently uses local demo state; live server and audio integration follow in M3–M8.