Feature Request: Wait before capture

Description

On startup motion directly start to capture frames and doing things like writing to a database.

Somehow my bttv card needs a litlle time to stabilise after system boot or after restarting motion. The first images coming from motion are white, or distorted or from the wrong input.

It would be nice if there's an option what makes motion to hold on capture for x seconds or x frames. Say a warmup period...

Also I like to thank you all for this great product!

-- WillemSpaans - 11 Mar 2009

Follow up

Motion already sleep for 2 seconds and/or try to capture 5 frames to let settle device ... nobody had any problem with that ... maybe

your capture card or your cameras has something bad. Please describe your hardware / motion config.

-- AngelCarpintero - 15 Mar 2009

Comments

I'm actually having this problem with all my SAA7134 cards - I get 1 or 2 video inputs out of 8 creating an initial event of some noise and then the camera stabilizing.

It would be great if motion could sleep for a little longer.

-- RomanGaufman - 18 Mar 2009

---

Angel,

Seems like the problem solved. I use Ubuntu 8.10 and installed motion with synaptic.

I took the latest source and compiled this. Now motion works perfect on restarts. Problem was probaly the old version in synaptic.

-- WillemSpaans - 18 Mar 2009

---

Well, I get this with r442 on all my DVRs with SAA7134 based cards. I generally just ignore it but it would be nice if motion waited a little longer initially.

-- RomanGaufman - 19 Mar 2009

---

Roman , did you have same issue when you restart motion ... it has 5 seconds .

-- AngelCarpintero - 19 Mar 2009

---

Yes, it looks like this: http://hackeron.dyndns.org/falseevent.mp4

-- RomanGaufman - 19 Mar 2009

---

Roman , try to increase in motion.c time of SLEEP after restart and try to restart motion, but looks strange that your card needs

so much time ... 4 or 8 inputs ?

motion.c - around Line 2510

SLEEP(5, 0); // maybe some cameras needs less time

-- AngelCarpintero - 22 Mar 2009

---

News ??!

-- AngelCarpintero - 09 Jul 2009

---

Ah, sorry, the problem was my workaround for the herringbone pattern (which is still an issue btw).

When you open an saa7134 device, sometimes it opens fine and sometimes there is a herringbone pattern over the image.

Running v4lctl -c /dev/video0 setnorm $norm at start solves this but causes motion to record an event - Maybe motion should set the norm at start to work around this herringbone problem?

-- RomanGaufman - 26 Aug 2009

---

"It would be nice if there's an option what makes motion to hold on capture for x seconds or x frames. Say a warmup period... "

I do like that request too.

The solutions sugested earlyer ( http://www.lavrsen.dk/foswiki/bin/view/Motion/FeatureRequest2006x04x08x080625 ) is not the ideal solution.

If you try to pause detection to fast that would fail for the reason that motion has not yet completet setting up everything. If waiting just a little to long you still get a event triggered until detection get's paused.

-- TheOtherBug - 02 Sep 2009

---