Great App....However...

[jack77]

Within an hour it crashes on my laptop ....Mac powerbook running Tiger 10.4 using seperate isight camera. It works well on 3g and wifi on my iphone so this is such a shame that this keeps happening. Anyone with a similar problem

[Stefan]

If the iCamSource is crashing on a Mac then there should be a crash logs in your Preferences > Logs > CrashReporter folder located within your home folder. If you find an iCamSource crash log please e-mail it to support@skjm.com and reference this forum post.

On older PPC Macs running Tiger the iCamSource has been known to crash due to high CPU usage. This is caused by the motion detection image processing that occurs every 500 ms (half-second) or so. You can check the CPU usage in the Applications > Utilities > Activity Monitor application.

One solution is to reduce the frequency at which the motion detection processing occurs, and you can do that by opening a Applications > Utilities > Terminal, and copy-and-pasting the follow line into it, and pressing Enter:

defaults write com.skjm.icamsource MotionDetectionWait -int 5000

If you then restart the iCamSource it will attempt to detect motion every 5 seconds as opposed to twice a second.

If you want to restore the value to its original setting, simply use this line:

defaults write com.skjm.icamsource MotionDetectionWait -int 500

[jack77]

If the iCamSource is crashing on a Mac then there should be a crash logs in your Preferences > Logs > CrashReporter folder located within your home folder. If you find an iCamSource crash log please e-mail it to support@skjm.com and reference this forum post.

On older PPC Macs running Tiger the iCamSource has been known to crash due to high CPU usage. This is caused by the motion detection image processing that occurs every 500 ms (half-second) or so. You can check the CPU usage in the Applications > Utilities > Activity Monitor application.

One solution is to reduce the frequency at which the motion detection processing occurs, and you can do that by opening a Applications > Utilities > Terminal, and copy-and-pasting the follow line into it, and pressing Enter:

defaults write com.skjm.icamsource MotionDetectionWait -int 5000

If you then restart the iCamSource it will attempt to detect motion every 5 seconds as opposed to twice a second.

If you want to restore the value to its original setting, simply use this line:

defaults write com.skjm.icamsource MotionDetectionWait -int 500

Yeah cheers for that...will ave a look tomoz... I'm no geek mind, so my hopes aren't high for finding the required info...lol

[jack77]

Tried everything u suggested....Still crashing? I copied and pasted the information into the Terminal....when I re-opened the Terminal it had gone...Is it supposed to do that?

[Stefan]

Did you copy-and-paste and hit enter (or return) to apply the changes?

If you copy and paste the following and hit enter (or return) in a Terminal window does it give you 500 or 5000?

defaults read com.skjm.icamsource MotionDetectionWait

[jack77]

Did you copy-and-paste and hit enter (or return) to apply the changes?

If you copy and paste the following and hit enter (or return) in a Terminal window does it give you 500 or 5000?

defaults read com.skjm.icamsource MotionDetectionWait

When i get home from work I'll try it again...I'm doin something wrong tho...

[Stefan]

If it gives you 5000 when you do the "read" command then it is saving it. What is the % CPU usage of the iCamSource in the Activity Monitor when running?

[jack77]

Did you copy-and-paste and hit enter (or return) to apply the changes?

If you copy and paste the following and hit enter (or return) in a Terminal window does it give you 500 or 5000?

defaults read com.skjm.icamsource MotionDetectionWait

When i get home from work I'll try it again...I'm doin something wrong tho...

It gives me 5000

[Stefan]

5000 is correct, then. It is waiting 5 seconds between motion detection processings.

What is the % CPU usage of the iCamSource in the Activity Monitor when running?

Also, if you could send the latest crash log(s) to support@skjm.com that'd be helpful as well.