count exact number of frames with ffprbe -count_frames #2373
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.
What changes are proposed in this pull request?
Count exact number of frames in a video.
How is this patch tested? If it is not, please explain why.
added a unit-test to the intensive group.
Release Notes
Is this a user-facing change that should be mentioned in the release notes?
notes for FiftyOne users.
Exact number of frames can be counted with
fiftyone.utils.video.exact_frame_count()
.This method uses
-count_frames
argument offfprobe
which decodes the entire video to count the frames and can be very slow.What areas of FiftyOne does this PR affect?
fiftyone
Python library changes