Hairpin not behaving
When I play this passage in MS, the volume of the piano jumps up suddenly at the beginning of the second measure, instead of gradually where the crescendo is indicated. If anyone can see the reason I'd appreciate it!
Musescore 3.4.2.9788.
| Attachment | Size |
|---|---|
| Crescendo.mscz | 14.62 KB |
Comments
I'm not sure why it's doing that, but I managed to fix it by adding another piano marking just before the crescendo. Hopefully that works for you. If not, I can try some more and see if anything makes a difference.
The "p" is on the top piano staff, but both the crescendo and the "mf" are on the bottom staff. They need to all be on the same staff if you want them to be considered together. Otherwise weird things happen.
In reply to The "p" is on the top piano… by Marc Sabatella
Which points at a bug, if they are all set to cover the part (default) rather than just the staff
In reply to Which points at a bug, if… by Jojo-Schmitz
Ideally it would work, but currently it is not designed to. I think there is already an issue somewhere with a suggestion to extend the design.
In reply to Ideally it would work, but… by Marc Sabatella
#198116: Diminuendo not abiding preceding dynamic of different staff in part or #62226: Problem with playback velocity with dynamics and hairpins?
In reply to #198116: Diminuendo not… by Jojo-Schmitz
Yes, thanks. Probably they are describing the same basic issue, but it would require more investigation to be sure.
Ah - thanks.
BTW my reason for the inconsistency is that sometimes attaching things to one staff or the other seems to give better results with auto-placement. If not for that, I’d say knowing the workaround is entirely sufficient - and it’s still very helpful.
In reply to Ah - thanks. BTW my reason… by scott.1
It shouldn't be the case that changing the staff would solve any autoplace problems, at least no any problems not better solved another way. But that's not to say there might be some cases that don't have great solutions. Feel free to post an example and explain the problem. This particular case, though, does seem to be one of them. Everything works perfectly if I delete the "p" on the bottom staff and add it instead to the top.
In reply to It shouldn't be the case… by Marc Sabatella
Marc, thanks. Just to explain, in this example the hairpin sits so close to the lower staff that it sort of disappears into it, and so I'd want to add some vertical separation there. But as the hairpin is attached to the upper staff, the placement offsets only seem to let me move it relatively to the upper staff - the lower staff still "sticks" to it.
My solution in this case has been to move the element to the lower staff (placement=Above). But this is how I ended up with dynamic markings inconsistently attached to either staff. Is there a better way?
I'd stress that there are very few times when I want to outsmart the autoplace logic, and this long-hairpin-next-to-empty-measure case may be too specific to worry about. I just did a score where it happened to come up repeatedly.
In reply to Marc, thanks. Just to… by scott.1
To add separation in cases like this I'd simply add a Spacer from the palette if I thought it necessary. To me, it isn't needed here at all, though. It would only be confusing to have it closer to the bottom staff if there were something actually going on the bottom staff that you didn't want to crescendo. And in that case you'd need to somehow notate that explicitly anyhow, or else anyone playing it wouldn't realize the crescendo didn't affect both staves.
Placement of hairpins is tricky, as we also try to align with dynamics on the same staff where it makes sense, and sometimes that code is a bit inflexible. Those are the times when I am most looking for workarounds, but attaching to the wrong staff isn't usually the best way. Setting the hairpin to "allow diagonal", for instance, will break the alignment with dynamics while still preserving other aspects of autoplace. That's a little known feature we could probably expose better.
In reply to To add separation in cases… by Marc Sabatella
The spacer idea is just what I needed. (And I do see your point here, but my eyesight is bad enough that a little extra space around things can be helpful.) Thanks again!