Problems about crescendos and diminuendos with MuseScore4
When I add a > (diminuendo) mark, it affects all parts of that line.
As following pics.
So do all other dynamix lining marks like crescendo.
| Attachment | Size |
|---|---|
| This diminuendo mark affects all 1.png | 69.92 KB |
| This diminuendo mark affects all 2.png | 81.57 KB |
Comments
It's normal that on piano, dynamics affects both staves. Additional controls for this are expected to return in the future.
In reply to It's normal that on piano,… by Marc Sabatella
It's also not unusual to see separate (and different) dynamics for the two staves of a single piano.
So this regression in MS4 is unfortunate, because the lack of volume control over the separate staves affects the playback of scores created in MS3 and earlier.
In reply to It's also not unusual to see… by DanielR
What can I do to improve or achieve the goal in other ways?
In reply to What can I do to improve or… by dodddsqa
You can:
- either wait for a future update of MS4 to fix the problem
- or use MS 3.6.2
- or use MS4 with 2 piano instruments (one for RH stave and the other for LH stave).
Sorry, not very comfortable suggestions...
In reply to You can: - either wait for a… by DanielR
See my recent for another alternativer (velocity override), but I like your last last suggestion here. The main downside is you lose cross-staff notation, but, as long as you don't need both that and the independent dynamics on the same system, you can use "hide empty staves" to show the right staff at the right time.
In reply to What can I do to improve or… by dodddsqa
The main shift in thinking with MuseScore 4 is towards overriding playback details on the notes themselves instead of on the dynamics. So, the idea would be, if you want the notes to sound other than what the dynamics indicate, you'd override the velocity on the notes. In theory, it's an OK setup, but a) it doesn't work for Muse Sounds), b) the mechanism for setting velocity is currently more awkward than need be, and c) it also doesn't necessarily keep up to date as you edit customized passages. These are known limitations being worked on for future updates.
Meanwhile, what you can do is switch to MS Basic, and manually set the velocities as desired via the Playback section in Properties.