From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from alsa0.perex.cz (alsa0.perex.cz [77.48.224.243]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id AF792D637A1 for ; Tue, 16 Dec 2025 19:51:09 +0000 (UTC) Received: from alsa1.perex.cz (alsa1.perex.cz [45.14.194.44]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by alsa0.perex.cz (Postfix) with ESMTPS id E690A60209; Tue, 16 Dec 2025 20:50:56 +0100 (CET) DKIM-Filter: OpenDKIM Filter v2.11.0 alsa0.perex.cz E690A60209 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=alsa-project.org; s=default; t=1765914666; bh=v72b1037DGoyY0kKmpIAU3+7I48+iz/TsvTF+IPxn9k=; h=From:To:In-Reply-To:References:Subject:Date:List-Id:List-Archive: List-Help:List-Owner:List-Post:List-Subscribe:List-Unsubscribe: From; b=Gsq0Zn5w2zSTbYn2k8l3Gy+ynM6GvN8KOlh5G9KSmpJDA/ePJvY6GUWB+kBx/Carj giw9Om9zfZ86szRAtK0P8Ew978XNqOMD2vmVqUvCYE49RcFuTA6hQKrTTW72eUNhY0 p8BSVqEDZEOXH8Qd0fUATggv5jRHhUZhbstC2tWM= Received: by alsa1.perex.cz (Postfix, from userid 50401) id 7D2EDF805D9; Tue, 16 Dec 2025 20:50:29 +0100 (CET) Received: from mailman-core.alsa-project.org (mailman-core.alsa-project.org [10.254.200.10]) by alsa1.perex.cz (Postfix) with ESMTP id 2AFDDF805D7; Tue, 16 Dec 2025 20:50:29 +0100 (CET) Received: by alsa1.perex.cz (Postfix, from userid 50401) id 3B91AF80217; Tue, 16 Dec 2025 20:50:14 +0100 (CET) Received: from webhooks-bot.alsa-project.org (vmi2259423.contaboserver.net [45.14.194.44]) by alsa1.perex.cz (Postfix) with ESMTP id 86861F80087 for ; Tue, 16 Dec 2025 20:50:11 +0100 (CET) DKIM-Filter: OpenDKIM Filter v2.11.0 alsa1.perex.cz 86861F80087 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit From: GitHub issues - opened To: alsa-devel@alsa-project.org Message-Id: <1881c9fb78a2d000-webhooks-bot@alsa-project.org> In-Reply-To: <1881c9fb781f0500-webhooks-bot@alsa-project.org> References: <1881c9fb781f0500-webhooks-bot@alsa-project.org> Subject: Behringer UMC404HD Line A/B volume too low when used in "Pro Audio" mode Date: Tue, 16 Dec 2025 20:50:14 +0100 (CET) Message-ID-Hash: DG3KRXSZHUCNJM3N6EZ7I4DGJJSKLDP5 X-Message-ID-Hash: DG3KRXSZHUCNJM3N6EZ7I4DGJJSKLDP5 X-MailFrom: github@alsa-project.org X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-alsa-devel.alsa-project.org-0; header-match-alsa-devel.alsa-project.org-1; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header X-Mailman-Version: 3.3.9 Precedence: list List-Id: "Alsa-devel mailing list for ALSA developers - http://www.alsa-project.org" Archived-At: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: alsa-project/alsa-ucm-conf issue #662 was opened from mrbumpy409: The Behringer UMC404HD shows five volume faders in alsamixer: * **Line A** and **UMC404HD 192k Output Front**: These faders are linked (changing one changes the other) and control the level of **L & R MAIN OUT** and **PLAYBACK OUTPUT A 1/L & 2/R** on the back of the unit. * **Line B** and **UMC404HD 192k Output Back**: These faders are linked and control the level of **PLAYBACK OUTPUT B 3/L & 4/R**. * **UMC404HD 192k Output 1**: The primary volume control for the unit. How these sliders are used by Pipewire depends on the mode selected for the Behringer: * **Default**: Two output devices are presented to the user: - **UMC404HD 192k Line A**: Controls the "Line A" volume in alsamixer. - **UMC404HD 192k Line B**: Controls the "Line B" volume in alsamixer. - The "UMC404HD 192k Output 1" slider in alsamixer appears to be unused. * **Direct UMC404HD 192k**: One output device is presented to the user: - **Direct UMC404HD 192k**: Doesn't seem to be manipulating any of the hardware output levels in alsamixer. - The "Line A" and "Line B" channels are not available via Pipewire in this mode. * **Pro Audio**: One output device is presented to the user: - **UMC404HD 192k Pro**: Controls the "UMC404HD 192k Output 1" output level in alsamixer. - The "Line A" and "Line B" channels are not available via Pipewire in this mode. I would imagine most people are using a Behringer UMC404HD for recording purposes, and therefore would likely be using it in "Pro Audio" mode (or at least they should be if they care about latency). Since a recent update (Fedora 43 KDE), the levels of the "Line A" and "Line B" channels (and their linked pairs) are being set by default to **41**, which results in audio that is far too quiet when using the line outputs (headphone output is unaffected). Furthermore, these low levels throw off the balance between the computer's output and the UMC404HD's live input monitoring. "Line A" and "Line B" channels should both be at **100** by default to match the Windows driver (and previous ALSA version?) and provide correct balance with the live monitoring feature. Currently, I have to run alsamixer on every boot to adjust "Line A" and "Line B" to **100**. Am I right to report this to ALSA, or is this something Pipewire should be handling? Pipewire doesn't appear to touch the "Line A" or "Line B" levels at all when in "Pro Audio" mode, so I'd assume this is ALSA's doing, but I don't really know. Issue URL : https://github.com/alsa-project/alsa-ucm-conf/issues/662 Repository URL: https://github.com/alsa-project/alsa-ucm-conf