Skip to content
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

Framerate Limit #118

Open
ryanmgriffiths opened this issue Dec 9, 2019 · 1 comment
Open

Framerate Limit #118

ryanmgriffiths opened this issue Dec 9, 2019 · 1 comment

Comments

@ryanmgriffiths
Copy link

ryanmgriffiths commented Dec 9, 2019

I am attempting to work some high frame rates (~300fps). I have everything set up correctly and the features list shows the correct absolute frame rate limit but using time.time and acquiring 300 frames with:

with Vimba as vimba:
camera = vimba.camera(0)
camera.open()
camera.arm('continuous', incrementing_function, frame_number)
start = time.time()

camera.start_frame......

while counter < frame_number:
pass

camera.end_frame.....
end = time.time() - start
#Disarm & close

the time taken is ~3,5 seconds which is an effective frame rate of 83fps. Furthermore if I reduce the absolute frame rate limit below this then I can see that the lower frame rate was being achieved. I get trashed frames when exceeding this limit.

I also have a similar program running in Visual Studio on the C API which is able to match the exact absolute frame rate limit set on Vimba Viewer. It doesn't seem like python speed should be the limitation since the frames are announced by calling the frame number as an argument to the arm function and the callback executes a simple incrementing counter.

@Gabry993
Copy link

Gabry993 commented Dec 9, 2019

Usually while loops with pass inside kill performances. Try to replace 'pass' with time.sleep(0.1) for example

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants