Hello<div><br></div><div>I checked a bit the usage of MDT_PREFER_MT32 and MDT_PREFER_GM,</div><div>and updated the comments concerning them.</div><div><br></div><div>Currently, MDT_PREFER_MT32 is a bit problematic. If the default audio</div>
<div>settings are used, and an engine defines MDT_PREFER_MT32, then on</div><div>desktop systems the Munt emulator is selected as a "best/preferred" device</div><div>(unless a real MT-32 device is present).</div>
<div><br></div><div>This isn't ideal IMHO, since it basically forces people to use Munt. Users</div><div>who haven't changed their music settings will probably not even know what</div><div>Munt is, and will be confused by the cryptic "you need XXX roms images" in</div>
<div>order to get it working.</div><div><br></div><div>The situation is a bit similar with MDT_PREFER_GM, but I consider this one</div><div>a "feature", as it'll pick up a GM MIDI device with the default music settings,</div>
<div>and most modern systems have GM MIDI capabilities. Thus, this one will</div><div>actually pick up a "good" setting in the games that want it, without forcing</div><div>the user to use Munt.</div><div><br></div>
<div><div>Therefore, I'm a bit baffled by the actual usage of MDT_PREFER_MT32... why is</div><div>this needed at all, other than to force people to use Munt with the default</div><div>audio settings? If a game engine requests MIDI output with MT-32 by default, and</div>
<div>the default settings can't handle that, wouldn't it be a better idea to switch to the</div></div><div>Adlib emulator by default, instead of Munt? IMHO, Munt shouldn't fire up with the</div><div>default settings, cause this is mostly confusing for people who don't know what</div>
<div>it is and get a dialog to provide ROM files which they probably don't have...</div><div><br></div><div>Regards</div><div>Filippos</div><div><br></div><div>-- </div><div>"Experience is the name every one gives to their mistakes" - Oscar Wilde <br>
</div>