machinery icon indicating copy to clipboard operation
machinery copied to clipboard

Motion Detection - Record N seconds before motion and stop N seconds after motion

Open n3fariox opened this issue 6 years ago • 11 comments

Motion detection currently only records N seconds after motion is detected.

Would be amazing to be able to be able to include N seconds before the motion event occurred, and stop recording after N seconds of no motion, to catch the surrounding footage.

n3fariox avatar Mar 17 '18 00:03 n3fariox

Lol. Hillarious.

"Back to the future..."

You do understand that it means that the device should know in advance what will happen in the future right ?

Le sam. 17 mars 2018 à 01:27, n3fariox [email protected] a écrit :

Motion detection currently only records N seconds after motion is detected.

Would be amazing to be able to be able to include N seconds before the motion event occurred, and stop recording after N seconds of no motion, to catch the surrounding footage.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/kerberos-io/machinery/issues/137, or mute the thread https://github.com/notifications/unsubscribe-auth/ACFEN4laqoqR24C2Hpc8IFAsnGcM7urLks5tfFhbgaJpZM4Sul-6 .

Orabig avatar Mar 17 '18 07:03 Orabig

hey @n3fariox @Orabig, well one way to solve this is to continuously save a buffer of the n last images in memory. Once motion is detected your start recording video, and you prepend the buffer.

@n3fariox I have been thinking about this but didn't found the time to implement something sufficient (good video quality). I'll keep this thread open, and close it once I got an appropriate solution.

cedricve avatar Mar 17 '18 08:03 cedricve

I'm afraid that keeping a buffer of N seconds of (undoubtely uncompressed) images would need much more memory than the Raspberry has. :( I'm rather pessimistic about the feasability of this feature

2018-03-17 9:18 GMT+01:00 Cédric Verstraeten [email protected]:

hey @n3fariox https://github.com/n3fariox @Orabig https://github.com/orabig, well one way to solve this is to continuously save a buffer of the n last images in memory. Once motion is detected your start recording video, and you prepend the buffer.

@n3fariox https://github.com/n3fariox I have been thinking about this but didn't found the time to implement something sufficient. I'll keep this thread open, and close it once I got an appropriate solution.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/kerberos-io/machinery/issues/137#issuecomment-373903165, or mute the thread https://github.com/notifications/unsubscribe-auth/ACFEN6kMszEjbMQhx-TBl-3OgW4nrkNZks5tfMbLgaJpZM4Sul-6 .

Orabig avatar Mar 18 '18 08:03 Orabig

@cedricve Thanks for the consideration. @Orabig :

  1. I have 4 Amcrest cameras and they all support up to 5 seconds of pre-event recording when using on-board motion detection, and I'm pretty sure they're more resource constrained than Raspberri Pi's. tinyCam Monitor on Android even supports up to 10s of past recording.
  2. You support many more distribution options than Raspberri Pi's. I'm currently running this via docker on an 8-core AMD build with 32GB of RAM.
  3. This is an optional feature. You could opt not to buffer the past to save the RAM.

n3fariox avatar Mar 18 '18 09:03 n3fariox

Ok, I apologize about my lack of knowledge about point 2. You made the point. My bad

2018-03-18 10:59 GMT+01:00 n3fariox [email protected]:

@cedricve https://github.com/cedricve Thanks for the consideration. @Orabig https://github.com/orabig :

  1. I have 4 Amcrest cameras and they all support up to 5 seconds of pre-event recording when using on-board motion detection, and I'm pretty sure they're more resource constrained than Raspberri Pi's. tinyCam Monitor on Android even supports up to 10s of past recording.
  2. You support many more distribution options than Raspberri Pi's. I'm currently running this via docker on an 8-core AMD build with 32GB of RAM.
  3. This is an optional feature. You could opt not to buffer the past to save the RAM.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/kerberos-io/machinery/issues/137#issuecomment-373985756, or mute the thread https://github.com/notifications/unsubscribe-auth/ACFEN8knWRPV0K7XjR0JI5JznWUnboH_ks5tfi_3gaJpZM4Sul-6 .

Orabig avatar Mar 18 '18 10:03 Orabig

This would be an infinitely valuable addition to the system for me, and would allow me to switch to Kerberos as my primary camera solution.

shrimpza avatar May 29 '18 09:05 shrimpza

Indeed we'll definitely do it. I just need to find to implement it or need someone else's help.

cedricve avatar May 29 '18 11:05 cedricve

Cross-linking with matching FeatHub suggestion: Add option to record pre and post event frames

bradleywehmeier avatar Jul 27 '18 19:07 bradleywehmeier

+1 for this feature

I've been evaluating a number of linux (Docker) surveillance systems recently and I've been impressed with the simplicity and stability of Kerberos.

The ability to include x seconds of video before a motion event is crucial for me. If this were included in Kerberos (along with object detection / highlighting) then we would have a clear winner.

knaksbrig avatar Sep 10 '18 11:09 knaksbrig

+1 for that Feature :D

CoReYeDe avatar Oct 29 '18 16:10 CoReYeDe

Another +1 for this feature. This would be awesome.

jruth85 avatar Dec 08 '18 19:12 jruth85