[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090316170015.GA9776@rhlx01.hs-esslingen.de>
Date: Mon, 16 Mar 2009 18:00:15 +0100
From: Andreas Mohr <andi@...as.de>
To: Takashi Iwai <tiwai@...e.de>
Cc: Andreas Mohr <andi@...as.de>,
Maxim Levitsky <maximlevitsky@...il.com>,
linux-kernel@...r.kernel.org, alsa-devel@...a-project.org,
Kernel Testers List <kernel-testers@...r.kernel.org>
Subject: Re: [alsa-devel] Bugs on aspire one A150
Hi,
On Mon, Mar 16, 2009 at 05:19:38PM +0100, Takashi Iwai wrote:
> At Mon, 16 Mar 2009 17:06:35 +0100,
> 私 wrote:
> >
> > > > What are "sliders"?
> > >
> > > Umm, volume level controls.
> >
> > Yes but there are many of such :)
> >
> > More exactly, from the driver perspective, there are no volume
> > controls but only there are control elements with integer values.
> > Do you mean "Capture Volume" control or which one?
Hmm, ok, this needs to be more precise:
In gamix (codec "HDA Intel : Realtek ALC268"), the Capture Volume control.
> > And, is the behavior consistent regardless of the value high, i.e.
> > the key is only whether the values for both channels are identical?
>
> BTW, what if you record with the following definition?
> Put the below to ~/.asoundrc
>
> pcm.imix {
> type plug
> slave.pcm "hw"
> ttable.0.0 0.5
> ttable.0.1 -0.5
> }
>
> and record like
>
> % aplay -Dimix -c1 foo.wav
Does NOT exhibit the "equal sliders == no sound" bug (apart from this sliders
are acting normally, i.e. slider low == no sound), despite being a
"plug" type definition (this is what you wanted to discern, right? ;).
Thanks!
Andreas
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists