Support > Beta Testing

iCamSource 2.4.6 BETA - Motion Event Image Minimum

(1/4) > >>

Stefan:
One of the most requested features that we receive from our users is the ability to assign a minimum threshold for the number of images required for a stored Motion Event. Depending on what type of scene a camera is viewing, iCamSources can end up accumulating large numbers of 1- and 2-image Motion Events which are of little use and are ultimately deleted.

Well now with version 2.4.6 BETA of the iCamSource you can assign a Motion Event Image Minimum for each camera in the bottom-right corner of the Motion Detection tab. You can assign a minimum value of 1 (the default) up to 9. The value represents the minimum required number of images that must be contained in a Motion Event for it to be retained during the periodic trimming process that occurs every 5 minutes or so.

(The most recent Motion Event will not be removed during the trimming process if it falls below the minimum, but all older Motion Events will be subject to removal if they do not contain the minimum number of images.)

* Since this is a BETA release we would recommend backing up any Motion Events that you do not want accidentally deleted in case there are still some issues to work out with the trimming logic.

The new versions can be downloaded below.


Windows - http://skjm.com/icam/iCamSetup2.4.6.exe


Mac OS X

When Mac OS X 10.8 (Mountain Lion) is released this summer it will contain a security feature called Gatekeeper (http://www.apple.com/macosx/mountain-lion/security.html) that by default will limit third-party Mac apps that are not downloaded from the Mac App Store or digitally signed by the developer. In order to prepare for Mountain Lion, we are going to be releasing two versions of the Mac iCamSource, one for Mac OS X 10.4 & 10.5 (Tiger & Leopard) and one for Mac OS X 10.6 (Snow Leopard) and later.

Mac OS X 10.4 and 10.5 do not have the ability to run digitally signed applications, so that is why they will need a separate build version.

Mac OS X 10.6 (Snow Leopard) and later - http://skjm.com/icam/iCamSource2.4.6.dmg
Mac OS X 10.4 & 10.5 (Tiger & Leopard) - http://skjm.com/icam/iCamSource_Tiger_Leopard_2.4.6.dmg


As always, if anyone has any questions, issues, or comments about the functionality, please let us know.

Thanks! :)

OUAnthony:
Awesome! Does it maintain support for Foscam audio and pan/tilt? If so, I'm gonna try it now...

Stefan:
Yes, it should contain all of the additional changes put into previous beta versions.

Merlin:
I upgraded last night and ran iCam through the night.  This morning on one of the cameras it had a single image and the Event Image Min was set at 2.  I have a couple of questions;

1.  Does this just trim after the motion sense has been detected and recorded or does it never record the event? 
2.  Does it just remove the frames selected of a motion event?  If it had 3 frames and 2 was selected, then only two of the frames would show up.
3.  If I select two frames for the Min, will it still send a notification to my iPhone on a single motion event (preferably not)?

Just trying to understand while I test...

Merlin

Stefan:

--- Quote from: Merlin on June 03, 2012, 09:08:06 AM ---I upgraded last night and ran iCam through the night.  This morning on one of the cameras it had a single image and the Event Image Min was set at 2.  I have a couple of questions;

1.  Does this just trim after the motion sense has been detected and recorded or does it never record the event? 
2.  Does it just remove the frames selected of a motion event?  If it had 3 frames and 2 was selected, then only two of the frames would show up.
3.  If I select two frames for the Min, will it still send a notification to my iPhone on a single motion event (preferably not)?

Just trying to understand while I test...

Merlin

--- End quote ---

To answer your questions:

1. The event is recorded and later trimmed, yes. A new motion event is created when motion has not been detected for at least 30 seconds. When a new event is created it is still unknown at that moment how many images it will ultimately contain, so it does need to be recorded and later trimmed if necessary.
2. No, only entire motion events are removed that do not meet the threshold. So in your example, a motion event with 3 images would not be removed or effected if the minimum was set to 2. A motion event with 1 image would be deleted completely. Additionally, if the minimum was set to 5 then any motion event that did not contain at least 5 images would be completely removed.
3. The motion event setting is separate from the push notification setting, so yes, it would still send a notification.

Since you had the minimum set to 2 and woke up to see a single motion event with a single image then that was most likely the most recent detection of motion, with other single-image motion events having been trimmed off. When motion is next detected that single image event will also be trimmed.

Navigation

[0] Message Index

[#] Next page

Go to full version