I just wander whether you know what you are missing using MT-32 not LAPC-I 😉

Oh? I assumed the LAPC-1 would sound identical to the MT-32... I thought it was basically an MT-32 + MPU-401 interface on a card.... For my purposes the only differences would be the lack of a hardware power button (to reset the synth) and the lack of a hardware control interface to set the reverb up!. (Which would mean I'd be locked into a 5/10 reverb setting by all the games that set reverb along with the rest of their sysex stuff).

It would also mean I could not use an LAPC-1 with DOSbox, because my machine has no ISA slots.... 😁

Am I mistaken?

let me rephrase that:

I just wander whether you know what you are missing using MT-32 not CM-32L 😀

I don't know if anyone here can answer this, I'd imagine only the person who wrote the win32-midi code could answer it without doing an inordinate amount of research. I see in dosbox.conf that there is a "config" statement, in addition to the "device" statement, in the [midi] block. I presume "config" is there for passing parameters to the device.

As I've now got two "synths" attached to the MPU-401 [physical MT-32 attached to my soundcard's MIDI port, and the Synth on the soundcard itself for General Midi], it would be really cool if I could specify which MIDI port the "win32" device should use. This would allow me to run games without dicking around in the control panel to switch back and forth.

robertmo,

Could you provide some details? I know absolutely nothing about the MT-32s cousins, besides the tiny bit I know about the LAPC-1.

The MT-32 lacks a small number of PCM sound-effects found in the later variants, which were utilized by an even smaller number of games. I wouldn't give it a second thought, honestly. Enjoy the MT-32.

Guest: you forget to say that after LAPC-I/CM-32L appeared games were mostly tested on lapc-i/cm-32l and that's why they don't work properly on mt-32 (buffer overflows in lots and lots of games)

Of course, my MT-32 emulator doesn't have such problems with overflows. Oh, and I promise to upload a DosBox 0.62 MT-32 emulator enabled version this weekend!

Sweet!

Not to be pushy, assuming, or anything more than slightly annoying in a strangely lovable way.. but, will this be a DosBox v0.62 with just MT-32 emulation added? Or, will it be like the 0.61 one where you had all the other test code in there (which unfortunately broke a few things making it necessary to choose between cool opengl, etc effects w/ blurring or MT-32 music... music won, btw).

Gotta say, I love your work. Both yours and the (rest of) the DosBox team. Thanks for all your efforts in the selfless pursuit of satisfying geeky nostalgia gamers world wide.

Drakk wrote:

Sweet!

Not to be pushy, assuming, or anything more than slightly annoying in a strangely lovable way.. but, will this be a DosBox v0.62 with just MT-32 emulation added? Or, will it be like the 0.61 one where you had all the other test code in there (which unfortunately broke a few things making it necessary to choose between cool opengl, etc effects w/ blurring or MT-32 music... music won, btw).

Gotta say, I love your work. Both yours and the (rest of) the DosBox team. Thanks for all your efforts in the selfless pursuit of satisfying geeky nostalgia gamers world wide.

Yes, I've kept my personal test code in for this build. Should be posted tomorrow.

> robertmo

Oh? I have vague memories of a tiny number of games that didn't run properly with the MT-32, despite claiming support. I remember buffer underruns beings part of the problems.... Interesting. I never knew why... And for the life of me, I can't recall which titles.