[FFmpeg-devel] release status

[Robert Swain]

2009/3/1 Michael Niedermayer <michaelni at gmx.at>:
> On Sun, Mar 01, 2009 at 08:58:23PM +0000, Robert Swain wrote:
>> 2009/3/1 Michael Niedermayer <michaelni at gmx.at>:
>> > On Sun, Mar 01, 2009 at 07:48:04PM +0000, Robert Swain wrote:
>> >> 2009/3/1 Michael Niedermayer <michaelni at gmx.at>:
>> >> > On Sun, Mar 01, 2009 at 07:10:59PM +0100, Diego Biurrun wrote:
>> >> >> There has been a flurry of activity during the past days. ?I must admit
>> >> >> I have lost track of current issues. ?So, are there any regression fixes
>> >> >> pending or any regressions or nasty new bugs that need to be addressed?
>> >> >>
>> >> >> Does HEAD compile and pass regression tests on all OSes and CPU
>> >> >> architectures? ?FATE looks reasonably green right now but I would
>> >> >> like to hear more explicit OKs from you as well.
>> >> >
>> >> > The sooner we release the sooner we are back to normal development
>> >> >
>> >> > if you ask about outstanding issues, well
>> >> > * h264 timestamps still have a heap of issues but less than 2 weeks ago, i
>> >> > ?suspect they could be fixed in 1-2 weeks if ivan works hard on them but it
>> >> > ?could take longer
>> >>
>> >> But are there any regressions versus before all this timestamp stuff kicked off?
>> >
>> > It wasnt working before
>> > If you ask me if the random timestamps where by luck sometimes correct and
>> > that by more luck they are wrong in that case now, well iam not aware of a
>> > specific case but i did not search for one either (it was said, you dont have
>> > to work for the release just dont be in its way ...)
>>
>> OK, so these changes have been improvements, good. I wasn't aware
>> things were significantly broken before and just had the impression
>> that you were trying to clean things up/generalise the implementation.
>
> hehe, no h264 timestamps where random, they still are in many cases,
> theres a reason why vsync is disabled on many conformance tests on fate ...

https://lists.mplayerhq.hu/pipermail/ffmpeg-user/2009-March/019303.html

It seems people are experiencing frame rate problems on h.264 files. I
knew I had a bad feeling about timestamp and frame rate code being
altered before a release. :(

I was confident in the current code not having caused regressions
after what you said earlier but now I'm not. I think we may have to
resort to creating a branch for the release and fixing up the code to
be release-worthy (i.e. no regressions).

Regards,
Rob