From: "Clemens Ladisch" <cladisch@fastmail.net>
To: Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.de>
Cc: ALSA development <alsa-devel@alsa-project.org>,
Lennart Poettering <mznyfn@0pointer.de>
Subject: Re: Channel mapping
Date: Thu, 22 Nov 2007 10:17:54 +0100 [thread overview]
Message-ID: <1195723074.30838.1222700857@webmail.messagingengine.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0711211922540.8325@tm8103.perex-int.cz>
Jaroslav Kysela wrote:
> On Wed, 21 Nov 2007, Takashi Iwai wrote:
> > Indeed, the mixer <-> PCM mapping can be useful. For such
> > information, the fixed size struct isn't suitable as multiple mixer
> > elements correspond to a single PCM channel.
>
> I think that we have already such interface, but maybe not well described
> and used. I would propose to use SNDRV_CTL_ELEM_IFACE_PCM for PCM mixer
> related controls and device & subdevice from control_id structure. In this
> way, we can easy group and assign all control elements to PCM substream.
At the moment, this is only used for sound cards that have multiple
substreams.
> We may have only one problem - to identify which elements are mixer
> related and which are not. Maybe, we can use one bit from access flags to
> determine, if it's a mixer control element if interface != MIXER.
I'm not sure if this information (mixer or not) is that useful - an
application is likely to access a mixer control with a 'known' meaning,
like volume or mute, and in this case it has to search the controls by
their name anyway.
Regards,
Clemens
next prev parent reply other threads:[~2007-11-22 9:17 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-20 0:51 [lennart@poettering.net: Status of ALSA "simple" mixer interface] Lennart Poettering
2007-11-21 11:09 ` Takashi Iwai
2007-11-21 11:11 ` Takashi Iwai
2007-11-21 15:23 ` Clemens Ladisch
2007-11-25 19:56 ` The sense or non-sense of the device listing API (was: Status of ALSA "simple" mixer interface]) Lennart Poettering
2007-11-25 20:38 ` Jaroslav Kysela
2007-11-21 11:14 ` Mono device definition Takashi Iwai
2007-11-21 11:20 ` Analog-SPDIF dup Takashi Iwai
2007-11-21 11:22 ` Softvol controls Takashi Iwai
2007-11-29 23:28 ` Lennart Poettering
2007-11-29 23:46 ` John Utz
2007-11-30 0:08 ` Lennart Poettering
2007-11-30 0:34 ` John Utz
2007-11-30 8:59 ` Takashi Iwai
2007-12-04 15:42 ` Jaroslav Kysela
2007-12-13 10:39 ` Takashi Iwai
2007-12-22 22:54 ` Lennart Poettering
2007-12-23 10:21 ` Jaroslav Kysela
2007-12-22 22:48 ` Lennart Poettering
2007-11-21 11:40 ` Disable conversions Takashi Iwai
2007-11-21 14:29 ` Takashi Iwai
2007-11-21 15:16 ` Jaroslav Kysela
2007-11-21 14:51 ` Takashi Iwai
2007-11-25 20:41 ` Lennart Poettering
2007-11-26 15:55 ` Jaroslav Kysela
2007-12-22 22:37 ` Lennart Poettering
2007-11-21 11:42 ` Channel mapping Takashi Iwai
2007-11-21 15:17 ` Clemens Ladisch
2007-11-21 14:57 ` Takashi Iwai
2007-11-21 15:27 ` Jaroslav Kysela
2007-11-21 15:04 ` Takashi Iwai
2007-11-27 16:54 ` Takashi Iwai
2007-11-21 15:52 ` Clemens Ladisch
2007-11-21 15:36 ` Takashi Iwai
2007-11-21 18:37 ` Jaroslav Kysela
2007-11-22 9:17 ` Clemens Ladisch [this message]
2007-11-22 8:55 ` Clemens Ladisch
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=1195723074.30838.1222700857@webmail.messagingengine.com \
--to=cladisch@fastmail.net \
--cc=alsa-devel@alsa-project.org \
--cc=mznyfn@0pointer.de \
--cc=perex@perex.cz \
--cc=tiwai@suse.de \
/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