On 2012.10.29 18:32, Stefano Di Martino wrote: > You mean under Windows? I just did this today, but I'll attach it again.
Sorry, missed the first one (catching up on e-mail). Apart from the assertion warnings, I don't see much of anything wrong, and I'm not even sure that the assertion is an issue at this stage. I have a similar audio device and the first interfaces are hijacked by the Windows A/V subsystems so don't register as HID => only the 4th interface will. From what I can see, libusbx properly recognises that the first 3 interfaces are no go and therefore attempts to use the 4th. I can't see the NO_MEM yet (still looking at it), and I also can't see string descriptors from lsusb. Does your device actually have string descriptors? Regards, /Pete ------------------------------------------------------------------------------ The Windows 8 Center - In partnership with Sourceforge Your idea - your app - 30 days. Get started! http://windows8center.sourceforge.net/ what-html-developers-need-to-know-about-coding-windows-8-metro-style-apps/ _______________________________________________ libusbx-devel mailing list libusbx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libusbx-devel
