-
-
Notifications
You must be signed in to change notification settings - Fork 181
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
HID error on macOS 13.3 #281
Comments
I verified it, and its a bit weird. Seems that with the new Mac update the interface id changed (to 0), while on a Linux VM it is still 3. So I simply changed it to 0 in the latest master which means that simply the first interface will be used. |
Ha! Interesting development. I've installed the latest version and can confirm it started working again. Thanks for the quick fix! 😄 |
Same issue applies to SteelSeries Arctis 7 on macOS 13.3.1 I found someone referencing the issue here: https://developer.apple.com/forums/thread/728001 |
That could be indeed an Apple bug. Maybe it also makes sense to create an issue at the libusb/hidapi repo, so that they also can check. In theory we can also simply set interfaceid to 0 for all devices which only use one. |
I thought about it again, and I think the best way to fix it, is to change this function: HeadsetControl/src/hid_utility.c Line 24 in 6641224
and set iid to 0 for macos. Will reopen the issue until it is done |
WIll keep the code-as is, but for further reference should an issue arise: Fixed here in HIDAPI: libusb/hidapi#534 |
Mac seems to user a different interfaceid now We simply take now the first enumerated interfaceid (0) Fixes Sapd#281
Description
Ever since updating to macOS Ventura 13.3 a few days ago
headsetcontrol
has stopped working for me. I'm getting some very generic sound error messages, eg:I'm not really sure how to debug this further, so any input is appreciated 😄
Headset Name
Corsair VOID PRO Wireless
On which OS does the problem happen?
MacOS
Device information
Detailed Device Information
The text was updated successfully, but these errors were encountered: