Mixer not remembering changes in the channels

• Jun 2, 2019 - 18:46
Reported version
3.1
Priority
P1 - High
Type
Performance
Frequency
Many
Severity
S2 - Critical
Reproducibility
Always
Status
fixed
Regression
Yes
Workaround
No
Project
  1. Install most recent revision to MS3. (3.1.0.7078)
  2. Make a new score
  3. Open Mixer and specify an instrument patch from installed soundfont library. (This problem appears to occur for libraries installed above the default MuseScore_General soundfont library.)
  4. Confirm that the patch delivers intended sound.
  5. Save file.
  6. Close MS3.
  7. Relaunch MS3, and open previously saved file.
  8. No sound, as the specified patch was not saved at item #5.
  9. Reapplying the patch in the Mixer again produces the requisite sound, but the patch specified is not saved.
  10. This problem only applies to files produced after revision 3.1.0.7078; files produced prior to this save changes in soundfont patches without problems.
  11. See https://musescore.org/en/comment/923882#comment-923882 for discussion.

Comments

Jun 4, 2019 - 05:09

Going back to 3.0.5 should be sufficient, as this is a 3.1 regression

Jun 4, 2019 - 11:08

And that does not have this issue? If so this would restrict the possible culprit changes quite a lot.

In reply to by Jojo-Schmitz

I don't know, frankly I don't see the relationship by reading the code of the PR submitted at that time, in the 289562 issue you mention ( https://github.com/musescore/MuseScore/commit/f131df20b2a2c4eaa0a567c3a…).

Just rechecked again in 3.1-RC, now exiting MuseScore, deleting the non-default soundfonts in the Synthetiser (so leaving the default sf only), then loading the saved sf's +mixer assigments using "Load from Score", and it loads and plays them ok)

...I just tried with the official 3.1 (final) and well, maybe I'm wrong, but using the "Save to Score" option in the Synthetiser (ie: explicitely saving the synth settings with the score) , saving the score, closing completely MuseScore, opening the score again, and lastly using "Load from Score" , works fine??

In reply to by Xianyue賢越

@Xianyue, well, since Musescore 2.0, I've always had to use the "Save to Score" button in the Synthetiser window to save with the score the list of used soundfonts and synth settings (and the Mixer patch assigments), when using customized settings in this area. Just saving the score (File / Save or Save As) at least for me didn't saved these customized items in the score file itself (when using non default settings for the soundfont/mixer patches/other synth settings).

Jun 4, 2019 - 14:04

In reply to by dilon2001

it's confusing to users, i always try to convince myself it means "commit" or "Apply to Score for later saving", common sense "Save" = "save everything"?

Jun 4, 2019 - 16:24

Came up again in https://musescore.org/en/node/290159.

I think this issues severity should be upgraded to S1 - Blocker due to all of the confusion it's causing and the large number of reports related to it.

In reply to by dilon2001

You are right, considering my sf2/sfz collection is getting bigger & bigger:
collection size.JPG

It is indeed there must have a way to save customized items out of these thousands of fonts for using later. In the same App, top menu "Save Style...", "Load Style..." to a .mss file is a good example of implementing this and practically more acceptable and feasible to users, it's independently existing there ready for use forever without loading any score and retrieving from it. Having "Save Fonts Config...", "Load Fonts Config..." also is helping to achieve overall App user interface and function consistency.

Similar to style saving, users can save customized fonts selection for different types of scores, and give them meaningful names like "Violin Duet", "Dancing Guitar", "String Quarts", "WoodwindMarch", "Magic Flutes", "MuseScore 3.2 Default" ....

Jun 4, 2019 - 17:21

Xianyue賢越, you need to put your comments not related to the issue at hand in the forum. It worked fine in the past and the regression needs to be fixed.

Jun 6, 2019 - 19:06

The nightly doesn't replace your installed version, so your last version is still there.

In reply to by Jojo-Schmitz

Thank you for your continued help. I can't seem to get 3.0.5.
I'm assuming that's because I have a Mac.
The latest version I can find is 2.3.2.
It is opening and playing my documents correctly. Regular Standard is working for percussion. I don't even
need to switch it.
I'm going to keep looking for 3.0.5. Perhaps I'm doing something wrong.

Jun 6, 2019 - 19:32

Someone familiar with Mac will have to help you with this. You should move further discussion of this to the forum since it's not really related to this issue.

Jun 8, 2019 - 22:02

In the meantime until a new release fixes this, is it posible to save the mixer settings directly to the mscx file? Or, what is equivalent, to write the edits directly to the mscx file.

Jun 9, 2019 - 20:13

In reply to by fmiyara

I am unable to save mixer patch changes in the MSCX format. So far the nightlys have not made a difference. I have been able to post using 3.0.5.

Jun 9, 2019 - 20:47

The fix has not been merged and no nightly created. As long as the issue status is PR created, you won't find a nightly for it. The nightly is created after the status is changed to Fixed.

In reply to by edukehtoer

I mean if there is some documented syntax to define the patch (or whatever is planned to be included to allow saving the mixer patch settings); one that, even if not written by MuseScore itself, is recognized when loading the score from the mscx to set automatically the patches to be used. If this were the case, it would be possible to manually input the required tags.

Jun 12, 2019 - 07:18

Does <controller ctrl="32" value="0"/> help?

In reply to by Jojo-Schmitz

Jojo-Shmitz,

> Does <controller ctrl="32" value="0"/> help?

Do you mean placing this Bank change each time I need the original sound?
For instance:

<Channel name="pizzicato">
<color>-65281</color>
<program value="45"/>
<controller ctrl="10" value="80"/>
<controller ctrl="32" value="0"/>
<synti>Fluid</synti>
<midiPort>1</midiPort>
<midiChannel>11</midiChannel>
</Channel>

Is this correct?
Is this what MuseScore will do when the bug be fixed?