Detect Motion Performance Concerns #1
Labels
No Label
bug
duplicate
enhancement
help wanted
invalid
question
wontfix
No Milestone
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: steven/storage-security#1
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This is running on a freaking fisher price computer meant for kids (raspberry pi 4). I don't yet have hardware to benchmark performance, but I suspect that attempting to detect motion between every frame inline with the rest of the code will result in low framerates in the saved video.
There are a few possible methods I've thought of to overcome this:
Idea #1 is probably better overall but requires more work. Idea #2 will be quick to implement, but may result in jittery video (plays fine for a second, then frame pauses for a few milliseconds, then plays fine again, etc). Idea #2 will also probably require more tuning as the more time between motionDetection runs, the more pixels in the frame may change which could result in having to tune the minimumArea parameter.