Problem with ScummVM's MT-32 emulation in Discworld

Ask for help with ScummVM problems

Moderator: ScummVM Team

Post Reply
mudpuppy
Posts: 13
Joined: Sun May 13, 2007 10:44 pm

Problem with ScummVM's MT-32 emulation in Discworld

Post by mudpuppy »

I am having a problem using ScummVM's built-in MT-32 emulator in Discworld (CD version).
I have the same problem with both ScummVM v1.6 under Linux Mint 17, and ScummVM v1.7 under Windows 7 x64, but only with Discworld.

Is this a known issue with Discworld? or is there some configuration change I need to make with Discworld that isn't necessary for other games?

When I start Discworld, it throws up this message:
The selected audio device 'MT-32 Emulator' cannot be used. See log file for more information. Attempting to fall back to the next available device...
Then the game proceeds to play, but uses Adlib for the midi music (at least I think it's Adlib).

If I close ScummVM immediately after seeing the error message, the log says
[2014-09-16 12:15:07] ScummVM 1.6.0 (Aug 8 2013 12:10:18)
[2014-09-16 12:15:07] Vorbis FLAC MP3 ALSA SEQ TiMidity RGB zLib FluidSynth Theora
[2014-09-16 12:15:07] --- Log opened.
[2014-09-16 12:15:07] WARNING: SDL mixer output buffer size: 1024 differs from desired: 2048!
[2014-09-16 12:15:59] WARNING: The MT-32 emulator requires one of the two following file sets (not bundled with ScummVM):
[2014-09-16 12:15:59] Either 'MT32_CONTROL.ROM' and 'MT32_PCM.ROM' or 'CM32L_CONTROL.ROM' and 'CM32L_PCM.ROM'!
[2014-09-16 12:17:07] --- Log closed successfully.
If I continue playing the game for a few more minutes, I get a lot of warnings about Adlib in the log:
[2014-09-15 21:55:40] ScummVM 1.6.0 (Aug 8 2013 12:10:18)
[2014-09-15 21:55:40] Vorbis FLAC MP3 ALSA SEQ TiMidity RGB zLib FluidSynth Theora
[2014-09-15 21:55:40] --- Log opened.
[2014-09-15 21:55:40] WARNING: SDL mixer output buffer size: 1024 differs from desired: 2048!
[2014-09-15 21:57:23] WARNING: The MT-32 emulator requires one of the two following file sets (not bundled with ScummVM):
[2014-09-15 21:57:23] Either 'MT32_CONTROL.ROM' and 'MT32_PCM.ROM' or 'CM32L_CONTROL.ROM' and 'CM32L_PCM.ROM'!
[2014-09-15 21:57:56] WARNING: AdLib: Unknown control change message 11 (67)!
[2014-09-15 21:57:57] WARNING: AdLib: Unknown control change message 11 (66)!
[2014-09-15 21:57:57] WARNING: AdLib: Unknown control change message 11 (65)!
[2014-09-15 21:57:57] WARNING: AdLib: Unknown control change message 11 (64)!
[2014-09-15 21:57:57] WARNING: AdLib: Unknown control change message 11 (63)!
[2014-09-15 21:57:58] WARNING: AdLib: Unknown control change message 11 (62)!
[2014-09-15 21:57:58] WARNING: AdLib: Unknown control change message 11 (61)!
[2014-09-15 21:58:03] WARNING: AdLib: Unknown control change message 11 (60)!
[2014-09-15 21:58:03] WARNING: AdLib: Unknown control change message 11 (59)!
[2014-09-15 21:58:04] WARNING: AdLib: Unknown control change message 11 (58)!
[2014-09-15 21:58:09] WARNING: AdLib: Unknown control change message 11 (59)!
[2014-09-15 21:58:10] WARNING: AdLib: Unknown control change message 100 (0)!
[2014-09-15 21:58:10] WARNING: AdLib: Unknown control change message 100 (0)!
[2014-09-15 21:58:10] WARNING: AdLib: Unknown control change message 100 (0)!
[2014-09-15 21:58:10] WARNING: AdLib: Unknown control change message 100 (0)!
[2014-09-15 21:58:10] WARNING: AdLib: Unknown control change message 100 (0)!
[2014-09-15 21:58:10] WARNING: AdLib: Unknown control change message 100 (0)!
[2014-09-15 21:58:10] WARNING: AdLib: Unknown control change message 6 (2)!
[2014-09-15 21:58:10] WARNING: AdLib: Unknown control change message 6 (2)!
[2014-09-15 21:58:10] WARNING: AdLib: Unknown control change message 6 (2)!
[2014-09-15 21:58:10] WARNING: AdLib: Unknown control change message 6 (2)!
[2014-09-15 21:58:10] WARNING: AdLib: Unknown control change message 6 (2)!
[2014-09-15 21:58:10] WARNING: AdLib: Unknown control change message 6 (2)!
[2014-09-15 21:58:10] WARNING: AdLib: Unknown control change message 11 (127)!
[2014-09-15 21:58:10] WARNING: AdLib: Unknown control change message 11 (127)!
[2014-09-15 21:58:10] WARNING: AdLib: Unknown control change message 11 (127)!
[2014-09-15 21:58:10] WARNING: AdLib: Unknown control change message 11 (127)!
[2014-09-15 21:58:10] WARNING: AdLib: Unknown control change message 11 (127)!
[2014-09-15 21:58:10] WARNING: AdLib: Unknown control change message 11 (127)!
[2014-09-15 21:58:10] WARNING: AdLib: Unknown control change message 101 (0)!
[2014-09-15 21:58:10] WARNING: AdLib: Unknown control change message 101 (0)!
[2014-09-15 21:58:10] WARNING: AdLib: Unknown control change message 101 (0)!
[2014-09-15 21:58:10] WARNING: AdLib: Unknown control change message 101 (0)!
[2014-09-15 21:58:10] WARNING: AdLib: Unknown control change message 101 (0)!
[2014-09-15 21:58:10] WARNING: AdLib: Unknown control change message 101 (0)!
[2014-09-15 21:58:39] --- Log closed successfully.
The same configuration and rom files work for MT-32 emulation in every other game I've played which supports MT-32, including Sierra games like the King's Quest games, Quest for Glory, Hoyle's Book of Games, etc. So far Discworld is the only game I've found that has a problem with ScummVM's MT-32 emulation. MT-32 emulation for Discworld doesn't work with either my MT32 roms or my CM32L roms. But since MT-32 emulation works properly for other games, I don't think the problem is with my configuration or my roms -- unless Discworld is looking for a particular version of the roms while other games don't.

Discworld does work with an actual MT-32 in ScummVM -- at least it works with an MT-100 (which contains an MT-32) on the Windows 7 computer after configuring ScummVM to use external midi. But I'd like to get MT-32 emulation working on the Linux Mint computer if possible.
User avatar
eriktorbjorn
ScummVM Developer
Posts: 3558
Joined: Mon Oct 31, 2005 7:39 am

Post by eriktorbjorn »

One possible explanation for the MT-32 emulator not working is that ScummVM was initializing it before it had had the time to add the "extra path" to the list of folders to look for files in. I've just committed a small fix to the development version of ScummVM that should fix that particular problem.
Post Reply