Motion Detection
ceewanna opened this issue · comments
This might not be a bug but from my testing so far it seems the system never seems to capture the start of the event. For instance, I am walking to the desk at a distance of around less than 6 meters. The vdo only shows when I am already at the desk but doesn't show when I was walking there.
This same event is easily captured in another system. I am working on. I am probably new to the settings. I have increased the sensitivity to 90 while the pixel difference has been around 5-16. forceCloseTimer is kept at 3 mins while dwellTimer has been decreased to the minimum 15 sec. There is prebufferLength: 4 which seems to be fixed by the system because it gets reset to 4 regardless of the value set in the xml file.
I'm having a similar issue with raspberry pi camera v3 and raspberry pi v4 board using HKSV. it detects the motion and completes the recording, but i always seem to lose the beginning of the recording (or maybe the motion is not "detected" until later). It would seem from the documentation that the "prebuffer" length is the number of seconds BEFORE MOTION IS DETECTED that should be saved to the beginning of the recording. I have the prebuffer set to the max of 8 seconds and even tried using forcePrebuffer=true to no avail.
Otherwise, video is good, recordings in HKSV are excellent quality, just seem to be missing the first 3-4 seconds after motion should have been detected.
@seydx: is the objective of "prebuffering" to have the recording session "stretch into the past" by a few seconds to be sure you capture the beginning of the motion event?
Also, does the prebuffering work with HSV? If not, is there a way to delay the main stream but not the substream so that motion captured by the substream gets recorded by HSV via the main stream (which is delayed by 2 seconds or so)?
Thanks!
This was useful. i was able to create a new rtsp stream for HSV and delay it a few seconds via GStreamer in MediaMTX.