| Next revision | Previous revision |
| lwc:musescore [2026/09/17 11:24] – created John Harrison | lwc:musescore [2026/09/17 11:37] (current) – [Verifying a Merge Against Real Playback] John Harrison |
|---|
| |
| ^ Action ^ How ^ Notes ^ | ^ Action ^ How ^ Notes ^ |
| | Insert N measures at a point | Add → Measures → Insert Measures | Type the count, inserts before/after selection | | | Insert N measures at a point | Add → Measures → Insert Measures (or [ctrl][ins])| Type the count, inserts before/after selection | |
| | | Delete selected measures | select measures then [ctrl][del] | | |
| | Collapse empty measures into a multimeasure rest | Ctrl+Shift+M | 4.4+; plain **M** on older 4.x | | | Collapse empty measures into a multimeasure rest | Ctrl+Shift+M | 4.4+; plain **M** on older 4.x | |
| | Multimeasure rest settings | Format → Style → Rests | Tab location has moved across 4.x versions — if not under "Rests," check what tabs are actually in your Style dialog | | | Multimeasure rest settings | Format → Style → Rests | Tab location has moved across 4.x versions — if not under "Rests," check what tabs are actually in your Style dialog | |
| |
| ^ Action ^ How ^ Notes ^ | ^ Action ^ How ^ Notes ^ |
| | Open Instruments panel | Press **I**, or the Layout tab (4.5+) | In 4.5+ this moved out of Edit/View into Layout — press F7 if not visible | | | Open Instruments panel | Press **I**, or the Layout tab | press F7 if not visible | |
| | Add instrument | Instruments panel → Add → search/select → Add | | | | Add instrument | Instruments panel → Add → search/select → Add | | |
| | Duplicate/copy an instrument within a score | No built-in feature | Workaround: add a new instrument of the same type, then Ctrl+A / Ctrl+C the source instrument's part, click first measure of new instrument, Ctrl+V. Doesn't carry custom staff text/formatting. | | | Duplicate/copy an instrument within a score | No built-in feature | Workaround: add a new instrument of the same type, then Ctrl+A / Ctrl+C the source instrument's part, click first measure of new instrument, Ctrl+V. Doesn't carry custom staff text/formatting. | |
| ^ Action ^ Shortcut ^ Notes ^ | ^ Action ^ Shortcut ^ Notes ^ |
| | Play / stop | Space | | | | Play / stop | Space | | |
| | Play only a MIDI keyboard's live sound (no note entry) | Make sure Note Input (N) is off | If notes keep entering anyway, check Edit → Preferences → Note Input for a MIDI auto-start setting, or disconnect the keyboard | | | Play only a MIDI keyboard's live sound (no note entry) | Make sure Note Input (N) is off | If notes keep entering anyway, check Edit → Preferences → Note Input for a MIDI auto-start setting | |
| | Export audio | File → Export → Audio | mp3/wav | | | Export audio | File → Export → Audio | mp3/wav | |
| | Export MIDI | File → Export → MIDI | For bringing into a DAW | | | Export MIDI | File → Export → MIDI | For bringing into a DAW | |
| | Isolate just the metronome click as audio | Mixer (F10) → Solo the **Metronome** channel → File → Export → Audio | Confirmed working in MuseScore 4 for isolating the click (soloing/muting individual instrument channels has known bugs; the Metronome channel solo does work) — export as WAV, not mp3, to avoid encoder padding/artifacts if you need to analyze click timing precisely | | | Isolate just the metronome click as audio | Mixer (F10) → Solo the **Metronome** channel → File → Export → Audio | export as WAV, not mp3, to avoid encoder padding/artifacts if you need to analyze click timing precisely | |
| |
| ===== Text, Technique & Style Markings ===== | ===== Text, Technique & Style Markings ===== |
| | Pizzicato → arco change | Apply "arco" from the **Text palette** (same place "pizz." lives) | This is a "Playing Technique" annotation, not plain text — it actually changes MIDI/audio playback. Typing "arco" via Ctrl+T is just visual text and does nothing to sound. Check the status bar when a technique text is selected to confirm which kind it is. | | | Pizzicato → arco change | Apply "arco" from the **Text palette** (same place "pizz." lives) | This is a "Playing Technique" annotation, not plain text — it actually changes MIDI/audio playback. Typing "arco" via Ctrl+T is just visual text and does nothing to sound. Check the status bar when a technique text is selected to confirm which kind it is. | |
| | Swing feel | Add "Swing" marking — filed under the **Tempo** palette in MS4, not Text (a commonly-flagged confusing placement) | Right-click the inserted Swing text → System Text Properties → Swing Settings tab → set note value + ratio. Add another marking and set it to "Off" to return to straight. Don't combine with the separate Format → Style → Score → Swing Settings global option — pick one method. | | | Swing feel | Add "Swing" marking — filed under the **Tempo** palette in MS4, not Text (a commonly-flagged confusing placement) | Right-click the inserted Swing text → System Text Properties → Swing Settings tab → set note value + ratio. Add another marking and set it to "Off" to return to straight. Don't combine with the separate Format → Style → Score → Swing Settings global option — pick one method. | |
| | General style settings | Format → Style… | Not a standalone "Style" menu (that was MS3) | | |
| |
| ===== Known Gotchas ===== | ===== Known Gotchas ===== |
| |
| ^ Issue ^ Explanation ^ | ^ Issue ^ Explanation ^ |
| | Section breaks auto-reset measure numbers by default | MuseScore's documented default: numbering always restarts at a new section unless you explicitly uncheck "Reset measure numbers for new section" on that break, in Properties. | | | Flatpak sandboxing hides real file paths | Writing to ''/tmp'' from the MuseScore flatpak actually lands in ''~/.var/app/org.musescore.MuseScore/tmp'', not the real ''/tmp''. Fix: ''flatpak override --user org.musescore.MuseScore --filesystem=/tmp'', or just save to ''~/Documents'' instead. | |
| | A section break with no numbering-reset override can also break the *metronome's* downbeat accenting | Empirically observed: a missing/misconfigured section break caused two adjacent measures to be heard as one unaccented run of beats in an exported metronome click track, even though the measure numbers and content were otherwise correct. | | |
| | `<Measure len="N/D">` (pickup/irregular measure length override) | Truncates the actual duration of a measure independent of its *declared* time signature — but empirically, MuseScore's metronome/playback still ticks according to the **declared** time signature's full beat count for that measure, not the truncated length. Easy to misread when reverse-engineering timing from the file. | | |
| | Flatpak sandboxing hides real file paths | Writing to `/tmp` from the MuseScore flatpak actually lands in `~/.var/app/org.musescore.MuseScore/tmp`, not the real `/tmp`. Fix: `flatpak override --user org.musescore.MuseScore --filesystem=/tmp`, or just save to `~/Documents` instead. | | |
| | Flatpak popup/dialog windows not opening (KDE/Wayland) | Known Qt/Wayland bug affecting popup and dialog positioning in some MuseScore 4 builds. Fix: force X11 — `QT_QPA_PLATFORM=xcb musescore4` (edit the Exec line in the `.desktop` file to persist this). | | |
| | Dialogs still broken even on X11 | Can be a corrupted layout/preferences state rather than the Wayland bug above. Try View → Restore the Default Layout first; if that doesn't fix it, reset MuseScore's config: move `~/.config/MuseScore/MuseScore4.ini` and `~/.local/share/MuseScore4` aside and relaunch. | | |
| |
| ===== Merging Multiple Scores into One (Movements/Album) ===== | ===== Merging Multiple Scores into One (Movements/Album) ===== |
| MuseScore 4 has no built-in Album/Join feature (it existed in MS2/3, not restored as of testing). | MuseScore 4 has no built-in Album/Join feature (it existed in MS2/3, not restored as of testing). |
| |
| **Community PowerShell script** — combines full `.mscz` files sequentially (concatenates the raw staff XML from each score, inserting a barline + section/page break between each), rather than doing a manual copy/paste per instrument: | **Community PowerShell script** — combines full ''.mscz'' files sequentially (concatenates the raw staff XML from each score, inserting a barline + section/page break between each), rather than doing a manual copy/paste per instrument: |
| * Script + thread: https://musescore.org/en/node/305513 — look for the attached **MusescoreCombine.txt** in the thread (renamed from `.ps1` because the forum blocks script uploads directly — rename back to `.ps1` after downloading) | * Script + thread: https://musescore.org/en/node/305513 — look for the attached **MusescoreCombine.txt** in the thread (renamed from ''.ps1'' because the forum blocks script uploads directly — rename back to ''.ps1'' after downloading) |
| * Runs fine on Linux under PowerShell 7 (`pwsh`) unmodified — it's pure zip/XML text manipulation via built-in cmdlets, no Windows-only APIs and no dependency on the `mscore` binary itself | * Runs fine on Linux under PowerShell 7 (''pwsh'') unmodified — it's pure zip/XML text manipulation via built-in cmdlets, no Windows-only APIs and no dependency on the ''mscore'' binary itself |
| * Usage: `pwsh MusescoreCombine.ps1 file1.mscz file2.mscz file3.mscz ...` — order = argument order, not filename or directory order. First file's header/style/instrument list becomes the whole merged score's. Output is `MergedSore.mscz` (script's own naming) in whatever directory you ran the command from. | * Usage: ''pwsh MusescoreCombine.ps1 file1.mscz file2.mscz file3.mscz ...'' — order = argument order, not filename or directory order. First file's header/style/instrument list becomes the whole merged score's. Output is ''MergedSore.mscz'' (script's own naming) in whatever directory you ran the command from. |
| * Preserves tempo/key/time-sig changes and ties correctly (raw XML concatenation), unlike manual copy/paste in the MuseScore UI, which drops tempo and key/time-signature changes across the paste boundary. | * Preserves tempo/key/time-sig changes and ties correctly (raw XML concatenation), unlike manual copy/paste in the MuseScore UI, which drops tempo and key/time-signature changes across the paste boundary. |
| * Each inserted section break defaults to a **3-second pause** between movements (MuseScore's normal section-break default) — if you don't want a gap, select the break → Properties → set "Pause before new section starts" to 0. | * Each inserted section break defaults to a **3-second pause** between movements (MuseScore's normal section-break default) — if you don't want a gap, select the break → Properties → set "Pause before new section starts" to 0. |
| * Requires identical staff/instrument layout (same instruments, same order) across all input files. | * Requires identical staff/instrument layout (same instruments, same order) across all input files. |
| |
| **Installing PowerShell (`pwsh`) on Ubuntu 24.04** — standalone `.deb`, no need to add the Microsoft apt repo for a one-off task: | **Installing PowerShell (''pwsh'') on Ubuntu 24.04** — standalone ''.deb'', no need to add the Microsoft apt repo for a one-off task: |
| <code bash> | <code bash> |
| POWERSHELL_VERSION=$(curl -s "https://api.github.com/repos/PowerShell/PowerShell/releases/latest" | grep -Po '"tag_name": "v\K[0-9.]+') | POWERSHELL_VERSION=$(curl -s "https://api.github.com/repos/PowerShell/PowerShell/releases/latest" | grep -Po '"tag_name": "v\K[0-9.]+') |
| sudo apt install -y ./powershell.deb | sudo apt install -y ./powershell.deb |
| </code> | </code> |
| 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. | |