hidapi
hidapi copied to clipboard
libusb
A Simple cross-platform library for communicating with HID devices
Assuming the manufacturer of a device did not use serial_numbers to make particular hid devices unique. Is there a way to uniquely map from a given already open hid_device opaque...
add new API function: `int hid_interrupt_read(hid_device *dev)` it will asynchronously interrupt blocking `hid_read` call, if any details: TBD Closes: #133
Using hidapi on windows is constrained by multiple issues, i.e. the inability to gain exclusive access to many devices (see https://github.com/signal11/hidapi/issues/231) and no access to mouse & keyboard devices (https://github.com/signal11/hidapi/issues/313)...
At Mixxx, users reported problems with USB 2.0 High-Speed devices, which are limited to Full-Speed mode for some reasons. Under MacOS and Windows they operate as High-Speed device. This is...
My device has two input reports: 0x01 with a size of 10Bytes 0x02 with a size of 53Bytes If I use hid_read / hid_read_timeout I get always 53Bytes, also for...
need add notes to README regarding multithreading, e.g. regarding Windows issues/non-full support maybe some more
The Linux libusb and macOS backends maintain an internal buffer of 30 (where did this number come from?) input reports. If I understand correctly, when hid_read is called repeatedly, one...
Currently hidapi is not able to close open device handle in a thread-safe manner. This is due to `CancelIo` function being used instead of `CancelIoEx` for closing a win32 device...
Many devices require fixed lengths for getting and setting feature reports. This info is available from the caps structure but it is not exposed. ex. dev->feature_report_length = caps.FeatureReportByteLength;
Right now, you can use `hid_read` to wait for something to be available or `hid_read_timeout` to limit how long you want to read. While sticking to single-threaded code when interacting...
