-
-
Notifications
You must be signed in to change notification settings - Fork 337
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
Crash with DFK 33UX273 Camera at 200 FPS and 1000 Exposure, Works Fine with Basler QCAM-UC1440-220CE #913
Comments
|
It is a function to convert img in raw format to numpy array
|
Thanks. At some point in the log, the payload size returned in the image trailer packet changes from 4665600 to 187396. Do you change some features between 2 call to |
Yes, after initializing the camera the application starts capturing(using __non_triggered_capture) and then during the capture the application configure some features, such as exposure, gain and gamma, for example. |
Is this an exhaustive list ? Any feature that may modify the payload size ? |
Full list: I think the only part that can change the payload size is the part where I configure the image size(which I called region in the list above). set window size method
create buffer method
|
You should also stop the acquisition thread when you want to set the region, otherwise there will still be buffer with the wrong size in the queues. Please have a look at |
Hi!
Describe the bug
When I use a camera The Imaging Source DFK 33UX273 with 200 fps and exposure 1000 my application crashes, but when I use a Basler QCAM-UC1440-220CE camera it doesn't crash
To Reproduce
I set the camera to 1000 us of exposure and set the fps to 200
Expected behavior
I hope to get the images for later processing with any camera
Camera description:
CAMERA THAT OCCURS THE BUG
CAMERA THAT DOESN'T OCCUR THE BUG
Platform description:
Additional context
capture loop
``
Log the imaging source
Logs basler
The text was updated successfully, but these errors were encountered: