View Single Post
Old 19th March 2019, 22:51   #10  |  Link
hello_hello
Registered User
 
Join Date: Mar 2011
Posts: 4,829
Quote:
Originally Posted by domator View Post
Thank you, hello_hello. Your scripts gives a really nice output.
Does it mean it was 24fps converted to 24fps by duplicating fields?
Also does TFM() keep all the fields or does it delete Even (or Odd) fields like many deinterlacers?
I assume it was 24fps originally and simply sped up to 25fps for PAL, if that's what you're asking. AssumeFPS(24000,1001) just slows it down again, but you'll have to apply a slowdown to the audio too. Generally without correcting the pitch, so the sound drops back to it's original pitch when it's slowed down.

TFM is a field matcher. It looks at the fields and tries to match them up for whole frames. It can de-interlace when it detects combing after the field matching, or if the source is really interlaced, but you can field match without any de-interlacing enabled if you want to.

TFM(pp=0)

TFM keeps all the fields for a film source (or 25fps progressive). For your sample I don't think there's any field duplication to speed it up to PAL. For some reason the fields can end up out of alignment though.

Instead of this (top and bottom fields)

A B C D E F
A B C D E F

progressive PAL is often encoded as interlaced and ends up something like this

A B C D E F
B C D E F G

So it looks interlaced but it's not, and TFM simply matches the fields again to output progressive frames. If you de-interlaced with Yadif(mode=1) instead, each frame of the 50fps output would be duplicated. That's why it can be used to check if it's really interlaced, or just foolin'.

When it de-interlaces, TFM de-interlaces to the original frame rate, so yes, for interlaced PAL it'd only output 25fps rather than 50fps.

Last edited by hello_hello; 19th March 2019 at 23:12.
hello_hello is offline   Reply With Quote