Tremolos and Fermatas for small chords remain big in 3.x, were small in 2.x

• Sep 22, 2019 - 12:28
Reported version
3.4
Type
Graphical (UI)
Frequency
Few
Severity
S4 - Minor
Reproducibility
Always
Status
active
Regression
Yes
Workaround
No
Project

In Version 2.3.2 when I put a one-note-tremolo on a small chorded note (when I tick the box "small chord"-box (there stands "Akkord" (german for chord) and then there is the box with "klein" (small) to tick at the inspector)) or also when I first put the tremolo on the note and then select it and tick the box "small chord" the tremolo sign stays in the normal size. In erlier versions the tremolo sign went small to, what I prefer for cue notes.
I'll attache two files to compare it. Have a look at rehearsal H and a few bars before rehearsal P.
The Kl1-file was made with an earlier version (I think its 3.1, and having small tremolos on the cue notes), The Kl2 file is made with Version 3.2.3.
PS: In Version 2 tremolos on small chords also went small.

If you can't see any files here, see:
https://musescore.org/en/node/293304


Comments

Tremolo seems an obvious bug and probably an easy fix. Fermatas are a bit more complicated, perhaps. In 2.x they were articulations, attached directly to the chord. In 3.x they are separate element types and treated as segment annotations similar to staff text. I guess we could treat a fermata as small if there exists a chord in the same voice on the same segment and it is made small. If it weren't for the compatibility issue, I might suggest it makes more sense to just have a separate "small" checkbox for the fermata.

In reply to by Marc Sabatella

The best would be to have a "small" checkbox in general for any articulation (optimum: any element types), whether the chord is small or not. This would also allow to mark whether the sign is i.e. complemented by the editor or is original written by the composer. This method is also used by many music publishers and why shouldn't it be able in MuseScore too? Maybe sometimes also professional editions will be typeset with MuseScore.

Femeratas used to be treated as articulations attached to the chord, but the implementation was changed to a separate element type that is attached to the segment. I think Werner made that change sometime during the MuseScore 2 -> MuseScore 3 development cycle. I may have once known and understood the reason, but I forget. Probably had something to do with either how it responds to automatic placement or else making it easier to control playback.

Type Functional Graphical (UI)
Reported version 3.4 3.5

I checked out the 3.5-beta version, where this bug is not solved. Maybe this gets changed in the stable version of 3.5.

PS: Is there a release date for a stable version 3.5 yet?