-
Notifications
You must be signed in to change notification settings - Fork 51
Feature request: isochronous buffer packets offset/length #2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Labels
Comments
libusb-win32 project is in a support only mode. Mailing list support is still provided, no changes to the codes and release. |
For isochronous transfer, please use libusbk.sys or WinUSB. So I will keep wontfix label here. |
Patches submitted:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
https://sourceforge.net/p/libusb-win32/feature-requests/12/
Updated: 2012-07-06 Created: 2010-11-23 Creator: Tim Schuerewegen
I am using libusb-win32 to communicate with a OV550/OV5620 based webcam. I am using isochronous async reads to get the video data from the webcam. However, there is one problem. The data in the buffer (after a reap) is not contiguous, ie. there are holes in it. In order for me to know which parts in the buffer are data and which parts are garbage/empty, I need access to the URB's IsoPacket array. The Offset/Length value pairs of the IsoPacket array are the only way I can piece the video frames back together.
Example:
As you can see the 0x60 bytes of data are spread across 2 iso packets. Without the IsoPacket array Offset/Length information I can not locate the 0x60 bytes of data from the buffer.
Thank you in advance.
The text was updated successfully, but these errors were encountered: