Hairpins crest and dim not working as expected.
I like to add hidden expression markings to make my scores play back more naturally. Since the update I'm having trouble getting dynamics to playback nicely. Rather than getting a gentle raise and fall I'm getting a sudden velocity increase.
Its doing the same thing with files created with the previous version.
I've uploaded the first few bars of a song I'm transcribing as an example.
Is this a bug or am I doing something wrong?
Cheers
M
| Attachment | Size |
|---|---|
| With One Look.mscz | 19.84 KB |
Comments
should say cresc but my computer likes to incorrect my spelling
The dim. does work, the cresc. does indeed not though, which is strange, as both have their velocity change property set and to the same value (10, which isn't much, so to better here the diff I changed to 64)
Same issue in 2.2.1 and 2.1, so not a regression.
Seems the time to get it into the issue tracker
Edit: No, it does work! To hear it, set the mp's velocity to some very low value, like 5 and the velocity change of the hairpins to some high value like 127
In reply to The dim. does work, the… by Jojo-Schmitz
I found a work around. It seams that you can't have a hairpin starting on a beat with a dynamic marking attached. If I begin the crescendo on the quaver rather than the dotted crotchet in voice one of the treble stave it works.
In reply to I found a work around. It… by Mark Deighton
No, I don't think that's the issue. In your original file the dynamic marking was attached to the wrong staff - the bottom instead of top staff. Hairpins only look for dynamics on the same staff. Plus the hairpin was set to only a change of 10.
In reply to No, I don't think that's the… by Marc Sabatella
The hairpin was set to affect the whole part not just the bottom staff. This saves you having to have two hairpins on a grand staff.
In reply to The hairpin was set to… by Mark Deighton
And actually the hairpin is attached to the top stave in the file I uploaded.
In reply to The hairpin was set to… by Mark Deighton
hairpins be default cover the part/instrument, dynamics too
In reply to The hairpin was set to… by Mark Deighton
The hairpin was attached to the top staff, but the dynamic was not. Even if the effect is set to part rather than staff, the algorithm that attempts to automatically calculate the right degree of change depends on the hairpins and the corresponding dynamics to be on the same staff. Even if you've specified an explicit velocity change for the hairpin, MuseScore still looks to the same staff to find the starting dynamic, and that's what is throwing things off here. Go back to your original and do nothing but move the initial "mp" to the top staff and you'll see all is well.
In reply to The hairpin was attached to… by Marc Sabatella
Now it makes sense. I didn’t think it mattered because both the dynamic mark and the hairpin were set to affect the whole piano part. I see now that it does. Thanks for your help.