In this case, you would select H.264 as the "Video compression format" option in the calculator. The calculator then uses this to predict the resource usage, assuming that this data is recorded as-is to the captured movie files (i.e. it is not being re-encoded to a different format for recording).
This incoming H.264 data still has to be decoded by SecuritySpy for various tasks (e.g. display to the screen, motion detection, web access etc.), and this is the main source of CPU usage related to the incoming video format.
Comments
This incoming H.264 data still has to be decoded by SecuritySpy for various tasks (e.g. display to the screen, motion detection, web access etc.), and this is the main source of CPU usage related to the incoming video format.