MuseSounds crescendo and dynamics are not working

• Jul 15, 2024 - 17:19

Hello,
I've just downloaded MuseScore Studio and MuseSounds. It seems to me that dynamics, crescendo, diminuendo are not working properly. See the attached video, and score.
Am i doing something wrong, or is this maybe a bug?

Otherwise I'm amazed by the software and the quality of work, you guys are awesome! Huge thanks!

Best wishes,
Attila

Attachment Size
dynamics_report.zip 1.59 MB

Comments

Seems like you've used a non-standard ZIP tool? Try attach just the score itself. if you feel a video would be useful too, post that to YouTube and put a link here.

In reply to by Marc Sabatella

Totally understand. If you check out the GitHub link, there is the video and the score file as well. Although I used 7-Zip to zip the score file in that case also.
I thought it's strange that you can't unzip it, but now I tried it with the Explorer's Extract All option, and yes it doesn't work. Sorry I never use Explorer, always Total Commender, and 7-Zip.

Now I used an online zip compressor for the task. Checked it with Win10 Explorer, it works.
"dynamics_report.zip" is the one i posted for this page.
"240715_cresc.zip" is the score attachment I mentioned that was posted on GitHub next to the video.

By the way, @bkunda already closed the issue on GitHub, because he assume this one might need to be solved at the library level.

Attachment Size
dynamics_report.zip 1.64 MB
240715_cresc.zip 16.88 KB

When you isolate each instrument the effect is clearer. The trombone suddenly increases in volume in measure 2 instead of gradually, sounding like a FFF or FFFF. In the violin, it never begins ppp. It's just loud. So the hairpins and dynamics both don't work here. Music like this makes for a good stress test of the software.

Attachment Size
240715_cresc.mscz 23.96 KB

In reply to by FBXOPWKDOIR2

If you set up the hairpins properly, they work better. There isn't much help for the trombone. Although the hairpin in the second measure is incorrect.
Listen to the violin. My version looks just like yours but works better. Why? Hairpins need to be between dynamics. Not overlapping them.

Attachment Size
240715_cresc22.mscz 23.96 KB

In reply to by bobjp

Yes, because moving them hairpins just a touch out will destroy the effect. People who write music are constantly changing the music, and so they don't have time to OCD every hairpin in the hope that it will work marginally for them. The hairpins should be more forgiving. They should snap to where we want them and work every time, not be little tempermental hairpinned divas. Maybe someday Musescore will get there, but not today.

In reply to by FBXOPWKDOIR2

Hmm, sounds like you are having some sort of difficulty using hairpins, but it isn’t clear what exactly you might be struggling with. Hairpins actually work extremely well and are not particularly difficult to add or to adjust - just see the Handbook section if you need a refresher on how they work. But if you have specific questions after reading the Handbook section, just ask and we’re happy to help!

In reply to by FBXOPWKDOIR2

So no, you didn't listen to my file. In it, the violin works far better than yours. Why? You didn't place the hairpins properly. It isn't a question of them snapping into place. Nothing works that way. Nothing. It's a question of adding them properly. For example: In the first measure of the violin part, the violin isn't playing ppp on the first note because you have the cresc hairpin starting there also. How do I know? Delete the ppp in your file and the hairpin extends to the first note. So, delete the hairpin. Put your dynamic on the first note. Range select the second note and the last not of the measure. select the cresc hairpin from the palette. Pretty simple, really.
Just because it doesn't work the way you think it should, doesn't mean it is defective.
There are plenty of things that I wish were different. But in this case, when you follow the design, it works.

In reply to by bobjp

You must be referring to the OP (sipi1995). That ain't my file. I am not the original poster. That file was included in the original ZIP file. I just uploaded it so no one needs to open the ZIP file.
But I didn't say it (Musescore) was defective. I said it needs to be more forgiving. It also needs to be more flexible with the dynamic levels during the hairpin. In other words, you guys should consider bringing back the ability to program the hairpins. If I need a f going to a fff in one beat and then the next note is ppp, I don't want to have to make invisible notes with invisible dynamics or whatever workaround exists. With MU3.6.2 I was able to program the velocity of the hairpin. I know velocities don't work in MU4. MU4 is written differently. But that doesn't mean a new subroutine can't be written. Let that be a challenge in the Google Summer of Code 2025 (assuming the world still exists at that time)

In reply to by FBXOPWKDOIR2

A far more powerful system is in development, no need to deal with old fashioned MIDI velocity. That’s still a little ways off, but meanwhile, 4.4 (coming soon) will introduce some great new improvements lime the ability to easily start or end a hairpin on any beat, to assign dynamics to specific voices, and more.

In reply to by FBXOPWKDOIR2

But you referred to their file. You pointed out what didn't work. Doesn't make any difference who posted it. I pointed out what was wrong with it, and how to make it better. No hidden anything. Please take the time to look at what I posted. Could it be better? Sure. Could MU4 be more flexible, as you put it? Sure. But the OPs file was incorrect. That's part of why it sounds bad. Do hairpins work perfectly yet. No.
You said that people who write music don't have time to fiddle with a bunch of things to get what they want. Let's be honest, f to fff in one beat, then ppp on the next is not very realistic. Second, writing music is all about fiddling with a bunch of things.

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