This PR addresses the problem described in issue #249, where dropped_frames was always reported as zero due to its assignment occurring after bc.stopCapture() in startCapture.py. The proposed change ensures that the correct number of dropped frames is reported in the logs.
Changes made:
Moved the assignment of dropped_frames from after bc.stopCapture() to just before it. This change ensures that dropped_frames is accurately reported before the capture stops.
This PR addresses the problem described in issue #249, where
dropped_frameswas always reported as zero due to its assignment occurring afterbc.stopCapture()instartCapture.py. The proposed change ensures that the correct number of dropped frames is reported in the logs.Changes made:
dropped_framesfrom afterbc.stopCapture()to just before it. This change ensures thatdropped_framesis accurately reported before the capture stops.Fixes #249