4.3.0 - February 23, 2016
The previous motion "mask" feature has been greatly expanded to allow for 8 "zones" instead. Your existing masks will become zone A, and hotspots are zone H.
The object detection rules page now features a setting for zone/line crossing. You may specify simple A>B movement or more complex AB>C etc.
The triggering object's zones are logged to the database as part of the Alert image list.
Motion zone letters are appended to the &TYPE macro for use with email, SMS and Run alerts.
Alerts may be triggered based on motion zones. This allows you to record trigger events without necessarily being notified in every case.
Video flip and rotate are now allowed when using direct-to-disc recording to BVR file format. The flip/rotate status is saved to the BVR file and the viewer/player components will perform these operations prior to display.
A number of tweaks have been made to the motion detector's shadow-elimination algorithm in order to make it more tolerant of clouds and lighting changes. More attention will be paid to this area as required to further eliminate false positive alerts.
In general, when a clip is deleted, its alert images are also deleted. However, if you specify to "save hi-res" alerts on the Record tab, these resulting JPEG files will NOT be deleted automatically with their clips, but will remain according to the age rule for alert images on the Options/Clips page. This will allow you to keep alerts for an extended period of time beyond the video clips themselves.
The motion detection algorithms have been once again reformulated, this time to be much simpler, and hopefully more reliable for those that were experiencing issues with shadows etc.
Looks interesting - but:
When running BI as service then the previous "masks" goes incorrect and BI crash when try to edit "zones".
Seems working correctly when running BI as a console.
Emailed Ken.
The previous motion "mask" feature has been greatly expanded to allow for 8 "zones" instead. Your existing masks will become zone A, and hotspots are zone H.
The object detection rules page now features a setting for zone/line crossing. You may specify simple A>B movement or more complex AB>C etc.
The triggering object's zones are logged to the database as part of the Alert image list.
Motion zone letters are appended to the &TYPE macro for use with email, SMS and Run alerts.
Alerts may be triggered based on motion zones. This allows you to record trigger events without necessarily being notified in every case.
Video flip and rotate are now allowed when using direct-to-disc recording to BVR file format. The flip/rotate status is saved to the BVR file and the viewer/player components will perform these operations prior to display.
A number of tweaks have been made to the motion detector's shadow-elimination algorithm in order to make it more tolerant of clouds and lighting changes. More attention will be paid to this area as required to further eliminate false positive alerts.
In general, when a clip is deleted, its alert images are also deleted. However, if you specify to "save hi-res" alerts on the Record tab, these resulting JPEG files will NOT be deleted automatically with their clips, but will remain according to the age rule for alert images on the Options/Clips page. This will allow you to keep alerts for an extended period of time beyond the video clips themselves.
The motion detection algorithms have been once again reformulated, this time to be much simpler, and hopefully more reliable for those that were experiencing issues with shadows etc.
Looks interesting - but:
When running BI as service then the previous "masks" goes incorrect and BI crash when try to edit "zones".
Seems working correctly when running BI as a console.
Emailed Ken.