[MPlayer-dev-eng] [PATCH] new mpeg muxer

[Nico Sabbi]

D Richard Felker III wrote:

>
>i'll explain.
>first of all, this should all be an option that has to be explicitly
>enabled.
>
>now the scenario is you're getting in video at 23.976 or 24 fps.
>i'm not sure of the difference between progressive sequence versus
>progressive frame flags. presumably all of these are set to true by
>the encoder.
>input frames should all have the same field parity set, either tff=1
>or tff=0, not alternating. rff should always be 0.
>
>if any of the above conditions on the input stream fail to hold (i.e.
>you don't really have progressive video suitable for telecine) it's
>probably good to bail out with an error or at least print nasty
>warnings.
>
>now what to do:
>
>replace the fps by 29.97 or 30, respectively.
>alternatively set rff=1 on every second frame.
>keep a running value for tff flag, initializing it with 1 (or the
>value from the first input frame) and alternate it after each time you
>use rff=1, always storing your tff flag in place of the one in the
>source video.
>
>so the final rff and tff flag pattern should come out looking like:
>rff 0101010101010101
>tff 1100110011001100
>(note: you can just keep a counter "mod 4" and use bit-0 as rff, bit-1
>as tff.. :)
>  
>

it's a clear explanation,thank you

>i don't know what to do with the progressive sequence/frame flags.
>billy biggs (vektor on freenode; sometimes he posts to this list) has
>done quite a bit of research on this subject and can probably tell you
>the correct values, as well as all the incorrect ones used on
>countless badly mastered dvds out there... :)
>
>rich
>  
>
reading the specs it seems that when both progressive fields are set
the output consists of double the fields (so even 2 or 3 frames).
I'll ask Billy