All of lore.kernel.org
 help / color / mirror / Atom feed
From: GitHub issues - edited <github@alsa-project.org>
To: alsa-devel@alsa-project.org
Subject: Channel count in GoXLR SplitPCM configuration
Date: Wed, 12 Mar 2025 18:33:32 +0100 (CET)	[thread overview]
Message-ID: <182c1e9bf1b47300-webhooks-bot@alsa-project.org> (raw)
In-Reply-To: <182c1e9bf19ab100-webhooks-bot@alsa-project.org>

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

       reply	other threads:[~2025-03-12 17:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <182c1e9bf19ab100-webhooks-bot@alsa-project.org>
2025-03-12 17:33 ` GitHub issues - edited [this message]
     [not found] <182c1e993e29ac00-webhooks-bot@alsa-project.org>
2025-03-12 17:33 ` Channel count in GoXLR SplitPCM configuration 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=182c1e9bf1b47300-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.