Fix video frame count estimation by detecting actual FPS from uploaded video#1992
Merged
grzegorz-roboflow merged 2 commits intomainfrom Feb 10, 2026
Conversation
rafel-roboflow
requested review from
PawelPeczek-Roboflow,
grzegorz-roboflow,
hansent,
probicheaux and
yeldarby
as code owners
grzegorz-roboflow
approved these changes
Feb 10, 2026
grzegorz-roboflow
deleted the
bug/dg-252-fix-frame-calculation-for-video-stored-at-5fps
branch
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Resolves DG-252
What does this PR do?
Previously, FPS was assumed to be 30 for all videos. This caused incorrect frame counts in the frontend preview when videos had higher or lower frame rates. This PR uses the actual FPS to calculate frames correctly.
Related Issue(s):
Type of Change
Testing
Test details:
Checklist
Additional Context
Before and after: