Two-note tremolos display incorrectly when the stave has custom scale
Reported version
3.5
Type
Functional
Frequency
Once
Severity
S3 - Major
Reproducibility
Always
Status
closed
Regression
Yes
Workaround
No
Project
1) Enter a two-note tremolo with the duration of a half note (or a dotted half note) using Musescore 3.5.
2) Change the tremolo stroke style into "All strokes attached to stems" (using the Inspector).
3) Change the size of the both notes (using the Inspector - Chord - Small), or change the scaling of the stave (Using right-click).
The stroke will not be attached well to the stems anymore as long as the stave scaling and/or notes size changes. As shown in the screenshot below or the attached score file.
| Attachment | Size |
|---|---|
| Two-note_Tremolo_Test.png | 108.81 KB |
| Two-note_Tremolo_Stroke_Test.mscz | 8.42 KB |
Fix version
3.6.1
Comments
Confirmed in 3.6 RC as well.
Not just for traditionally styled ones, but for others too... Should be a regression because the
mag()calculations were added by me.See https://github.com/musescore/MuseScore/pull/7271.
Fixed in branch 3.x, commit 82a1fd8429
_fix #315147: two-note tremolos display incorrectly when the stave has custom scale
The issue is caused by the stave scale multiplied twice: once in
spatium()and once inmag(). To avoid this, I created a functionchordMag()for chords (and also for tremolos which calls the one for chords) which doesn't multiply stave scale, and used that instead ofmag()for tremolo calculations._Fixed in branch master, commit da4543fdea
_fix #315147: two-note tremolos display incorrectly when the stave has custom scale
The issue is caused by the stave scale multiplied twice: once in
spatium()and once inmag(). To avoid this, I created a functionchordMag()for chords (and also for tremolos which calls the one for chords) which doesn't multiply stave scale, and used that instead ofmag()for tremolo calculations._Automatically closed -- issue fixed for 2 weeks with no activity.