From: Janich R. <ja...@gm...> - 2006-02-21 15:58:34
|
Hi. I've used motion for about a month now (3.2.3) and wants to upgrade to 3.2.= 4 . Mainly because this version doesnt halt if connection to cameras isnt present at startup. But, Ive got problems with 3.2.4. Looks like this dudes problem: http://sourceforge.net/mailarchive/forum.php?thread_id=3D9460846&forum_id= =3D45090 Snippet of results with 'motion -n -d 2' (notice the .avi): [1] File of type 8 saved to: .avi [1] File of type 1 saved to: /mnt/cam/3/image/2006/02/21/14/1353-00.jpg [1] File of type 1 saved to: /mnt/cam/3/image/2006/02/21/14/1353-01.jpg This happens with any of these combinations: - motion-3.2.4-1.i386.rpm - ffmpeg (any rpms & rebuilded src rpms) - motion-3.2.4-1.src.rpm - ffmpeg (any rpms & rebuilded src rpms) In the light of my nearcomming desperation, I tried fetching the source instead. So, 3.2.4 doesnt work, but I got it running again with the appropriate path= s in 3.2.4_snap5. (./configure && make && make install) And one other thing, I even tried rebuilding with a --target=3Dpentium3, an= d to my surprise it actually worked after a 'rpm -ivh --ignorearch'!! Snippet of results with 'motion -n -d 2' (notice the .avi) (this is with either 'solution'): [1] File of type 8 saved to: /mnt/cam/3/movie/2006/02/21/143250.avi [1] File of type 1 saved to: /mnt/cam/3/image/2006/02/21/14/3249-00.jpg Now I gets lots(!!!) of these errors instead: [msmpeg4v2 @ 0x978790]warning, clipping 1 dct coefficients to -127..127 (found some info here: http://www.lavrsen.dk/twiki/bin/view/Motion/KnownProblems) [1] vid_return_code 6 (this goes for all 4 cameras, cant find any usefull info) Cant find any explanation. Works with Livna ffmpeg rpm & custom rebuilded rpm targetted at pentium3, forced into an AMD Athlon(tm) XP 2600+. :D -- Janich Rasmussen, Ja...@gm... && Krudtting.dk |