Motion Detection - CPU

[mgiddens]

I understand that motion detection increases CPU utilization.  I've just bought iCam and I would like to have iCamSource running all the time and schedule the recording and notification of motion events.  I've got this working satisfactorily. On the motion detection tab, I have "Enable Motion Detection" checked  and I've left "Send Notifications" and "Record Motion" unchecked (because I'm using the scheduler).  My expectation was that having those last two items unchecked would, in effect, suppress the actual motion detection (and lower CPU utilization) as it serves no purpose to detect the motion if no action is going to be taken.

As it stands, when I come home and need to use my computer, I have to either disable motion detection or stop iCamSource to alleviate the high CPU utilization.  Then, when I leave in the morning, I have to re-enable motion detection or re-start iCamSource.  Am I missing something or is it by design that I'm going to have to manually interact with iCamSource all the time?

Thanks!

[OUAnthony]

How old is your computer? Older computer = less processing power.

How many cameras are you using? More cameras = more processing power used.

What type of cameras (USB or IP cameras)? USB cameras use more processing power, as they provide a higher frame rate, etc.

What is the resolution of the cameras? Anything over 640x480 will use more processing power, as they need to be downsized to 640x480 for iCam. If possible, change the resolution to 640x480 for the cameras. You can also try reducing the image quality in icamsource, as well as decrease the sensitivity of motion detection.

What is the frame rate of the cameras? Higher frame rate = more processing power used. If possible, lower the frame rates of the cameras to 5 fps.

Do you have audio enabled? Audio will use more processing power. Try disabling audio on all camera feeds.

With all of that being said, this is what I'm experiencing...

My system: 4 or 5 year old dual-core processor, 4 IP cameras (one with audio enabled), all cameras set to 640x480 and 5fps, motion detection/recording/notification enabled on all cameras.

Processor used when cameras not being viewed via iCam app: 12-19%

Processor used when viewing all cameras (thumbnails): 22-33%

Processor used when viewing one camera feed (with audio): 20-30%

I'd probably expect USB cameras to use roughly double the processing power...maybe even more, especially with audio...and especially if you're using a higher-resolution webcam (which are very common these days).

[mgiddens]

I'm okay with the increased CPU requirement of motion detection.  Using your suggestions, I could minimize it to some degree.  (I'm running a Late-2011 MacBook Pro 2.5 GHz quad-core i7 w/16GB ram).  I think the fundamental question I have is that when "Send Notifications" and "Record Motion" are both unchecked, what's the point of iCamSource actually performing motion detection?  I understand that iCamSource performs motion detection whenever "Enable Motion Detection" is checked so I guess I'm questioning why that is the case (and to make sure I'm not missing something) and wondering if it wouldn't make better sense for the program to behave differently.

Right now, I'm not recording or notifying, so there's no need for my CPU to be under the load that it is. It's under that load because iCamSource is performing motion detection (for no purpose).   But I'd really like to leave iCamSource up and running and let the scheduler handle starting/stopping recording and notification (and by extension, motion detection).  Presently, in order to alleviate the CPU utilization,  I have to stop iCamSource when I sit down to work and start it up again when I leave.  Just doesn't seem right.... it seems like a mistake.

Anyway, if I have to, I can always enable auto-start and rely on the OS to launch/kill iCamSource on a schedule.

Thanks for taking the time to help.