[FFmpeg-devel] [PATCH 27/28] fixed: wrong fps for rmvb files (patch by taxigps)

Vladimir Pantelic pan
Thu Jul 1 09:39:55 CEST 2010

Kostya Shishkov wrote:

>>  so these values are there (r->next_pts, r->cur_pts), just not used for
>>  timestamps it seems
> Those values are not _packet_ information (32-bit timestamp there),
> they are extracted from frame header (and, obviously, only 13 bits long).
> As I've mentioned in my previous mail to this thread, FFmbc extracts
> them from codec data and uses for PTS, should we do the same?

opps, missed your comment. yes, I guess a parser that looks into the
frame header is a good solution.

More information about the ffmpeg-devel mailing list