Mixer settings treated inconsistently as part of score in the context of saving
Reported version
3.0
Type
Functional
Frequency
Many
Severity
S3 - Major
Reproducibility
Always
Status
active
Regression
No
Workaround
Yes
Project
If I change mixer settings without changing the score, the score is not shown as "changed" (with a * in the tab).
If I then close the file or program, there is no offer made to save, and the changed mixer settings are lost.
If, however, the score also has been changed, and I choose to save when asked, the changed mixer settings are indeed saved with the score.
Also, if I explicitly save the score, even if it does not show the *, the new mixer settings are also saved.
So, some "other settings" are only saved automatically when the score itself has changed, but they can be saved by hand at will. This is confusing, and probably not intended. Probably changing other settings are meant to trigger a change file action, just as changing score does.
Comments
When loading a score and just playing it, the patches stored in the mixer are not used (e.g 3rd line of the example is patched with oboe but piano is played instead). If I open the mixer and display the corresponding column, then close it and starts again playing, oboe is played. This happens since
version 3.0.3.5734 on all my files of different origins (these are not mine)
@jeanlouisgreg1 different issue, see #284426: Instruments play as piano with odd side effects