Continuous Capture Frequency

jltnol
edited July 2015 in SecuritySpy
So regardless of whether I have the continuous capture frequency set to 1 frames per second, or 30 frames per second, the file size for sixty seconds of capture is about the same. To me, it would seem a lower frame rate would result in a smaller file size..

Even with the lowest frame rate of 1 per second, and the highest playback frame rate of 99, the file size is the same... just trying to understand how this capture frequency really works..... 1 frame per second should be very jerky video, but it's still smooth... just playback is faster...

Comments

  • If the incoming video format is temporally compressed (i.e. MPEG-4 or H.264), and you have enabled the "No recompression" option for the camera in the Video Device Settings window (which is on by default), then the incoming video gets saved directly to the files, and it's not possible for SecuritySpy to change its frame rate.

    So, if you want a lower frame rate recorded to the video files, there are three options: 1. Lower the rate at which the camera is actually sending video, via its settings pages, 2. Turn off the "No recompression" option, which will increase CPU usage because then SecuritySpy will decompress then compress the video internally, or 3. Change the video format of the video that the camera is streaming to JPEG, if this is supported by your camera (however this is a less efficient format that will result in large captured files sizes).

    Hope this helps.
  • I just noticed a similar issue. I have continuous capture set to 1 frame every 15 seconds with 5 frames per second playback. However, I'm getting 60GB files that appear to be straight off of the camera feed. Your explanation answers that question, but that was only part of the puzzle. I used to be getting TL files of about 1.5GB, but I had a SecuritySpy adding a text overlay, so it was recompressing the file. The files started getting huge when I removed the overlay. It's all making sense now.
  • Yes indeed, if you have enabled the overlay, SecuritySpy has to decompress and then recompress the data in order to add the overlay, so in this case the "No recompression" option is ignored, which will have the effects you describe.