From: GitHub issues - opened <github@alsa-project.org>
To: alsa-devel@alsa-project.org
Subject: SSL2.conf Defines Incorrect Number of Capture Channels
Date: Tue, 6 Jan 2026 00:21:30 +0100 (CET) [thread overview]
Message-ID: <1887f91c6681ec00-webhooks-bot@alsa-project.org> (raw)
In-Reply-To: <1887f91c65b40100-webhooks-bot@alsa-project.org>
alsa-project/alsa-ucm-conf issue #676 was opened from TheBakedPotato:
The file at `ucm2/USB-Audio/SolidStateLabs/SSL2.conf` has the line
```
Define.DirectCaptureChannels 4
```
However, I believe that should actually be
```
Define.DirectCaptureChannels 2
```
since the SSL2 (**not** the SSL2+) only has 2 physical inputs.
As well, now, with that change, a third audio "profile" appears ago for the SSL2 output device of `Direct SSL 2`.
<img width="416" height="78" alt="Image" src="https://github.com/user-attachments/assets/14998079-d81d-444f-80b1-b198ad049428" />
The `[ALSA UCM error]` still appears, but now the correct "profile" is available. As well, now my music player, Amberol, is able to persist the volume change between songs. Before if I changed the volume and proceed to the next song the audio in the Amberol application would get set to max.
The output in `journalctl` is still present
```
Jan 05 18:11:39 endeavour-zone wireplumber[1533]: spa.alsa: Error in ALSA UCM profile for _ucm0001.hw:S2,0 (HiFi: Mic2: source): CaptureChannels=4 > avail 2
Jan 05 18:11:39 endeavour-zone wireplumber[1533]: spa.alsa: Errors in ALSA UCM profile for card SSL 2
Jan 05 18:11:40 endeavour-zone wireplumber[1533]: spa.bluez5: BlueZ system service is not available
```
if the HiFi profile is selected. I'm assuming because the file `SSL2-HiFi.conf` needs to be updated for the correct number of hardware capture channels.
Issue URL : https://github.com/alsa-project/alsa-ucm-conf/issues/676
Repository URL: https://github.com/alsa-project/alsa-ucm-conf
parent reply other threads:[~2026-01-05 23:22 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1887f91c65b40100-webhooks-bot@alsa-project.org>]
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=1887f91c6681ec00-webhooks-bot@alsa-project.org \
--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