SaurusX
8th May 2018, 17:30
I posted this at videohelp, but I wanted to get another take on it in case the eyes are different on this forum.
In the clip below TFM gives some less than desirable results by providing poor field matches. Looking at the calculated mic metrics it's obvious why the field combo (c,n,p,b,or u) is being chosen, but it's wrong much of the time given the resulting "low-res" artifacts. With an override file I can force a good match, which is correct to the eyes and usually a "c" combo (but not always).
I would prefer not to create a huge override file correcting for these frames by forcing a certain match or replacing the current frame with an identical "good" neighbor. Am I missing a processing step here or is the source just bad all around?
TFM code being used:
TFM(slow=2,pp=7,mode=3,mi=70,cthresh=8, ovr="E:\Old Computer Files\Video Editing Tools\MeGUI_2624_x86\avisynth scripts\TMNT2k3\TMNT_xmas.txt")
Usual override command to force good field combo:
13953 c
EXAMPLE CLIP (https://mega.nz/#!hSoiQBDK!ryxw2AOC5PRXJYmCaQ3fsJRjsz4d84vBdD4q4V3Dt1E)
In the clip below TFM gives some less than desirable results by providing poor field matches. Looking at the calculated mic metrics it's obvious why the field combo (c,n,p,b,or u) is being chosen, but it's wrong much of the time given the resulting "low-res" artifacts. With an override file I can force a good match, which is correct to the eyes and usually a "c" combo (but not always).
I would prefer not to create a huge override file correcting for these frames by forcing a certain match or replacing the current frame with an identical "good" neighbor. Am I missing a processing step here or is the source just bad all around?
TFM code being used:
TFM(slow=2,pp=7,mode=3,mi=70,cthresh=8, ovr="E:\Old Computer Files\Video Editing Tools\MeGUI_2624_x86\avisynth scripts\TMNT2k3\TMNT_xmas.txt")
Usual override command to force good field combo:
13953 c
EXAMPLE CLIP (https://mega.nz/#!hSoiQBDK!ryxw2AOC5PRXJYmCaQ3fsJRjsz4d84vBdD4q4V3Dt1E)