Skip to contentSkip to conversation

ALSA:usb-audio: Disable Arturia Audiofuse 16Rig

PATCH In review Phil Willoughby 2 participants 5 messages Mar 19 – Mar 27 Sound

lore
Share & tools
lore
#0 lore raw

cover ALSA:usb-audio: Disable Arturia Audiofuse 16Rig

I am working on properly supporting this device, and I have published that work in progress here:

I intend to continue working on this driver, test it fully with all the sample rates & clock sources that the device supports, and then contribute the necessary changes back to the mainline kernel. This will take at least several weeks because I need to source additional hardware to do that testing.

Because the device has 32 input channels we will need the patch to support that merged before it can be properly supported.

This patch chain prevents snd-usb-audio from claiming the device.

This is necessary because the startup sequence of snd-usb-audio puts the Arturia Audiofuse 16Rig into an invalid state from which it cannot be recovered other than by disconnecting the external power; even the front-panel on/off switch stops working.

Phil Willoughby (1):
ALSA:usb-audio: Disable Arturia Audiofuse 16Rig

 sound/usb/quirks-table.h | 7 +++++++
 1 file changed, 7 insertions(+)

base-commit: b3c48fa1fb397b490101785ddd87caf2e5513a66

Signature · 1 line
2.53.0
#1 lore raw

PATCH 1/1 ALSA:usb-audio: Disable Arturia Audiofuse 16Rig

There's an out of tree driver which works for some use-cases here:

---
 sound/usb/quirks-table.h | 7 +++++++
 1 file changed, 7 insertions(+)
sound/usb/quirks-table.h +7 -0
index eafc0d73cca1..728a2a4b5566 100644
@@ -3541,6 +3541,13 @@ YAMAHA_DEVICE(0x7010, "UB99"),
 		}
 	}
 },
+{
+	/* Arturia AudioFuse 16Rig has an out-of-tree driver */
+	USB_DEVICE(0x1c75, 0xaf20),
+	QUIRK_DRIVER_INFO {
+		.ifnum = QUIRK_NODEV_INTERFACE
+	},
+},
 {
 	/*
 	 * Fiero SC-01 (firmware v1.0.0 @ 48 kHz)
Signature · 1 line
2.53.0
#2 lore raw
Quoted 7 lines · Phil Willoughby

There's an out of tree driver which works for some use-cases here:

In general, we don't care much about the out-of-tree driver. If it's upstreamed, of course we'd love to help. But this kind of change is no-go.

thanks,

Takashi

Quoted 26 lines
---
 sound/usb/quirks-table.h | 7 +++++++
 1 file changed, 7 insertions(+)
sound/usb/quirks-table.h +7 -0
index eafc0d73cca1..728a2a4b5566 100644
@@ -3541,6 +3541,13 @@ YAMAHA_DEVICE(0x7010, "UB99"),
 		}
 	}
 },
+{
+	/* Arturia AudioFuse 16Rig has an out-of-tree driver */
+	USB_DEVICE(0x1c75, 0xaf20),
+	QUIRK_DRIVER_INFO {
+		.ifnum = QUIRK_NODEV_INTERFACE
+	},
+},
 {
 	/*
 	 * Fiero SC-01 (firmware v1.0.0 @ 48 kHz)
Signature · 1 line
2.53.0
#3 lore raw
Quoted 5 lines · On Friday, 27 March 2026 12:20:59 Greenwich Mean Time you wrote:
Quoted 3 lines · Phil Willoughby

There's an out of tree driver which works for some use-cases here:

Quoted 8 lines
Quoted 4 lines

In general, we don't care much about the out-of-tree driver. If it's upstreamed, of course we'd love to help. But this kind of change is no-go.

I'm happy to work on patches for an in-tree driver.

It would need the patch chain you sent me that replaces the hardcoded channel max with MAX_CHANNELS and makes the channel mask 64-bits, because it has 34 channels.

I'd also need to add one or two new quirk flags or device-id matching
branches: which approach is preferred?

Phil

#4 lore raw
Quoted 16 lines · Phil Willoughby
Quoted 5 lines · On Friday, 27 March 2026 12:20:59 Greenwich Mean Time you wrote:
Quoted 3 lines · Phil Willoughby

There's an out of tree driver which works for some use-cases here:

Quoted 8 lines
Quoted 4 lines

In general, we don't care much about the out-of-tree driver. If it's upstreamed, of course we'd love to help. But this kind of change is no-go.

Quoted 5 lines

I'm happy to work on patches for an in-tree driver.

It would need the patch chain you sent me that replaces the hardcoded channel max with MAX_CHANNELS and makes the channel mask 64-bits, because it has 34 channels.

If it's confirmed to work, I can submit and merge this beforehand.

Quoted 2 lines

I'd also need to add one or two new quirk flags or device-id matching
branches: which approach is preferred?

Well, it's hard to tell without comparing both changes...

thanks,

Takashi