Overlay rendering too intensive

Question

Overlay rendering too intensive

lukeswitz opened this issue 5 years ago · 3 comments

Switching back to an overlay for motion detection has caused some problems. Memory leaks from cameraviewhandler and monitor activity combine to form a laggy, useless interface. Movement overlay appears once every ten second max until it crashes out.

Archie supplied more logs than could ever be needed to track this down, seems the library was added using the readme setup which assumes a good camera on a new device.

I’d vote to go back to the simple “xxxx detected” UX

Answer 1 · 2019-04-21T11:59:13.000Z

Seems the creation and rotation of the bitmap on frame processing causes this. The matrix rotation hangs the cameraView

Answer 2 · 2019-04-22T11:40:04.000Z

No use. Cart pushing horse.

Answer 3 · 2019-04-22T14:10:37.000Z

Here is my proposal for overhauling the camera moving forward: 1) use hardware video mp4 recording on a loop. Records 30 second loops. 2) use preview frame to detect motion as we do now, but dont worry about rotation, matrix etc 3) if motion is detected, save the current video loop. Seems like this approach will pop many balloons with one stone.

…

On Mon, Apr 22, 2019, at 8:37 AM, Luke Switzer wrote: No use. Cart pushing horse. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#397 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAAHRAZL5XM7AYOVHBLTYITPRWPZLANCNFSM4HHLP2YQ>.