slurs and ties on voices that have crossed systems
Hello,
I'm having a little trouble with MU3 after having imported a piano piece from MU2. This piece has instances where voices cross from one system to another and it seems that this disrupts slurs and ties made on those notes that have crossed systems. Any manual changes aren't possible as the auto placement system doesn't like this either.
Is this a known bug? Anything can be done?
Thanks for all the hard work.
Comments
This is a known bug that is eluding attempts to fix it. Be patient and it will be fixed eventually. See #279182: Cross-staff slurs/ties trying to avoid note on wrong staff.
In reply to This is a known bug that is… by mike320
Ok thanks, I read through the thread and see the issue.
On a related note, I noticed when using MU2 that the way in which voices are handled in systems could cause confusion especially in pieces that typically have unclear and overlapping voices (i.e. many modern piano pieces). For instance a 'blue' voice 1 from the upper system could be confused for the voice 1 of the lower system after having crossed over, as they are the same color. I found that this was very inconvenient in complex music with lots of system changes. As the 'voices' are not related to true contrapuntal voices in scores, it might be possible and convenient for the software to automatically assign voices when the musical line crosses systems.
So if I was say working in treble clef, inputing notes, and then crossed into the bass, the software would automatically switch me into the voice appropriate to the bass. This would keep the voices organized and no confusion could be had as to what system a voice belonged to. If this change were made it might also fix this current issue in MU3, as you'd never encounter the current situation. Of course you might find then that a strict limitation of 4 voices per system was not enough, but maybe you could add a 5th at some late date. Anyway just musing. I will wait for you solution. MU3 is pretty much impossible for all but the simplest piano scores until this is fixed.
In reply to Ok thanks, I read through… by lgsonnet
When you use cross staff notation (ctrl+shift+arrow) you are moving the displayed location of the note, while the note is actually still in the other staff. This does allows you to keep all of the notes in a fugue type score in the same voice continuously and also gives you the opportunity to force a fifth voice into the other staff for notation purposes. Changing this would cause a huge programming situation to handle when you have something like alternating 16th notes with a common beam being displayed in the two staves as is quite common.
MuseScore does give you a big clue that you are looking at cross-staff notation in the stayus bar. It tells you which staff a note was entered into. I often use this knowledge help people who have posted scores in these forums. I can always tell when notes have been moved to another staff.
MuseScore 3 under Windows 7 Short Old Man Db.mscz Short Old Man Db.mscz
This may be related. I have noticed that when a note with an accidental is tied to the same note in the next
measure and in the next system, the accidental is not observed in the second measure. See Cb in measure 9 of the alto staff tied to C measure 10 in the attached file. I can workaround this by adding a flat sign to the C in measure 10 but I can't enclose the flat sign in parentheses because place text insists on placing the text above or below the note.
In reply to This may be related. I have… by billevans3@juno.com
This is unrelated and not a bug. You have not used a tie, but a slur. Slurs are added by pressing s, or using the slur in the lines palette. Ties are added by pressing the + button or the Tie icon in the note entry palette.
In reply to This is unrelated and not a… by mike320
Thanks mike320. Initially, I couldn't get the tie to work because I was trying to tie a Cb to a C. Then I realized that I needed to add the 'flat' accidental to the C in the second measure before adding the tie. Now the flat on the second C is automatically removed when the tie is added! The tie works exactly as it should.
Thanks Again!