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: Tue, 24 Feb 2004 17:12:44 GMT [thread overview]
Message-ID: <200402241712.RAA29352@liam2.demon.co.uk> (raw)
In-Reply-To: <Pine.HPX.4.33n.0402231010240.20713-100000@studcom.urz.uni-halle.de>
Clemens Ladisch <clemens@ladisch.de> wrote:
>
>add aplaymidi & arecordmidi utilities
>
I'm getting empty MIDI files containing only the MIDI header.
$ arecordmidi -l
Port Client name Port name
64:0 Rawmidi 0 - Sound Blaster 16 MPU Sound Blaster 16 MPU-401
$ cat /proc/asound/card0/midi0
Sound Blaster 16 MPU-401
Output 0
Tx bytes : 9856
Input 0
Rx bytes : 205806
$ arecordmidi -p 64:0 music.mid
<Ctrl-C>
$ cat /proc/asound/card0/midi0
Sound Blaster 16 MPU-401
Output 0
Tx bytes : 9856
Input 0
Rx bytes : 205946
$ ls -l music.mid
-rw-r--r-- 1 uab1 gab1 34 Feb 24 17:07 music.mid
$ file music.mid
music.mid: Standard MIDI data
$ od -c music.mid
000000 77 84 104 100 0 0 0 6 0 0 0 1 1 128 77 84
M T h d \0 \0 \0 006 \0 \0 \0 001 001 200 M T
000010 114 107 0 0 0 12 0 255 81 3 7 161 32 150 96 255
r k \0 \0 \0 \f \0 377 Q 003 \a 241 226 ` 377
000020 47 0
/ \0
Any ideas? I can record MIDI files ok using the old OSS sound drivers
and OSS sequencer software.
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-24 17:12 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 [this message]
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
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=200402241712.RAA29352@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