From: "Arun Raghavan" <arun@arunraghavan.net>
To: "Mark Hills" <mark@xwax.org>, "Asahi Lina" <lina@asahilina.net>
Cc: alsa-devel@alsa-project.org, linux-sound@vger.kernel.org,
"Takashi Iwai" <tiwai@suse.com>,
"Jaroslav Kysela" <perex@perex.cz>
Subject: Re: Handling complex matrix mixers in ALSA
Date: Thu, 04 Jul 2024 12:06:22 -0400 [thread overview]
Message-ID: <d971252e-5342-4971-8f94-76b38182915b@app.fastmail.com> (raw)
In-Reply-To: <5e0a07da-c5d2-1209-0f26-d164f25a31f1@xwax.org>
On Thu, 4 Jul 2024, at 4:55 AM, Mark Hills wrote:
[...]
>> I think for something like this you pretty much have to rely on
>> device-specific tools to make the UX manageable
>
> For a full UX, perhaps. But the concept of a matrix mixer itself is
> general enough.
>
> Perhaps there could be a UI tool which is self contained with one purpose,
> to control a 'standard' matrix mixer. It could be invoked alongside
> alsamixer or other mixer tool, and multiple times if there are multiple
> matrix mixers on a piece of hardware.
If this were generalised, it might be possible for the functionality to be exposed via the audio server as well, which allows for things like sandboxing, etc. to work nicely too.
-- Arun
prev parent reply other threads:[~2024-07-04 16:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-30 16:04 Handling complex matrix mixers in ALSA Asahi Lina
2024-07-01 0:06 ` Takashi Sakamoto
2024-07-01 2:45 ` Geoffrey D. Bennett
2024-07-01 14:17 ` Takashi Iwai
2024-07-02 0:46 ` Takashi Sakamoto
2024-07-12 9:48 ` Asahi Lina
2024-07-13 1:35 ` Takashi Sakamoto
2024-07-04 8:55 ` Mark Hills
2024-07-04 16:06 ` Arun Raghavan [this message]
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=d971252e-5342-4971-8f94-76b38182915b@app.fastmail.com \
--to=arun@arunraghavan.net \
--cc=alsa-devel@alsa-project.org \
--cc=lina@asahilina.net \
--cc=linux-sound@vger.kernel.org \
--cc=mark@xwax.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