From: GitHub issues - edited <github@alsa-project.org>
To: alsa-devel@alsa-project.org
Subject: SSL2 Debian13, Kernel 6.18.21, lates alsa-ucm sound issues
Date: Sun, 3 May 2026 09:53:00 +0200 (CEST) [thread overview]
Message-ID: <18abfeee59809400-webhooks-bot@alsa-project.org> (raw)
In-Reply-To: <18abfeee595a7100-webhooks-bot@alsa-project.org>
alsa-project/alsa-ucm-conf issue #749 was edited from brandtan:
Hi Team,
everytime I start discord my other peep can hear themselves.
The issue is: Since firmware version 1.2 of SSL2 Audio interface, they addded loopback channels ( RL & RR )
THose channels are automaticall being routed to respectice inputs obviously and in addition to that, these channels are being routed to any kind of audio software: Discord, Mumble, OBS etc...
What can be done against it.
Latest kernel, latest alsa-ucm, latestes everything. I tried nothing since I do not know what to do.
Issue URL : https://github.com/alsa-project/alsa-ucm-conf/issues/749
Repository URL: https://github.com/alsa-project/alsa-ucm-conf
next parent reply other threads:[~2026-05-03 7:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <18abfeee595a7100-webhooks-bot@alsa-project.org>
2026-05-03 7:53 ` GitHub issues - edited [this message]
[not found] <18a80958db4d6000-webhooks-bot@alsa-project.org>
2026-04-20 10:18 ` SSL2 Debian13, Kernel 6.18.21, lates alsa-ucm sound issues GitHub issues - opened
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=18abfeee59809400-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