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
if you have an overrides file for TFM and you override combed frame detection : 500,530 - 650,675 +
this works fine in modes 0-6, and all those frames will be "clean frame (forced)" or "combed frame (forced)", but not in mode 7. in mode 7 it ignores these instructions and just goes with the standard detection, unless you also override a field match 500,530 - 520 p 650,675 + 660 c
this will result in "clean frame (forced)" on frame 520 and "combed frame (forced)" on frame 660 but the other frames will not follow the overrides
so you can work around the problem of a range of frames being incorrectly detected by also manually overriding the field matches with whatever it matched anyway, or by changing the MI value for a range of frames, but it would be simpler if this could behave as expected!
The text was updated successfully, but these errors were encountered:
I've just realised this is also the case in all modes when micmatching happens - a micmatched frame can't have the combed flag overridden without also overriding the match itself
if you have an overrides file for TFM and you override combed frame detection :
500,530 -
650,675 +
this works fine in modes 0-6, and all those frames will be "clean frame (forced)" or "combed frame (forced)", but not in mode 7. in mode 7 it ignores these instructions and just goes with the standard detection, unless you also override a field match
500,530 -
520 p
650,675 +
660 c
this will result in "clean frame (forced)" on frame 520 and "combed frame (forced)" on frame 660 but the other frames will not follow the overrides
so you can work around the problem of a range of frames being incorrectly detected by also manually overriding the field matches with whatever it matched anyway, or by changing the MI value for a range of frames, but it would be simpler if this could behave as expected!
The text was updated successfully, but these errors were encountered: