This is awesome, but with my old hardware (and my gpu not supported) cpu goes to 100% with deepstack processing even a single cam at 10fps. Much lower than 1.00, the motion detector may not operate effectively and events may be The camera is not triggered or selected for streaming or viewing. This means that only key frames are fed to the motion detector when When limit-decoding is being used, only key frames are decoded unless all video is requiredįor display or analysis. One way to compensate for this is to use pre-trigger time on the Record page. Means that video frames between a trigger event and the next key frame rate may be lost.
Reolink client windows manual#
If you want to get the word straight from the developer check out the online manual and Ctrl+F search for “key frame”, but a lot of the relevant information is in these paragraphs:ĭirect-to-disc recording can only begin on a key frame boundary-if the rate is too low, this
Reolink client windows how to#
I presume it is because he doesn’t know how to adjust/compensate for them in the software. Almost all of this comes from the forums where the site owner has a real grudge against the cameras. There is a lot of misinformation out there regarding Reolink cameras and Blue Iris. When you enable that option Blue Iris will only decode the key frames and do motion detection on those which in the case of Reolink cameras would be every other second.Īs far as DeepStack integration goes, the documentation says that as long as your pre-trigger buffer is at least as long as key frame interval you should be good. When you are keeping 10-15 seconds of pre-trigger video buffer I do not think that is such an issue.Īlso, I only think that what you said comes into play when you enable “Limit decoding unless required”. So if your key frame interval were something ridiculous like every 10 seconds, you could only start a recording on that key frame and may lose video. I pull images straight from the cameras and feed them to DeepStack directly instead of waiting for motion detection to hopefully trigger and feed images to DeepStack and then hopefully start recording.īut, as far as I know and have read in Blue Iris documentation, the reason for a 1fps key frame interval is that recording can only start on a key frame. Reolink allows this ratio to drop too low to allow accurate motion detection especially at night when it drops to 1.3 or lower. BI relies on a ratio of 1:1 between frame and iframes for accurate moon detection.
0 kommentar(er)
