Second ending hairpin applies to first repeat
In a repeated section with a first and second ending, the hairpin in the second ending happens in the first measure of the repeat.
For example, the attached score starts forte, but when the section repeats, a diminuendo to piano happens in the first measure, even though that is only present in the second ending.
| Attachment | Size |
|---|---|
| repeat_dynamic_bug.mscz | 24.84 KB |
Comments
Confirmed (MuseScore 4 on Win 11) but to my ears more a diminuendo to mf in the repeat halfway measure 1 and 2.
Workaround: add an invisible f in measure 2.
NB: after moving the anchor of the dim. hairpin one eighth further playback is correct.
I found no mention of this bug on
https://github.com/musescore/MuseScore/issues?page=1&q=is%3Aissue+is%3A…
Please report this issue on GitHub, so the developers can have a look.
https://github.com/musescore/MuseScore/issues/new/choose
In reply to Confirmed but to my ears… by MichLeon
Just out of curiosity, why do we have to report things again on Github when this is Support and Bug Reports? Isn't that done automatically when we report it the first time?
In reply to Just out of curiosity, why… by FBXOPWKDOIR2
Yes, no
In reply to Yes, no by Jojo-Schmitz
Hi. I need to transpose this score. I tried to import the pdf, but it corrupts my score.
Can someone transpose it from D Major to C major?
In reply to Hi. I need to transpose this… by opreaoliviavi
opreaoliviavi please start your own thread for help.
In reply to opreaoliviavi please start… by bobjp
Oh, they've done that already after posting in Translation and before posting here.
https://musescore.org/en/node/354548
In reply to Hi. I need to transpose this… by opreaoliviavi
Unrelated post and duplicate of https://musescore.org/en/node/354548
Edit: !
In reply to Yes, no by Jojo-Schmitz
I know that's what is preferred now (because it wasn't before). What I want to know is, why? Warum? Por quoi? 115 104 117?
In reply to I know that's what is… by FBXOPWKDOIR2
@FBXOPWKDOIR2
"why do we have to report things again on Github when this is Support and Bug Reports? Isn't that done automatically when we report it the first time?"
No, it is not done automatically. The forums on musescore.org are for support by fellow users (volunteers), and to sort out cases where there is a simple solution - like reading the Handbook or understanding how to access all aspects of the Properties panel.
But the developers - either paid staff or community volunteers - don't read these forums much. They use Github to triage and assign the various bug fixes and enhancements, and to control their testing and release. That is why confirmed bugs have to be formally reported on Github, for which you need to create a free account. Then you can generate a new issue (with "steps to reproduce" and a sample score showing the problem):
https://github.com/musescore/MuseScore/issues/new/choose
[EDIT]
... and BTW you always did have to report bugs twice:
- once on the Support forum (to confirm that it really is a bug);
- then on the discontinued Issue Tracker (where you could follow the bug's progress to a released fix).
Github just replaces the old Issue Tracker.
In reply to @FBXOPWKDOIR2 "why do we… by DanielR
Not quite true, some of the paid developers do read here (but IMHO too few), and all/most of the unpaid volunteers.
But yes, issues need to get reported in the official issue tracker on GitHub.
In reply to Just out of curiosity, why… by FBXOPWKDOIR2
FBXOPWKDOIR2
This forum is for people to post something that they are having problems with. Others join in and either suggest fixes or proper methods. If the discussions don't lead to a solution, then there is an offical posting by one of the participants to guthub. There are no developers on the forums nor automatic anything.
In reply to FBXOPWKDOIR2 This forum is… by bobjp
LOL Guthub! That's exactly the word I would choose!
Reported to github https://github.com/musescore/MuseScore/issues/19365