MT-32 rom path

[Michael Doma]

Dear Toni,

tried this new feature and I'm happy with it (OctaMED loads and plays midi)! But why hardcode the rom path instead of using the well-proven rom scanner? People don't read changelogs...! Is this going to change?


For anyone wondering about the difference between MT-32 and CM-32L, I have found this:

As I can see, the exactly VCA circuitry (as per the schematic) is identical. But right, the output amplifiers after the VCA are a bit different. Seems, the LPF implementation and the reverb are also identical. And obviously, there are differences in routing the PCM ROMs as there are two in CM-32L.

Anyway, I think new MT-32 differs from the old one much more than from CM-32L.

Generation 1 - v1.x MT-32
Generation 2 - v2.x MT-32, CM-32L, CM-64, LAPC-I
Generation 3 - CM-32LN, CM-500, LAPC-N

Regards,

Michael

[Toni Wilen]

Because it is not directly Amiga related, very few care about that thing and there is already sort of standard for MT ROM and and I am not interested in having all kinds of weird stuff in ROM scanner.

[Michael Doma]

Just in case anyone tries the MT-32 to get a better sound when playing General Midi files (like i did) :

Although Roland has released some SysEx-Midi-files*) that reconfigure the MT-32/CM-32L into a General Midi device, this doesn't work very well for many General Midi files out there...

*) https://www.midimusicadventures.com/...ties/mt2gm.exe

So better use the "Microsoft GS Wavetable Synth" instead and replace your GM.DLS file with a better one. That file holds all GM instrument data and is located in \Windows\SysWow64\drivers and in \Windows\system32\drivers.
Such a replacement can be found here:

https://www..com/download/budzyjadukpjeud/gm.dls

There are others floating around.

Only use MT-32/CM-32L for Midi files (or games) that are specifically designed for that device.