[Ffmpeg-devel] [BUG] seeking crash in x264 with b_pyramid

[Måns Rullgård]

Nico Sabbi <nicola_sabbi at fastwebnet.it> writes:

> M?ns Rullg?rd wrote:
>
>>Erik Slagter <erik at slagter.name> writes:
>>
>>
>>
>>>I also have issues, but not related to b_pyramid. For instance, mplayer
>>>(very latest CVS) plays raw h264 files double speed,
>>>
>>>
>>
>> How does mplayer read raw H.264?
>>
>
> it has its own demuxer
>
>>For fixed framerate streams, H.264 specifies the field rate, even
>>when using progressive encoding.  There has been some confusion
>>about this in the past, with the result that some codecs take the
>>numbers to mean frame rate for progressive sequences.  Hence the
>>double speed.  This was fixed in lavc and x264 in January.  If
>>mplayer uses its own H.264 "demuxer", or uses an old version of
>>lavc, it would show this problem.
>
> do you mean that when fixed_frame_rate_flag in vui_parameters() is set
> the nominal framerate should be halved?

Yes, if fixed_frame_rate_flag is set the frame rate is
time_scale / (2 * num_units_in_tick).

-- 
M?ns Rullg?rd
mru at inprovide.com