bug when switching notes between staves?

• Apr 23, 2020 - 04:20

hey folks

when i move a note from the treble clef to bass clef in a score, the note seems to 'remember'; it came from a differennt staff. for instance - in the attached file -the first note in voice 1 - the 'g' in the bass clef - was successfully moved to the bass clef, but if you move the note up or down in pitch, it 'jumps' back to the first clef. Also, if you try and highlight the note, it stretches the hightlight to include the treble clef.

there are other behaviors it does as well. For instance - chaznge it from an eight note to a quarter note, and the new rest gets created in the TREBLE clef, not in the bass clef, where the note is.

is this a bug? am i not moving notes between staves correctly (I use the cntrl shift combo)

thanks

Attachment Size
test.mscz 7.39 KB

Comments

• Apr 23, 2020 - 08:45

No bug. octave higher/lower is Ctrl+up/down arrows. You most likely pressed Shift+Ctrl+up/down as that is cross-staff notation.

Reply

• Apr 23, 2020 - 09:22

You are moving notes correctly if you want to have something like a scale that starts in the upper staff but ends in the lower staff and is connected by a beam between the two staves. The notes continue to "belong" to the stave where they were first entered but show up on the stave you have moved them to. If you just want to move a note from one staff to another but have no need for a beam to connect it to the other stave then just cut and paste. The ctrl shift arrow manoeuvre is a bit of a kludge to enable cross-staff beaming and should not really be used unless that is what you want.

Reply

• Apr 23, 2020 - 15:42

ok thanks. I thought there was a command to actually Permanently Move the note from staff a to staff b, breaking all linkage to the previous staff. Unfortunately for me, i have a very long score that has some serious corruption in it after a midi import (about 90 measures) and i need to do some moving around. The cut n past isnt really an option, because of corrupted measures the corruption is moving with the cut n paste (usually issues where the measure has an incorrect amount of beats).

thanks anyway!

Reply

• Apr 24, 2020 - 02:28

Judging by your posted 'test.mscz' example, it seems that you are not merely transcribing an actual piano score. The illogical use of cross-staff notation coupled with the weird voice assignments, along with you (just now) mentioning a need to implode/explode indicates a bigger picture - like maybe you are trying to create a piano reduction of an ensemble score?

I don't know, however...
There is no bug in cross-staff notation. MuseScore keeps track of the 'true location' of notes. To confirm, click on a note and verify in the Status Bar. (https://musescore.org/en/handbook/viewing-and-navigation#status-bar)

So, for example, in your posted 'test.mscz' file, clicking on the whole note in the bass clef (Staff 2) of measure 3 shows:
Note; Pitch E3; Duration: Whole; Voice: 2; Measure: 3; Beat: 1; Staff 1 (Piano).
To get that E3 permanently into the bass clef, thus breaking the linkage to Staff 1, you cut and paste (as already mentioned).

Reply

• Apr 23, 2020 - 09:19

Cross-staff notation moves the note visually to make it easier or clearer for the (usually piano) player. The note's duration, pitch etc. is still part of the Stave and Voice from which it came. I can think of all kinds of programming confusion if this were not the case.

Reply

• Apr 23, 2020 - 10:33

So if you really want to move the note from one staff to another and not visually displace it only; use cut and paste.

Reply

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