[bug] Changing Measure length adds beats only in Voice 1 - corrupts the measure
OS: Windows 10 Version 2009 or later, Arch.: x86_64, MuseScore Studio version (64-bit): 4.5.2-251141402, revision: ac9d3bc
Background: I work with old scores that don't have a bar size, usually for that I start with score with 12/4 bar size, then resize / split / merge them on the go.
Scenario:
1) Select a measure
2) Open Measure properties
3) Make the Measure size bigger either by typing new or pressing up button (e.g. was 15/4, add 1/4, up to 16/4)
Expected:
Rests added across all voices
Actual result:
Rests added only in Voice 1
Voice 1 has an effective length of 16/4
Voice 2 has an effective length of 15/4
ABC note input in Voice 1 allows to input music in the rests
ABC note input in Voice 2 works as if length is 15/4 - skips the added size and hops to next mesure!
Workaround:
adding notes using the mouse fixes the voice, but this is tedious work
Workaround2:
saving, closing, reopeoning the file doesn't add the missing rests in Voice 2, but let's you input the music with ABC in the added beats, effectively fixing the issue.
| Attachment | Size |
|---|---|
| 1_entering Measure properties.png | 44.77 KB |
| 2_Adjust measure size.png | 34 KB |
| 3_Corrupter measure.png | 28.63 KB |
| 4_Voice 2 note entry - skipped position.png | 17.62 KB |
| error_in_bar_7.mscz | 83.08 KB |
Comments
I'm a mouser. So it took me a bit to figure out what you did.
I guess that in trying to put a quarter note on the last beat of measure 7, you started with the half note F in voice two. And got two quarter notes. Then you hit F again hoping to put a voice 2 F on the last beat. Didn't work, as you show. But instead of hitting F again, consider hitting the right arrow key to advance the cursor to the last beat. Then hit F. Worked on my system. Only one extra keystroke.
In reply to I'm a mouser. So it took me… by bobjp
In case my initial description is confusing, I've recorded a small video:
https://youtu.be/jwAqxkRQJFo?si=Vzy5_UngLiQJSDe4
But instead of hitting F again, consider hitting the right arrow key to advance the cursor to the last beat. Then hit F. Worked on my system.
This works if you close and open the project - some kind of restorative mechanism kicks in while opening the file. The attached project, if opened, will be already "fixed". I've attached it in case it can give smb a hint on what went wrong.
Note: if you've encountered the issue, then hit "Save" without closing the score - the issue is still there. You have to close MS and open the score again for it to go away.
Erroneous behaviour is observed immdiately after adding the Measure Length (see video).
I expect to be able to continue typing as usual, yet I have to resort to workarounds (use mouse to "fix" the bar, or close/reopen Musescore)