Length change of voice-2 note/rest adds unnecessary rest to following measure

• Mar 18, 2024 - 18:02

Increasing the length of a voice 2, 3, or 4 note/rest adds an unnecessary same-voice rest to the following measure which I always have to manually delete.

Here are the steps to reproduce:
1. Make a new score.
2. Enter Note Input Mode and set the voice to 2, 3, or 4.
3. Add a quarter note or quarter rest to the first beat of the first measure.
4. Exit Note Input Mode.
5. Select the note/rest and change the length of it to half (for example by pressing "6" on your computer keyboard).
6. See the error: A rest of the same voice is added to the measure after.

I believe this began on version 2.0. If this behavior is intended, what purpose does it serve? If not, should I report it to Github if it hasn't been already?

(I am using MuseScore 4.2.1 on macOS 12.7.2.)


"I believe this began on version 2.0. "
"If this behavior is intended, what purpose does it serve? "
I believe this was discussed at one point. Frankly, I don't remember, even some clue. There must be a reason, but you'd have to go back to the posts in version 2... In any case, it's absolutely harmless. So, nothing to worry about.
I think @Marc (Sabatella), if he reads this thread, should be able to explain it to you.

In reply to by cadiz1

Wow...I just found it again. 2014! #28886: Full measure rest created in next measure if changing length of chordrest in voice 2,3,4 creates rest at end of measure
Considered as minor, has never been fixed.

Complete comment of Marc, I quote: "It was never truly corrupt - just looked that way because of the bad layout.
To me, this is minor because the situation that leads to this isn't all that common and it is simple to just delete the rest, but if you feel like raising the priority, go for it."

In reply to by Riley Sullivan

Well, it will be classified as minor in the same way. And so she'll be at the back of the queue. Who in the last 10 years has really cared about this? There are many more of these minor things. And what's the point of cluttering up Github any further? When there are so many other issues (to date, nearly 2400...!) of quite different importance to resolve, so many V3 features still missing (this is really infuriating, the first time in Musescore history that there has been such a drastic loss of features in a major release)... That's my opinion. But if you report it, at least there'll be a trace of it, but only a trace, I'm afraid.

Do you still have an unanswered question? Please log in first to post your question.