From: "Mark J. Small" <msmall@eastlink.ca>
To: linux-msdos@vger.kernel.org
Subject: Re: Arggh, midi is driving me nuts.
Date: Mon, 13 Jun 2005 14:00:07 -0300 [thread overview]
Message-ID: <200506131400.07957.msmall@eastlink.ca> (raw)
On June 11, 2005 04:25 pm, you wrote:
> Hello.
>
> Mark J. Small wrote:
> > I have tried linking from ~/.dosemu/run/dosemu-midi
> > to /dev/midi, /dev/amidi, /dev/snd/midiC0D0,1,2,3.
>
> Here's what can get you on track.
> Remove the dosemu-midi entirely
> and play some midi from under
> dosemu. It will create the new
> dosemu-midi, just a regular file,
> and it should contain the raw midi
> data. If it does - on dosemu side
> everything is fine.
> Then do something like
> cat dosemu-midi >/dev/midi
> It will write the recorded midi
> data to your device and you should
> hear some noice. If the noice is
> there, everything is allright.
Thanks for the reply.
I think I've got it figured out now. My problem was that I did most of my
troubleshooting using the tie fighter installer. It doesn't seem to work
well with doesmu's midi stuff. When I tried to test the midi settings within
the tie fighter installer, the dosemu-midi file was created but was size
zero. When I tried to play with megamid, things worked as you said.
Now a have a symlink from dosemu-midi to /dev/amidi, and megamid will play
midi files happily from within dosemu.
I guess Tie Fighter does something that is incompatable with dosemu's midi
support.
Digital sound is pretty choppy too when I play the game unless I set the
resolution to 320x240. I guess an Athlon XP 2000 can't quite emulate an
early Pentium. Doh.
Mark
Mark
next reply other threads:[~2005-06-13 17:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-13 17:00 Mark J. Small [this message]
2005-06-13 17:42 ` Arggh, midi is driving me nuts Robert Komar
-- strict thread matches above, loose matches on Subject: below --
2005-06-13 20:43 Mark J. Small
2005-06-13 17:54 Mark J. Small
2005-06-11 19:25 Stas Sergeev
2005-06-10 16:39 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=200506131400.07957.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