linux-usb.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 219111] Xone:23C mixer not recognized as a 2in/2out device
Date: Sat, 10 Aug 2024 19:37:44 +0000	[thread overview]
Message-ID: <bug-219111-208809-UGQdzbhgLX@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-219111-208809@https.bugzilla.kernel.org/>

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

--- Comment #55 from Alan Stern (stern@rowland.harvard.edu) ---
The really important thing is bNumConfigurations.  If it is set to 1 then the
device doesn't make config 2 available, but if it is set to 2 then the device
does make config 2 available (even if the computer decides to use config 1).

The configuration descriptor includes four interfaces.  Interface 0 is the
audio control interface; it describes two USB terminals (one in, one out) and
two audio terminals (one in, one out).  It also says that the input terminals
each have 2 channels (regular stereo).

Interfaces 1 and 2 are for audio streaming.  Interface 1 is the USB-out
connection; it runs at 48000 Hz with 24-bit samples, it can be synchronized to
a clock on the device, and it can also operate in a vendor-specific way. 
Interface 2 is the USB-in connection; it also runs at 48000 Hz with 24-bit
samples and it also has a vendor-specific alternate setting.

Interface 3 is for MIDI.  As far as I can see, you aren't using it.

The packet capture shows the computer issuing a few vendor-specific requests. 
I have no way to know what they mean, but they involve getting data from the
device, not sending data to the device.  So they probably don't affect the way
the device operates.

The thing we really need to know is how the Windows driver tells the device to
switch to configuration 2.  I haven't seen anything in the packet captures that
show how it does this.  (However, the most recent capture shows that at the
361-second mark, the computer deconfigures the device and the sets it back to
configuration 1.  I can't tell why that happened.)

Or maybe the Windows driver uses the vendor-specific alternate settings rather
than the standard USB audio class settings.  The packet captures don't show the
computer telling the device which alternate setting to use.  This must happen,
because the default setting uses no bandwidth and transfers no audio data, but
it doesn't show up in the packet captures.  (It does show up in the usbmon
traces.)

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

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

  parent reply	other threads:[~2024-08-10 19:37 UTC|newest]

Thread overview: 57+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-30 18:11 [Bug 219111] New: Xone:23C mixer not recognized as a 2in/2out device bugzilla-daemon
2024-07-30 18:13 ` [Bug 219111] " bugzilla-daemon
2024-07-30 18:14 ` bugzilla-daemon
2024-07-30 18:14 ` bugzilla-daemon
2024-07-30 18:16 ` bugzilla-daemon
2024-07-31 14:59 ` bugzilla-daemon
2024-07-31 15:38 ` bugzilla-daemon
2024-07-31 15:46 ` bugzilla-daemon
2024-07-31 15:47 ` bugzilla-daemon
2024-07-31 18:14 ` bugzilla-daemon
2024-07-31 18:53 ` bugzilla-daemon
2024-07-31 19:20 ` bugzilla-daemon
2024-07-31 19:21 ` bugzilla-daemon
2024-07-31 19:27 ` bugzilla-daemon
2024-07-31 19:28 ` bugzilla-daemon
2024-08-01  7:41 ` bugzilla-daemon
2024-08-01 15:01 ` bugzilla-daemon
2024-08-04 10:39 ` bugzilla-daemon
2024-08-04 15:38 ` bugzilla-daemon
2024-08-04 19:13 ` bugzilla-daemon
2024-08-05 13:41 ` bugzilla-daemon
2024-08-05 13:41 ` bugzilla-daemon
2024-08-05 14:55 ` bugzilla-daemon
2024-08-05 16:13 ` bugzilla-daemon
2024-08-05 16:15 ` bugzilla-daemon
2024-08-05 16:20 ` bugzilla-daemon
2024-08-06 14:09 ` bugzilla-daemon
2024-08-06 14:12 ` bugzilla-daemon
2024-08-06 14:41 ` bugzilla-daemon
2024-08-06 15:46 ` bugzilla-daemon
2024-08-06 15:50 ` bugzilla-daemon
2024-08-06 19:08 ` bugzilla-daemon
2024-08-07 12:28 ` bugzilla-daemon
2024-08-07 12:29 ` bugzilla-daemon
2024-08-08  7:30 ` bugzilla-daemon
2024-08-08 12:02 ` bugzilla-daemon
2024-08-08 16:19 ` bugzilla-daemon
2024-08-08 17:12 ` bugzilla-daemon
2024-08-08 18:22 ` bugzilla-daemon
2024-08-08 18:36 ` bugzilla-daemon
2024-08-08 19:49 ` bugzilla-daemon
2024-08-08 20:11 ` bugzilla-daemon
2024-08-09  1:38 ` bugzilla-daemon
2024-08-09  8:14 ` bugzilla-daemon
2024-08-09  9:33 ` bugzilla-daemon
2024-08-09 14:06 ` bugzilla-daemon
2024-08-09 14:56 ` bugzilla-daemon
2024-08-09 15:20 ` bugzilla-daemon
2024-08-09 15:29 ` bugzilla-daemon
2024-08-09 15:44 ` bugzilla-daemon
2024-08-10 10:48 ` bugzilla-daemon
2024-08-10 11:48 ` bugzilla-daemon
2024-08-10 15:49 ` bugzilla-daemon
2024-08-10 17:10 ` bugzilla-daemon
2024-08-10 17:19 ` bugzilla-daemon
2024-08-10 19:37 ` bugzilla-daemon [this message]
2024-08-11  1:52 ` bugzilla-daemon

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=bug-219111-208809-UGQdzbhgLX@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@kernel.org \
    --cc=linux-usb@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).