-
Notifications
You must be signed in to change notification settings - Fork 72
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Number of encoded frames does not match number of decoded frames #155
Comments
jailuthra
added a commit
that referenced
this issue
May 6, 2020
Earlier we relied on getting a sentinel (pts -1) packet back to know when the decoder is flushed. This does not work for short segments as the decoder buffers packets internally. Now we maintain the difference between packets sent - frames received and mark decoder as flushed when this becomes 0 (usually). Sometimes the decoder might not return all frames (see #155), so we give up after sending SENTINEL_MAX packets and not getting any valid frame back.
jailuthra
added a commit
that referenced
this issue
May 6, 2020
Earlier we relied on getting a sentinel (pts -1) packet back to know when the decoder is flushed. This does not work for short segments as the decoder buffers packets internally. Now we maintain the difference between packets sent - frames received and mark decoder as flushed when this becomes 0 (usually). Sometimes the decoder might not return all frames (see #155), so we give up after sending SENTINEL_MAX packets and not getting any valid frame back.
jailuthra
added a commit
that referenced
this issue
May 15, 2020
Earlier we relied on getting a sentinel (pts -1) packet back to know when the decoder is flushed. This does not work for short segments as the decoder buffers packets internally. Now we maintain the difference between packets sent - frames received and mark decoder as flushed when this becomes 0 (usually). Sometimes the decoder might not return all frames (see #155), so we give up after sending SENTINEL_MAX packets and not getting any valid frame back.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Under particular conditions, the number of encoded frames does not match number of decoded frames.
lpms/ffmpeg/ffmpeg_test.go
Lines 1117 to 1209 in d722afc
The text was updated successfully, but these errors were encountered: