fix: tskip use the wrong recon #6
Open
Conversation
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
Contributor
|
Hi eltonxiao. Actually this is just a mirror repository. You should better send your important patch with an email to x265-devel@videolan.org. For details see |
|
I’m really interested in ensuring accurate TSkip calculations for chroma, as it directly affects encoding efficiency and quality. My approach would be to carefully review the variable usage in energy calculations, test the impact of this fix across multiple scenarios, and ensure consistency with the standard reconstruction process. I’ll work on preparing a proper patch submission soon. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
fix bug:
for chroma tskip,
the energy calculation is based on wrong variable.