You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using the grab function we were originally getting timeout errors. We found that the _read() function takes a long time (~0.6s) and so we changed the timeout threshold to a very large 1.5s.
We then started getting frame width errors, where varying frame widths eg.(1203, 969, 52646, 1284) were found by the _convert_frame() funciton when we repeatedly tried to grab images.
Do you have any idea why this might be happening? Why it takes so long for the data to be read? The only thing we can think of is a slow USB connection. We're talking to the grabber through linux on an oracle virtual machine with USB 3.0 FYI
Thanks in advance
The text was updated successfully, but these errors were encountered:
Hi Louis, the Grabber is not USB 3 capable, unless it's been updated - so
it's unlikely that will make things any faster. You can try the official
libraries if you like, that would at least determine if flirpy is the cause
of the slowdown. I suspect it's because our driver implementation is not
particularly efficient, but with the camera I tested with it wasn't that
slow!
When using the grab function we were originally getting timeout errors. We found that the _read() function takes a long time (~0.6s) and so we changed the timeout threshold to a very large 1.5s.
We then started getting frame width errors, where varying frame widths eg.(1203, 969, 52646, 1284) were found by the _convert_frame() funciton when we repeatedly tried to grab images.
Do you have any idea why this might be happening? Why it takes so long for the data to be read? The only thing we can think of is a slow USB connection. We're talking to the grabber through linux on an oracle virtual machine with USB 3.0 FYI
Thanks in advance
The text was updated successfully, but these errors were encountered: