Revision history [back]

you should not rely on cap.get(cv2.CAP_PROP_FPS), it might be entirely bogus. replace it with a straight 30

then, all you have to control the playrate is minimizing the overall workload (3 videowriters ? bad idea !) and carefully throtteling with the sleep time in waitKey()

last but not least: those classes are utility functions to acquire images for computer-vision . don't try to abuse those for video editing, etc.

you should not rely on cap.get(cv2.CAP_PROP_FPS), it might be entirely bogus. replace it with a straight 30

you have to measure your actual fps, then you have to calculate "how many frames go into 30 seconds, and count them in your program

then, all you have to control the playrate is minimizing the overall workload (3 videowriters ? bad idea !) and carefully throtteling with the sleep time in waitKey()

last but not least: those classes are utility functions to acquire images for computer-vision . don't try to abuse those for video editing, etc.

you should not rely on cap.get(cv2.CAP_PROP_FPS), it might be entirely bogus. bogus, and never takes into account, how much time is actually spent in your frame loop.

you have to measure your actual fps, then you have to calculate "how many frames go into 30 seconds, and count them in your program

then, all you have to control the playrate is minimizing the overall workload (3 videowriters ? bad idea !) and carefully throtteling with the sleep time in waitKey()

last but not least: those classes are utility functions to acquire images for computer-vision . don't try to abuse those for video editing, etc.

you should not rely on cap.get(cv2.CAP_PROP_FPS), it might be entirely bogus, and never takes into account, how much time is actually spent in your frame loop.

you have to measure your actual fps, and put that into your VideoWriter. then you have to calculate "how many frames go into 30 seconds, and count them in your program

then, all you have to control the playrate is minimizing the overall workload (3 videowriters ? bad idea !) and carefully throtteling with the sleep time in waitKey()

last but not least: those classes are utility functions to acquire images for computer-vision . don't try to abuse those for video editing, etc.

you should not rely on cap.get(cv2.CAP_PROP_FPS), it might be entirely bogus, and never takes into account, how much time is actually spent in your frame loop.

you have to measure your actual fps, and put that into your VideoWriter. then you have to calculate "how many frames go into 30 seconds, and count them in your program

then, all you have to control the playrate is minimizing the overall workload (3 videowriters ? bad idea !) and carefully throtteling with the sleep time in waitKey()

last but not least: those classes are utility functions to acquire images easily for computer-vision . don't try to abuse those for video editing, etc.etc. if you need a time-exact recording software, use vlc,ffmpeg,gstreamer, not opencv.