Walking behind obstacles creates multiple clips

[milhouse6]

A single trigger moving behind fixed obstructions, like a person walking behind porch posts, creates multiple clips and triggers multiple consecutive alarms. Any way to avoid this?

Kind thanks!

[Devin]

Hi milhouse6,

Depending on your scene you may be able to reduce or eliminate these false detections by setting a time for the "Include objects visible longer than: ___seconds" option in the rule editor. I'd recommend starting with one second and play around with different durations to see if you can reach the desired result.

If you could provide a screen shot with an example of the false triggers I may be able to provide other suggestions.

Regards,

-Devin

[milhouse6]

Thanks Devin,

I've played with that previously. All that ended up happening was the elimination of clips I want. I guess this is a feature request:
- 'include X seconds before clip'
- 'include X seconds after clip'
- 'merge clips from the same camera with overlapping timestamps'

Does this make sense?

[Devin]

Hi milhouse6,

Thanks for the feature requests, I'll add them to our list.

I may be able to give other suggestions of you could send a screenshot of the false triggers you are seeing.

Regards,

-Devin

[habari]

I have an interest in this as well. In my mind, the issue is concatenation of events that occur within a target field within a certain time frame. So, if a person crosses behind a barrier and reappears moments later within the same field of view, that should be treated as a single event and not generate two clips or two triggers. To increase the duration that a target has to be visible eliminates useful data by ignoring a brief appearance before or after the barrier, the opposite of what security software should do.

[flynreelow]

This is exactly the question I was going to post to the boards. There is no reason why these clips should be broken up into 2, if something is just crossing a beam, post, etc.

Let me know what you guys figure out to get this "merged" to 1 single clip, instead of 2.

edit...


Tried to upload a screenshot (256 kb max?) Really?

[milhouse6]

This is one of the issues preventing me from renewing (and referring) for now. Another is the inability to "teach" false positives (tree limbs blowing in the wind, squirrels, passing headlight reflections etc), and the last is the inability to watch a clip at full screen (and/or zoom) on Windows without exporting the clip.

It's such a tease to have such an almost perfect piece of software.

[Semper Vaporo]

I had a similar problem with a tree that was in the middle of my front yard and split the scene in two. Mother nature eliminated the problem by removing the majority of the tree for me (I had to pay someone to finish the job), but I realize not everyone can rely on that. Prior to that I decided which side of the tree was of most importance and set the rule to have a bounding box on that side of the tree. (I didn't care about what happened on the other side... or at least I pretended I didn't!)

I have another scene that has a neighbor's bush that sometimes, when shaking in the wind, was interpreted as a 'person'. (Ma Nature took it out too, but the neighbor put another in its place!) So I created a really odd shaped bounding box that skirted the bush (basically a rectangle with a keyhole shape that comes in from the side closest to the bush and goes around the bush. (Bounding boxes do not have to have only 4 "corners", you can create new points by clicking on an edge between the white dots, then drag them to create complex/bazaar shapes to fit the need.)

Sometimes I have had to get really creative to reduce the false positives or multiple-alerts on what was really "one event". Thankfully, SH has lots of ways to be creative with the rules.

[Devin]

Hi milhouse6,

If you could send us a screenshot or video of a false detection we may be able to offer advice on how to reduce or eliminate them. If you prefer to not share images of your scene over the forums you can also email me at [email protected]

Regards,

-Devin

[flynreelow]

I just emailed [email protected] .....