Motion - Bug Report 2005x 06x 23x 065932

BUG: Motion will not run with ffmpeg 0.4.9pre1 CVS build from at least 20050517 and on.

BUG: Motion will not run with ffmpeg 0.4.9pre1 CVS builds from at least 20050517 and on.

The ffmpeg guys have changed the API again on the CVS version of ffmpeg.

The problem is that we have these two lines in ffmpeg.c

c->frame_rate = rate;
c->frame_rate_base = 1;

It seems that the ffmpeg guys has changed the API again. And now removed the two from the AVCodecContext structure.

So here we go again. More complications. We have users with ffmpegs with the old API and the new API. Let me express that I am SICK AND TIRED of the ffmpeg project. Why can't they do proper formal releases like any other decent project so we know what the user base is having installed. They have been on this rediculous 0.4.9pre1 since last year and never released anything. So all the debs and RPMs are from misc CVS snap shots. It is completely out of control.

For now please make sure you install an ffmpeg version from before 17 of May 2005.

You can look in avicodec.h (normally in /usr/include/ffmpeg) and the line


The build 4753 or earlier is OK. 4754 is not OK.

For Fedora core 4 I can say that ffmpeg-0.4.9-0.lvn.0.15.20050427.4 is OK.

Test case


Motion version: 3.2.1
ffmpeg version: cvs20050517
Shared libraries: ffmpeg, mysql, postgresql
Server OS:  

-- KennethLavrsen - 23 Jun 2005

Follow up

Fix record

PerJonsson fixed this. The fix is available in 3.2.2_snap4 and forward

BugReportForm edit

TopicTitle Motion will not run with ffmpeg 0.4.9pre1 CVS build from at least 20050517 and on.
BugStatus Released
AssignedBugTo KennethLavrsen
SubmittedBy KennethLavrsen
Topic revision: r2 - 11 Jul 2005, KennethLavrsen
Copyright © 1999-2024 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Please do not email Kenneth for support questions (read why). Use the Support Requests page or join the Mailing List.
This website only use harmless session cookies. See Cookie Policy for details. By using this website you accept the use of these cookies.