alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: GitHub issues - opened <github@alsa-project.org>
To: alsa-devel@alsa-project.org
Subject: Scarlett Solo gen 3, Direct Scarlett profile is missing, "Input 1 Mic" option is missing too.
Date: Sun, 23 Nov 2025 17:36:22 +0100 (CET)	[thread overview]
Message-ID: <187ab00d33f34b00-webhooks-bot@alsa-project.org> (raw)
In-Reply-To: <187ab00d32dfbc00-webhooks-bot@alsa-project.org>

alsa-project/alsa-ucm-conf issue #648 was opened from scaledteam:

Hello! I just discovered that Alsa UCM might be cause of my issues, but i don't know how to confirm and diagnose that. So i'm asking for help.

When i was using Arch Linux, it allowed me to select mono microphone input. It's important feature, because many communication programs just average microphone and instrument input, resulting in loosing half of the volume, which cannot be compensated with 200% gain in pavucontrol.

Now i switched to Linux Mint and i lost that feature. But ucm files in /usr/share/alsa seems identical to archlinux. Just to be sure i tried Manjaro liveusb and i found all of this options, no config required.

There is alsa info just in case: [alsa-info.txt](https://github.com/user-attachments/files/23697024/alsa-info.txt)

Can someone help me with this?

Linux mint:
<img width="700" height="421" alt="Image" src="https://github.com/user-attachments/assets/c555d380-bb2b-4fcf-b835-d0c92ce59897" />

Manjaro:
![Image](https://github.com/user-attachments/assets/e2ecae99-0fb0-4203-82f2-b9c4c97a733f)

![Image](https://github.com/user-attachments/assets/5c277b7a-f19c-4e0b-a786-b51eb51ee5f9)

Issue URL     : https://github.com/alsa-project/alsa-ucm-conf/issues/648
Repository URL: https://github.com/alsa-project/alsa-ucm-conf

           reply	other threads:[~2025-11-23 16:37 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <187ab00d32dfbc00-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=187ab00d33f34b00-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;
as well as URLs for NNTP newsgroup(s).