From: GitHub issues - opened <github@alsa-project.org>
To: alsa-devel@alsa-project.org
Subject: Steinberg UR22C: Version 1.2.14 introduced "[ALSA UCM error]"
Date: Tue, 15 Apr 2025 19:16:48 +0200 (CEST) [thread overview]
Message-ID: <18368d6d49dfe300-webhooks-bot@alsa-project.org> (raw)
In-Reply-To: <18368d6d49bd4300-webhooks-bot@alsa-project.org>
alsa-project/alsa-ucm-conf issue #547 was opened from NoXPhasma:
Since version 1.2.14 the `node.description` of the Steinberg UR22C shows `[ALSA UCM error]`:
```
node.description = "Steinberg UR22C [ALSA UCM error] Direct Steinberg UR22C"
```
Reverting to version 1.2.13 fixes this issue.
Issue URL : https://github.com/alsa-project/alsa-ucm-conf/issues/547
Repository URL: https://github.com/alsa-project/alsa-ucm-conf
next parent reply other threads:[~2025-04-15 17:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <18368d6d49bd4300-webhooks-bot@alsa-project.org>
2025-04-15 17:16 ` GitHub issues - opened [this message]
[not found] <18368da1e537d500-webhooks-bot@alsa-project.org>
2025-04-15 17:20 ` Steinberg UR22C: Version 1.2.14 introduced "[ALSA UCM error]" 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=18368d6d49dfe300-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox