workaround when reading broken video frames #5726
Closed
+10
β0
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Some videos are being read with additional fake/broken frames that may
cause an unexpected early exit. This attempts to skip over these broken
frames if more were expected, based on the initally acquired frame
count.
According to other reports upstream, the number of broken frames read
varies. To avoid getting stuck in an endless loop, e.g. when the video
is actually broken, this gives up after 1000 reads.
see #2064
see opencv/opencv#15352
π οΈ PR Summary
Made with β€οΈ by Ultralytics Actions
π Summary
Improving video stream handling in YOLOv5's dataset utility.
π Key Changes
π― Purpose & Impact
The changes should make YOLOv5 more robust in handling video data, leading to a smoother user experience and less time troubleshooting video input issues.