![]() The downside of this is that it counts as two cameras for licensing purposes, so I'm not sure if you currently have space for this within your current SecuritySpy license. Then you can specify whatever capture frame rates you want under the "Continuous Capture" and "Motion Capture" tabs.Īn alternative would be to set up an additional camera instance in SecuritySpy using the camera's substream, which you can set up to be a lower frame rate (and/or quality, resolution etc.) and use this second instance for continuous capture. To achieve this, enable the "Recompress video data" option under Preferences -> Cameras -> Device for the camera in question. This re-encoding process can use significant CPU time, and degrades image quality (but you can mitigate this by selecting a high encoding quality in the camera). It is already possible to do what you are suggesting, however the downside is that in order to change the frame rate of the H.264 stream, SecuritySpy has to decode and re-encode the stream (as opposed to using the raw video data provided by the camera and saving this directly to disk). and no other messages or problems have been noted so far! Motion came back (re-enabled) after a min. (Failed to record video frame 5575,818 The key frame interval from the network device is too high, locate and change this setting in the device (may be called l-frame interval / l-frame rate / GOV length / Intra frame period))" including more comprehensive H.264 / H.265 compatibility with Dahua. "Error performing motion capture for the camera "Hikvision 2.8mm", motion capture mode has been disarmed. Version 5.5 of our macOS CCTV software SecuritySpy just released, including AI. This was the one time problem message from security spy. I took some screen shots - is it possible to post them here somehow? The picture quality is not degraded at all by the H.264+, I will leave it on and test more :-) There is no need to interact directly with the cameras IP address. I did get a problem message from security spy but it seems to have resolved itself and is working now. Simply connect the camera to your network, and in the Preferences -> Cameras -> Device section in SecuritySpy, create a new network device, click the Auto-Discovered Devices button, and select the camera from the list. I also noticed that my memory pressure went from yellow to green. I turned on the H.264+ and my CPU usage went down from ~21% (following a motion event) to about ~15% with H.264+ enabled. ![]() I'm moving from a WiFi setup over to hard cables and just testing with my first POE camera. Yes, that is what I thought after looking at the Hikvision write up.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |