From: Takashi Iwai <tiwai@suse.de>
To: Andreas Mohr <andi@lisas.de>
Cc: Maxim Levitsky <maximlevitsky@gmail.com>,
linux-kernel@vger.kernel.org, alsa-devel@alsa-project.org,
Kernel Testers List <kernel-testers@vger.kernel.org>
Subject: Re: [alsa-devel] Bugs on aspire one A150
Date: Mon, 16 Mar 2009 21:28:39 +0100 [thread overview]
Message-ID: <s5htz5tyzyg.wl%tiwai@suse.de> (raw)
In-Reply-To: <20090316180638.GB25647@rhlx01.hs-esslingen.de>
At Mon, 16 Mar 2009 19:06:38 +0100,
Andreas Mohr wrote:
>
> On Mon, Mar 16, 2009 at 06:34:35PM +0100, Takashi Iwai wrote:
> > At Mon, 16 Mar 2009 18:30:00 +0100,
> > Andreas Mohr wrote:
> > >
> > > Hi,
> > >
> > > On Mon, Mar 16, 2009 at 06:15:39PM +0100, Takashi Iwai wrote:
> > > > At Mon, 16 Mar 2009 18:00:15 +0100,
> > > > Andreas Mohr wrote:
> > > > > > > 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? ;).
> > > >
> > > > Interesting. This implies that one channel is inverted indeed.
> > >
> > > Oh, you mean "inverted" as in "_hardware_ channel which provides opposite
> > > sample values as compared to the other channel"?
> >
> > Right. My guess is that the hardware provides left (or right) channel
> > is multiplied by -1 (yep "inverted" is no correct word choice).
> >
> > > > As default the alsa-lib plugin downmixes a stereo stream to a mono
> > > > stream simply by left/2 + right/2. The above changes the routing
> > > > policy as left/2 - right/2.
> > >
> > > That exactly matches my current stream of thought (while reading
> > > "one channel is inverted" above).
> > >
> > > > So we need to pass some information to change this kind of thing...
> > >
> > > That's something specific to ALC268 codec setup, right?
> > > ("ALC268 digital mic == left plus right channel, but inverted setup"?)
> >
> > No. It's specific to the digital-mic side.
>
> I just tried connecting a headset and switching to E-Mic.
> What I can say is:
> - opposite levels does NOT happen there (E-Mic is "analog micro"-based, right?)
> - leaving E-Mic unplugged will actually record from i-Mic (due to properly
> working EAPD mechanism, right?)
The record from mic-jack is via analog path. The phase-inversion
appears only for digital-mic, AFAIK.
> BTW, the output (of arecord -Dplughw:0 -c2 -traw -fdat foo.wav) _does_ have
> inverted channels:
>
> 00000130 2A 02 D2 FD 65 02 A5 FD 10 00 E7 FF 99 FF 72 00 *...e.........r.
> 00000140 53 FE A7 01 ED FF 12 00 4F FF A6 00 86 00 81 FF S.......O.......
> ... and so on in the entire file ...
>
>
> One question still: is this a hardware defect (i.e. could this possibly
> be swapped cables of the microphone connector in this model or so?
> Not plausible but...), or is this an existing property
> of the HDA's dig-mic base? You indicated it's the latter I think...
My guess is that it's a hardware implementation.
Maybe for the noise suppression via mic array.
The question is whether the left / right channels recorded from
digital mic are really raw data, or they are for modified data
(for differential, etc)... It's hard to guess without the actual
data.
Takashi
next prev parent reply other threads:[~2009-03-16 20:30 UTC|newest]
Thread overview: 96+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-08 3:26 Maxim Levitsky
2008-11-08 11:57 ` Alan Jenkins
2008-11-09 0:52 ` Maxim Levitsky
2008-11-09 8:54 ` [alsa-devel] " Takashi Iwai
2008-11-09 13:31 ` Andreas Mohr
2008-11-09 15:13 ` Andreas Mohr
2008-11-09 18:58 ` Takashi Iwai
2008-11-09 20:09 ` Andreas Mohr
2008-11-12 11:08 ` Takashi Iwai
2008-11-12 17:07 ` Maxim Levitsky
2008-11-12 18:05 ` Andreas Mohr
2008-11-14 18:05 ` Maxim Levitsky
2008-11-22 19:00 ` Maxim Levitsky
2008-11-22 19:43 ` Andreas Mohr
2008-11-24 14:35 ` Takashi Iwai
2009-03-15 9:21 ` Andreas Mohr
2009-03-16 12:03 ` Andreas Mohr
2009-03-16 12:09 ` Takashi Iwai
2009-03-16 13:30 ` Andreas Mohr
2009-03-16 14:18 ` Takashi Iwai
2009-03-16 14:31 ` Andreas Mohr
2009-03-16 14:42 ` Takashi Iwai
2009-03-16 14:50 ` Andreas Mohr
2009-03-16 15:34 ` Takashi Iwai
2009-03-16 16:02 ` Andreas Mohr
2009-03-16 16:06 ` Takashi Iwai
2009-03-16 16:19 ` Takashi Iwai
2009-03-16 17:00 ` Andreas Mohr
2009-03-16 17:15 ` Takashi Iwai
2009-03-16 17:30 ` Andreas Mohr
2009-03-16 17:34 ` Takashi Iwai
2009-03-16 18:06 ` Andreas Mohr
2009-03-16 20:28 ` Takashi Iwai [this message]
2009-03-16 21:22 ` Andreas Mohr
2009-03-17 0:52 ` Maxim Levitsky
2009-03-17 7:57 ` Takashi Iwai
2009-03-17 11:30 ` Maxim Levitsky
2009-03-17 12:52 ` Takashi Iwai
2009-03-17 7:57 ` Takashi Iwai
2009-03-17 10:05 ` Andreas Mohr
2009-03-17 10:38 ` Andreas Mohr
2009-03-17 10:47 ` Andreas Mohr
2009-03-17 11:25 ` Takashi Iwai
2009-03-17 16:18 ` Andreas Mohr
2009-03-17 20:32 ` Takashi Iwai
2009-03-18 9:05 ` Andreas Mohr
2009-03-18 9:19 ` Takashi Iwai
2009-03-20 18:56 ` Andreas Mohr
2009-03-20 20:33 ` Takashi Iwai
2009-03-22 12:55 ` Andreas Mohr
2009-03-23 6:51 ` Takashi Iwai
2008-11-12 17:20 ` Maxim Levitsky
2008-11-12 18:53 ` HDA-emu 0.0.1 (Re: [alsa-devel] Bugs on aspire one A150) Takashi Iwai
2008-11-09 10:43 ` Bugs on aspire one A150 Alan Jenkins
2008-11-12 17:48 ` Maxim Levitsky
2008-11-14 19:06 ` Maxim Levitsky
2008-11-14 19:59 ` Alan Jenkins
2008-11-15 12:52 ` Maxim Levitsky
2008-11-15 12:55 ` Matthew Garrett
2008-11-10 16:51 ` Bob Copeland
2008-11-10 21:33 ` Maxim Levitsky
2008-11-10 22:12 ` [ath5k-devel] " Nick Kossifidis
2008-11-12 17:51 ` Maxim Levitsky
2008-11-13 14:58 ` Bob Copeland
2008-11-14 3:47 ` Bob Copeland
2008-11-14 18:57 ` Maxim Levitsky
2008-11-17 17:28 ` Bob Copeland
2008-11-17 18:55 ` Maxim Levitsky
2008-12-01 15:33 ` Maxim Levitsky
2008-12-13 13:28 ` Maxim Levitsky
2008-12-13 14:08 ` Nick Kossifidis
2008-12-13 14:36 ` Maxim Levitsky
2008-12-13 14:38 ` Maxim Levitsky
2008-12-13 14:24 ` Bob Copeland
2008-12-13 14:31 ` Maxim Levitsky
2008-12-30 4:26 ` Bob Copeland
2008-12-30 12:43 ` Maxim Levitsky
2008-12-31 9:18 ` Andreas Mohr
2008-12-31 13:59 ` Andreas Mohr
2008-12-31 14:06 ` Bob Copeland
2008-12-31 14:03 ` Bob Copeland
2008-12-31 16:51 ` Maxim Levitsky
2009-01-01 13:41 ` Andreas Mohr
2009-01-01 14:15 ` Maxim Levitsky
2009-01-01 20:27 ` Andreas Mohr
2009-01-01 15:09 ` Bob Copeland
2008-12-13 13:15 ` Maxim Levitsky
2008-12-13 13:35 ` Rafael J. Wysocki
2008-12-13 14:21 ` Maxim Levitsky
2008-12-13 17:42 ` Rafael J. Wysocki
2008-12-13 18:04 ` Maxim Levitsky
2008-12-14 22:29 ` J.A. Magallón
2008-12-14 22:57 ` J.A. Magallón
2008-12-14 23:18 ` Maxim Levitsky
2008-12-14 23:24 ` J.A. Magallón
2008-12-14 23:35 ` J.A. Magallón
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=s5htz5tyzyg.wl%tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=andi@lisas.de \
--cc=kernel-testers@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maximlevitsky@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®