From: Lennart Poettering <mznyfn@0pointer.de>
To: John Utz <john.utz@dmx.com>
Cc: Takashi Iwai <tiwai@suse.de>, alsa-devel@alsa-project.org
Subject: Re: Softvol controls
Date: Fri, 30 Nov 2007 01:08:11 +0100 [thread overview]
Message-ID: <20071130000810.GA20465@tango.0pointer.de> (raw)
In-Reply-To: <20071129154657.2a7a2be1@jutz-gnto64>
On Thu, 29.11.07 15:46, John Utz (john.utz@dmx.com) wrote:
John,
> > > Check snd_ctl_elem_info_is_user(). All softvol controls are
> > > implemented as user elements.
> >
> > Hmm, how am I supposed to get the snd_ctl_elem_info_t from a
> > snd_mixer_elem_t or snd_mixer_selem_id_t?
> >
> > I figure there is no useful documentation or even example how this is
> > supposed to work? Hmm, is there any real documentation available which
> > describes the relation of ctl, hctl, mixer and smixer at all? For the
> > uninitated the whols structure looks overly complex and redundant.
>
> Here's my take on it....HTH
>
> dont hesitate to ask
Hu? Neither "snd_ctl_elem_info_t" nor "snd_ctl_elem_info_is_user()"
is even mentioned in your source code excerpt?
I know how to change volumes and stuff via the ALSA mixer API. What I
am looking for is a way to detect whether a mixer element is
implemented in softwaer only and thus doesn't influence your ouput
when you open a PCM device with "hw:0", "front:0", "surround51:0" and
suchlike.
Lennart
--
Lennart Poettering Red Hat, Inc.
lennart [at] poettering [dot] net ICQ# 11060553
http://0pointer.net/lennart/ GnuPG 0x1A015CC4
next prev parent reply other threads:[~2007-11-30 0:08 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 [this message]
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
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=20071130000810.GA20465@tango.0pointer.de \
--to=mznyfn@0pointer.de \
--cc=alsa-devel@alsa-project.org \
--cc=john.utz@dmx.com \
--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