Accidentals in the wrong order for multivoice unisons with octaves

• Mar 30, 2019 - 16:00
Reported version
3.0
Priority
P1 - High
Type
Functional
Frequency
Once
Severity
S3 - Major
Reproducibility
Always
Status
active
Regression
No
Workaround
Yes
Project

Measure 158 of the file. Here's a pic of it, highlighted to show voices. accidentals.png

As you can see, while the second voice is inside of the first voice, their accidentals are outside the first voice. This is not readable. I don't know of a workaround, but it might be that if you turn off auto place you can drag the accidentals somewhere saner and add some leading space to accommodate them. It might be a regression, as I don't remember this being an issue in MS2.


Comments

Title Accidentals in the wrong order for close Second + First voice scoring Accidentals in the wrong order for multivoice unisons with octaves
Severity S2 - Critical S3 - Major
Workaround No Yes
Priority P1 - High

It seems to work as expected most of the time. Something very specific about the arrangement of accidentals in that particular chord - I note if you do anything to the lower E, it fixes itself. I think it probably relates to some special casing we do to align the accidentals for notes an octave apart. You can easily fix it via manual adjustment, no fiddling with leading space or disabling of autoplace required. It's a bit of a corner case, and the exact same thing happens for this case in 2.3.2, but indeed, something we should fix.