|
|
Joined: May 2006
Posts: 132
Senior Member
|
OP
Senior Member
Joined: May 2006
Posts: 132 |
Did a bit of digging, but didn't really find the documentation I need for this. Hopefully I didn't just miss something really obvious (and if I did, it's fodder for the MAME FAQ at least, right?)
How exactly does MAME's MIDI output work? How can I direct it to a Windows MIDI device so that I can have a MT-32 hooked up to my virtual machine?
I've been looking at this in QMC2 and I've got a Sound Blaster hooked up and a midi port attached as a result, but I'm not sure what to do next.
|
|
|
|
|
Joined: Mar 2001
Posts: 16,676 Likes: 4
Very Senior Member
|
|
Very Senior Member
Joined: Mar 2001
Posts: 16,676 Likes: 4 |
On the command line, -listmidi shows available MIDI I/O ports on your machine. You then -midiout "name of port that's connected to the MT-32".
Not sure if QMC2 actually supports that properly or not - it's definitely a special case compared to normal slot devices.
|
|
|
|
|
Joined: May 2008
Posts: 4,899
Very Senior Member
|
|
Very Senior Member
Joined: May 2008
Posts: 4,899 |
Is "-midiout" documented somewhere  ? So no, QMC2 doesn't support this (yet).EDIT: oh, if it's a slot-device it should work.
Last edited by qmc2; 06/11/15 10:57 AM.
A mind is like a parachute. It doesn't work unless it's open. [Frank Zappa]We're searching for QMC2 translators and support for existing translations. Interested? See here!
|
|
|
|
|
Joined: Mar 2001
Posts: 16,676 Likes: 4
Very Senior Member
|
|
Very Senior Member
Joined: Mar 2001
Posts: 16,676 Likes: 4 |
When MIDI is available, it will appear in -listslots. For instance, "mame64 at486 -isa5 mpu401" will then have this in -listslots: isa5:mpu401:mpu401:mdin midiin MIDI In port
isa5:mpu401:mpu401:mdout midiout MIDI Out port The special case is that you have to parse the -listmidi output to get the actual values they accept, you can only determine their presence with -listslots. For instance, on my Linux machine:
MIDI input ports:
Midi Through Port-0
KeyStudio MIDI 1 (default)
MIDI output ports:
Midi Through Port-0 (default)
M-Audio MIDI Out A
M-Audio MIDI Out B The two listed under "input ports" are available for -midiin, and the "output ports" work with -midiout. Note that you must include the full name as listed, with the shortcut that the port listed as (default) can also be named as just "default".
Last edited by R. Belmont; 06/11/15 11:00 AM.
|
|
|
|
|
Joined: May 2008
Posts: 4,899
Very Senior Member
|
|
Very Senior Member
Joined: May 2008
Posts: 4,899 |
OK, as I said in my edit, if it's a slot device it should work... but QMC2 doesn't use "-listmidi" to suggest actual MIDI output devices (yet).
A mind is like a parachute. It doesn't work unless it's open. [Frank Zappa]We're searching for QMC2 translators and support for existing translations. Interested? See here!
|
|
|
|
|
Joined: Mar 2001
Posts: 16,676 Likes: 4
Very Senior Member
|
|
Very Senior Member
Joined: Mar 2001
Posts: 16,676 Likes: 4 |
Ok. It's valid for there to be no MIDI devices of a type, so be careful parsing
|
|
|
|
|
Joined: May 2008
Posts: 4,899
Very Senior Member
|
|
Very Senior Member
Joined: May 2008
Posts: 4,899 |
I get this on my system: MIDI input ports:
Midi Through Port-0 (default)
MIDI output ports:
Midi Through Port-0 (default) Does this mean "Midi Through Port-0" is a valid string for "midiin" and "midiout" in my case? If I understand your last post correctly you're saying that the output after "MIDI input ports:" and/or "MIDI output ports:" could also be empty? Right?
A mind is like a parachute. It doesn't work unless it's open. [Frank Zappa]We're searching for QMC2 translators and support for existing translations. Interested? See here!
|
|
|
|
|
Joined: Mar 2001
Posts: 16,676 Likes: 4
Very Senior Member
|
|
Very Senior Member
Joined: Mar 2001
Posts: 16,676 Likes: 4 |
Correct and correct. That Through port is a virtual pipe provided by ALSA.
|
|
|
|
|
Joined: May 2008
Posts: 4,899
Very Senior Member
|
|
Very Senior Member
Joined: May 2008
Posts: 4,899 |
Thank you! QMC2 SVN r6730 should support this now (despite possible bugs).
A mind is like a parachute. It doesn't work unless it's open. [Frank Zappa]We're searching for QMC2 translators and support for existing translations. Interested? See here!
|
|
|
|
|
Joined: May 2008
Posts: 4,899
Very Senior Member
|
|
Very Senior Member
Joined: May 2008
Posts: 4,899 |
I wanted to test my implementation, and this is the command line QMC2 generates when I map the two MIDI interfaces to the midiin/midiout devices (which should be fine): mame64 <...> at486 -isa5 mpu401 -midiin "Midi Through Port-0" -midiout "Midi Through Port-0" I'm unable to test this, though, because MAME reports a missing ROM: roland_6801v0b55p.bin NOT FOUND (tried in at486 ibm5170 mpu401) However, the isa_mpu401 device doesn't have any ROMs:
<machine name="isa_mpu401" sourcefile="src/emu/bus/isa/mpu401.c" isdevice="yes" runnable="no">
<description>Roland MPU-401 MIDI Interface</description>
<chip type="cpu" tag=":mpu401:mpu6801" name="M6801" clock="4000000"/>
<slot name=":mpu401:mdin">
<slotoption name="midiin" devname="midiin_port" default="yes"/>
</slot>
<slot name=":mpu401:mdout">
<slotoption name="midiout" devname="midiout_port" default="yes"/>
</slot>
</machine>
Maybe I'm missing something, but how can it be expecting this ROM then?
A mind is like a parachute. It doesn't work unless it's open. [Frank Zappa]We're searching for QMC2 translators and support for existing translations. Interested? See here!
|
|
|
|
2 members (ssj, r09),
36
guests, and
2
robots. |
|
Key:
Admin,
Global Mod,
Mod
|
|
|
Forums9
Topics8,879
Posts116,752
Members4,957
| |
Most Online890
Jan 17th, 2020
|
|
|
|
