Dynamics fails?

• Apr 19, 2021 - 04:38

Hi, friends. Im have problems with "crescendos", just like you could see on the image attachment. The dynamics "fff" are very similar to "f". Or, its mean, the notes dont "cres" to volume like I require and dont thus marking the difference (in dynamics).

Thanks for your help

Attachment Size
para musescore foro.png 111.63 KB


In reply to by vicentecamus2872

That score does start its live before 3.6, created in July 2020, long before MuseScore 3.6. May not be relevant for the issue at hand though.
However, there is an increase in velocity, so the hairpins do work, don't they?

In reply to by vicentecamus2872

I hear the crescendo just fine. It's a little anticlimatic because there are double stops to being with then the final chord is single notes. On real violins, double stops aren't necessarily louder than single notes, but to a synthesizer, they are. Anyhow, you can tweak the velocity settings for the dynamics in question in the Inspector to start softer if you like.

In reply to by vicentecamus2872

Again, as I explain,ed the double stops are louder than single notes. And if you personally find you wish the difference between mf and fff were larger even with that removed from the equationl feel free to customize it. But once again - the crescendo abs9lutely positively works, it's just there isn't as big a difference between a double stop mf and a single note fff as you'd prefer, so customzie that and all is well. And then feel free to submit a suggestion to the issue tracker that the default soundfont for strings consider making a bigger difference in the volume of mf versus fff.

In reply to by vicentecamus2872

In this version you broke it by extending the crescendo marking to after the dynamic, that won't work indeed. There needs to be a dynamic after the hairpin.

Again, go back to original example, try turning down the velocity of the mf to a lower value where it's much more noticeably softer than the fff even when playing double stop. I guarantee you will be able to hear it. Try a value of "20" for instance.

Again, this shows the program is working just fine - it's not that the crescendo doesn't work, it's that a double stop mf isn't that much quieter than a single note played fff. It has nothing to do with crescendo, it's just about how loud a double stop at mf is - it's louder than it should be, we agree on that. But again, the crexcnedo itself works fine - it correctly increase the volume that amount. With a quieter start note you can hear it more clearly

In reply to by vicentecamus2872

Some observations.
I think both sides are correct, sort of.
I'm old enough to have written many pieces of music on paper. To me it is a continuing wonder that I can put notes into a program, add dynamics and have it playback at all.
So while the crescendo works, "just fine" only goes so far. There is a crescendo from mf to fff, but the fff is underwhelming. The original example is not a very good one, scoring wise. I spent some time creating better examples and the result is similar. The crescendo works. but if you watch the volume meter, there isn't much difference regardless of whether the final marking is f, ff, and fff. And that's OK actually. I know there are those who spend a lot of time in the inspector. They adjust every little thing trying to get good playback. I guess it depends on what your goal is. I don't produce music for real players. But I often have two scores. One that I could hand to real players, and one for playback. The playback score doesn't have to look proper. I can mark it up in ways that would not be correct at all. To me, the default p playback is too loud. To get a maximum effect I would probably start with a pp. then hairpin to fff. Even so, I would have to write properly for the instruments involved. Only then would there be a chance of things working.
Writing in notation software is a two-edged sword. You have always watch for the backswing.

Do you still have an unanswered question? Please log in first to post your question.