From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - driver 0001631]: Audiophile USB will not capture.
Date: Fri, 23 Dec 2005 18:40:22 +0100 [thread overview]
Message-ID: <eb50e8f0c970261e2c9cf297a36fca91@bugtrack.alsa-project.org> (raw)
A NOTE has been added to this issue.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1631>
======================================================================
Reported By: smithbone
Assigned To: Clemens Ladisch
======================================================================
Project: ALSA - driver
Issue ID: 1631
Category: USB - usb-audio
Reproducibility: always
Severity: major
Priority: normal
Status: assigned
Distribution: 1.0.10
Kernel Version: 2.6.15-rc5-git1
======================================================================
Date Submitted: 12-08-2005 17:38 CET
Last Modified: 12-23-2005 18:40 CET
======================================================================
Summary: Audiophile USB will not capture.
Description:
If I try to capure audio from my Audiophile USB I get the following.
$ arecord -vv -D hw:1,1 -f S24_3BE -t raw -c 2 -r48000 test.raw
Its setup is:
stream : CAPTURE
access : RW_INTERLEAVED
format : S24_3BE
subformat : STD
channels : 2
rate : 48000
exact rate : 48000 (48000/1)
msbits : 24
buffer_size : 24000
period_size : 6000
period_time : 125000
tick_time : 4000
tstamp_mode : NONE
period_step : 1
sleep_min : 0
avail_min : 6000
xfer_align : 6000
start_threshold : 1
stop_threshold : 24000
silence_threshold: 0
silence_size : 0
boundary : 1572864000
arecord: pcm_read:1303: read error: Input/output error
======================================================================
----------------------------------------------------------------------
sander - 12-23-05 18:40
----------------------------------------------------------------------
I mailed this analysis to the alsa-devel list two months ago. It seems to
have found a nice home here :)
SUMMARY:
- only 48001-96000hz capturing works
- only capturing through plughw:x,1 works
- format is 24/32 bits regardless of plug conversion (? at least, as
reported by audacity)
- only the signal on the jack inputs is captured
- only 2-channel capture
- only the SYNC/48001-96000/S24_3BE altset on device #1 can be captured,
only through plughw.
signal (from the jacks, not the cinch connectors)
-------------------------------------------------
s1) arecord -D plughw:0,1 -t wav -c 2 -r 96000 -f S16_LE -d 2 -vv test.wav
- output :
Plug PCM: Linear conversion PCM (S24_3BE)
Its setup is:
stream : CAPTURE
access : RW_INTERLEAVED
format : S16_LE
- audacity reports 24b/96khz
- amplitude suspects 24 bit sound despite S16_LE setting
- altset reportedly used :
Format: S24_3BE
Channels: 2
Endpoint: 5 IN (SYNC)
Rates: 48001 - 96000 (continuous)
- see (n1) and (e3)
s2) arecord -D plughw:0,1 -t wav -c 2 -r 96000 -f S32_LE -d 2 -vv
test.wav
- output :
Plug PCM: Linear conversion PCM (S24_3BE)
Its setup is:
stream : CAPTURE
access : RW_INTERLEAVED
format : S32_LE
- audacity reports 32b/96khz
- altset used same as (s1)
no signal
---------
n1) arecord -D plughw:0,1 -t raw -c 2 -r 96000 -f S24_3BE -d 2 -vv
test.raw
- output :
Plug PCM: Hardware PCM card 0 'Audiophile USB (tm)' device 1 subdevice 0
Its setup is:
stream : CAPTURE
access : RW_INTERLEAVED
format : S24_3BE
n2) arecord -D plughw:0,1 -t raw -c 2 -r 96000 -f S24_LE -d 2 -vv
test.raw
n3) arecord -D plughw:0,1 -t raw -c 2 -r 96000 -f S24_3LE -d 2 -vv
test.raw
n4) arecord -D plughw:0,1 -t raw -c 2 -r 96000 -f U24_3LE -d 2 -vv
test.raw
n5) arecord -D plughw:0,1 -t raw -c 2 -r 96000 -f U24_3BE -d 2 -vv
test.raw
errors/'lock'
-------------
e1) arecord -D plughw:0,1 -t raw -c 2 -r 48000 -f S16_LE -d 2 -vv
test.raw
- output :
Plug PCM: Linear conversion PCM (S16_BE)
Its setup is:
stream : CAPTURE
access : RW_INTERLEAVED
format : S16_LE
e2) arecord -D plughw:0,1 -t raw -c 2 -r 48000 -f S16_BE -d 2 -vv
test.raw
- output :
Plug PCM: Hardware PCM card 0 'Audiophile USB (tm)' device 1 subdevice 0
Its setup is:
stream : CAPTURE
access : RW_INTERLEAVED
format : S16_BE
e3) arecord -D plughw:0,0 -t wav -c 2 -r 96000 -f S16_LE -d 2 -vv
test.wav
e3) arecord -D plughw:0,1 -t wav -c 1 -r 96000 -f S16_LE -d 2 -vv test.wav
Issue History
Date Modified Username Field Change
======================================================================
12-08-05 17:38 smithbone New Issue
12-08-05 17:38 smithbone Distribution => 1.0.10
12-08-05 17:38 smithbone Kernel Version => 2.6.15-rc5-git1
12-23-05 18:40 sander Note Added: 0007135
======================================================================
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
next reply other threads:[~2005-12-23 17:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-23 17:40 bugtrack [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-03-14 16:18 [ALSA - driver 0001631]: Audiophile USB will not capture bugtrack
2006-03-14 16:18 bugtrack
2006-03-14 16:17 bugtrack
2006-03-14 16:17 bugtrack
2005-12-08 16:38 bugtrack
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=eb50e8f0c970261e2c9cf297a36fca91@bugtrack.alsa-project.org \
--to=bugtrack@alsa-project.org \
--cc=alsa-devel@alsa-project.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