flossy83

Got it, thank you.

Alright, I've had a play around with it and can see the aliased frames you're talking about like this one:  In my opinion these individual aliased frames appear to...

Another thing is TFM is comparing fields for similarity and the top and bottom fields might actually have more similarity when the frame is aliased like that, resulting in a...

> it may well be the case that this is just baked in and that's how it is You can check it by looking at the raw frames with just...

>the only idea I've had so far is to look at the resulting frame after field matching and do a FieldDiff() and if the 2 fields are so similar within...

Seem to have hit a dead end, because `compareFieldsSlow2_core` only tells us which field is the better match out of two possible matches. It doesn't give a metric like "both...

Oh also there's a black row of pixels flashing at the bottom of frame which is artificially making the previous frame an even worse match - can avoid it with...

Just to update I am still working on this issue daily and have made some small progress - the FieldDiff value is still useful in that I can scale it...

> what I feel would be really useful is if TFM had some way of detecting these (which I think is what you're still working on?) which was able to...