[Bug 220143] New: DLZ Creator XS (USB Audio) not working – accepts hw params but playback fails (write error -77)

[bugzilla-daemon@kernel.org]

https://bugzilla.kernel.org/show_bug.cgi?id=220143

            Bug ID: 220143
           Summary: DLZ Creator XS (USB Audio) not working – accepts hw
                    params but playback fails (write error -77)
           Product: Drivers
           Version: 2.5
    Kernel Version: 6.14.0-15-generic
          Hardware: All
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P3
         Component: USB
          Assignee: drivers_usb@kernel-bugs.kernel.org
          Reporter: maps@knutsson.it
        Regression: No

The Mackie / LOUD Audio DLZ Creator XS USB audio interface is detected
correctly by ALSA, and presents itself with:
Vendor ID: 0a73
Product ID: 003a

USB interface: High-speed

ALSA detection: card 2 (via aplay -l)

The device only accepts:

Format: S32_LE

Sample rate: 48000 Hz

Channel count: 4

When using:
speaker-test -D hw:2,0 -c 4 -F S32_LE -r 48000
…the device accepts snd_pcm_hw_params() successfully but fails at playback:

Write error: -77, File descriptor in bad state
xrun_recovery failed: -77
The same happens with:

aplay -D hw:2,0 <converted 4ch/32bit/48000Hz file>
The interface disconnects and reconnects after such playback attempts in many
cases. No audio is heard. All simpler formats (e.g., 1 or 2 channels, or
16-bit) are rejected with Invalid argument.

Reproduce Steps:
Plug in DLZ Creator XS to USB 2.0 or 3.0 port

Confirm device appears via aplay -l

Run:
speaker-test -D hw:2,0 -c 4 -F S32_LE -r 48000
Observe that device accepts format, then playback fails

lsusb -v output:
Bus 003 Device 013: ID 0a73:003a Mackie Designs DLZ Creator XS
iManufacturer           1 LOUD Audio, LLC
iProduct                2 DLZ Creator XS
iSerial                 3 no serial number

Tested with
Ubuntu 24.04 (kernel 6.5)
Ubuntu 25.05 (kernel 6.14)

Same behavior across systems

Device works flawlessly under Windows with official driver

Comment
It appears the device requires a very specific channel layout and potentially
vendor-specific initialization or control messaging before playback is
possible. If this device is non-compliant with UAC2 spec, perhaps it should be
explicitly blacklisted or set up with a vendor-specific quirk?

I would be happy to run more usbmon/alsa-info traces if needed.

I apologize beforehand, as I have not filled out a bug report before.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.