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: Mon, 05 Aug 2024 14:55:53 +0000 [thread overview]
Message-ID: <bug-219111-208809-GUSkNYbP81@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 #22 from Alan Stern (stern@rowland.harvard.edu) ---
It doesn't help. It shows that the device provides one input and one output
stream, plus a MIDI connection -- no more. And it also shows the device claims
to have only one configuration, not two. (Plus it shows Windows setting the
data rates to 44100 samples per second, whereas your earlier Linux usbmon trace
showed the data rates being set to 48000 samples per second, but I assume this
doesn't matter much.)
Are you certain that the device has two input and two output streams under
Windows? The USB packet capture gives no indication of it.
Also, how does the device behave under Linux if you set the old_scheme_first
parameter to Y? In comment #6 you didn't say.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2024-08-05 14:55 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 [this message]
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
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-GUSkNYbP81@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).