builtin.conf: enable antiringing in high quality profile
General consensus is that ortho scalers antiring while fast is not that good, let's use it in high-quality profile only.
This commit is contained in:
1 parent
7858e1fdaf
commit
6e54aa328d
2 files changed
+8
-4
No files matched your search
@@ -5871,12 +5871,15 @@ them.
|
||||
being increased a bit).
|
||||
|
||||
``--scale-antiring=<value>``, ``--cscale-antiring=<value>``, ``--dscale-antiring=<value>``, ``--tscale-antiring=<value>``
|
||||
Set the antiringing strength. This tries to eliminate ringing, but can
|
||||
introduce other artifacts in the process. Must be a float number between
|
||||
0.0 and 1.0. The default value of 0.0 disables antiringing entirely.
|
||||
Set the antiringing strength. This option tries to eliminate ringing, but can
|
||||
introduce other artifacts in the process. The value must be a floating-point
|
||||
number between 0.0 and 1.0.
|
||||
|
||||
The default is 0.0. The ``high-quality`` profile sets this to 0.6, which is
|
||||
a fairly conservative value and should subtly enhance image quality.
|
||||
|
||||
Note that this doesn't affect the special filters ``bilinear`` and
|
||||
``bicubic_fast``, nor does it affect any polar (EWA) scalers.
|
||||
``bicubic_fast``, nor does it affect any polar (EWA) scalers with vo_gpu.
|
||||
|
||||
On ``--vo=gpu-next``, this also affects polar (EWA) scalers. Certain
|
||||
filter aliases may also implicitly enable antiringing, regardless of this
|
||||
|
||||
@@ -53,6 +53,7 @@ allow-delayed-peak-detect=yes
|
||||
|
||||
[high-quality]
|
||||
scale=ewa_lanczossharp
|
||||
scale-antiring=0.6
|
||||
hdr-peak-percentile=99.995
|
||||
hdr-contrast-recovery=0.30
|
||||
|
||||
|
||||
Reference in new issue
Block a user