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 E15B3C28B28 for ; Wed, 12 Mar 2025 17:34:02 +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 7981160278; Wed, 12 Mar 2025 18:33:50 +0100 (CET) DKIM-Filter: OpenDKIM Filter v2.11.0 alsa0.perex.cz 7981160278 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=alsa-project.org; s=default; t=1741800840; bh=+VAdVO+pnjkPuAI58PTf9mJmRp+M+UlP8G7odW7yLA4=; 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=Z4ySUEKYKT9AE1PJEVw0kCbEXo9OqDw2KTU1d8tqplPSOyeRI51D9OiS6CiKDXNFQ ZekeKusNCsOj5VmH1cETzJFPrWZ1A7h8eIiomcPnLszoeEXIyun4GRrHqPzcOJTF+4 3nNJyuNKpOKWVgupD0SGzMZkkmMXMCcUnKv+8pdg= Received: by alsa1.perex.cz (Postfix, from userid 50401) id 8345BF805C1; Wed, 12 Mar 2025 18:33:25 +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 60B08F805BA; Wed, 12 Mar 2025 18:33:25 +0100 (CET) Received: by alsa1.perex.cz (Postfix, from userid 50401) id 85EEDF80301; Wed, 12 Mar 2025 18:33:21 +0100 (CET) Received: from webhooks-bot.alsa-project.org (vmi2259423.contaboserver.net [45.14.194.44]) by alsa1.perex.cz (Postfix) with ESMTP id D436EF80095 for ; Wed, 12 Mar 2025 18:33:19 +0100 (CET) DKIM-Filter: OpenDKIM Filter v2.11.0 alsa1.perex.cz D436EF80095 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: <182c1e993f0f8c00-webhooks-bot@alsa-project.org> In-Reply-To: <182c1e993e29ac00-webhooks-bot@alsa-project.org> References: <182c1e993e29ac00-webhooks-bot@alsa-project.org> Subject: Channel count in GoXLR SplitPCM configuration Date: Wed, 12 Mar 2025 18:33:21 +0100 (CET) Message-ID-Hash: NZFY5ATLZFIMWK53MSU3KCENNKWE23OE X-Message-ID-Hash: NZFY5ATLZFIMWK53MSU3KCENNKWE23OE 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 #518 was opened from pv: Similar issue as #515, and related to #444: We have a report https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/4602#note_2819696 that GoXLR UCM profile with SplitPCM=1 specifies always 23 channels, but the device can't be opened with exactly 23 channels. According to https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/4602#note_2819696 the device may have 21, 23, or 25 depending on firmware/etc details. In Pipewire, I think we add a workaround that just uses the available channel count even if it is different from what UCM profile specifies, but logs warnings if the counts are different so these issues in the profiles can be caught. Issue URL : https://github.com/alsa-project/alsa-ucm-conf/issues/518 Repository URL: https://github.com/alsa-project/alsa-ucm-conf