On Sun, Jun 17, 2012 at 7:08 PM, Ellis Whitehead <ellis.whiteh...@gmail.com> wrote: > I have a project http://gcead.sourceforge.net/ that records data from > an isochronous acquisition device. The USB communication utilizes > libusbx on linux and libusb-win32 on windows, and both work fine > (thanks!).
Great. Thanks for the report. There are not many examples using libusb-win32's async API, especially for isochronous transfer. When libusbx-1.0.13 integrates libusb0.sys support, you might be able to consolidate to use libusbx if isochronous support is added to libusbx. http://sourceforge.net/apps/trac/libusbx/roadmap > On mac, however, data is frequently dropped, and we see the following > error message repeated many thousands of times: > > libusbx: error [darwin_async_io_callback] async size truncation > detected - please report this error > libusbx: warning [darwin_transfer_status] transfer error: unknown > error (value = 0xe000400f) > > I'm using libusbx 1.0.14. Is there anything you can suggest to get is > working? > Hmm, there is no such version as libusbx-1.0.14, do you mean libusbx-1.0.12? You can produce detailed debug log if you set the environmental variable LIBUSB_DEBUG to 4. That debug log may help to identify the potential problem. -- Xiaofan ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ libusbx-devel mailing list libusbx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libusbx-devel
