-
Notifications
You must be signed in to change notification settings - Fork 36
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
Can't Set CV_CAP_PROP_BUFFERSIZE #13
Comments
I have also notice that |
On my Raspberry Pi project, |
Closing as this is an OpenCV issue |
Problem
Given an unknown source framerate and unknown frame processing time for each frame, we want to be able to always grab the most recent frame at the time of a
read()
call. In contrast to traditional process-every-frame stream workflows, which opencv-python seems to have been designed around.Ideally we could follow
cap.set(CV_CAP_PROP_BUFFERSIZE,1)
and then always have the most recent frame available. Unfortunately, contrary to this suggestion, we don't appear to be able to set this property in Python:It appears everyone tries to manually flush the buffer themselves e.g. 1 2a 2b
Current Workaround
As a workaround, I parameterized the buffer skipping rate. So users of this package still have to be conscious of their source framerate and set a flush rate accordingly.
Possible Solutions
Some options to consider to fix this:
CAP_PROP_BUFFERSIZE
property for OpenCV.The text was updated successfully, but these errors were encountered: