Katie Boundary
11th March 2025, 16:41
I've always wondered why TFM bothers with including modes other than 0. I've always set it to 0 to save a few CPU cycles and reduce the chances of an incorrect match.
I tried ripping and converting "Due South" yesterday, only to find that TFM at my preferred settings was having difficulty with finding proper matches for most fields. Suspecting that it might have been shot at true 60 hz, I tried bob(), which revealed nonlinear field behavior. Suspecting a field order error, I tried complementparity().bob(), but that didn't fix it. On a hunch, I tried setting TFM to Mode 1, and lo and behold, progressive film frames magically appeared. It just turned out to be one of those whack telecine jobs done by people on PCP.
I think that mentioning this sort of use case in the TFM documentation would be more helpful than just "increases your chances of finding a match if one exists".
I tried ripping and converting "Due South" yesterday, only to find that TFM at my preferred settings was having difficulty with finding proper matches for most fields. Suspecting that it might have been shot at true 60 hz, I tried bob(), which revealed nonlinear field behavior. Suspecting a field order error, I tried complementparity().bob(), but that didn't fix it. On a hunch, I tried setting TFM to Mode 1, and lo and behold, progressive film frames magically appeared. It just turned out to be one of those whack telecine jobs done by people on PCP.
I think that mentioning this sort of use case in the TFM documentation would be more helpful than just "increases your chances of finding a match if one exists".