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

Multimeasure rest input should be made more intuitive #25961

Open
2 tasks done
Lebedinoje-O0 opened this issue Dec 31, 2024 · 2 comments
Open
2 tasks done

Multimeasure rest input should be made more intuitive #25961

Lebedinoje-O0 opened this issue Dec 31, 2024 · 2 comments
Labels
feature request Used to suggest improvements or new capabilities UX/interaction

Comments

@Lebedinoje-O0
Copy link

Your idea

The current way of entering multimeasure rests in the Musescore studio is non-intuitive. When you press M, multimeasure rests are created everywhere in the score. I mean every range of consecutive empty measures in the score. Single empty measures do not turn into multimeasure rests.

I propose a new way of multimeasure rest input. You can select the range of measures you want, and then press M. It should only create a multimeasure rest for the selected range of measures. When you select a multimeasure rest of length n and press Delete, the rest should turn into n empty measures.

Problem to be solved

This would make writing multimeasure rests easier and more intuitive. This is often needed in part scores, and sometimes, when you are composing, arranging, or transcribing a piece of music in the Musescore studio, you might need silence for a specific number of measures. Currently, when you press M, a multimeasure rest spanning the total length of empty measures is created. This also allows for 1-measure multimeasure rests. This is an example shared on Stack Exchange, which is better notated with a 1-measure multimeasure rest on both staves.

Prior art

In Noteflight, you can easily select the range of measures and click the "Multimeasure Rest" button. This is not how it works in the Musescore studio.

Additional context

No response

Checklist

  • This request follows the guidelines for reporting issues
  • I have verified that this feature request has not been logged before, by searching the issue tracker for similar requests
@muse-bot muse-bot added the feature request Used to suggest improvements or new capabilities label Dec 31, 2024
@MarcSabatella
Copy link
Contributor

The idea of allowing multimeasure measures to be enable only for individual passages is fine, but just to be clear: you really shouldn't be needing to do any of what you're describing. Multimeasure rests are created automatically when you create your parts from the score. And even if for some reason you are entering a part directly, just don't enable the multimeasure rests until you are done entering notes. There shouldn't be a reason to have to constantly fiddle with that command at all.

If that isn't clear, please ask for help on the official Support forum at musescore.org and attach your score and explain the difficulty you are having in more detail. Again, though, in most cases you never even need to think about mutlimeasure rests as it is 100% automatic.

@Lebedinoje-O0
Copy link
Author

Lebedinoje-O0 commented Jan 9, 2025

@MarcSabatella My idea makes it more intuitive. Flat.io allows you to select the first measure of the rest and type the number of measures the rest can span. Poll on X (formerly Twitter [CHIRPBIRDICON]) for Musescore studio development for version 4.5. In the poll, allow Xers to vote either for automatic multimeasure rests, the Noteflight method where you select the range of measures and use the multimeasure rest button, and the Flat method which allows you to select the first measure and type the number of measures the rest can span in the "Multimeasure Rest" dialog box. When the Noteflight or the Flat method receive the most votes (they are more intuitive), add an option in the Tools menu in v4.5, which turns every range of empty measures in your score into a multimeasure rest. Don't mention Noteflight or Flat in the poll. Since Noteflight and Flat are much less powerful than the Musescore studio, new users would like to see intuitiveness in the Musescore studio, as well as those migrating from Noteflight and Flat. Keep on focusing on matching the capabilities of Finale, Sibelius and Dorico, but also make it intuitive while making sure that all the needed functionality is fitted into the intuitive methods.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature request Used to suggest improvements or new capabilities UX/interaction
Projects
None yet
Development

No branches or pull requests

4 participants