[Ffmpeg-devel] Re: [PATCH] PKT_FLAG_B

[Baptiste Coudurier]

Hi

Michael Niedermayer wrote:
>> [...]
>>
>> Basically what I would like to access the frame type explicitly for GXF
>> muxer, and for MOV muxer, to write or not 'ctts' atom. Like I said,
>> having access to AVCodecParser might be a good solution too.
> 
> hmm iam still not completely sure what you propose ...
> but a muxer must use the timestamps given to it, if they are wrong than
> they are, its not the muxers job to second guess them
> 
> if for example pts are wrong for x264 b pyramid and xvid then these
> encoders / wrapers must be fixed, if they are wrong in the source
> then the source should be fixed, maybe with some generic pts
> recalculation like -genpts ...

Well, generic pts recalculation is indeed a good solution. It is also
actually needed when doing AVI->MOV, or raw h264->MOV. Maybe
AVTimestampFilter, automatically activated for formats which does not
contain pts ?

In GXF muxer, we would still reside on the fact that pts/dts are correct
though, to assume B frame type, a bit weird IMHO.

Also why isn't AVCodecParser/AVBitstreamFilter linked to AVCodecContext
? I was thinking about automatically activating an AVBistreamFilter in
codec was h264 in MOV muxer.

-- 
Baptiste COUDURIER                              GnuPG Key Id: 0x5C1ABAAA
SMARTJOG S.A.                                    http://www.smartjog.com
Key fingerprint                 8D77134D20CC9220201FC5DB0AC9325C5C1ABAAA
Phone: +33 1 49966312