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
Gray line at the bottom of the frame #2817
Comments
I was able to reproduce the issue with the default configuration of rav1e binary. Inspecting the output in AOM Analyzer, we see that the artifact is contained within a 32x64 block that straddles the lower boundary. Will need to look deeper to identify why the distortion occurs in this case. It is also notable that the frame dimensions are not multiples of 8. |
Not necessarily related but it's also interesting how bad the decision is in terms of distortion. The ringing is pretty severe. |
Is distortion being measured in transform domain during partitioning? That might be what is giving bad results. |
Doesn't look like it is. |
It looks like the underlying cause is that our distortion measurement at the boundary expects input frames to be padded. |
This avoids a spatial discontinuity (and correspondingly large DCT coefficients) when there is a large DC error in the prediction. Fixes xiph#2817 https://beta.arewecompressedyet.com/?job=master-2021-10-01_064210-48149f18&job=pad_extend-2021-10-01_064216-b67291a2
This avoids a spatial discontinuity (and correspondingly large DCT coefficients) when there is a large DC error in the prediction. Fixes xiph#2817 https://beta.arewecompressedyet.com/?job=master-2021-10-01_064210-48149f18&job=pad_extend-2021-10-01_064216-b67291a2
This avoids a spatial discontinuity (and correspondingly large DCT coefficients) when there is a large DC error in the prediction. Fixes xiph#2817 subset1: https://beta.arewecompressedyet.com/?job=master-2021-10-01_064210-48149f18&job=pad_extend-2021-10-01_064216-b67291a2 objective-1-fast: https://beta.arewecompressedyet.com/?job=master-2021-10-01_170338-48149f18&job=pad_extend-2021-10-01_170346-a9bc2791
This avoids a spatial discontinuity (and correspondingly large DCT coefficients) when there is a large DC error in the prediction. Fixes xiph#2817 subset1: https://beta.arewecompressedyet.com/?job=master-2021-10-01_064210-48149f18&job=pad_extend-2021-10-01_064216-b67291a2 objective-1-fast: https://beta.arewecompressedyet.com/?job=master-2021-10-01_170338-48149f18&job=pad_extend-2021-10-01_170346-a9bc2791
This avoids a spatial discontinuity (and correspondingly large DCT coefficients) when there is a large DC error in the prediction. Fixes xiph#2817 subset1: https://beta.arewecompressedyet.com/?job=master-2021-10-01_064210-48149f18&job=pad_extend-2021-10-01_064216-b67291a2 objective-1-fast: https://beta.arewecompressedyet.com/?job=master-2021-10-01_170338-48149f18&job=pad_extend-2021-10-01_170346-a9bc2791
This avoids a spatial discontinuity (and correspondingly large DCT coefficients) when there is a large DC error in the prediction. Fixes xiph#2817 subset1: https://beta.arewecompressedyet.com/?job=master-2021-10-01_064210-48149f18&job=pad_extend-2021-10-01_064216-b67291a2 objective-1-fast: https://beta.arewecompressedyet.com/?job=master-2021-10-01_170338-48149f18&job=pad_extend-2021-10-01_170346-a9bc2791
We've merged a fix that fixes the image in this issue. I've also managed to construct a worst case image that isn't fixed even by the merged fix, I've filed issue #2823 for it. This one isn't really a logic error like our merged fix, but is just a natural result of our edge conditions. The best solution I have so far to fix #2823 also causes metrics losses in non-worst-case pictures, so it's unclear if it's an overall improvement. Let me know if you see any actual real-world pictures that still cause artifacts. |
Describe the bug
Encoding adds an artifact at the bottom edge of the image
To Reproduce
Encode this image:
Expected behavior
Pixels on the left side of the last line should all be white.
Required Information
Rust 1.55. x86-64 macOS 11.6. NASM version 2.15.05 compiled on Aug 29 2020. rav1e 0.5.0-beta.2
The text was updated successfully, but these errors were encountered: