All of lore.kernel.org
 help / color / mirror / Atom feed
From: GitHub issues - opened <github@alsa-project.org>
To: alsa-devel@alsa-project.org
Subject: Steinberg UR44C (0499:1730) incorrectly matched to UR44 UCM profile (PlaybackChannels mismatch)
Date: Mon, 29 Jun 2026 00:00:31 +0200 (CEST)	[thread overview]
Message-ID: <18bd5dadf0facb00-webhooks-bot@alsa-project.org> (raw)
In-Reply-To: <18bd5dadf0d1b400-webhooks-bot@alsa-project.org>

alsa-project/alsa-ucm-conf issue #799 was opened from abentley:

Note: Google AGY wrote this, but I have manually verified all claims.

The Steinberg UR44C (USB ID  0499:1730 ) is currently matched to the  Steinberg/UR44  UCM profile in  ucm2/USB-Audio/USB-Audio.conf  via the following rule:
                                                                                                                                                                     
   If.steinberg-ur44 {
       Condition {
           Type RegexMatch
           String "${CardComponents}"                                                                                                                                
           Regex "USB0499:17((00)|(30)|(04))"
       }
       True.Define.ProfileName "Steinberg/UR44"
   }

However, the UR44 UCM profile defines  PlaybackChannels=4  (since the original UR44 only has 4 output channels).
The UR44C hardware actually exposes 6 playback channels (as confirmed by  /proc/asound/cardX/stream0 ):
   Playback:
     Interface 1
       Altset 1
       Format: S32_LE
       Channels: 6

This mismatch causes WirePlumber/PipeWire to fail to load the UCM profile with the following validation error:

   spa.alsa: Error in ALSA UCM profile for _ucm0003.hw:UR44C,0 (HiFi: Line2: sink): PlaybackChannels=4 < avail 6
   spa.alsa: Errors in ALSA UCM profile for card Steinberg UR44C

Suggested Fix:
Exclude the UR44C product ID ( 1730 ) from the  steinberg-ur44  regex condition so it falls back to standard ALSA Card Profiles (ACP) instead of attempting to load  the incompatible UR44 UCM profile.

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

       reply	other threads:[~2026-06-28 22:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <18bd5dadf0d1b400-webhooks-bot@alsa-project.org>
2026-06-28 22:00 ` GitHub issues - opened [this message]
     [not found] <18bd5dc4b29a8500-webhooks-bot@alsa-project.org>
2026-06-28 22:02 ` Steinberg UR44C (0499:1730) incorrectly matched to UR44 UCM profile (PlaybackChannels mismatch) GitHub issues - edited

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=18bd5dadf0facb00-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.