Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - driver 0001631]: Audiophile USB will not capture.
Date: Thu, 8 Dec 2005 17:38:01 +0100	[thread overview]
Message-ID: <2cc37f71bff4e78596f7a295fbe04cf6@bugtrack.alsa-project.org> (raw)


The following issue has been SUBMITTED.
======================================================================
<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-08-2005 17:38 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
======================================================================

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 
======================================================================




-------------------------------------------------------
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

             reply	other threads:[~2005-12-08 16:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-08 16:38 bugtrack [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-12-23 17:40 [ALSA - driver 0001631]: Audiophile USB will not capture bugtrack
2006-03-14 16:17 bugtrack
2006-03-14 16:17 bugtrack
2006-03-14 16:18 bugtrack
2006-03-14 16:18 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=2cc37f71bff4e78596f7a295fbe04cf6@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