Wrong Timing in Note Entry
Reported version
3.4
Type
Functional
Frequency
Once
Severity
S2 - Critical
Reproducibility
Always
Status
by design
Regression
No
Workaround
No
Project
1) Open a new score.
2) Enter notes on keyboard.
3) Enter a half rest
4) Enter a quarter rest. We have now use 3 of our 4 beats at 4/4 time.
5) Enter an eighth rest. We now have one eighth note left to use.
6) Enter an eight note.
The eighth note is followed by an extra eighth rest, such that the measure is now 4 1/2 beats long.
Attachment | Size |
---|---|
Capture.PNG | 9.15 KB |
Comments
It's also impossible to delete. It ruins the entire measure forever.
In reply to It's also impossible to… by vikingbaerser
Are you using “Insert note“ to enter that eight note? That is the only way that I can reproduce this, in which case it wouldn't be a bug.
My programmer's intuition tells me that it's probably an off-by-one error somewhere, but it's probably also a good idea to add a sanity check to the measure code for such conditions.
I'm using "Enter notes with a keyboard (N)"
I was using the keyboard and/or the mouse to select durations, 0 to add rests, and I hit E to add the last note.
In reply to I was using the keyboard and… by vikingbaerser
Did you by any chance hold CTRL+SHIFT while hitting E? CTRL+SHIFT+Note Name inserts a note rather than overwriting what is there.
I can still reproduce it every single time, using either the keyboard or the mouse.
No ctrl shift.
I just created half a dozen new scores and tried it selecting durations with the keyboard or the mouse, tried it getting them wrong a couple of times and getting them right. I can still reproduce it every single time.
I tried it starting with different staff configurations....
I tried it on the default staff instead of starting a new score, and it didn't reproduce.
In reply to No ctrl shift. by vikingbaerser
Are you in insert mode? Shortcut N just turns note entry on or off it doesn't change the entry mode. What does the note entry button look like?
This: or this:
That was after I closed and restarted the program, and after it worked, a new score worked too. So, I don't know how your codebase is organized, but hopefully that gives you an idea where to fix it. In the meanwhile, I guess I have a workaround of restarting the program.
Hmm, I think it WAS insert mode before. Is it really supposed to mess up the timing like that?
In reply to That was after I closed and… by vikingbaerser
So after restarting MuseScore you can't reproduce it then?
In reply to So after restarting… by SteveBlower
Well, insert mode is used to erm... insert things. If you don't want to insert things, don't use insert mode.
That seems counterintuitive but I guess you could do cool things with it, like bending time and shit. It might still be a good idea to introduce the concept a bit more, since it's not really in traditional music as far as I would expect your typical user to be savvy about. I didn't have any idea there was a difference, or any idea that such a thing could even be done, and I read about most of the tour dialogs.
What I'm saying is, I doubt I'm the first person to be confused enough by this mechanic to think it's a critical failure in the software, and if it was presented a little better, I wouldn't have had to waste your time and mine today to figure it out.
Why do the rests not also "insert" the same way? Why is it inserting an additional rest when I was trying to insert a note? Is there any kind of guide to this mechanic or the logic behind it?
Try this: https://musescore.org/en/handbook/note-input#note-input-modes