All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lennart Poettering <mznyfn@0pointer.de>
To: alsa-devel@alsa-project.org
Subject: Re: Master vs. Front/Rear/LFE/... elements
Date: Sun, 10 May 2009 00:11:39 +0200	[thread overview]
Message-ID: <20090509221139.GC23851@tango.0pointer.de> (raw)
In-Reply-To: <s5hiqkd2gra.wl%tiwai@suse.de>

On Thu, 07.05.09 15:18, Takashi Iwai (tiwai@suse.de) wrote:

> > > Fixing it isn't too difficult with vmaster stuff in the driver side,
> > > but this breaks the compatibility, and hard to find the real test
> > > machines nowadays.  In short, "don't touch a working system unless it
> > > gets broken" phase.
> > 
> > Breaks compatibility with what exactly? OSS?
> 
> Yes, and old ALSA-native apps without PA.

Hmm. why exactly should that happen? I mean, the ALSA mixer API knew
definitions like snd_mixer_selem_channel_id since about the beginning
of time. Just making use of it shouldn't cause breakage in programs.

And even when if it does, this would be the 'softest' kind of breakage
one can think of. Also, most of the apps in question are Free Software
and could hence be fixed easily.

> > May I assume that they always are dependant?
> 
> If both exist, then they should be dependent, and Master should be
> really Master.

Hmm, ok. So you say "Master" in this case is more "outside" and
"Front" is more to the "inside", right? I.e. from the applications PoV
Front is first, Master follows as last step, right?

> > Hmm, could you be more explicit which apps you think would break? I
> > mean, the ALSA mixer API always allowed multichannel audio, however no
> > driver actually made use of that. If a client is using the ALSA mixer
> > API properly it should not break. And if it doesn't use it properly
> > it's not ALSA's fault...
> 
> kmix surely won't work.  GNOME mixer?  I don't think it would.

The new GNOME mixer links against PA, so it would support it
indirectly. ;-)

> Many media players (new and old) support a mixer adjustment more or
> less, and certainly many of they won't work with multi channels.

But to which effect? The worst thing that could happen is that they
wouldn't show the Surround channels properly. But usually they
wouldn't show that anyway..

Lennart

-- 
Lennart Poettering                        Red Hat, Inc.
lennart [at] poettering [dot] net
http://0pointer.net/lennart/           GnuPG 0x1A015CC4

  reply	other threads:[~2009-05-09 22:11 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-06 17:58 Master vs. Front/Rear/LFE/... elements Lennart Poettering
2009-05-07  8:49 ` Takashi Iwai
2009-05-07 10:09   ` Mark Brown
2009-05-07 10:30     ` Takashi Iwai
2009-05-07 10:53       ` Mark Brown
2009-05-07 12:56       ` Lennart Poettering
2009-05-07 13:10         ` Mark Brown
2009-05-07 13:12         ` Pavel Hofman
2009-05-08  6:36     ` Eliot Blennerhassett
2009-05-07 12:46   ` Lennart Poettering
2009-05-07 13:18     ` Takashi Iwai
2009-05-09 22:11       ` Lennart Poettering [this message]
2009-05-11  9:26         ` Takashi Iwai
2009-05-12  7:47   ` James Courtier-Dutton
2009-05-12  8:02     ` Jaroslav Kysela
2009-05-12  9:21     ` Mark Brown
2009-05-12 13:15     ` Lennart Poettering

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=20090509221139.GC23851@tango.0pointer.de \
    --to=mznyfn@0pointer.de \
    --cc=alsa-devel@alsa-project.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.