Autoplace: slurs intersect stems in other voices at start segment
Reported version
3.2
Priority
P2 - Medium
Type
Functional
Frequency
Once
Severity
S4 - Minor
Reproducibility
Always
Status
active
Regression
No
Workaround
Yes
Project
| Actual behaviour: | Expected behaviour: |
|---|---|
|
|
Note the placement of the top slur. It "belongs" to the 16th notes in Voice 2, so it could have been written below the notes as is usual for a slur in Voice 2, but has been shifted above them to make room for the notes on the lower staff, thus causing the collision.
Workaround: manual placement, or write slur below notes instead of above them.
| Attachment | Size |
|---|---|
| slur-stem.mscz | 4.62 KB |
Comments
A better workaround might be to go ahead and attach the start of the slur to the voice 1 note. Then it renders as expected. It's actually by design we allow certain collisions with the start & end segment, as otherwise autoplace would need to do pretty crazy things to avoid, for instance, an accidental on the last note. Still, there might be ways to improve the situation, not clear exactly how though.