I'd actually like to second this... but instead of changing the default intensity, maybe make MuseScore remember the volume intensity from the previous session? Or maybe make MuseScore remember the intensity for each project individually?
The simplest way to achieve this is to store the whole synthetizer state after every volume change. Do you people think this is an acceptable solution? Is there any potential usability problem with it?
This is how the volume setting is handled (in MuseScore 2):
* When changed through the Play Panel, volume will not be remembered on the next session - as the issue describes.
* When changed through the Synthetizer panel the volume is not stored by default, but the user has some additional options:
- clicking "store" causes the synthetizer state (including volume) to be saved in the synthetizer.xml file, and the new settings are automatically loaded when the program is started again.
- clicking "save" causes the synthetizer state to be saved in the score file; these settings are not loaded automatically, to do that the user must go to the Synthetizer Panel and click "load".
Having said that, what would be the best way to solve this issue?
OK, you're right - synthesizer volume settings are no longer remembered by default as they were in 1.3. On the other hand, the default is now a normal volume level, not the unusually quiet default of 1.3, so there will be less need to ever override it. And less likelihood that any override you make will be one'd want to make permanent by having it automatically become the new default. [EDIT: or maybe I see a reasonable default only because I previously changed it and hit Store?]
So I'm not convinced any change is needed, except that the labeling of "store" versus "save" does nothing for me. I think "Store" should be something more like "Set as default". "Save" should be something more like "Save to score" (and according to http://musescore.org/en/node/20818, it seems that may have been the case at one point).
I'm assuming there is a reason that that the "Save to score" settings are not automatically loaded with the score later, but I'd like to hear that reason explained. My initial reaction is that an explicit load should not be necessary. I guess it's so you can set up some large soundfont to be used but not have to load it every time you load the score. Or maybe it has to do with having multiple scores open - loading the soundfont with a score would change the soundfont as used for other scores. I can see that being a bad thing. And having MuseScore constantly loading and unloading soundfonts every time you switch between scores would not be ideal either.
Anyhow, I can see that loading soundfonts by default with the score might not be a great idea, but I suspect there is a better use model than the current save / load, waiting to be discovered.
Well, after some weeks no other opinion was given. After reading Marc's arguings, I agree that the current way of operation is ok, except for the button labels. In my opinion this old issue could be closed this way.
As a first-time contributor, I have a question about implementing this solution: are we allowed to change the GUI labels? Couldn't this break some translations?
As stated, there is not much to do about it. Submitted a pull request changing the button labels, to better inform the user about the way Musescore 2 works.
Comments
I'd actually like to second this... but instead of changing the default intensity, maybe make MuseScore remember the volume intensity from the previous session? Or maybe make MuseScore remember the intensity for each project individually?
This is a better idea. Default at full might be too loud.
Think that might be better :)
See also #12742: MuseScore not remembering volume from previous session
The simplest way to achieve this is to store the whole synthetizer state after every volume change. Do you people think this is an acceptable solution? Is there any potential usability problem with it?
Doesn't MuseScore already remember the synthesizer volume? Hasn't it pretty much always done this?
Marc,
This is how the volume setting is handled (in MuseScore 2):
* When changed through the Play Panel, volume will not be remembered on the next session - as the issue describes.
* When changed through the Synthetizer panel the volume is not stored by default, but the user has some additional options:
- clicking "store" causes the synthetizer state (including volume) to be saved in the synthetizer.xml file, and the new settings are automatically loaded when the program is started again.
- clicking "save" causes the synthetizer state to be saved in the score file; these settings are not loaded automatically, to do that the user must go to the Synthetizer Panel and click "load".
Having said that, what would be the best way to solve this issue?
OK, you're right - synthesizer volume settings are no longer remembered by default as they were in 1.3. On the other hand, the default is now a normal volume level, not the unusually quiet default of 1.3, so there will be less need to ever override it. And less likelihood that any override you make will be one'd want to make permanent by having it automatically become the new default. [EDIT: or maybe I see a reasonable default only because I previously changed it and hit Store?]
So I'm not convinced any change is needed, except that the labeling of "store" versus "save" does nothing for me. I think "Store" should be something more like "Set as default". "Save" should be something more like "Save to score" (and according to http://musescore.org/en/node/20818, it seems that may have been the case at one point).
I'm assuming there is a reason that that the "Save to score" settings are not automatically loaded with the score later, but I'd like to hear that reason explained. My initial reaction is that an explicit load should not be necessary. I guess it's so you can set up some large soundfont to be used but not have to load it every time you load the score. Or maybe it has to do with having multiple scores open - loading the soundfont with a score would change the soundfont as used for other scores. I can see that being a bad thing. And having MuseScore constantly loading and unloading soundfonts every time you switch between scores would not be ideal either.
Anyhow, I can see that loading soundfonts by default with the score might not be a great idea, but I suspect there is a better use model than the current save / load, waiting to be discovered.
Well, after some weeks no other opinion was given. After reading Marc's arguings, I agree that the current way of operation is ok, except for the button labels. In my opinion this old issue could be closed this way.
As a first-time contributor, I have a question about implementing this solution: are we allowed to change the GUI labels? Couldn't this break some translations?
As stated, there is not much to do about it. Submitted a pull request changing the button labels, to better inform the user about the way Musescore 2 works.
See PR #732
Merged. MuseScore 3815c2a1c1
Automatically closed -- issue fixed for 2 weeks with no activity.