SS4 Bugs
When a network camera is configured for both continuous and motion, any instance of a motion triggering ends the continuous clip (the C clip is then saved, then a new one starts). Instead of having solid 10-minute clips, now I have random clip lengths all based on when a motion clip was triggered. My continuous clips are set for every 10 minutes.
Another new bug I've discovered (for my setup at least) is that motion clips catch the first frame, then drop about 20 frames, record 1, drop 20, then record the rest of the full scene. In short, even with rendering turned on, it would appear there is a consistent frame drop (or consistent choppiness) for the first few seconds of a motion clip. To work around this, you could set pre-capture to a higher number, but then the thumbnail on the web server grid would not show an accurate scene, usually it's empty.
Another new bug I've discovered (for my setup at least) is that motion clips catch the first frame, then drop about 20 frames, record 1, drop 20, then record the rest of the full scene. In short, even with rendering turned on, it would appear there is a consistent frame drop (or consistent choppiness) for the first few seconds of a motion clip. To work around this, you could set pre-capture to a higher number, but then the thumbnail on the web server grid would not show an accurate scene, usually it's empty.
Comments
-
I have also found a bug. I created a schedule 11pm-5am every day. I want an email action only active during this schedule. However when I select the schedule under the action preference window it will never save. Just defaults back to Manual Schedule.
-
Hi - all the above problems should be fixed in the latest beta version of SecuritySpy (currently 4.0.2b3). Please confirm.
-
I turned off rendering and read the "how to optimize SS", remasked the scenes so and this problem with the frame drop is gone. Thanks.
