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 0E7AFC28B2E for ; Wed, 12 Mar 2025 17:34:19 +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 C741A6027D; Wed, 12 Mar 2025 18:34:06 +0100 (CET) DKIM-Filter: OpenDKIM Filter v2.11.0 alsa0.perex.cz C741A6027D DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=alsa-project.org; s=default; t=1741800856; bh=cMg+el/0vopaRWOviCpzOyrhRUwTW6p0ONgRCEHrPbU=; 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=T8esLwLblD4I33YDJrHpfjup5inAcBn7sDBnpJC5JM68W5E6CYEWMzzfBtb1lmO6K jpKaLa8t8t9Nx5IbbnMQDPetgzZ1VJpOCwpXPVHOTeF/+b3phfn/QAG4ObB/OgMalc IDL6F565NsSaXuWRNR0eEUnVbeN8Y7XfVk6PmVVA= Received: by alsa1.perex.cz (Postfix, from userid 50401) id 14F53F805E1; Wed, 12 Mar 2025 18:33:37 +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 06BB5F805E2; Wed, 12 Mar 2025 18:33:37 +0100 (CET) Received: by alsa1.perex.cz (Postfix, from userid 50401) id AC114F805C3; Wed, 12 Mar 2025 18:33:32 +0100 (CET) Received: from webhooks-bot.alsa-project.org (vmi2259423.contaboserver.net [45.14.194.44]) by alsa1.perex.cz (Postfix) with ESMTP id 11536F805BA for ; Wed, 12 Mar 2025 18:33:31 +0100 (CET) DKIM-Filter: OpenDKIM Filter v2.11.0 alsa1.perex.cz 11536F805BA MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit From: GitHub issues - edited To: alsa-devel@alsa-project.org Message-Id: <182c1e9bf1b47300-webhooks-bot@alsa-project.org> In-Reply-To: <182c1e9bf19ab100-webhooks-bot@alsa-project.org> References: <182c1e9bf19ab100-webhooks-bot@alsa-project.org> Subject: Channel count in GoXLR SplitPCM configuration Date: Wed, 12 Mar 2025 18:33:32 +0100 (CET) Message-ID-Hash: P4NSRTLNFLBJYNXGU6YKSHCDV45O2MYA X-Message-ID-Hash: P4NSRTLNFLBJYNXGU6YKSHCDV45O2MYA 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 edited from pv: Similar issue as #515, and related to #444: We have a report https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/4602 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