[FFmpeg-devel] [PATCH] Fix possible SIGFPEs with bad mov timings. Based on chromium patch 35_mov_bad_timings.patch

Ronald S. Bultje rsbultje
Fri Nov 20 20:07:12 CET 2009


On Fri, Nov 20, 2009 at 1:23 PM, Michael Niedermayer <michaelni at gmx.at> wrote:
>> num is 1 for mov.
> :(

Can we implement a hack or fix or something so that the den is shifted
by one while all timestamps in the file discard their last bit? As
Michael said, if the timebase is this huge, it's not like every single
bit is all that relevant. It'll stay in sync just fine.

IMO this is easily fixed, setting a bogus timebase just because
Google's engineers said so isn't helping. People will just scream that
FfMpEg sUx0rZZZ!!11 (hey, there ya go, yet another search engine hit
for that one!)


More information about the ffmpeg-devel mailing list