A MuseScore User cannot save an instrument group selection in the "Change Instrument..." dialog of the "Edit Staff/Part Properties" dialog
When selecting the "Change Instrument..." dialog from the "Edit Staff/Part Properties" dialog, "Common instruments" is always the default selection for the instrument group. The user will need to always make a manual selection of another group such as "All instruments" or "Ethnic instruments". Users will benefit by being able to have their most recent selection saved for subsequent "Change Instrument" dialog invocations.
Advanced users will especially benefit from being able to have "All instruments" as their default selection.
Although not a major issue, this enhancement would greatly streamline many workflows.
Comments
Agreed!
+1
Better yet, a default group set in preferences.
In reply to Better yet, a default group… by ♪𝔔𝔲𝔞𝔳𝔢𝔯 ℭ𝔯𝔞𝔣𝔱𝔢𝔯♪
I think remembering the last choice is better. I don't always do classical scores, so If I do a jazz score I don't want to constantly change from Orchestra to Jazz for that score.
I have added this feature to MuseScore 3.0-dev, PR here: https://github.com/musescore/MuseScore/pull/3830
Thanks to everyone who commented here - this feature would seem to offer better ease of use to an already awesome program. Special thanks to TheOtherJThistle for adding the feature so quickly!
In reply to Thanks to everyone who… by sales@ajcinc.com
No problem, the only catch is that it won't be available until musescore 3 comes out, and even then my change might not be added into it. We'll see, I guess.
In reply to No problem, the only catch… by TheOtherJThistle
@TheOtherJThistle - I'm new to the MuseScore community. What's the process by which features get merged into main releases? Assuming this feature is does get accepted, what's a reasonable timeframe for a release? Also thinking it might be interesting to setup a dev environment and pull your changes for a build (I'm on a Mac) - any thoughts/advice?
Thanks again!
One of the main collaborators can decide to merge any features in from a pull request. Development for musescore 2.x has finished, so additions will only be made to musescore 3. To give you a sense of when that will come out, you'd be lucky if an alpha build of it came out before the end of this year (basically it'll be a while).
If you want to build the current master branch of musescore 3, follow these instructions: https://musescore.org/en/handbook/developers-handbook/compilation/compi…
It won't have my changes in yet, but if they do get merged in then it will have them eventually.
In reply to One of the main… by TheOtherJThistle
Alright - thanks for the detailed answer. We'll all hope with crossed fingers.
How difficult would you say it is to setup an initial dev/build environment for a someone versed in SW dev? What platform(s) do you work in?
Thanks again!
New PR: https://github.com/musescore/MuseScore/pull/4539
In reply to New PR: https://github.com… by TheOtherJThistle
The same thing happens in the instruments dialog. Doe this fix this also, or does there need to be another issue?
The fix is for both dialogs, so no.
Fixed in branch master, commit 59c92f5c62
fix #274540: save user choice of instrument genre
Fixed in branch master, commit f4fcf53ff6
_Merge pull request #4539 from jthistle/274540-v2-select-instrument-stay-same
fix #274540: save user choice of instrument genre_
Automatically closed -- issue fixed for 2 weeks with no activity.