To Amcrest: Suggestions for Improving Motion Detection Algorithm

[maxbraketorque]

Dear Amcrest,

Your camera seems pretty nice, and your firmware has some nice features, but the motion detection algorithm is far too simplistic. I think you would make so many people happy if you could add the following features to your motion detection algorithm:

1) Add an "Upper Threshold Limit" setting. This feature would prevent an event from being triggered if too many detection blocks (I think you call them pixels) are simultaneously activated. This could be used to prevent false triggers from things like lights being turned off/on, snow, or other events that have the potential to activate a large number of pixels simultaneously. This setting would be a percentage value just like the existing Threshold. The existing Threshold would be renamed to "Minimum Threshold".

2) Add a "Movement Time" setting. This would be the amount of time for the percentage of activated detection blocks above the "Threshold" (or within the Threshold range if you add my suggested "Upper Threshold Limit" feature) that is required for an event to be triggered. This would allow eliminating false trigger events from things like lights being turned off/on, leaves occasionally rustling, image noise, etc. This setting would range from 0 to perhaps 100 seconds.

3) Add a "Block Neighbor Distance" setting. This would set the max distance between activated blocks where a Threshold judgement can be applied. This would prevent simultaneously activated blocks far from each other from being able to count towards the Threshold stage of detection. This setting would have a range from 0 to 28. 28 is currently the number of detection blocks across the diagonal at least for the IP3M-943.

4) Make your detection blocks smaller. This would be helpful for detecting motion at a distance.

I think Items #1 and #2 would be of the most benefit, but #3 and #4 would also be great to have.

On a side-note, the name "Anti-Dither" makes no sense to most people. How about renaming it to something like "Inactivity Reset Time"? The name "Record Delay" also makes no sense. If I understand properly, its the amount of time that the camera continues to record after no further motion has been detected. I suggest using the name "Post Record Time". I think most people would easily understand that.

[Melvin]

Hello maxbraketorque ,

Thank you for the feedback and suggestions. I will pass this on to the concerned department.