From: Joachim Feise <jfeise+alsa@ics.uci.edu>
To: alsa-user@lists.sourceforge.net, alsa-devel@lists.sourceforge.net
Subject: Re: cs46xx (Turtle Beach Santa Cruz), kernel 2.6 recording silence
Date: Sat, 14 Feb 2004 12:59:35 -0800 [thread overview]
Message-ID: <402E8C37.5020308@ics.uci.edu> (raw)
In-Reply-To: <Pine.LNX.4.50.0402141243210.18246-100000@string.physics.ubc.ca>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Bill Unruh said on 2/14/2004 12:44:
>>>a) Line in is muted
>>>b) Line in has its amplitude all the way down.
>>
>>Nope. Checked all that.
>>Using alsamixer, I unmuted line in, and set the amplitude to 100%.
>>
>
> On many cards the input amplitude is IGain, not linein. linein just
> determines how much of the input goes to the output.
Well, alsamixer does not show any IGain column for this card.
I have tried unmuting and upping the amplitude on everything.
Audio into Line-in or Mic in goes fine to the output.
Recording still doesn't work.
I am not sure if I'm missing an option somewhere, or if this
is a deeper problem.
- -Joe
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (MingW32)
iD8DBQFALow3Kc8oZ1MoTeoRAhTuAKDze8keWd9BuTU3Y1cD8p4q+YMPwgCdFsBb
QazKzm53J2OxVltT6PiSruc=
=FrCI
-----END PGP SIGNATURE-----
-------------------------------------------------------
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
prev parent reply other threads:[~2004-02-14 20:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-14 18:08 cs46xx (Turtle Beach Santa Cruz), kernel 2.6 recording silence Joachim Feise
2004-02-14 19:08 ` Bill Unruh
2004-02-14 19:50 ` [Alsa-user] " Joachim Feise
2004-02-14 20:44 ` Bill Unruh
2004-02-14 20:59 ` Joachim Feise [this message]
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=402E8C37.5020308@ics.uci.edu \
--to=jfeise+alsa@ics.uci.edu \
--cc=alsa-devel@lists.sourceforge.net \
--cc=alsa-user@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox