@160334357029011 My experience with v8.12.1 is that it consistently stops recording after a period of time. More concerning is that, on my Win11 machine, the app continues to run for an extended period of time after the visible app is closed. After closing the application, I have watched the Reolink process in task manager continue operating using 17%CPU, 3 to 8 Gig of memory and 1 to 3Mbps of network use for over 40 minutes. The application can only be restarted by ending the task using task manager. Seems troublesome and nefarious. I have attempted to use v8.8.5 but it stops recording as well. Anyone else experiencing this behaviour?

I have an RLC-810A surveilling my driveway. I can't seem to adjust any of the motion detection parameters to stop the camera from recording on non-motion of my vehicles. When I view it in single camera, High, I can see the Motion Mark(Beta) blue boxes detecting constant motion on my parked vehicles and recordings continuously start. I have Sensitivity / Motion Detection set to Medium levels and Sensitivity / Smart Detection set to 50 for person and pet. The only way I can seem to stop the constant motion detection of my parked vehicles is to set Sensitivity / Smart Detection / Vehicle to 5 or below but this results in zero motion detection of all actual movement, vehicle, person, or otherwise. I have made a few attempts at using the object size parameters with no success. Is there a guide available for setting up all of these parameters for good functionality? Any ideas, or questions? Thanks

@160334357029011 My experience with v8.12.1 is that it consistently stops recording after a period of time. More concerning is that, on my Win11 machine, the app continues to run for an extended period of time after the visible app is closed. After closing the application, I have watched the Reolink process in task manager continue operating using 17%CPU, 3 to 8 Gig of memory and 1 to 3Mbps of network use for over 40 minutes. The application can only be restarted by ending the task using task manager. Seems troublesome and nefarious. I have attempted to use v8.8.5 but it stops recording as well. Anyone else experiencing this behaviour?

I have found that after closing the v8.12.1 client app on my win11 PC, often times I could not start the app again without restarting my PC. Further investigation showed that task manager lists 5 PIDs for the client when running. After closing the client, 4 PIDs will sometimes remain open for many minutes afterwards with one PID using a LARGE block of memory. I have found that while these residual PIDs are running, the client will not start when it is attempted. Only after closing the residual processes with task manager will the client restart normally. Is this a bug, feature, something nefarious? In addition, the client has become VERY laggy as of the last few updates. The client video is 5 to 10 seconds behind real time. This is relatively new and troubling.