From: Zipdox <zipdox@zipdox.net>
Cc: linux-sound@vger.kernel.org, perex@perex.cz,
linux-kernel@vger.kernel.org, tiwai@suse.com
Subject: Re: [PATCH] USB Audio Class 2 Mixer unit support for GET_CUR, SET_CUR and RANGE
Date: Mon, 5 Oct 2026 11:55:40 +0200 [thread overview]
Message-ID: <f3661b8b-6d4e-4244-8a7c-a5811b1fbea1@zipdox.net> (raw)
In-Reply-To: <2dfe5d78-9c87-42a2-a306-ab5c58b17756@zipdox.net>
On 9/28/26 12:59 PM, Takashi Iwai wrote:
>> From a UX perspective, I would prefer if the lowest setting on the
>> control equals mute. This makes the most sense for a "mixer". Like I
>> mentioned before, extending the range down by 1 and making that
>> translate to -32768 seems like a convenient solution. When setting,
>> simply check if it's a mixer unit (UAC1 or UAC2, both do this) and if
>> the set value is equal to the minimum, and set the value to
>> -32768. For getting, check if it's a mixer unit and check if the
>> retrieved value is -32768, and then set the value to the minimum. The
>> only caveat is that the resolution might not align anymore with the
>> range. What do you think of this idea?
>
> I thought of it, too. OTOH, it'll be a bit tricky, because the range
> isn't usually covering -32767 but only a part. So -32768 won't be
> reached continuously.
>
> I'm inclined to have a simple mute switch in addition.
>
>
> thanks,
>
> Takashi
>
A mute switch could work if you add the necessary state management code.
For now I think that's the most straightforward solution, seeing I don't
know how ALSA would handle a misaligned range and resolution in the case
of my proposal. Could you write a patch?
next parent reply other threads:[~2026-10-05 10:01 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2dfe5d78-9c87-42a2-a306-ab5c58b17756@zipdox.net>
2026-10-05 9:55 ` Zipdox [this message]
2026-09-15 8:54 Zipdox
2026-09-15 11:08 ` Takashi Iwai
2026-09-15 12:54 ` Zipdox
2026-09-15 14:19 ` Takashi Iwai
2026-09-16 7:43 ` Zipdox
2026-09-16 15:40 ` Takashi Iwai
2026-09-16 16:58 ` Takashi Iwai
2026-09-16 18:22 ` Takashi Iwai
2026-09-17 14:23 ` Zipdox
2026-09-17 14:49 ` Takashi Iwai
2026-09-17 14:54 ` Zipdox
2026-09-17 16:15 ` Takashi Iwai
2026-09-17 16:33 ` Zipdox
2026-09-17 16:40 ` Takashi Iwai
2026-09-18 8:35 ` Zipdox
2026-09-28 10:59 ` Takashi Iwai
2026-10-05 13:54 ` Zipdox
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=f3661b8b-6d4e-4244-8a7c-a5811b1fbea1@zipdox.net \
--to=zipdox@zipdox.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=perex@perex.cz \
--cc=tiwai@suse.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®