From: Takashi Iwai <tiwai@suse.de>
To: Miha Tomsic <miha.tomsic@guest.arnes.si>
Cc: alsa devel <alsa-devel@lists.sourceforge.net>
Subject: Re: Problem with alsamixer, amixer
Date: Thu, 10 Oct 2002 17:18:51 +0200 [thread overview]
Message-ID: <s5hzntmcof8.wl@alsa2.suse.de> (raw)
In-Reply-To: <1034262491.1337.230.camel@josef>
At 10 Oct 2002 17:08:11 +0200,
Miha Tomsic wrote:
>
> Hello!
>
> This is an old problem I reported a year or so ago.
>
> I have SBPCI 128 with ak4531 codec. The problem is that I can't set
> capture to certain channels (the channels that are using capture route
> CD, Line, PCM 1) if they are muted. Or if capture is already set, muting
> those channels will switch capture off.
>
> This is happening if I am using alsamixer or amixer with sset. If I am
> using amixer with cset I can set anything I want.
>
> I guess the problem lies in the ak4531 and the way simple controls are
> handled. I don't know enough about alsa internals so poking around the
> sources of alsamixer, amixer and ak4531 didn't help me understand what
> should I do to make it working.
can you change each one switch or volume value by the follwoing way?
- call "alsactl -f foo store"
- modify the file "foo"
- call "alsactl -f foo restore"
if it works, then the problem is alsamixer or alsa-lib.
the latest alsamixer can handle playback and capture separately, so
this problem should have been fixed.
Takashi
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
next prev parent reply other threads:[~2002-10-10 15:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-10 15:08 Problem with alsamixer, amixer Miha Tomsic
2002-10-10 15:18 ` Takashi Iwai [this message]
2002-10-10 15:34 ` Miha Tomsic
2002-10-11 9:44 ` Takashi Iwai
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=s5hzntmcof8.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@lists.sourceforge.net \
--cc=miha.tomsic@guest.arnes.si \
/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