frigate: [Support]: post/pre capture does not work

Describe the problem you are having

hi! i setup post_capture and pre_capture to be 10 seconds each. this does not seem to work, resulting in cutoff clips.

Version

0.10.0-B912851

Frigate config file

record:
  enabled: true
  retain_days: 0
  events:
    pre_capture: 10
    post_capture: 10
    retain:
      default: 10

Relevant log output

n/a

FFprobe output from your camera

Frigate stats

{
back: {
camera_fps: 5,
capture_pid: 239,
detection_fps: 11.8,
pid: 231,
process_fps: 5,
skipped_fps: 0
},
detection_fps: 12,
detectors: {
coral: {
detection_start: 1637138416.91632,
inference_speed: 8.74,
pid: 225
}
},
front: {
camera_fps: 5.1,
capture_pid: 237,
detection_fps: 0.2,
pid: 228,
process_fps: 5.1,
skipped_fps: 0
},
service: {
storage: {
/dev/shm: {
free: 3201.8,
mount_type: "tmpfs",
total: 3221.2,
used: 19.4
},
/media/frigate/clips: {
free: 65039.4,
mount_type: "ext4",
total: 3936911.9,
used: 3671816.5
},
/media/frigate/recordings: {
free: 65039.4,
mount_type: "ext4",
total: 3936911.9,
used: 3671816.5
},
/tmp/cache: {
free: 15704,
mount_type: "ext4",
total: 117608.4,
used: 95886.1
}
},
uptime: 1191,
version: "0.10.0-b912851"
}
}

Operating system

Other Linux

Install method

Docker Compose

Coral version

USB

Network connection

Wired

Camera make and model

Reolink 410 / 520

Any other information that may be helpful

seems like this beta update broke it.

About this issue

Original URL
State: open
Created 3 years ago
Comments: 28 (6 by maintainers)

Most upvoted comments

If the user is exclusively using event recordings (retain days set to 0), then all that has to be done is waiting a little longer before deleting segments from the cache. Then, if an event is backdated, the appropriate segments (motion or all) will be included in the event since they overlap with the time range.

If a user has specified that they want motion retain mode for events, then the segments that are in the pre/post capture period that don’t contain motion should be deleted.

You can already essentially get this behavior by retaining 1 day of any motion.

blakeblackshear on Jul 2, 2023

You can’t predict the future. There isn’t a way to know that an event is about to start in 120s.

If you have motion mode enabled then you should already have any segments where pixel values changed.

If you want more precapture, then you could just freeze the first frame and show a static image for the first 120s. /s

You really just need to use all mode if you want to save video of a still image.

blakeblackshear on Jun 30, 2023

The retention will only ever be what your config is set to keep, if the segment has no motion it won’t be kept. That being said, based on what you describe you may want to increase the value of max_disappeared slightly to make that detection a part of the same event

NickM-27 on Jun 16, 2023