All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lee Revell <rlrevell@joe-job.com>
To: Chris Rankin <rankincj@yahoo.com>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: Audigy2 Microphone capture: alsa-driver-1.0.9rc1 works, alsa-driver-1.0.9rc2 doesn't
Date: Wed, 30 Mar 2005 16:36:19 -0500	[thread overview]
Message-ID: <1112218579.18237.17.camel@mindpipe> (raw)
In-Reply-To: <20050330213009.41195.qmail@web52901.mail.yahoo.com>

On Wed, 2005-03-30 at 22:30 +0100, Chris Rankin wrote:
> I've just compared the results with the alsa-driver-1.0.9rc1 and alsa-driver-1.0.9rc2 tarballs
> with my Audigy2 sound card.
> 
> The summary: I can record via the microphone with rc1, but can't with rc2.
> 
> The command I'm using is:
> 
> $ arecord -d10 -f cd -t wav > test.wav
> 

This is a known problem.  We have isolated it to something committed to
CVS between 3-22 and 3-24 IIRC (check list archive).  I posted the "cvs
diff" output.  We need someone to go though that patch and figure out
which change is responsible.

Lee



-------------------------------------------------------
This SF.net email is sponsored by Demarc:
A global provider of Threat Management Solutions.
Download our HomeAdmin security software for free today!
http://www.demarc.com/Info/Sentarus/hamr30

  parent reply	other threads:[~2005-03-30 21:36 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-30 21:30 Audigy2 Microphone capture: alsa-driver-1.0.9rc1 works, alsa-driver-1.0.9rc2 doesn't Chris Rankin
2005-03-30 21:26 ` James Courtier-Dutton
2005-03-30 21:36 ` Lee Revell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-03-30 22:00 Chris Rankin
2005-03-30 23:01 Chris Rankin
2005-03-31 20:44 ` Peter Zubaj
2005-03-31 21:28   ` Lee Revell
2005-03-31 22:20     ` Lee Revell
2005-03-31 22:52 Chris Rankin
2005-03-31 23:29 ` Lee Revell

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=1112218579.18237.17.camel@mindpipe \
    --to=rlrevell@joe-job.com \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=rankincj@yahoo.com \
    /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.