Opened 12 years ago

Closed 7 years ago

Last modified 6 years ago

#6104 closed defect (outdated)

CoreMIDI option does not function on ScummVM in OS X 10.5.8

Reported by: SF/ashram13 Owned by: csnover
Priority: normal Component: Port: Mac OS X
Version: Keywords:
Cc: Game:


Trying to use the true MT-32 feature of ScummVM 1.4.1 on a PowerMac G5 running Mac OS X 10.5.8 with a Roland UM-ONE USB MIDI interface connected to a Roland MT-100 (which is a Roland MT-32 with a QD drive).

The ScummVM configuration is set to output music data to CoreMIDI and the true MT-32 option is selected.

The Activity Monitor utility indicates that MIDIServer is running when ScummVM playing a game configured with the true MT-32 setting on, but the UM-ONE interface is not outputting any data at all to the MT-100. No matter what game I try, there is no MIDI output on the interface.

The interface has had the correct driver from Roland installed. Audio MIDI Setup utility indicates that the UM-ONE is present and I can confirm that the USB MIDI interface is working as I can send MIDI data to the MT-100 through the setup utility. As the settings on ScummVM are correct and the USB MIDI driver properly installed, the problem may be with ScummVM and how it works with CoreMIDI version 1.6 under OS X Leopard.

To further confirm a potential bug with ScummVM with a legacy OS, ScummVM version 1.4.1 on a MacBook Pro running OS X Lion 10.7.4 (CoreMIDI version 1.8) with the same USB MIDI interface and the same MT-100 with ScummVM having the same exact settings as that of the installation on my PowerMac G5 functions perfectly.

Ticket imported from: #3544900. Ticket imported from: bugs/6104.

Change History (13)

comment:1 by digitall, 12 years ago

ashram13: Coremidi has a number of known issues i.e. see open bug #3057005 - "MT-32 MIDI in OSX Broken Between 1.0 and 1.1 Releases":

But this sounds like an issue that should be fixed by the changes applied by Fingolfin in commits: 9095de46741c9044c2deff8ecfc911903203b6fe ad1c2a45f12bb5401ae5c0d73ef948dea734c467 ba1396954d64306578f4459f2aa418b6055c1dd2 and 78baa27e0ef9abee006327323172a2a009690e44

ashram13: Can you please try the latest development build from the link below and confirm here if that fixes the issue:

If so, then the issue will be fixed in the next release i.e. v1.5.0

comment:2 by digitall, 12 years ago

Owner: set to digitall
Resolution: outdated
Status: newpending

comment:3 by SF/ashram13, 12 years ago

Per your advice, I have downloaded the latest development build in PowerPC binary.

Unfortunately, there is no change. No MIDI data is being output from the interface under ScummVM.

comment:4 by SF/ashram13, 12 years ago

Status: pendingnew

comment:5 by digitall, 12 years ago

Owner: digitall removed
Resolution: outdated

comment:6 by digitall, 12 years ago

ashram13: OK. You have indicated that this is broken on latest development master and v1.4.1 release for OSX PPC.

Please can you try earlier versions of ScummVM to see if you can find a working version i.e. to determine if this is a recent regression? Earlier versions can be found from:

Also, can you determine the version of CoreMIDI on your OSX 10.5.8 PPC and report that?

comment:7 by criezy, 12 years ago

A note here: the commits mentioned by tdhs use a new API for CoreMIDI that was introduced in OS X 10.5. But I think the PPC build still uses the old API even on OS X 10.5. I suppose it should be possible to compile the code with the new API on 10.5 PPC and this might fix this issue.

comment:8 by SF/ashram13, 12 years ago

CoreMIDI.framework and CoreMIDIServer.framework on 10.5.8 in my G5 is 1.6.1.

MIDI data is being output in version 1.2.1. There is no MIDI output on version 1.3.0 and above.

comment:9 by SF/ashram13, 12 years ago

To clarify, there is MIDI output on ScummVM version 1.2.1 on the MacOS disk image running off my G5 running Leopard.

ScummVM version 1.3.0 and above has no MIDI output on the same computer.

comment:10 by digitall, 12 years ago

Sigh... I can't got any further as I don't use OSX. I will pass this to our OSX porter, but he is very busy IRL and the cause could be very tricky.

If you are technically capable, then doing a Git bisection for the regression would be the next step i.e. Get the ScummVM source code git tree from and run a local build: i.e. should just be ./configure && make clean && make from command line if you have the required libraries installed by Fink or similar.

Once you have confirmed the issue with the latest development HEAD, you can run "git bisect" and test a number of revision until you find the one which triggers this:

comment:11 by Strangerke, 11 years ago

Component: --Unset--Ports

comment:12 by csnover, 7 years ago

Owner: set to csnover
Resolution: outdated
Status: newclosed

People have been successfully using CoreMIDI lately, so closing as outdated.

comment:13 by digitall, 6 years ago

Component: PortsPort: Mac OS X
Note: See TracTickets for help on using tickets.