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

Fix frame-decode errors. #3721

Closed
wants to merge 7 commits into from
Closed

Fix frame-decode errors. #3721

wants to merge 7 commits into from

Conversation

tyan0
Copy link
Contributor

@tyan0 tyan0 commented Jan 19, 2024

This pull request is for both #3710 and #3713.
I am not very sure that these are the correct fixes even though the frame decode errors are indeed resolved, so please review them. Especially for #3713.

tyan0 and others added 7 commits December 6, 2023 09:25
In CWelsDecoder::ReorderPicturesInDisplay(), iLastWrittenPOC was
not set in unbuffered-reordering case. Due to this problem, it
sometimes reordered the frames incorrectly. This patch fixes the
issue.
When bNewSeqBegin got true, iRefCount was forcibly reset even if the
buffer was still used for reordering. Due to this problem, the buffer
in use was sometimes overwritten with newly decoded frame. This commit
is for fixing that problem.
Previously, when more than 2 frame sequences exist in the reordering
buffer, the reordering does not work correctly. This is because the
management based on bLastGOP flag does not work in this case.
Instead, this patch introduces frame sequence number (iSeqNum) to
distingish frames belonging to each sequence and drops bLastGOP flag.
... and fix trivial issue of that function. This solves the some
frame decode error.
@joakim-tjernlund
Copy link

Does this PR need rebasing?

@tyan0
Copy link
Contributor Author

tyan0 commented Jan 24, 2024

I had synchronized to this master and rebased to the master in my forked repository. So, "Files changed" includes only the commit 1792403 and f7d35f2. However, "Commits" also shows previous five commits for unknown reason.

What was wrong in my steps?

@joakim-tjernlund
Copy link

I had synchronized to this master and rebased to the master in my forked repository. So, "Files changed" includes only the commit 1792403 and f7d35f2. However, "Commits" also shows previous five commits for unknown reason.

What was wrong in my steps?

Seems to be a Merge in there somehow, not sure how it got there.

But you can checkout a clean master and cherrypick the two patches and push --force to this branch again

@tyan0 tyan0 closed this Jan 24, 2024
@tyan0 tyan0 deleted the bug_fix_2 branch January 24, 2024 13:52
@tyan0 tyan0 mentioned this pull request Jan 24, 2024
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.

2 participants