Adopt a sole MIDI input when creating a managed profile, publish other unclaimed inputs to Config, and let the user add them as durable surfaces. Legacy empty profiles can add a safe Master fader, then Save and use the existing MIDI Learn flow without editing TOML. Tests: cargo test --workspace --all-targets --all-features; cargo test --workspace --doc --all-features; cargo clippy --workspace --all-targets --all-features -- -D warnings; cargo build --workspace --release --all-features; default/no-default/midir/pulse cargo checks |
||
|---|---|---|
| .. | ||
| images | ||
| README.md | ||
| build.md | ||
| ci-coverage.md | ||
| configuration.md | ||
| midi-identity.md | ||
| pulse-daemon-fixture.md | ||
| related-projects.md | ||
README.md
Documentation
Use and configuration
- Build prerequisites — Linux packages, Rust toolchain, feature combinations, and the current FreeBSD CI mode.
- Advanced configuration — process layouts, managed profiles, TOML concepts, migration, validation, and operational commands.
- Example PipeWire/APC MINI profile
- Example desktop profile
- Hands-on functional checklist
Design and development
- Architecture and library research
- Implementation tasks and acceptance tests
- Project-agent and commit workflow
- MIDI identity design
- Pulse-compatible daemon fixture
- CI coverage and badge lifecycle
Ecosystem
The README screenshots are deterministic renders of the real TUI. Regenerate them after presentation changes with:
cargo run --locked -p tui --example doc_screenshots