-
Notifications
You must be signed in to change notification settings - Fork 54
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
Frame width varying with the TeaxGabber and Tau2 #56
Comments
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!
…On Fri, Aug 27, 2021 at 12:52 PM Louis Timperley ***@***.***> wrote:
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
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#56>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAYDMJ2FI6U46NHAI3DFZ3DT66DCLANCNFSM5C5PT2NA>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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: