[Config Support]: 0.15.0-beta1 does not honor pre_capture settings in record #15073
-
Describe the problem you are havingIn release 0.14.1, I had this configuration and pre_capture was working correctly:
In 0.15.0-beta1, this has been auto-adjusted on startup to look like this:
However, I am no longer getting the 15-second of pre_capture on my recordings. No errors occur on startup; it just behaves as though the pre_capture setting is not there. I have reverted back to 0.14.1 to confirm it still works. I have also tried the image ghcr.io/blakeblackshear/frigate:9ae839a-amd64 and it also behaves the same way. Version0.15.0-33825f6 Frigate config filelogger:
# normal is info
default: warning
tls:
enabled: false
mqtt:
host: 192.168.1.120
port: 1883
user: mqtt-user
password: redacted
stats_interval: 60
detectors:
coral:
type: edgetpu
device: usb
birdseye:
enabled: true
mode: motion
inactivity_threshold: 15
review:
alerts:
labels:
- car
- motorcycle
- bicycle
- cat
- dog
- bear
- bird
- raccoon
- fox
- squirrel
- rabbit
- person
record:
enabled: true
alerts:
retain:
days: 30
pre_capture: 15
post_capture: 15
detections:
retain:
days: 30
pre_capture: 15
post_capture: 15
snapshots:
# Optional: Enable writing jpg snapshot to /media/frigate/clips (default: shown below)
# This value can be set via MQTT and will be updated in startup based on retained value
enabled: true
# Optional: save a clean PNG copy of the snapshot image
clean_copy: true
bounding_box: true
timestamp: false
crop: true
# Optional: height to resize the snapshot to (default: original size)
height: 175
objects:
# Optional: list of objects to track from labelmap.txt (default: shown below)
track:
- car
- motorcycle
- bicycle
- cat
- dog
- bear
- bird
- raccoon
- fox
- squirrel
- rabbit
- person
ffmpeg:
hwaccel_args: preset-vaapi
model:
path: plus://xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
## BEGIN Cameras and re-stream section
go2rtc:
streams:
front_door:
rtsp://user:[email protected]:554/cam/realmonitor?channel=1&subtype=0#loryta
cameras:
front_door:
ffmpeg:
output_args:
record: preset-record-generic-audio-copy
inputs:
- path: rtsp://user:[email protected]:554/cam/realmonitor?channel=1&subtype=1
roles:
- detect
- path: rtsp://127.0.0.1:8554/front_door
input_args: preset-rtsp-restream
roles:
- record
detect:
width: 854
height: 480
objects:
track:
- person
- dog
- cat
- bear
- deer
- bird
- raccoon
- squirrel
- rabbit
filters:
person:
min_area: 350
version: 0.15-0 Relevant Frigate log outputno relevant logs Relevant go2rtc log outputno relevant logs Frigate statsNo response Operating systemDebian Install methodDocker Compose docker-compose file or Docker CLI commandservices:
frigate:
container_name: frigate
# only so GPU stats can be seen
privileged: true
# restart: unless-stopped
restart: "no"
image: ghcr.io/blakeblackshear/frigate:0.15.0-beta1
shm_size: "512mb" # update for your cameras if needed. See shm_cameras.txt
# network_mode is host for webRTC
network_mode: "host"
devices:
- /dev/bus/usb:/dev/bus/usb
- /dev/dri/renderD128 # for intel hwaccel, needs to be updated for your hardware
volumes:
- /etc/localtime:/etc/localtime:ro
- /frigate/config/:/config/
- /frigate/media:/media/frigate
- type: tmpfs # Optional: 4GB of memory, reduces SSD/SD Card wear
target: /tmp/cache
tmpfs:
size: 4000000000
environment:
FRIGATE_RTSP_PASSWORD: "password"
PLUS_API_KEY: "redacted" Object DetectorCoral Screenshots of the Frigate UI's System metrics pagesNo response Any other information that may be helpfulNo response |
Beta Was this translation helpful? Give feedback.
Replies: 5 comments 1 reply
-
Please describe where you're looking and expecting to see the pre capture and where you're not seeing it. |
Beta Was this translation helpful? Give feedback.
-
FYI this is still the same in 0.15.0-beta2. I changed the category to "report a bug" because I think that's more appropriate. If I need to re-submit this in some other way, I can do that. |
Beta Was this translation helpful? Give feedback.
-
Still happens in 0.15.0-beta3. |
Beta Was this translation helpful? Give feedback.
-
@NickM-27 I can confirm that I am seeing the same issue in beta 3. I also have the same config as OP except mine is 10 seconds. the recording starts at the moment the object is spotted instead of 10 seconds before. |
Beta Was this translation helpful? Give feedback.
-
Fixed in #15598 |
Beta Was this translation helpful? Give feedback.
Fixed in #15598