All of lore.kernel.org
 help / color / mirror / Atom feed
From: GitHub pull_request - opened <github@alsa-project.org>
To: alsa-devel@alsa-project.org
Subject: USB-Audio: add Steinberg UR44C profile
Date: Sun, 23 Aug 2026 01:29:15 +0200 (CEST)	[thread overview]
Message-ID: <18ce44706ab81900-webhooks-bot@alsa-project.org> (raw)
In-Reply-To: <alsa-project/alsa-ucm-conf/pr/835@alsa-project.org>

alsa-project/alsa-ucm-conf pull request #835 was opened from polyv0x:

## Summary

- stop matching the UR44C to the incompatible four-playback/six-capture
  UR44 profile
- add a dedicated six-playback/eight-capture UR44C UCM profile
- expose split HiFi PCMs for DAW Mix 1, DAW Mix 2, FX Bus, Direct Out
  1-6, and Streaming L/R

The channel layout comes from the device's USB descriptors:

| Direction | Channels |
| --- | --- |
| Playback | DAW Mix1 L/R, DAW Mix2 L/R, FX Bus L/R |
| Capture | DIRECT OUT 1-6, Streaming L/R |

This retains ACP's Pro Audio profile while also providing working HiFi and
Direct UCM profiles instead of only falling back to ACP.

## Testing

- `ucm-validator2`: `make configs` passes for the complete configuration tree
- `alsaucm -c hw:0 dump text` loads the profile against the connected UR44C
- WirePlumber 0.5.15 / PipeWire 1.6.8 exposes:
  - HiFi: 3 sinks and 10 sources
  - Direct: 1 six-channel sink and 1 eight-channel source
- activated HiFi and verified every split node was instantiated, then switched
  back to Pro Audio
- no UCM or channel-count errors in the WirePlumber log

[alsa-info for the tested UR44C](https://gist.github.com/polyv0x/8b95168b5705d141a9910d56a979be78)

Fixes #799

Request URL   : https://github.com/alsa-project/alsa-ucm-conf/pull/835
Patch URL     : https://github.com/alsa-project/alsa-ucm-conf/pull/835.patch
Repository URL: https://github.com/alsa-project/alsa-ucm-conf

           reply	other threads:[~2026-08-22 23:30 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <alsa-project/alsa-ucm-conf/pr/835@alsa-project.org>]

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