From: GitHub issues - opened <github@alsa-project.org>
To: alsa-devel@alsa-project.org
Subject: Ucm2 device sorting / ordering
Date: Wed, 15 May 2024 17:33:02 +0200 (CEST) [thread overview]
Message-ID: <20240515153302.6DD18F80224@alsa1.perex.cz> (raw)
In-Reply-To: <1715787157441715479-webhooks-bot@alsa-project.org>
alsa-project/alsa-lib issue #397 was opened from beatboxa:
The sort order that devices are probed and ultimately listed in my OS sound settings is reversed--though consisten--from the order that they appear (top to bottom) in the UCM configuration files. And they also do not appear consistent with configured device priority.
In other words, if the UCM configuration file hypothetically lists the following, from top to bottom:
1. Device 1 - priority 300
2. Device 2 - priority 100
3. Device 3 - priority 200
These devices will be probed and listed in the OS in the following order:
1. Device 3
2. Device 2
3. Device 1
I am currently creating a UCM config file for a device with 32 discreet output channels and 30 discreet input channels (and both stereo and mono device versions of many of these), so the sort order is crucial for user experience in a list this long.
Related:
- https://github.com/alsa-project/alsa-ucm-conf/pull/416#issuecomment-2111101525
- https://github.com/alsa-project/alsa-lib/issues/245#issuecomment-1168910073
Issue URL : https://github.com/alsa-project/alsa-lib/issues/397
Repository URL: https://github.com/alsa-project/alsa-lib
next parent reply other threads:[~2024-05-15 15:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1715787157441715479-webhooks-bot@alsa-project.org>
2024-05-15 15:33 ` GitHub issues - opened [this message]
[not found] <1715787347486447811-webhooks-bot@alsa-project.org>
2024-05-15 15:35 ` Ucm2 device sorting / ordering GitHub issues - edited
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=20240515153302.6DD18F80224@alsa1.perex.cz \
--to=github@alsa-project.org \
--cc=alsa-devel@alsa-project.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).