![]() This example shows the cameras going down to a keyrate of 0.25 means that the iframe rates are over 4 times the FPS and that is why motion detection is a disaster with these cameras and Blue Iris. ![]() The iframe rates (something these cameras do not allow you to set) should equal the FPS, but at worse case be no more than double. The Blue Iris developer has indicated that for best reliability, sub stream frame rate should be equal to the main stream frame rate and these cameras cannot do that and there is nothing you can do about that with these cameras. ![]() It is these same games that make the camera look great as a still image or video but turn to crap once motion is introduced. This is mainly why people are having issues with these cameras and there are many threads showing the issues people have with this manufacturer and Blue Iris. The iframes not matching (that you cannot fix or change with a reolink) is why they miss motion in Blue Iris and why people have problems. Now this is a ratio, so it should be a 1.00 if it matches the FPS. ![]() Blue Iris works best when the FPS and the iframes match. Now look at the key - that is the iframes ratio. This was a screenshot of a member here where they had set these cameras to 15FPS within the cameras (and look some of the sub FPS were dropped to 5 and KEY of 0.25 which is a recipe for missed motion): I have a cheapo camera for overview purposes so it doesn't matter, but it exhibits this same behavior even though in the settings I can set an iframe. It is just Reolinks is one of the more consumer end cameras people buy and come to this site as to why it is pointed out often about. Some people have got some of the models to work with BI kinda, but it still doesn't overcome the poor night performance.īlue Iris and Reolinks do not work well together, but the same principles applies for almost any low end consumer grade camera. Reolinks do not work well with Blue Iris and is even worse with DeepStack if you ever decide to go that route.īlue Iris is great and works with probably more camera brands than most VMS programs, but there are brands that don't work well or not at all - Rings, Arlos, Nest, Some Zmodo cams use proprietary systems and cannot be used with Blue Iris, and for a lot of people Reolink doesn't work well either. Using Find/Inspect, ONIF to find the camera and it identifies it as IPC-BO, Generic/ONVIF/RTSP H.264/265/MJPG/MPEG4 That was worse with delays or no picture at all.įirmware: v3.1.0.804_22011511v1.0.0.30 (this is the new firmware I installed off Reolinks firmware page, not the original version that came with the camera) Seems to work the best but getting huge lag times of 15-20 secondsĪlso tried using ONVIF. ![]() Using the Reolink App and Reolink desktop, everything seems ok running at CLEAR (3840x2160 25 fps).īut trying to configure to BI5 has been a challengeĪny configuration advice to configure with Blue Iris?Īn image comes up in Blue iris, but it freezes often for up to 30 seconds at a time.Īlso, it gets even more choppy (missing frames of 5-10 seconds) when I am using BI5 desktop or the BI Android app and/or I use the Reolink PC interface or the Reolink Android interface to look at this same cameras, they almost seem like they are playing tug of war over the stream. Updated the firmware today and now its not interfacing with Blue Iris properly. Having a lot of problems here configuring the 823-A with BI5. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |