From: Takashi Iwai <tiwai@suse.de>
To: "J.A. Magallon" <jamagallon@able.es>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.12-rc3-mm3: ALSA broken ?
Date: Wed, 18 May 2005 15:39:41 +0200 [thread overview]
Message-ID: <s5hoeb8sleq.wl@alsa2.suse.de> (raw)
In-Reply-To: <1116369585l.8840l.0l@werewolf.able.es>
At Tue, 17 May 2005 22:39:45 +0000,
J.A. Magallon wrote:
>
>
> On 05.17, Takashi Iwai wrote:
> ...
> > >
> > > Example: go into 4ch mode. Check this control. Then switch to 6ch mode.
> > > The Center jack has no sound (it should, shouldn't ?). Check it and voilà.
> > > It looks that the logic in the channel selection needs to set this flag also...
> >
> > Yep, you're right. Try the patch below.
> >
> >
>
> Thanks, this patch worked. When in 6ch mode, the boolen flag we talk about
> still controls if the line jack is input or output. In 4ch mode, it is always
> input. If i chech it, switching to 6ch does not toggle it. They are
> independent controls.
>
> Anyways. I can't get rid of the flag. It is initialized to on by default.
> Isn't strange to have two ways of controlling this ?
>
> Now we have:
>
> Surround jack mode: [Shared/Independent]
> Channel mode [2/4/6]
> Center/LFE jack as mic [on/off]
> Spread Front... [on/off]
Apply *both* patches I sent. They don't conflict.
> Would not be nice something like:
>
> Surround jacks mode: [Shared/Independent]
> Line Jack: [in/surround-out/extra-front-out]
> Mic Jack: [in/center-out/extra-front-out]
>
> It looks like internally you can control all ouputs independently.
> Just an idea that looks more logical/intuitive to me...
I don't think so. You'll want to have spreaded front to indepent
surround jacks, too.
> Ah, and could the input level controllers for line and mic be forced
> to mute when used as inputs ?
This is doable but tricky since you have to remember the last values.
Takashi
next prev parent reply other threads:[~2005-05-18 13:40 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-05 5:10 2.6.12-rc3-mm3 Andrew Morton
2005-05-05 7:08 ` 2.6.12-rc3-mm3 Richard A Nelson
2005-05-05 11:55 ` 2.6.12-rc3-mm3 Francois Romieu
2005-05-05 18:00 ` 2.6.12-rc3-mm3 Andrew Morton
2005-05-05 12:39 ` 2.6.12-rc3-mm3 Rafael J. Wysocki
2005-05-05 12:58 ` 2.6.12-rc3-mm3 Rafael J. Wysocki
2005-05-05 22:47 ` 2.6.12-rc3-mm3: Kernel BUG at "mm/slab.c":1219 Rafael J. Wysocki
2005-05-05 14:57 ` 2.6.12-rc3-mm3 Valdis.Kletnieks
2005-05-05 15:22 ` 2.6.12-rc3-mm3 Adrian Bunk
2005-05-05 15:49 ` 2.6.12-rc3-mm3 Valdis.Kletnieks
2005-05-05 16:44 ` 2.6.12-rc3-mm3 Adrian Bunk
2005-05-05 14:59 ` 2.6.12-rc3-mm3 Borislav Petkov
2005-05-08 0:07 ` 2.6.12-rc3-mm3: ALSA broken ? J.A. Magallon
2005-05-08 23:24 ` J.A. Magallon
2005-05-11 14:23 ` Takashi Iwai
2005-05-12 22:27 ` J.A. Magallon
2005-05-13 9:57 ` Takashi Iwai
2005-05-17 12:02 ` J.A. Magallon
2005-05-17 12:20 ` Takashi Iwai
2005-05-17 22:39 ` J.A. Magallon
2005-05-18 13:39 ` Takashi Iwai [this message]
2005-05-26 23:51 ` J.A. Magallon
2005-05-27 9:41 ` Takashi Iwai
2005-05-27 21:18 ` J.A. Magallon
2005-05-30 13:37 ` Takashi Iwai
2005-05-30 14:30 ` J.A. Magallon
2005-05-30 15:21 ` Takashi Iwai
2005-05-30 17:58 ` Takashi Iwai
2005-05-27 14:52 ` Lee Revell
2005-05-28 0:11 ` J.A. Magallon
2005-05-30 13:26 ` Takashi Iwai
[not found] ` <20050526001828.0b3959f6.akpm@osdl.org>
2005-05-27 6:54 ` J.A. Magallon
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=s5hoeb8sleq.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=jamagallon@able.es \
--cc=linux-kernel@vger.kernel.org \
/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