[MEncoder-users] Deinterlacing problem

[Rich Felker]

[resending because i accidentally sent to the wrong list to bring it
back on-list.. this is why replying off-list is bad!! :)]

On Thu, Jul 21, 2005 at 06:28:50PM +0200, Grzegorz Nowak wrote:
> Thanks for the quick response!

no problem. but..
PLEASE DO NOT REPLY OFF-LIST!!
PLEASE DO NOT TOP-POST!

> Yes my mistake... thought pal worked the same way just with 25 not 30
> fps.. that's why 50000/1001.. so now it's 50 :)

:)

> Then i forced xvid with -ffourcc XVID... so I could se what was going
> on in the video by opening it with vdub... Is FMP4 really better than
> xvid or divx?

Neither is "better"; it's just more correct. the fourcc is supposed to
identify which encoder produced the video. in the past lavc
masqueraded as 'DIVX' to get popular windows crap to play its files,
but that caused problems if advanced mpeg4 features not supported by
divx were used during encoding, so now that everyone has ffdshow
anyway we decided to use a correct fourcc.

> The result was, that mencoder switches the wrong
> fields... that means.. If the correct image order is a b c d ... then
> my result is b a d c... that's why it seams it's jumping.. it's not
> bobbing.. it's just the wrong "order" or what is the correct word?

OK, I see. tfields should auto-detect the field order as long as it's
the first filter in the chain, but it might fail to do so for dv (this
is a bug in the dv decoder, not tfields, if it fails to indicate the
field order). try using -vf flip,tfields=4,flip and see if that fixes
the problem. it will be slower to encode, but it should work.

Rich