----- Original Message ----- > From: "Bob McGowan" <bob_mcgo...@symantec.com> > > On 9/25/14, 7:12 AM, "Rob Owens" <row...@ptd.net> wrote: > > >I tested 'motion' on Wheezy yesterday. It detects motion and takes still > >shots, but it is not creating movies out of the still shots. > > > >I have set: > > > ># Use ffmpeg to encode mpeg movies in realtime (default: off) > >ffmpeg_cap_new on > > > >and > > > ># Gap is the seconds of no motion detection that triggers the end of an > >event > ># An event is defined as a series of motion images taken within a short > >timeframe. > ># Recommended value is 60 seconds (Default). The value 0 is allowed and > >disables > ># events causing all Motion to be written to one single mpeg file and no > >pre_capture. > >gap 60 > > > >Can anybody confirm that movie output works on Wheezy? > > > >One thing that may be a factor in my case is that my test webcam is very > >slow. I am only getting one picture every 2 or 3 seconds when motion is > >detected. I have framerate set to 2 fps. Maybe motion is aware that my > >pics are too far apart in time and is deciding not to combine them into a > >movie. > > > >-Rob > > > > I should have added a caveat to my original response, I hadn't actually > tried it, since my needs pointed me to a more feature full system. > > > Looking at the 'gap' description, I wonder if you need to set it to '0' in > order to get a movie? >
You made me re-read the gap description, and I think the solution for me might actually be to increase the gap (although I will try zero as well). Currently, each of my pictures is about 2 minutes apart due to slowness of my webcam. With the gap set at 60 seconds, each picture would be its own event so there would be no need to create a movie. I will try this tonight. Thanks for the response. -Rob -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/395458369.3840753.1411664744282.javamail.zim...@ptd.net
