You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The target belongs to the metric, not to the search
A quality search on a machine without libvmaf recommended the bottom of
the CRF range on every file and reported the target as never reached.
The settings said VMAF >= 95. The FFmpeg in use had no libvmaf, so the
search quietly measured with SSIM instead — and kept the 95. SSIM counts
to 1.0. Every probe read below target, the bisection walked to the bottom
of the range and recommended it, file after file, for a reason nothing on
screen explained. The ordinary Windows 'essentials' FFmpeg build has no
libvmaf, so this was the common case, not the exotic one.
A number outside a metric's own range is no longer treated as a target:
the metric's default is used instead, in the search, in the Quality tab
and in loaded presets. The tab no longer selects a metric this build
cannot compute and says why when it substitutes; a search that has to
substitute reports it in its progress and in its result. And a search that
reaches nothing now names what it did reach, rather than leaving the
unreachable number unstated.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01QdAC2Zh8ccUhNm5zyQjsCw
0 commit comments