-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[MU4 Task] Dynamics placement per-staff, rather than global #16509
Comments
I was thinking about this too, recently. Maybe we should work towards a system where "style settings" can have multiple scopes: file-wide (to sync it between full score and part scores), score-wide, staff-wide... Of course, not for all style settings all scopes are applicable; for settings like "show system dividers", a staff scope would be pointless. At some point there was some discussion about what to do with the "staff type" settings (that can be found in the "Staff/Part properties" dialog); this might also be a good solution for some of those. |
There are many options that could go in here: placement of dynamics, tuplet markings, articulations, fingerings, even which staves should have system markings duplicated above them, which staves should be always shown/hidden in different situations, etc. I know @Tantacrul is keen to dismember (or at least totally overhaul) the current silly Stave/part properties window, too. It is easy to imagine other 'per-stave' options that could be added: e.g. an option for 'old-style' vocal beaming (notes only beamed together for melismas), and so on. |
Came up again in https://musescore.org/en/node/364157 |
In scores with vocal music as well as instruments, a global setting for dynamics placement is not enough. Vocal staves should normally have their dynamics default to above the music, while instruments should default to below, and grand staves should default to between the two staves. It's not enough to detect lyrics and shift the dynamics - sometimes vocal scores don't have lyrics on some singers but the dynamics should still appear above the staff.
The text was updated successfully, but these errors were encountered: