Denis Arnst

Someone would have to provide support who owns the headset with this problem. But the best would be, to rewrite it (and possible making new captures) for using it in...

You need to rewrite the libUSB commands to hidapi. Both are very similar, except that hidapi abstracts some things. For that I would look into the documentation of boths. Here...

I guess you probably missed something, because if the data matches - it should work. Did you compare your data with the latest working revision? (https://github.com/Sapd/HeadsetControl/blob/master/src/devices/logitech_g430.c the commented code) The...

Note that the usageids are only relevant for Windows. Also Headsetcontrol has a semi-support for them. Because it only solely supports one usageid/usagepage pair. That means if the headset has...

> @Sapd Is there a non-blocking variant of the read command? If I switch off the headset but let the USB key plugged in HeadsetControl seems to stall on hid_read()...

You could try adding the productID of your device to `steelseries_arctic_7.c`

> So the code seems to be using `hid_write` to speak to the supported Arctis headsets but when I sniff the USB for this one, I see that it's using...

> it looks like the hid_error is not implemented yet is a hidapi thing? Yep. With some implementations (apparently the MacOS Implementation: https://github.com/libusb/hidapi/issues/310) it is simply not implemented. On Linux...

Im not 100% sure why sometimes relevant packets are not visible via WireShark. Can you also try it with the USBLyzer trial?

I made some notes, regarding the data in your first screenshot: ``` bmRequestType 0x21 // HID, Recipent is interface bRequest 0x01 // CLEAR_FEATURE wValue 0x0200 // This defines the Feature...