Hair pins avoid beams by different amounts
Reported version
3.0
Priority
P1 - High
Type
Functional
Frequency
Once
Severity
S3 - Major
Reproducibility
Always
Status
active
Regression
No
Workaround
No
Project
As first reported in https://musescore.org/en/node/279737. Using the file layout test.mscz you see
As you can tell, the bottoms of the beams are almost the same, but the difference between the two hairpins is significant.
Comments
I suspect the issue is that autoplace sees hairpins as a rectangles. The rectangle for the first doesn't actually quite collide with the beam but I guess it's too close for comfort.
For slurs we solve this by creating smarter shapes, not just a single rectangle but a whole series of them that approximate the shape fo slur well. We also don't move the slur at all unless there is an actual collision. In principle we could do the same for hairpins. This would help keep them aligned in cases like this.
In reply to I suspect the issue is that… by Marc Sabatella
What about locking adjacent hairpins vertically to each other? Similar to when a separate dynamic marking follows a hairpin? Oh, perhaps the option of a separate, singular cresc/decresc hairpin? Just some musings.
Adjacent hairpins are not always vertically aligned and doing this automatically is just something else to override.
In reply to Adjacent hairpins are not… by mike320
Yes, it is possible users would not want adjacent hairpins to be aligned, but aligning them would be, by far, the more common use case. The sample from the OP makes me want to gouge out my eyes and trying to align by hand on my 30 part score to make them look right is what brought me to this ticket in the first place.