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 Audient iD14 MkI (2708:0002) profile
Date: Sun, 23 Aug 2026 21:02:53 +0200 (CEST)	[thread overview]
Message-ID: <18ce847c53b4eb00-webhooks-bot@alsa-project.org> (raw)
In-Reply-To: <alsa-project/alsa-ucm-conf/pr/836@alsa-project.org>

alsa-project/alsa-ucm-conf pull request #836 was opened from willyp713:

Add UCM2 support for the Audient iD14 MkI USB audio interface (`2708:0002`).

The HiFi use case exposes:

- two logical stereo playback pairs (`Output 1/2` and `Output 3/4`)
- two mono analogue capture devices (`Mic/Line Input 1` and `Mic/Line Input 2`)

The Direct use case preserves the raw 4-output/10-input stream for DAWs. This follows the existing iD14 MkII profile's policy of leaving the state-dependent digital capture channels out of the ordinary desktop profile.

The device's FU12 monitor-mix volume behaves asymmetrically below unity. The card-level `FixedBootSequence` initializes all four channels to 0 dB on boot or hotplug, including when Direct is selected (Direct has no verb). The HiFi enable sequence reapplies unity. A `ControlExists` check supports both the historical `Speaker Playback Volume` control and the `Monitor Mix Playback Volume` name from the accepted kernel quirk:

https://lore.kernel.org/r/20260823015353.686080-1-mrwillporter@gmail.com

Hardware-tested on Bazzite with PipeWire 1.6.8 and kernel `7.2.0-ogc4.1.fc44.x86_64`, including both playback pairs, mono inputs, Direct access, channel isolation, software volume, and a physical USB reconnect. The current upstream validator also passes against:

- alsa-ucm-conf `00175aa645c482111d096c3d8230f182a875d286`
- alsa-tests `53d34b6`

The required `alsa-info.sh` output will be attached to this PR.

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

       reply	other threads:[~2026-08-23 19:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <alsa-project/alsa-ucm-conf/pr/836@alsa-project.org>
2026-08-23 19:02 ` GitHub pull_request - opened [this message]
2026-08-23 19:13 ` USB-Audio: Add Audient iD14 MkI (2708:0002) profile GitHub pull_request - 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=18ce847c53b4eb00-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.