Use Per-Frame Durations instead of Average #148
Merged
philipp-fischer merged 2 commits intodevelopfrom Jul 7, 2025
Merged
Conversation
Signed-off-by: Max <mehrlich@nvidia.com>
Signed-off-by: Max <mehrlich@nvidia.com>
Collaborator
|
Cool 😎 |
philipp-fischer
approved these changes
Jul 7, 2025
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.
In PyAV-Org/PyAV#1880 I added support for the ffmpeg
durationfield on frames (it was previously only present in packets). That PR was shipped in PyAV 14.4.0 and this PR updates energon to use this field instead of a computed average duration.Since variable frame-rate videos can have frames with differing durations this PR makes our decode loop more accurate.