On Sun, Nov 4, 2012 at 12:54 PM, gregor herrmann <[email protected]> wrote: > Control: tag -1 + moreinfo > > On Sat, 20 Oct 2012 23:21:37 -0400, H. S. wrote: > >> Earlier (till yesterday, part of the output included something like: >> Oct 18 09:40:28 red motion: [0] ffmpeg LIBAVCODEC_BUILD 3482368 >> LIBAVFORMAT_BUILD 3478784 >> >> That line is missing from the console output now (and also from the one >> I quoted above). I believe this is due to my recent Debian updates. Apt >> log shows the following changes since last night which may be related >> to this problem: >> [UPGRADE] ffmpeg:amd64 7:0.11.1-dmo5 -> 7:1.0-dmo1 >> [UPGRADE] gstreamer0.10-ffmpeg:amd64 0.10.13-5 -> 1:0.10.13-dmo1 >> [UPGRADE] libxine2-ffmpeg:amd64 1.2.2-4 -> 1:1.2.2-dmo3 >> [UPGRADE] libavcodec54:amd64 7:0.11.1-dmo5 -> 7:1.0-dmo1 >> [UPGRADE] libavdevice54:amd64 7:0.11.1-dmo5 -> 7:1.0-dmo1 >> [UPGRADE] libavformat54:amd64 7:0.11.1-dmo5 -> 7:1.0-dmo1 >> [UPGRADE] libavutil51:amd64 7:0.11.1-dmo5 -> 7:1.0-dmo1 > > > -dmoN means that you are using packages from deb-multimedia.org. > Do you have the same problem when you use the packages from Debian > proper? >
Just reinstalled my whole system. On this newly installed and updated wheezy system, motion doesn't even start capturing properly! I am using the same conf file I was using till several days ago when it was working fine. Now when I start motion, it just spits out the initialization lines on the prompt and then does nothing at all. With the above dmo1 packages it was at least capturing some image, albeit at a much slower rate. Thanks. -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
