How to create soundfonts that work with the new crescendo playback of MS 3.1.

After making the settings as in the picture:
You must also click the "Set as default" and "Save to Score" buttons.

And now I've retested with 3.1-Beta2; It works.

It is absolutely unhealthy to make all other fonts useless (by default) , inventing a nonsensical and nonfitting procedure, instead of using a simple and standard CC#11.

CC#7 and CC#11 combination is a standard system existing since 1996 and works even with the most primitive soundfonts.

cites from: Complete MIDI v0.1, Detailed Specification (1996); The MIDI Manufacturers Association, Los Angeles, CA

cite...
"Findings: Note surprisingly, all hardware respondents said that their devices were continuous. There were two cases in their hands. The recommended volume of CC#7 (volume) and CC#11 (expression) was used by MIDI. Roland uses the same response curve, and other Japanese manufacturers.

Of the 20 software respondents, all used CC#7 and 11 use CC#11. The largest number of software respondents (6) said they used CC#7 for dynamic expression during music playback. In 2 other cases, CC # 11 was set to a preset level and kept there."
...cite end here.

It is not a good idea to use CC#02 breathing control from the beginning. Because procedure is different (used like: velocity > aftertouch).

cite...
"Devices such as wind controllers can send Aftertouch from increasing breath pressure after the initial attack. The type of tone modification created by the Aftertouch is determined by the receiver. Aftertouch may be assigned to affect volume, timbre, vibrato, etc."
...cite (opere citato)

Strange inventions (such as: "Constant velocity; Use CC#02 (or CC#11) for dynamics") just create problems.
See what the MIDI spec says:

cite ...
Volume, Expression & Master Volume Response
Volume (CC # 7) and Expression (CC # 11) should be implemented as follows:
CC#7 is used (CC#11 is assumed #127 which):
 L (dB) = 40 log (V / 127) // where V = CC # 7 value

For situations in which controllers are used:
L (dB) = 40 log (V / 127 ^ 2) // where V = (volume x expression)
... cite (op. cit.)

A clearer formulation:
L (dB) = 40 log ((V * E) / (127 ^ 2)) // where V = volume and E = expression
If you eliminate the "40log" portion of this formula, the code for velocity and expression remains in your hand. ((V*E) / (127 ^ 2))

And the response of the software and keyboards/sound-modules should also be adjusted and measured.

cite...

               total     
CC#7 CC#11 amplitude 
--------------------
127   127   0.0dB    
 96   127  -4.8dB    
 64   127 -11.9dB    
 32   127 -23.9dB    
 16   127 -36.0dB    
  0   127  -inf.     
 
                total 
CC#7 CC#11  amplitude
--------------------
  127   96   - 4.8dB
  127   64   -11.9dB
  127   32   -23.9dB
  127    0   -inf.
   64   64   -23.9dB
   32   96   -28.8dB

...cite (op. cit.)

1996-2019 🤦‍♂️🤷‍♂️

It's a long message, and I know most of you aren't interested in that.
I keep writing it in vain; I'm sorry.

Yes, as far as I know, Zerberus doesn't support dynamic expression yet.

This is definitely possible in the SFZ format, but if I recall, Zerberus (MuseScore's SFZ player) is missing support for the opcodes necessary to make MIDI CC #2 or #11 control dynamics.

You edited your soudnfont to add the controllers as per https://musescore.org/en/node/287965#comment-951785? It should have worked, but if not, then in order for anyone to say for sure why not, you'd need to upload your soundfont somewhere and post a link here.

There is no parameter for crossfade transition in Soundfont. You can only set in which velocity regions each of the three samples will play (for example: for p-samples: 0-63, for mf-samples: 64-99, for f-samples: 100-127 ).

You could try setting the CC2 modulator amount to a smaller value. I often use 800 or 700 for the instruments used in the MuseScore GM, which means the piano dynamic levels aren't so extremely quiet compared to forte. The modulator amount works like this:

• 960 = -96 dB when CC2 is set to 0
• 800 = -80 dB when CC2 is set to 0
• 700 = -70 dB when CC2 is set to 0

Well, what I've done in MuseScore GM varies from instrument to instrument. Generally, with expressive instruments, it's not just volume, but also tone that varies with dynamics. I'm not sure which instrument this screenshot is taken from, but you can see CC2 affecting attenuation and filter. It's also important, as I've mentioned before, that you properly cancel at the instrument level any default modulators you no longer want active (e.g. note-on-velocity to attenuation). In the MuseScore GM instruments, some of the modulators are set at the instrument level and some at the preset level, but the default modulators must always be canceled or overridden at the instrument level.