Note entry mode minor bug
When entering notes in Step Time on the middle stave of a pipe organ score generated from the start centre, whenever a barline is crossed the entry note jumps by one (or sometimes two) octaves
Attachment | Size |
---|---|
Toccata_and_Fugue_in_d_minor_(Dorian).mscz | 54.3 KB |
Comments
MuseScore tries to stay as close to the previous note as possible, are you saing this don't happen in your case?
In case you didn't know: Ctrl+Up and Ctrl+Down are the shortcuts to get them to another octave.
And I can't reproduce your issue
This happens to me in staves with clef changes but it's not an every time occurrence. I don't know how to reproduce it so it can be fixed. I find it quite annoying.
In reply to This happens to me in staves… by mike320
Clef changes may explain it, as mentioned MuseScore tried to use the closest pitch to the previous, with a clef change it'd still do, rather than changing the octave along with the clef, so the note may appear an octave away, but really is not?
In reply to Clef changes may explain it,… by Jojo-Schmitz
Since I cannot reproduce a score with the issue consistently, I'll explain a common occurrence.
A cello starts in the bass clef. In measure 5 I might change to the tenor clef, which is very common. I enter all of these notes into octave 4 F, E, D, C into that measure. The next F I press should be an F4. If this is in the next measure, sometimes it is, some times it's an F3.
This is a typical example not a specific occurrence: I have no way of telling you why it does that because I have thought "Aha! I've found a place with the bug!" So I set it up the exact same scenario again using 5 measures rather than the 283 up to that point in my existing score and sometimes I get the F4 sometimes I get the F3. So I undo the note entry in my 283rd measure of my score and enter the note again. The F sometimes ends up in octave 4 when I try it again and sometimes in octave 3. When I give the octaves the notes are in they are 100% consistent. They look, sound and are reported in the status bar in the same octave regardless of if it's the right octave (4 in my example) or not (3 in my example).
This happens with any clef change, treble to bass, alto to treble and so on. I have seen many notes display 2 octaves low when the normal range of the instrument is there (like a cello with a treble clef).
BTW, I've seen this happen in any instrument with clef changes including but not limited to the Cello, viola, bassoon, horn (in a variety of keys) and piano (not cross staff).
In reply to Since I cannot reproduce a… by mike320
I recall fixing one bug in this algorithm, see #284886: Notes not entered in first measure entered into wrong octave. But I too occasionally still see this. My assumption is that somehow the clef change is being missed but I'm not sure how.
In reply to I recall fixing one bug in… by Marc Sabatella
I remember that. I also remember seeing this within hours or days of that issue being fixed. I suspect I see it more because I use clef changes more.