1
iCam Support / Re: Motion Detection - CPU
« on: November 07, 2012, 03:05:56 PM »
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.
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.