Violin "Stutter" on Decrescendo Hairpin (with No Decrescendo)
Since I can't explain this easily, the searches I have tried in the forums have not come up with something that matches what I am hearing. I have a multi-note violin part that has a hairpin decrescendo to mp. When I first put the hairpin it does not do this effect, but it also doesn't decrescendo. Then after a while it starts doing the effect, which kind of sounds like the end of the theme from "Severance". I thought it was some effect button, but it appears to be a bug. And through all of that, the part does not decrescendo. We export this part as a WAV to Logic Pro, so I am somewhat dependent on it doing this correctly or I will have to apply a bunch of automation. In the attached file, this happens at measure 57-58 (it happens twice more after that). Has anyone else seen this? TIA
OS: macOS 15.5, Arch.: arm64, MuseScore Studio version (64-bit): 4.5.2-251141402, revision: ac9d3bc
| Attachment | Size |
|---|---|
| Kiss From a Rose.mscz | 805.18 KB |
Comments
Measure 57 stuttered right away for me. No, I've never heard this before. I only listened to the string part. There are lots of dynamics that don't work. Especially mp after ff. I re-entered those mp marks and they started to work. As to the problem measure, I fixed it by re-entering the hairpin and dynamic in a better place. Works on my system.
You have many places where hairpins go through dynamic marks. Marks need to be at the end to work properly
In reply to Measure 57 stuttered right… by bobjp
I will try again, but I noticed that after doing what you did, it eventually reverted to form. My friend and I are working on this arrangement and I really thought he was shooting for the "Severance" effect ... until he told me his frustrations at getting dynamics to work on the strings. Anyway, thanks for taking a poke at this and I will try your file!
In reply to I will try again, but I… by mjzwick
So it looks like you eliminated the "stutter", but the strings still don't decrescendo. I even added a pianissimo to the first eighth note in the third beat of measure 58 - NADA. I tried changing them to piano instead. Nope. I suspect that the "stutter" bug was inadvertently found when trying to get the decrescendo to work, but that measure 57-58 combo just doesn't seem to want to follow the dynamic markings. Ugh.
In reply to So it looks like you… by mjzwick
I re-opened the version I sent you. I had to, once again, delete and re-enter the mp in measure 43.
There is some kind of problem with this score, for sure. It is very difficult to say for sure what wrong.
I recall one score someone posted where the tuba all of a sudden held a note until the end of the score. It turns out that about twenty measures earlier, the person had put a pizz over one of the tuba notes. Obviously a tuba can't do that. It didn't affect the note it was on. With the pizz removed, the tuba didn't hold the later note.
The point is that somewhere in your score there is something that doesn't add up, so to speak. No idea what that might be. It could be something totally innocent looking that you wouldn't think wouldn't be a problem. I see so many hairpins through dynamics that should be corrected. A hairpin in the piano part on a whole note can't be played. Same with the acoustic guitar. Unless those instruments are going through an amp and volume pedal. Even so, there is natural decay of the sound. At least there is in Muse sounds. I don't use Basic sounds.
Measure 58 in the voice 1 part is suspect. It works, but looks awkward. I think the p should be at the beginning of the measure. I know you want the volume to decrease to the end of the note. A real singer will do that without cramming the dynamics together. Play back will be close enough. Notation software can't always do what we think it should. It's a toss up, sometimes.
In reply to I re-opened the version I… by bobjp
Thanks for sticking with this. I noticed that if I changed the "pp" to "p" at the end of the hairpin in 58, the stuttering goes away. If I instead put a "ppp", it comes back. This might be an issue with the sound font and changing the dynamics. But even though using the "p" instead gets rid of the stuttering, it does not actually decrescendo. Oh well, I guess I will need to use volume automation in Logic Pro to get what I need. The mysteries of Musescore :-)
In reply to Thanks for sticking with… by mjzwick
I did create a four-measure test for strings and using a decrescendo hairpin to pp, and it didn't go full stutter, BUT you can hear the sound font pulse in what I think is supposed to simulate vibrato. So, best I can figure, the context of our chart really kicks this into overdrive. I don't think it is a Musescore bug, but it might be a sound font one.
In reply to I did create a four-measure… by mjzwick
I agree. I spent a few hours working with just those 8 or so measures. I deleted everything else. I got close, but not quite right. There are a few problems with Muse sounds also.
A few technical notes. You have a lot of red notes in the string part because you scored it for violins. They can't play those notes, even though the font can.
The Bartok Snap pizz is going to be louder. I had better luck with volumes with the regular pizz. But it is clear from your score that MuseScore has dynamic issues.
Good luck to you.
In reply to I agree. I spent a few hours… by bobjp
Oh, and just for the fun(?) of it, I opened the score in 3.6.2. No studder, but also hairpin action.