This was, in the immortal words of Bill and Ted, bogus. Then, barely outside my return window, Reolink updated their support page to say that the cameras would only work with their 8-channel NVR or proprietary viewer apps. However, I bought these cameras because I believed they supported open standards such as ONVIF, so I’d just swap the NVR for a copy of Blue Iris running on my server.Īt the time, the Reolink support page clearly indicated that all of their non-battery-powered cameras supported RTSP.Īfter the system was installed, it became apparent that the cameras did not in fact support RTSP-the only port open on them was port 9000. Unfortunately, the NVR is pretty anemic: it’s clearly an existing model with slight changes to support 4K cameras, and it struggles to support more than one viewer at a time. It came in a “kit” of six cameras and an NVR (a dedicated recording box that also powers the cameras). It’s fairly nice hardware, actually-it has a 4K video sensor, a microphone, power over Ethernet, and is nominally waterproof. Way back in late 2019, I dissected a Reolink B800 IP camera to demonstrate the various parts of an embedded Linux system. A brief history of the Baichuan protocol.The new client shows promise but it's quite buggy. I guess I'll try leaving it at Fluent for a while to see if that helps out. I have no other theories - I'm open to trying to help if someone wants to test more variables. That hasn't seemed to help, so that theory must be wrong. They're all 10fps Fluent, 20fps Clear, for example. One thing I have tried to explore is whether or not varying stream settings might confuse the software, so I've set all my cameras to the same settings as much as possible. I'm not sure if that plays into the problem or not. I always set my feeds to Standard quality instead of Fluent. The program starts out just fine, it's hard to say when the problem happens, but it's likely within half an hour, for sure, possibly earlier than that. High CPU usage, after a time, and eventually frozen video. Same/similar problem - on multiple computers of mine, ranging from my Ryzen 9 5950X to more mid-range AMD and Intel processors. ![]() Has anybody found the same issues on their setup? What have you tried that seems to fix problems like above? The only fix I found was to go back to version 7.2.2.33, which has its own set of problems. I must exit out the reolink pc client in order to stop the turbo-ing cpu issue. THis prevents me from having a monitor with this pc client open at all times. Now all cams are apparently auto-upgrade whether I want to or not.ģ.on my AlderLake very updated system, my cpu usage consistently zooms to 99% due to this reolink app version, which starts "turbo-ing" this way after a just a few minutes of normal functioning. Only shutting the cams off will stop this crazed spinning.Ģ.on all reolink cams I own (523wa, 511wa, 811a, 410a, e1zooms, e1outdoors, argus3pros), the ability to choose whether to auto-upgrade the firmware or not has disappeared. Ever since the upgrade to the 8.5.2.0 version of the PC client, I've noticed these consistent problems:ġ.on my reolink 523wa cams, the "auto-tracking" feature must be turned off, otherwise the camera will consistently start spinning rapidly & continuously 360degrees upon an initiation of auto-tracking, especially during "patrol" function.
0 Comments
Leave a Reply. |