Skip to content
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

Fixed decoder needing flush in some cases #21

Merged
merged 1 commit into from
Oct 15, 2022

Conversation

msabansal
Copy link

In a local test environment i have an h264 stream that returns 0 on the first call to decode_frame_no_delay and iBufferStatus != 0.

In this case we should check the numbers of frames remaining in buffer (0 or 1) and flush the buffer if it is 1.

@ralfbiedert
Copy link
Owner

Thanks!

@ralfbiedert ralfbiedert merged commit ac13495 into ralfbiedert:master Oct 15, 2022
@ralfbiedert
Copy link
Owner

Ah, I forgot to mention. In your own interest, could you also submit a follow-up PR containing a test case and a minimal .h264 file triggering the issue?

It's not strictly necessary, but otherwise there is a risk for that logic to accidentally get refactored out at some point.

@msabansal
Copy link
Author

@ralfbiedert thanks for merging. I was unsure of a test on this. The file decodes without any error without this code. Only that output has artifacts and that too on subsequent call to decode.

Unclear if I should add something that compares output to an image

@msabansal msabansal deleted the fix_decode branch October 15, 2022 13:23
@msabansal
Copy link
Author

For now added a simple test to validate fame is decoded properly #22

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants