From: Dave Phillips <dlphillips@woh.rr.com>
To: x.zupftom@web.de
Cc: linux-msdos@vger.kernel.org, Tony Borras <tonyb@sysdev.org>
Subject: Re: MIDI input
Date: Thu, 12 Jun 2008 20:50:22 -0400 [thread overview]
Message-ID: <4851C44E.7000102@woh.rr.com> (raw)
In-Reply-To: <163630495@web.de>
x.zupftom@web.de wrote:
> [snip]
>
> I already tried
> cat /dev/midi1 > test.txt
> and it writes some garbage to test.txt - so MIDI input via midi1 is working. My problem is now how to connect /dev/midi1 to dosemu-midi_in. If it's already connected by
> ln -s /dev/mid1 ~/.dosemu/run/dosemu-midi_in
> then how can I test whether Dosemu receives the data?
I've been running Voyetra's Sequencer Plus Gold under DOSemu for many
years. I load the ALSA virtual MIDI module (modprobe snd-virmidi) then I
link the DOSemu MIDI I/O like so:
ln -s /dev/snd/midiC2D0 ~/.dosemu/run/dosemu-midi
ln -s /dev/snd/midiC1D0 ~/.dosemu/run/dosemu-midi_in
where midiC2D0 is the ALSA virmidi module and midiC1D0 is the external
MIDI port on my PCI soundcard.
Just to be sure, I tested MIDI input with these connections before I
posted this message. It worked fine. :)
Best,
dp
next prev parent reply other threads:[~2008-06-13 0:50 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-12 23:47 MIDI input x.zupftom
2008-06-13 0:50 ` Dave Phillips [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-07-12 13:38 x.zupftom
2008-06-18 22:41 x.zupftom
2008-06-19 12:11 ` Dave Phillips
2008-06-18 20:47 x.zupftom
2008-06-18 22:09 ` Dave Phillips
2008-06-18 13:09 x.zupftom
2008-06-18 13:37 ` Dave Phillips
2008-06-16 21:22 x.zupftom
2008-06-16 23:23 ` Dave Phillips
2008-06-15 9:42 x.zupftom
2008-06-16 16:38 ` Dave Phillips
2008-06-13 21:54 x.zupftom
2008-06-13 18:09 x.zupftom
2008-06-12 22:12 x.zupftom
2008-06-12 22:57 ` Tony Borras
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=4851C44E.7000102@woh.rr.com \
--to=dlphillips@woh.rr.com \
--cc=linux-msdos@vger.kernel.org \
--cc=tonyb@sysdev.org \
--cc=x.zupftom@web.de \
/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