MT-32 original hardware display message

General chat related to ScummVM, adventure gaming, and so on.

Moderator: ScummVM Team

Post Reply
John_Beavers
Posts: 3
Joined: Fri Jan 04, 2019 2:45 am

MT-32 original hardware display message

Post by John_Beavers » Fri Jan 04, 2019 1:59 pm

Hello everyone !

I'm currently seting up a SCUMMVM instance.
I send the sound signal to a real Roland MT-32 device (via midi).

Natively (and via dosbox) you get nice little messages on the display of the machine.
For example, before Monkey2 begins you can read "Lucasfilm games".

With SCUMMVM, all messages are replaced with "SCUMMVM 2.0.0".

Here is an illustration :
https://www.journaldulapin.com/wp-conte ... 68x448.jpg

Is there a way to get the original message on the MT-32 display with SCUMMVM ? What could I do ?

Thank you for your time :)
Cheers !

digitall
ScummVM Developer
Posts: 1007
Joined: Thu Aug 02, 2012 1:40 pm

Re: MT-32 original hardware display message

Post by digitall » Fri Jan 04, 2019 6:25 pm

I would suggest testing with earlier stable releases of ScummVM i.e. 1.0.0 and see if this is a recent regression.

Those messages are set by MIDI SysEx messages which are dependent on the game, game engine and backend driver down through SDL / native MIDI driver and USB to MIDI interface. I am not sure where we send "SCUMMVM 2.0.0" as I can't locate that in the relevant backend MIDI or audio code nor the engine code for SCUMM games so it may be the default set by the native MIDI driver based on the Window ID of the source program or something.

I would assume you are using Windows? We would need a lot more detail i.e. OS version, USB-MIDI cable type to begin to try to track down why this occurs.

I think this does work as the "INSERT BUCKAZOID" message is emitted from Space Quest III using the SCI engine.

John_Beavers
Posts: 3
Joined: Fri Jan 04, 2019 2:45 am

Re: MT-32 original hardware display message

Post by John_Beavers » Fri Jan 04, 2019 10:48 pm

Hello digitall,
Thank you for your input,

I tested it with Space Quest 3 and got the "INSERT BUCKAZOID" message just fine. Nice cross-test :)

I do use Windows 10 Pro.
To plug the MT-32 (old, no jack on the back) I use a "Behringer U-PHORIA UMC204HD". It is a USB audio interface.

https://www.musictribe.com/Categories/B ... HD/p/P0BK0

I mainly use it to record Microphones with XLR cables and it happens to have what seems to be a solid MIDI Out.
Basically it goes like PC > USB midi interface > MT-32 > Speakers.

I use ScummVM 2.0.0 (it did the same with an old 1.4.1 version I had at first).
I tryed version 1.0.0 found on github and got "SCUMMVM 1.0.0" on the screen. I tested with monkey2.

It is interesting that it works with Space Quest 3 though.

digitall
ScummVM Developer
Posts: 1007
Joined: Thu Aug 02, 2012 1:40 pm

Re: MT-32 original hardware display message

Post by digitall » Sat Jan 05, 2019 12:02 am

Hmm. Well, not surprising as internally ScummVM is not a single engine, but a collection of reimplemented engines for various games. SCI which is used for Space Quest 3 sends the required SysEx data to the MT-32 to get that message. Which games do not show the same messages? I assume mainly Monkey2 and other SCUMM games. This is probably as that functionality was not duplicated compared to the original interpreter since this does not appear to be a recent regression.

John_Beavers
Posts: 3
Joined: Fri Jan 04, 2019 2:45 am

Re: MT-32 original hardware display message

Post by John_Beavers » Sat Jan 05, 2019 1:20 am

I see, it makes sense.

Here are 6 other tests I did tonight :

Indy Atlantis : SCUMMVM 2.0.0
Quest for glory : Original message (<< TRIAL BY FIRE >> and then QUEST FOR GLORY II)
Larry 3 : Both Original messages at the begining and the joke when you exit.
Simon the sorcerer : Nothing
Future Wars : Nothing (expected)
Beneath a steel sky : Buffer Overflow >< (I'll use Munt for this one)

I am still amazed by the fact that you can have MT-32 music, sound effects and voices at the same time !
This is why I use SCUMMVM.
If Lucas games do not display the right message, it is a fair price to pay and I don't think I can ask for a better solution.

Thank you again for digging into that. I hope this post will help or at least inform others in the future.

Post Reply