fingering default position conflicts with staff lines
I don't like the default vertical position MuseScore has chosen for these fingerings circled in red, because they cross the staff lines:
I don't like the default vertical position MuseScore has chosen for these fingerings circled in red, because they cross the staff lines:
Do you still have an unanswered question? Please log in first to post your question.
Comments
In principle, it shouldn't be too hard to tweak the algorithm to avoid the staff. The real trick, though, would be changing it to allow fingering for piano chords to be stacked rather than placed next to the noteheads. This is complicated by the fact that fingering is attached to the *note* rather than the *chord*, and it's awkward to have the position of the fingering of one note depend on the position of fingerings of other notes. I sometimes think we should add a new "chord fingering" element that allows you to create stacked arrangements more easily. This sort of redesign should probably go along with a scheme to make *entry* pof the fingering symbols easier.
In reply to In principle, it shouldn't be by Marc Sabatella
I think I agree that should extend the text class into a new "chord fingering" class which would handle stacked fingering for chords, as well as ensuring fingerings always display outside of the grand staff.
In reply to I think I agree that should by ericfontainejazz
I'm just making a note now that musescore current places fingering for a chord to the left of the noteheads:
And that works ok for at least simple chords, but clearly won't work for chords that have lots of accidentals and with notes close together, e.g. this hypothetical extreme case:
Probably best to have option to configure fingering placement for chords as stacked above staff or to side of fingering, since the side might even work better for simpler music.
fingerings also conflict with ornaments...here is what a fingering looks like on a note above the staff that already had a staccato and accent:
In reply to fingerings also conflict with by ericfontainejazz
Yes, in general, collision avoidance for all markings is a *huge* and extremely complex topic.