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: Audiocard device is split into multiple PipeWire inputs and reports "[ALSA UCM error]"
Date: Mon, 14 Sep 2026 18:45:24 +0200 (CEST)	[thread overview]
Message-ID: <18d53dc0129eb200-webhooks-bot@alsa-project.org> (raw)
In-Reply-To: <18d53dc01290ce00-webhooks-bot@alsa-project.org>

alsa-project/alsa-ucm-conf issue #856 was opened from artom76:

Hello,
I am having a problem with a Steinberg UR44C USB audio interface on Fedora 44.
My goal is to use the UR44C with FL Studio running through Wine/Bottles and record from multiple physical inputs at the same time. I am using PipeASIO as the ASIO driver. The UR44C itself supports 8-channel capture. ALSA can access the device as an 8-channel device, but PipeWire does not expose it as one 8-channel input device. Instead, PipeWire creates multiple separate input nodes, for example:
alsa_input.usb-Yamaha_Corporation_Steinberg_UR44C-00.HiFi__Line3__source
Steinberg UR44C [ALSA UCM error] Front 1

There are also additional nodes such as "Front 2 & 3" and "Front 3 & 4".
All of these UR44C input nodes contain "[ALSA UCM error]" in their description.
This causes a problem for PipeASIO and FL Studio. Instead of receiving one ASIO device with multiple input channels, FL Studio sees the inputs as separate devices/nodes. I need the UR44C to be available to the ASIO layer as one multi-channel device so that I can record several inputs simultaneously.

PipeASIO itself is installed and working correctly. FL Studio can see PipeASIO, and I have already tried increasing the number of PipeASIO inputs and changing its input/output configuration, but this does not solve the problem because the UR44C inputs are already split into separate PipeWire nodes before they reach PipeASIO.
What I would like to know is whether the current UCM configuration for the Steinberg UR44C is incorrect or incomplete, and whether there is a recommended UCM configuration that exposes the UR44C capture device as a single 8-channel PCM/device instead of multiple separate nodes.

Thank you.

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

           reply	other threads:[~2026-09-14 16:46 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <18d53dc01290ce00-webhooks-bot@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=18d53dc0129eb200-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.