This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | |
| lwc:musescore [2026/09/17 11:35] – John Harrison | lwc:musescore [2026/09/17 11:37] (current) – [Verifying a Merge Against Real Playback] John Harrison |
|---|
| If apt complains about ''_apt'' sandbox permission denied on the local file, move the .deb somewhere ''_apt'' can read first: ''''sudo cp powershell.deb /tmp/ && sudo apt install -y /tmp/powershell.deb''''. This usually means your home directory's permissions are blocking the ''_apt'' user from traversing into it. | If apt complains about ''_apt'' sandbox permission denied on the local file, move the .deb somewhere ''_apt'' can read first: ''''sudo cp powershell.deb /tmp/ && sudo apt install -y /tmp/powershell.deb''''. This usually means your home directory's permissions are blocking the ''_apt'' user from traversing into it. |
| |
| ===== Verifying a Merge Against Real Playback ===== | |
| |
| Useful technique for confirming a merged/edited score's timing actually matches what MuseScore will play, without needing to reverse-engineer tempo/time-signature math by hand: | |
| |
| - Solo the Metronome channel in the Mixer and export just the click track as WAV (see Playback section above). | |
| - Detect click onsets from the waveform (short percussive transients — a simple amplitude-threshold peak search works well; MuseScore's metronome accents downbeats at a measurably louder amplitude than other beats, which lets you segment the clicks into per-measure groups automatically). | |
| - Compare the click count per measure against the beats-per-measure implied by each measure's time signature in the score's XML — mismatches pinpoint exactly which measure has a structural problem (missing section break, unexpected pickup/irregular measure, etc.) far faster than guessing from the notation alone. | |