From 7af88dd853bc8b0a1510f0fc95da14fa036854b3 Mon Sep 17 00:00:00 2001 From: motbob Date: Thu, 22 Aug 2024 03:06:15 -0400 Subject: [PATCH] Add paragraph about silent failures (#15) * add paragraph about silent failures * typo --- src/wobbly/failures.md | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) diff --git a/src/wobbly/failures.md b/src/wobbly/failures.md index 1260ffc..00ac2b0 100644 --- a/src/wobbly/failures.md +++ b/src/wobbly/failures.md @@ -119,3 +119,21 @@ that captures just the fade. Wobbly may be able to accurately decimate that for you. If the pattern remains the same, there is no reason to do this. + +## Scenes that are likely to silently fail + +Wobbly is reliant on the metrics it is fed, +and those metrics do not always perform well in scenes +with low-contrast combing or with a very slow pan/zoom. +An example of the former scene is a scene with rain and no other animation. +Depending on what pattern guessing method you used, +Wobbly may not mark these types of scenes as having an ambiguous pattern, +meaning that they will fail silently and you will not know +that there is a problem that you need to fix. +These scenes also usually cannot be caught by looking at combed frames, +high-mic frames, or frames with high dmetrics. +There is no solution to this other than to pay close +attention to those types of scenes when you are QCing your encode. +You need to understand the metrics being used +and use that knowledge to predict failure. +Looking at the metrics in the overlay can assist your understanding. \ No newline at end of file