Fingering collides with other score elements
Reported version
2.3
Type
Functional
Severity
S1 - Blocker
Status
closed
Regression
No
Workaround
No
Project
1. Open attached score.
2. Drag an object from the Fingering palette to a note, or select note and double-click object.
Result: The object collides with the chord.
Discussion: Only applies to chords - single notes work correctly.
Using MuseScore 2.0 Nightly Build (5497) - Mac 10.7.3.
| Attachment | Size |
|---|---|
| Fingering collides with chord.mscz | 1.38 KB |
Comments
Single notes do not work correctly either certainly not for guitar
Fingerings in guitar and piano are normally placed just to the left of the note.
As you can see the fingering in this attached guitar piece is colliding with other score elements, making a lot of work in cleaning it up.
Applying adjustments in style don't appear to work.
Some of this fingering was placed after entering a negative offset of 3mm in the X axis - you can see it has actually shifted to the right!
In that score, the position of fingering is off, and the numbers collide (rather than colliding with notes themselves). Might be different.
You have multi-voice in the score, something in which collisions could happen?
The resulted collisions you see are from selecting the note to be fingered then double-clicking the relevant Fingering Palette icon.
I did try with a string number in voice 2 as well, but the result was to place it above the stave instead of near the note it was intended for, so there is clearly work to do in this area.
If we can get default finger number positions sorted first, then move on to string numbers I think this would help.
In what way do you mean the position of fingering is off? As I said most of these were placed in the default fingering position.
Regarding multivoice - yes - multivoice is standard in most keyboard and guitar pieces, and so needs to be considered when writing algorithms.
I later created this , but in hindsight, I probably shouldn't have opened this issue, because there's other elements in the same situation.
I suspect it is more helpful to the devs to have seprarte issues opened for each case rather than one huge one containing a large number.
I did think that, but wasn't sure.
As of 4189822f54153277fd90b1971958a39f4dbe339b things are better. Not perfect but better. That's about as good as we're likely to do for the foreseeable future.
Deleted.
Looks as if it got fixed.
Automatically closed -- issue fixed for 2 weeks with no activity.