So here comes the next test build
This will probably be the last Excel sheet style test build. The options are as follows:
1) "resolution": The resolution in which madVR does motion vector search. Resolution "2" has 4 times more pixels than resolution "1". So it probably also costs 4x as much speed. Consequently, I'd prefer to pick resolution "1", which is also what all the recent test builds used. But I'll let you test resolution "2", just to be sure we're not missing a potentially dramatic quality improvement.
2) "search distance": The max supported motion vector distance. In theory higher should be better because it will detect motion better in very high motion scenes. However, supporting larger motion vectors also means a higher chance to detect a false positive motion vector. So this might not be as clear cut as it seems. A big problem with testing is that supporting a large search distance will only help with those few video samples which really have such large motion vectors, while it might harm a little bit in all other video samples. Generally, I tend to prefer going as large as possible here, though. Unless it comes with a significant quality loss.
3) "block size": The area around each pixel which is compared to find a matching motion vector. In theory going large here is "good" because it helps reject false positives better. However, if there's a small object moving around, we might not detect the movement properly if we require too large a neighborhood of pixels to match. So going too large will also hurt in some cases. So we need to find the best compromise.
Both search distance and block size also depend on the resolution. For example, both block size and search distance must be doubled if we double the resolution, to achieve the same effect. So for the bigger resolution, probably we also need to use bigger search distance and block size, which again costs more speed. One more reason to pick the lower resolution, if it's possible without losing too much quality.
FYI, the setting "resolution: 1, search dist: 2, block size: 3" should produce the same results as the previous test build at 35%. So you don't need to retest "resolution: 1, search dist: 2, block size: 3", you can just copy the numbers.
P.S: We already tried testing some of this a while ago, but it was before we have the "threshold" logic in the Excel sheet, and Neo's and Fer's results heavily contradicted each other. So I'm hoping this time around with the increased number of test scenes, and the "threshold" logic in the Excel sheet, we'll get more conclusive results.