search

zemidf1 / ispyconnect

Automatically exported from code.google.com/p/ispyconnect
0 stars 0 forks source link

Recording (almost) never stops in low CPU conditions, and schedule doesn't get applied to some cameras #15

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Install iSpy on a box with low CPU power (I suppose this could be simulated 
with running some higher-priority process that eats a large chunk of the CPU?)
2. Set up some remote cameras and at least one local (requires some CPU power). 
The average framerate for all cameras is less than 1 FPS.
3. Trigger the motion detector in some cameras, so that recording starts

What is the expected output?
1) The schedule applying correctly
2) The recording stopping whenever there is no movement anymore

What do you see instead?
1) The schedule doesn't apply - I often see a camera on that should have been 
off hours ago
2) Recording doesn't stop at all (fills upto the maximum file system's 
filesize), or occasionally stops after a significant amount of time, despite 
not having motion detection events

What version of the product are you using? On what operating system?
v4.3.7.0 on Windows XP

Please provide any additional information below.

I suppose the problem is with the low frame rate of the cameras - iSpy's event 
handlers are probably tied to them hitting in a particular second or something 
like that?

When the local camera that eats most of the CPU is disabled, this bug doesn't 
seem to occur anymore.

Original issue reported on code.google.com by cuba.add...@gmail.com on 6 Sep 2012 at 8:39

GoogleCodeExporter commented 9 years ago 
This is due to thread priority - some threads are background threads and only 
run when the computer is in a waiting state. If your PC is running at 100% (or 
close) then those threads will never run. Basically the issue is that you need 
to either get a more powerful PC or reduce the resolution/ number/ framerate of 
your cameras.

Original comment by ad...@developerinabox.com on 9 Sep 2012 at 7:39

GoogleCodeExporter commented 9 years ago 
Perhaps there could be a way to change this thread priority with a 
configuration setting then?

I would gladly reduce the frame rate for the cameras to something like 0.3FPS 
(they are currently running at 0.5-0.8), but unfortunately iSpy's configuration 
doesn't let me set a frame rate setting lower than 1 FPS.

Original comment by cuba.add...@gmail.com on 9 Sep 2012 at 8:08