From: Clemens Ladisch <clemens@ladisch.de>
To: Felix Homann <linuxaudio@showlabor.de>
Cc: "Takashi Iwai" <tiwai@suse.de>,
"Aurélien Leblond" <blablack@gmail.com>,
alsa-devel@alsa-project.org, "Grant Diffey" <gdiffey@gmail.com>,
"Daniel Mack" <zonque@gmail.com>
Subject: Re: Fast Track Ultra mixer - opinions anyone?
Date: Mon, 16 Apr 2012 15:10:25 +0200 [thread overview]
Message-ID: <4F8C1A41.2080807@ladisch.de> (raw)
In-Reply-To: <CAFz=ag4SmifT2jVE-NqcWXg_+go_WYD06c9ZM0HtC1KHKg7k6Q@mail.gmail.com>
Felix Homann wrote:
> IMO, the effect section on the FTUs really sucks. I can't believe that
> anybody can really use it in a reasonable way. So should we really add
> another 40 controls to the mixer which can cause a lot of pain when
> misadjusted (i.e. anything else but 0)?
>
> For those reasons I would prefer not to put effect support in the
> kernel. What do you think?
If you want to be able to use these effects at all, there must be _some_
way to access the controls.
Generic mixer programs like alsamixer are not really suitable for
complex devices; you'd need to write a custom mixer.
If you want to prevent the controls from showing up in alsamixer, set
their .iface to SNDRV_CTL_ELEM_IFACE_CARD instead of _MIXER. (But if
these controls don't show up in alsamixer, you wouldn't be able to reset
them if they are misadjusted ...)
> Currently alsamixer does not report any dB changes when you change a
> control value.
Set the TLV. For standard controls, the code reads the values from
the USB descriptors, but for control you create by hand, you have to
create these, too.
Regards,
Clemens
next prev parent reply other threads:[~2012-04-16 13:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-16 10:38 Fast Track Ultra mixer - opinions anyone? Felix Homann
2012-04-16 11:06 ` Aurélien Leblond
2012-04-16 11:11 ` Grant Diffey
2012-04-16 12:45 ` Felix Homann
2012-04-16 13:10 ` Clemens Ladisch [this message]
2012-04-18 11:47 ` Felix Homann
2012-04-18 14:32 ` Felix Homann
2012-04-18 15:02 ` Felix Homann
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=4F8C1A41.2080807@ladisch.de \
--to=clemens@ladisch.de \
--cc=alsa-devel@alsa-project.org \
--cc=blablack@gmail.com \
--cc=gdiffey@gmail.com \
--cc=linuxaudio@showlabor.de \
--cc=tiwai@suse.de \
--cc=zonque@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 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.