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

Quality issue on FSR input to target Res table #19

Open
brunogm0 opened this issue Aug 29, 2021 · 1 comment
Open

Quality issue on FSR input to target Res table #19

brunogm0 opened this issue Aug 29, 2021 · 1 comment

Comments

@brunogm0
Copy link

brunogm0 commented Aug 29, 2021

Hi,
So I've checked the suggested input Res like 1477x831, 1130x635, 1506x847... Do not follow good practice of divisibility by 4 to minimize artifacts from rounding or padding.
One part of the justification comes from 4x4 blocks are standard in processing. Another is padded pixels/edges bleeds spectral energy/noise. Examples integer scaling and/or Wavelet, cosine, haar transform these blocks.

At <=1080p target this is much more important.

For example TRIXX boost skips some non-divisible scales in their config slider.

(In the documents a few Res where badly rounded or off-by-one )

Ps.: at least require mod 2 vertical input (2x2, 2x4 slices)

@brunogm0
Copy link
Author

brunogm0 commented Nov 22, 2021

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

No branches or pull requests

1 participant