Hi Ralph,
Sorry for any inconvenience. We should have informed all beta testers about a potential conflict using soundfonts in the beta with 3.0.6-151 and higher compared to the full version 3.0.6.
Here is the general concept: Composer 3.0.7 includes a new feature "sf3 soundfont". Composer will come with the high quality .sf3 soundfont FluidR3Mono_GM.sf3 already included in the standard delivery. sf3 soundfont have a very high compression rate compared to sf2 soundfont. We have received the obligation to use these sf3 soundfonts. This gives us the opportunity to directly include high quality soundfont into the installation package.
The logic in the software is that when Composer 3.0.7 is installed, a former Composer 3.0.6 gets uninstalled. In case the soundfont setting was set to the standard soundfont TimGM6mb.sf2, this setting is replaced by the setting to the new soundfont FluidR3Mono_GM.sf3. In case somebody already loaded other sondfonts than the standard soundfont of 3.0.6 TimGM6mb.sf2, nothing is changed. With Composer 3.0.6-151 this switching of the soundfont setting is active.
The issue with the beta version 3.0.6-151 vs. 3.0.6 now is that during installation of 3.0.6-151 the new sf3 soundfont are switched active but these sf3 soundfont won't work on 3.0.6.
The workaround is to switch back the old soundfont TimGM6mb.sf2. This can be accomplished as described
here.
The old soundfont TimGM6mb.sf2 will then be available for 3.0.6-151 as well. In a next beta update the settings will be again switched to the new ones.
As mentioned, this is only an issue with the beta vs. 3.0.6 because both versions share the same settings in the Registry.
Hope this help. If you may have a issue, please let us know.
Reinhold