Piano MIR v0.1.0

Piano MIR 0.1.0

Desktop GUI and command-line tools for known-score piano performance assessment,
with note evidence, chroma comparisons, timing feedback, and exported reports.
The original piano/music-note logo is retained in the GUI and native app icons.

macOS (Apple Silicon)

Unzip Piano-MIR-0.1.0-macos-arm64.zip, then drag Piano MIR.app to
Applications and open it. Requires macOS 11 or newer on an Apple Silicon Mac.
This build is ad-hoc signed, not Apple Developer ID signed or notarized; macOS
may require approval in System Settings > Privacy & Security on first launch.

The app stores its working files and rust_outputs under
~/Library/Application Support/Piano MIR/. The CLI is inside
Piano MIR.app/Contents/MacOS/rust_piano_mir; run it from a terminal with your
own input/output paths. Intel Macs are not supported by this archive.

Windows (x86-64)

Unzip the Windows archive to a writable folder and double-click
Launch Piano MIR.cmd. Keep the accompanying folders beside the executables.
The GUI executable contains the original logo for Explorer and shortcuts.
The Windows executables are not Authenticode signed.

Inputs and examples

Use your own matching score JSON and WAV via the GUI file pickers. The public
repository includes a Minuet MIDI but does not include the Minuet
score.json and audio.wav; the Run Minuet Demo action needs those files.
The release does not add or claim to include this missing recording.

Small CSV examples are included for a CLI smoke test:

rust_piano_mir --score examples/score_regions.csv --audio examples/audio_regions.csv --out rust_outputs/aligned_regions.csv --summary-out rust_outputs/assessment_summary.json

Prefix with the executable path (and use .exe on Windows). See the main
README for the score format, MIDI conversion, assessment presets, and reports.

Rebuilding

Use the checked-in lockfile. On macOS run bash scripts/package-macos.sh.
On Windows with Rust and the Visual Studio C++/Windows SDK build tools, run
powershell -File scripts/package-windows.ps1. Packages are written to dist/.
The release workflow tests and packages both platforms, and creates a GitHub
release with ZIP archives and SHA-256 checksums when a matching version tag
(such as v0.1.0) or release branch (codex/release-0.1.0) is pushed.