- Jul 31, 2015
- 167
- 12
Uh oh! You are flirting with danger on this; sounds like you are trying to record only on motion. What happened is that the pre-record didn't kick in because it probably didn't properly detect motion until after a legitimate motion had occurred.I can't figure out why the clip didn't record earlier. I have pre-record set to 7 seconds. Also, there is a security flood that didn't trigger, Ill have to check that.
Uh oh! You are flirting with danger on this; sounds like you are trying to record only on motion. What happened is that the pre-record didn't kick in because it probably didn't properly detect motion until after a legitimate motion had occurred.
What were you using to record the video?I can't figure out why the clip didn't record earlier. I have pre-record set to 7 seconds. Also, there is a security flood that didn't trigger, Ill have to check that.
It's Blue Iris 4 on my Surface 3 128G 4G wired to my crummy Foscams. My Surface is WiFi though since I don't have the docking station.What were you using to record the video?
You need to disable object detect reject in the motion tab...also, remember that pretrigger is set in frames...so if you want 7 seconds on a 15fps camera it must be set to 105..It's Blue Iris 4 on my Surface 3 128G 4G wired to my crummy Foscams.
You need to disable object detect reject in the motion tab...also, remember that pretrigger is set in frames...so if you want 7 seconds on a 15fps camera it must be set to 105..
Also if you are recording direct to disk, set your cameras iframe interval to match the fps...d2d only begins recording when a full frame is sent.
What is your make time?
In that camera its the key frame...so you have it set right...make the changes in blue iris, if you want 7 seconds in your case it should be set to 70....also dont forget about object detect reject, its very important to disable it.I had it all wrong then, couldn't find iframe interval. Make time is 1 second.
~
Ok, you might want to increase the make time to at least 0.7 otherwise you will get tons of alerts (the object detect was preventing triggers, both false and positive ones (causing you to miss valid motion events))In the second night setting I deselected the object detect/reject. It was on last night.
Thanks Fenderman, I changed the settings as you suggested. I'm also going to install lower watt bulbs instead of the flood and point them down. We need them when getting home after dark.Ok, you might want to increase the make time to at least 0.7 otherwise you will get tons of alerts (the object detect was preventing triggers, both false and positive ones (causing you to miss valid motion events))
Also I would increase the end trigger/break time to at least 15-30 seconds, in both profiles.