Skip to content
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

Feature request: dynamics and hairpins should automatically go above vocal staves #17883

Closed
nweininger opened this issue Jun 6, 2023 · 4 comments
Assignees
Labels
P3 Priority: Low

Comments

@nweininger
Copy link

Transferring a very old feature request here from: https://musescore.org/en/comment/1193294#comment-1193294

Still a major issue for large scores containing both vocal and instrumental staves, where no one default placement is right for all instruments.

@bkunda
Copy link

bkunda commented Jun 7, 2023

There's an easy way to achieve this already – by changing the Position of a dynamic/hairpin and choosing "Set as default style for this score".
I'll leave it to @oktophonie to decide whether this should be set as default for vocal staves.

@bkunda bkunda added the P3 Priority: Low label Jun 7, 2023
@MarcSabatella
Copy link
Contributor

MarcSabatella commented Jun 7, 2023

The problem is that this setting is score-wide. The request here is to make it staff-specific, so that mixed instrumental/vocal scores can have correct dynamic placement by default on all staves. Which absolutely makes sense to me. The hard part is figuring out which other style settings are worth making staff-specific and how to design the UI for that.

@nweininger
Copy link
Author

nweininger commented Jun 8, 2023

FWIW, for a minimal UI option, I think having the dynamics position dropdown in Format -> Style -> Dynamics have an "Auto" setting along with "Above" and "Below", where in "Auto" mode MuseScore just selects a position for each staff based on the type of instrument, would satisfy most choral-orchestral composers.

@oktophonie
Copy link
Contributor

Duplicate of #16509 and very much on the radar.

@oktophonie oktophonie closed this as not planned Won't fix, can't repro, duplicate, stale Jun 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P3 Priority: Low
Projects
None yet
Development

No branches or pull requests

4 participants