Tremolos for small chords remain big in 3.x
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
You need to attach the score, the PDFs you attached to https://musescore.org/en/node/293304 are not sufficient
.
Here I attache example files from MuseScore 2.3.2 and 3.4.2 for the described problem (and I made a PDF of each file too)
Thanks for the files
Confirmed. Seems a regression to me
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.
that 'small' checkbox could even get set by automatically when importing MuseScore 2 scores with small chords having a fermata
In reply to Tremolo seems an obvious bug… 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.
In reply to Tremolo seems an obvious bug… by Marc Sabatella
Why are fermatas treated as segment annotations? Isn't a fermata only applicable to a single chord/rest/barline?
https://github.com/musescore/MuseScore/pull/6265 addresses the issue for tremolos.
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.
In reply to Femeratas used to be treated… by Marc Sabatella
Probably because of the fact that it can be attached to barlines while other articulations can't?
Ah, yes, maybe that's it.
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?
In reply to I checked out the 3.5-beta… by kae
There has already been a fix proposed for the tremolo case for 3.5. It hasn't been merged yet. And no, there's no release date so far.
Fixed in branch 3.x, commit 7588e8dd14
_Partially fix #294768: tremolos don't have cue size
This is because the
mag()factor isn't taken into consideration.Along with multiplying
mag()in some places, I also created a new member functionminHeight()forTremoloclass to calculate the effective height of tremolo strokes, that is, the height the strokes spread across a given vertical line, without multiplyingspatium(), to resolve an issue of stem length (a bit longer than intended when direction is down and has single-note tremolo on it) which is not obvious in normal size but obvious in cue size. Several places are already using this effective height, so a separate function for calculating it is really convenient to use._Fixed in branch 3.5rc, commit e399f99f4b
_Partially fix #294768: tremolos don't have cue size
This is because the
mag()factor isn't taken into consideration.Along with multiplying
mag()in some places, I also created a new member functionminHeight()forTremoloclass to calculate the effective height of tremolo strokes, that is, the height the strokes spread across a given vertical line, without multiplyingspatium(), to resolve an issue of stem length (a bit longer than intended when direction is down and has single-note tremolo on it) which is not obvious in normal size but obvious in cue size. Several places are already using this effective height, so a separate function for calculating it is really convenient to use._The fermata case still isn't fixed, but there was some discussion on Telegram on whether it's really a bug. I think the conclusion was that we don't make fermatas small by default, but allow users to set them to small.
Right, and in the MuseScore inspector, it will I. Theory be able to just mark everything in a selection small all at once (assuming the element supports it; fermatas still need to).
The reason it’s not practical to do it automatically with the notes is that the Germans is not actually attached to the note the way articulations are. They were in MuseScore but led to other problems. Fermatas are more like text or other “annotations” now - and yes, those will all need to support “small” property.
Fixed in branch master, commit 785253c09c
_fix #294768: tremolos don't have cue size
This is because the
mag()factor isn't taken into consideration.Along with multiplying
mag()in some places, I also created a new member functionminHeight()forTremoloclass to calculate the effective height of tremolo strokes, that is, the height the strokes spread across a given vertical line, without multiplyingspatium(), to resolve an issue of stem length (a bit longer than intended when direction is down and has single-note tremolo on it) which is not obvious in normal size but obvious in cue size. Several places are already using this effective height, so a separate function for calculating it is really convenient to use._Automatically closed -- issue fixed for 2 weeks with no activity.