Dynamics marking affects the measures before it
I have this score:
change_01.mscz
It sounds fine. But when I add one more measure with changed dynamics:
change_02.mscz
the sound (probably the dynamics) of the foregoing five measures also changes.
Why is this happening? Shouldn't the new dynamics marking only affect the subsequent measures, and leave the previous ones untouched?
Comments
What initial dynamic do you want? There is no indication in your score.
In reply to What initial dynamic do you… by Brer Fox
Isn't it like 'mf' by default?
In reply to What initial dynamic do you… by Brer Fox
You can specify either 'mf' or 'mp' for the very first note of the score - the problem will continue to exist in either case.
In reply to What initial dynamic do you… by Brer Fox
What's wrong with the forum? I can't type the message fully! Here is a picture of what I wanted to type here:
![text_02.jpg]( "text_02.jpg")
I opened the mscx in MuS 3.6.2 and it works as expected.
Either a problem with listening - let it play much slower - or a bug in MuS 4.
In reply to I opened the mscx in MuS 3.6… by HildeK
I never had this problem in MS3, but I am using now only MS4.
In reply to I opened the mscx in MuS 3.6… by HildeK
"a problem with listening"
-- What do you mean by this? When I play back a score with those last four notes and when I play it back without them I can clearly hear the difference. If there is any problem on my side, it must be a hallucination then, not listening. But then it's rather strange that I start hallucinating only when those four notes are added to the score. :)
In reply to "a problem with listening" -… by innerthought
Sorry! I didn't mean to offend you. I just meant that when you play fast eighth or sixteenth notes, you can't hear the dynamics quite as easily.
If you can clearly hear the difference, then it's just a bug in MuS 4.
In reply to Sorry! I didn't mean to… by HildeK
:) No worries. I am not offended.
I wonder if I should report it on GitHub.
What stops me from doing that is that I already reported a similar bug half a year ago ( https://github.com/musescore/MuseScore/issues/14946 ), except that was about saxophones. I am not sure if it is worth then to be considered a separate bug or if it's the same thing.
Sadly, it's been already six months but the saxophone bug is still there.
In reply to :) No worries. I am not… by innerthought
Nevertheless, it makes sense to report it.