From: Will <walsac2@liam2.demon.co.uk>
To: clemens@ladisch.de
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: [PATCH] add aplaymidi & arecordmidi utils
Date: Wed, 25 Feb 2004 00:10:52 GMT [thread overview]
Message-ID: <200402250010.AAA06565@liam2.demon.co.uk> (raw)
In-Reply-To: <Pine.HPX.4.33n.0402241856320.5168-100000@studcom.urz.uni-halle.de>
Clemens Ladisch <clemens@ladisch.de> wrote:
>
>If you get correct output when you run "amidi -p virtual -d" and
>aconnect your keyboard to that port, then it may be a bug in
>arecordmidi. I'll test when I'm at home.
>
This is what I get:
$ amidi -p virtual -d &
$ pmidi -l
Port Client name Port name
64:0 Rawmidi 0 - Sound Blaster 16 M Sound Blaster 16 MPU-401
65:0 Emu8000 WaveTable Emu8000 Port 0
65:1 Emu8000 WaveTable Emu8000 Port 1
65:2 Emu8000 WaveTable Emu8000 Port 2
65:3 Emu8000 WaveTable Emu8000 Port 3
66:0 OPL3 FM synth OPL3 FM Port
72:0 Virtual Raw MIDI 1-0 VirMIDI 1-0
73:0 Virtual Raw MIDI 1-1 VirMIDI 1-1
74:0 Virtual Raw MIDI 1-2 VirMIDI 1-2
75:0 Virtual Raw MIDI 1-3 VirMIDI 1-3
128:0 Client-128 Virtual RawMIDI
The MIDI keyboard is on port 64:0:
$ aconnect 64:0 128:0
playing various notes on the MIDI keyboard gives correct MIDI output in ASCII:
90 29 4A
90 29 00
90 2D 4C
2D 00
90 2B 5A
90 2B 00
90 28 59
90 28 00
90 24 26
24 00
24 51
90 24 00
90 24 63
24 00
90 24 75
90 24 00
90 24 7B
90 24 00
24 65
90 24 00
24 50
90 24 00
90 24 3D
90 24 00
90 24 47
90 24 00
90 24 44
90 24 00
90 24 3A
90 24 00
90 26 6B
90 26 00
28 68
90 28 00
29 5F
2B 68
90 29 00
29 65
90 2B 00
28 5E
29 00
90 26 69
28 00
24 70
etc
William
-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
next prev parent reply other threads:[~2004-02-25 0:10 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-23 9:18 [PATCH] add aplaymidi & arecordmidi utils Clemens Ladisch
2004-02-23 9:41 ` Jaroslav Kysela
2004-02-24 17:12 ` Will
2004-02-24 17:36 ` Clemens Ladisch
2004-02-24 17:51 ` Will
2004-02-24 17:58 ` Clemens Ladisch
2004-02-25 0:10 ` Will [this message]
2004-02-25 8:23 ` Clemens Ladisch
2004-02-25 13:22 ` Will
2004-02-25 13:58 ` James Courtier-Dutton
2004-02-25 14:11 ` Will
2004-02-24 17:26 ` Will
2004-02-24 17:43 ` Clemens Ladisch
2004-02-25 13:02 ` Will
2004-02-25 14:04 ` Takashi Iwai
2004-02-25 14:19 ` Will
2004-02-25 14:26 ` Takashi Iwai
-- strict thread matches above, loose matches on Subject: below --
2004-03-02 15:20 CVS ALSA failed upgrade in Linux 2.6.3 William
2004-03-02 15:36 ` Takashi Iwai
2004-03-02 15:52 ` William
2004-03-02 16:39 ` Takashi Iwai
2004-03-02 17:28 ` William
2004-03-02 17:33 ` Takashi Iwai
2004-03-02 17:59 ` William
2004-03-02 18:04 ` Takashi Iwai
2004-03-03 14:50 ` William
2004-03-02 21:08 ` James Courtier-Dutton
2004-03-02 23:35 ` William
2004-03-03 1:07 ` James Courtier-Dutton
2004-03-03 15:54 ` William
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=200402250010.AAA06565@liam2.demon.co.uk \
--to=walsac2@liam2.demon.co.uk \
--cc=alsa-devel@lists.sourceforge.net \
--cc=clemens@ladisch.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