Re: [Motion-user] creating avi goes wrong.

[Marcel J.E. M. <ma...@me...>]

On Mon, Aug 22, 2005 at 08:51:29PM +0200, Kenneth Lavrsen wrote:
> 
> >Hm, I recompiled from the 3.2.3 source and now it works fine.
> >Guess something has gone wrong when building the rpm.
> >
> >-Marcel
> 
> I have a pretty good idea what the problem is.
> 
> ffmpeg has changed API twice the last 3 months. Motion RPM is built to a 
> specific version of ffmpeg.
> 
> ffmpeg-0.4.9-0.lvn.0.15.20050427.4.i386.rpm and 
> ffmpeg-devel-0.4.9-0.lvn.0.15.20050427.4.i386.rpm
> 
> If you do not install the same or some that are compatible Motion will fail 
> to work with ffmpeg.
> 
> The solution is then either:
> To install the same version as I have used.
> Or rebuild the RPM.
> 
> This is done by downloading the SOURCE rpm instead of the normal rpm. I 
> uploaded that the same evening I uploaded the deb package.
> 
> http://prdownloads.sourceforge.net/motion/motion-3.2.3-1.src.rpm?download
> 
> To rebuild it you simpy run
> 
> rpmbuild --rebuild motion-3.2.3-1.src.rpm
> 
> You will need the same development packages as when you build from sources! 
> You probably have the binary libraries but you also need the header files 
> and they are in the xxx-devel packages.
> 
> glibc and glibc-devel, libjpeg and libjpeg-devel, zlib and zlib-devel, 
> ffmpeg and ffmpeg-devel, mysql and mysql-devel, postgresql-libs and 
> postgresql-devel.
> 
> The rebuild command in reality compiles Motion from sources and make your 
> own motion rpm. And you can then install this rpm. Because you compile it 
> yourself the Motion code will be built to the API in the ffmpeg version you 
> have.
> 
> The best is to build from real sources because then you get all the CPU 
> architecture specific optimizations as well.
> 
> Kenneth

Kenneth,

I actually have ffmpeg-0.4.9-0.2.20050427.2.fc4 (from freshrpms) installed.
And recompiled using the its companion devel package.
Maybe I was a bit unclear but (using the motion rpm) the movies are actually
created expect the filename always is '.avi'. A hidden file in the current 
directory. It looks as if the target_dir and ffmpeg_filename are not taken
into account somehow.
After recompiling from source it worked fine...

-Marcel