OpusElectronics

Any use of libusb_get_device_list() shows the issue on Windows. First thing I tested was testlibusb.c in your examples, and it's pretty slow. As slow in another program I wrote. I...

hotplug support in Windows would be useful, extending libusb_wrap_sys_device() would be useful as well but probably not as convenient, as finding the device path on Windows would probably be relatively...

Thanks. I would prefer a common code base for both Windows and Linux, but I'll have a look at libusbK nevertheless.

I will try to investigate what system calls exactly take this long. I had noticed a bit of a long enumeration time with FTDI libraries on Windows too, which could...

Note that the USBView tool from the Windows SDK lists USB devices very fast on the same machine. (Probably under 100 ms) Could be worth looking at the source code....

``` [timestamp] [threadID] facility level [function call] -------------------------------------------------------------------------------- [ 0.000011] [00002938] libusb: debug [libusb_init] created default context [ 0.000017] [00002938] libusb: debug [libusb_init] libusb v1.0.26.11724 [ 0.000149] [00002938] libusb: debug...

I think we're onto something. I checked - this is an internal USB bluetooth adapter that I don't use, so I have disabled it in the device manager. Could it...

Yes, enabling it makes it faster - but it's still slow. ```[timestamp] [threadID] facility level [function call] -------------------------------------------------------------------------------- [ 0.000019] [000041fc] libusb: debug [libusb_init] created default context [ 0.000025] [000041fc]...

At least we know what causes the issue, well kinda. Interestingly, as I said, it also seems to affect FTDI libraries on Windows. Possibly for the same reason. What I...

I'll have a look at the source code, which from what I've gathered is in the os/windows_winusb.c file. Fixing the issue on a more general level rather than just "blacklisting"...