Feature request: maximum duration for motion capture events

jtodd
jtodd
in SecuritySpy

I'd like to request a feature to have a "maximum duration" on motion capture events.

Why? Sometimes things like spider webs trigger continual motion, and then I end up with a single file event that is many hours long. Or when workers are in a spot continuously, creating single events that last a whole day. While I understand that the motion implies that there should be a capture, I think it is reasonable to say that a single motion event has a maximum duration otherwise trying to view a multi-hour long stream gets a bit tedious. Also problematic are file sizes for things like automatic backups - multi-gig files are hard to digest. This can be an optional setting, so the existing behavior can be retained by not specifying a duration.

Comments

  • Ben
    Ben

    Thanks for the suggestion, I can see that such a feature would make large files more manageable, I'll see what we can do in a future update.

Categories