From: Nathaniel Gray <n8gray@caltech.edu>
To: alsa-devel@lists.sourceforge.net
Subject: recording issues
Date: Wed, 1 Oct 2003 14:34:29 -0700 [thread overview]
Message-ID: <200310011434.29210.n8gray@caltech.edu> (raw)
My sound card uses different devices for capture (device 0) and playback
(device 1). I have two issues with capture right now:
1. If I do something like:
arecord -f dat -D hw:0,1 -d 5 foo.wav
it seems to record for much longer than 5 seconds. In fact, "time
arecord..." tells me that it goes for 10 seconds. If I then try to
play back the result with aplay:
aplay foo.wav
the playback is too fast. The same thing happens with the -f cd format.
I thought I'd try forcing mono recording but:
[n8gray@golux alsa]$ arecord -D hw:0,1 -c 1 -r 48000 -f S16_LE -d 5
foo.wav
Recording WAVE 'foo.wav' : Signed 16 bit Little Endian, Rate 48000 Hz,
Mono
arecord: set_params:833: Channels count non available
2. Is there a way to make the OSS emulation use hw:0,0 as the playback
device and hw:0,1 as the capture device?
Here's some info:
[n8gray@golux alsa]$ cat /proc/asound/version
Advanced Linux Sound Architecture Driver Version 0.9.7a.
Compiled on Oct 1 2003 for kernel 2.4.21-0.16mm-mdkcustom.
[n8gray@golux alsa]$ cat /proc/asound/cards
0 [I82801CAICH3 ]: ICH - Intel 82801CA-ICH3
Intel 82801CA-ICH3 at 0xd800, irq 11
[n8gray@golux alsa]$ cat /proc/asound/devices
0: [0- 0]: ctl
25: [0- 1]: digital audio capture
16: [0- 0]: digital audio playback
24: [0- 0]: digital audio capture
1: : sequencer
33: : timer
Can anybody help?
Thanks,
-Nathan
--
>>>-- Nathaniel Gray -- Caltech Computer Science ------>
>>>-- Mojave Project -- http://mojave.cs.caltech.edu -->
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
next reply other threads:[~2003-10-01 21:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-01 21:34 Nathaniel Gray [this message]
2003-10-02 7:36 ` recording issues Giuliano Pochini
2003-10-02 17:37 ` Nathan Gray
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=200310011434.29210.n8gray@caltech.edu \
--to=n8gray@caltech.edu \
--cc=alsa-devel@lists.sourceforge.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.