From: GitHub pull_request - opened <github@alsa-project.org>
To: alsa-devel@alsa-project.org
Subject: ucm2 USB-Audio: add RME Fireface 802 (CC+USB mode) and UFX III, fix typos in existing UCX/UCX-II
Date: Fri, 3 Apr 2026 22:07:47 +0200 (CEST) [thread overview]
Message-ID: <18a2f19e23921b00-webhooks-bot@alsa-project.org> (raw)
In-Reply-To: <alsa-project/alsa-ucm-conf/pr/737@alsa-project.org>
alsa-project/alsa-ucm-conf pull request #737 was opened from huddx01:
Adds UCM profiles for RME Fireface 802 and UFX III devices and fixes a pre-existing bug in the existing UCX/UCX-II profiles.
New devices:
- Fireface 802 CC mode (0424:3fdd, 22ch) - tested on Debian Trixie
- Fireface 802 USB/driver mode (2a39:3fcd, 30ch) - tested, but my driver/module not yet stable enough for upstream submission
- Fireface UFX III CC mode (2a39:3fde, 94ch) - tested on Debian Trixie
Additional Bug fixes - I noticed while looking at the RME dir:
- Fireface-UCX-HiFi.conf: 9 occurrences of PlackbackPriority -> PlaybackPriority
- Fireface-UCX-II-HiFi.conf: 10 occurrences of PlackbackPriority -> PlaybackPriority,
typo "AES3 XLR Ouptut" -> "AES3 XLR Output" (transposed letters)
Channel layout sources:
- CC mode channel count verified via /proc/asound/card*/stream0
- USB mode channel layout derived from Wireshark USB captures, see:
https://github.com/huddx01/oscmix/wiki/Fireface-802
https://github.com/huddx01/oscmix/wiki/Fireface-UFX-III
alsa-info output for Fireface 802 CC mode attached below.
[alsa-info.txt](https://github.com/user-attachments/files/26470990/alsa-info.txt)
Request URL : https://github.com/alsa-project/alsa-ucm-conf/pull/737
Patch URL : https://github.com/alsa-project/alsa-ucm-conf/pull/737.patch
Repository URL: https://github.com/alsa-project/alsa-ucm-conf
parent reply other threads:[~2026-04-03 20:08 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <alsa-project/alsa-ucm-conf/pr/737@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=18a2f19e23921b00-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.