From: "Mark J. Small" <msmall@eastlink.ca>
To: linux-msdos@vger.kernel.org
Subject: Arggh, midi is driving me nuts.
Date: Fri, 10 Jun 2005 13:39:49 -0300 [thread overview]
Message-ID: <200506101339.50231.msmall@eastlink.ca> (raw)
I've been scouring the documentation and google searches for days trying to
get midi music to play with dosemu. I know this can be done, but it just
doesn't seem to be working for me.
I'm running a developer build 1.3.1 on a debian Sarge system. Kernel version
is 2.6.11. 7 I have a Soundblaster Live card and the wavetable is working
properly.
I can play midi files using midiplay -a foobar, pmidi -p 65:0 foobar, and
kmid. I can alsa use timidity as an alsa device, and play using pmidi -p
129:0.
I have tried linking from ~/.dosemu/run/dosemu-midi
to /dev/midi, /dev/amidi, /dev/snd/midiC0D0,1,2,3.
I have also tried loading a virtual midi card using modprobe snd-virmidi. I
then use aconnect to connect 75:0 to the one of the wavetable ports. I then
link dosemu-midi to /dev/midi1, /dev/amidi1, /dev/snd/midiC0D3.
In all cases, I get no sound at all when I try to play a midi file using
megamidi. If I try to use the Tie Fighter Sound Setup program, the sound
setup freezes.
IF I turn on sound and hardware debug messages I can zillions of these:
MPU401: Read status port = 0xbf
Can anyone tell me what I'm doing wrong? I've seen in the mailing list
archives that Marko Sormunen has an identical setup working properly.
Mark Small
next reply other threads:[~2005-06-10 16:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-10 16:39 Mark J. Small [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-06-11 19:25 Arggh, midi is driving me nuts Stas Sergeev
2005-06-13 17:00 Mark J. Small
2005-06-13 17:42 ` Robert Komar
2005-06-13 17:54 Mark J. Small
2005-06-13 20:43 Mark J. Small
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200506101339.50231.msmall@eastlink.ca \
--to=msmall@eastlink.ca \
--cc=linux-msdos@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox