0.10.0 Beta 6 #2447
Replies: 13 comments 34 replies
-
Beta Was this translation helpful? Give feedback.
-
For your info @blakeblackshear my frozen RTMP and WebUI are gone with the Beta6.
|
Beta Was this translation helpful? Give feedback.
-
Is it too late for a feature request? It'd be nice to have a configurable recording length for each Thanks I search int the source code. Looks like the temp recording is first written to |
Beta Was this translation helpful? Give feedback.
-
Loving the hourly footage deletion, can we please get the same for snapshots? I can see the footage getting deleted every hour, but the snapshots and images are getting deleted at differing intervals. And then can we get options for longer intervals as per this request - #2365 |
Beta Was this translation helpful? Give feedback.
-
Just updated to this beta from 0.90.0 and everything seems to be running well so far. As it's already been mentioned, noticing a lot of the "Cache is taking longer than 5 seconds to clear" but that's about it. I do like the new stationary object logic. I have a zone setup that covers the sidewalk in front of our house and just a small part of the street. The idea was to record vehicles that would park in front of our house but ignore everything driving by on the street. Previously, this would cause a ton of events for a vehicle parked in front of our house whenever a car drove by (especially at night when lights hit the parked car). Now there seems to be a lot less of those false events since it's tracking the parked car continuously, but it does seem to end every once in a while and start a new event when a vehicle drives by. |
Beta Was this translation helpful? Give feedback.
-
Can you share a config for that camera as I'm bit confused - wanted to use zones for specific cameras but only way I've got this working is list zones I want to record inside required_zones (record->events->required_zones), as I understand this I'll have events recorded only for those zones - what if I want to use zones for lets say two cameras and for rest rely on mask with no zones? |
Beta Was this translation helpful? Give feedback.
-
Is there a difference in how frigate handles notifications in v.0.10 as it's not sending the snapshots for notification previews and when I press view snapshot I get an error 502 bad gateway. It was working fine on v.0.9. I'm using the notification blueprint. |
Beta Was this translation helpful? Give feedback.
-
You note: " For example, a car that enters the driveway, parks, and then leaves 5 hours later will be one continuous event. " This is definitely happening to me and its consuming a great deal of disk space. Under retain you use "active-objects" which is confusing since its also recording stationary objects. Perhaps I misinterpreted? My record config:
|
Beta Was this translation helpful? Give feedback.
-
Just migrated from the latest stable to this beta and looking good so far. Anyone got an automated method for deleting all the 24/7 clips that do not have any motion associated with them? I'd like to trim down all of the clips rather than just delete entire days or have to manually go through and work out which clips correspond to which events. Is there a way to pull the info out of the DB? I can then automate from there. |
Beta Was this translation helpful? Give feedback.
-
@kiat-huang You should read the docs for the beta, that is already something that is supported within frigate itself: record:
retain:
days: x
mode: [all, motion, active_objects] |
Beta Was this translation helpful? Give feedback.
-
Anyone knows why the recordings of my events stop working after a few hours since 0.10? I changed my retain settings like this:
If a new event is triggered it shows up in the events tab and works perfectly, if I come back a few hours the event and snapshot are still there but the recording is gone. Trying to stream the m3u8 file returns an nginx 404. Trying to download the MP4 gets a timeout with the following error being logged:
If I look into the /media/frigate folder I can see that the recordings folder is completely empty but the clips folder has the clips saved. Any ideas why it's trying to access the empty recordings folder? If I look into the folder directly after recording I can see the recording there just fine. edit: Looking at a recording with debug logs enabled it seems that it gets deleted during routine cleanup but Frigate then complains that it can't find the file it just deleted?
Even though it says "Expiring 0 recordings" the files are gone afterwards? |
Beta Was this translation helpful? Give feedback.
-
I have a question regarding CPU utilization in Frigate. I have 4 cameras setup, and when there is no motion detected, my cpu utilization is about 35%. If I look at the process specifics in Glances, most of this is used by 4 "ffmpeg" processes. This makes sense, since these are required to detect motion. However, if I turn off the detection switches for all 4 cameras, the cpu utilization remains the same. Is this expected? I would think that if detection were disabled these processes would not be required. Just trying to understand how this works. BTW, this is true even if I disable snapshots and recordings for all 4 cameras. Thanks |
Beta Was this translation helpful? Give feedback.
-
Locking this discussion and moving to beta 7 |
Beta Was this translation helpful? Give feedback.
-
Major Changes for 0.10.0
Updated docs are available for preview here.
Changes since beta 5
Retain modes
This release adds the ability to define retain modes for the initial retention period and for event data beyond the initial retain period. There are three modes:
The default record settings will retain only segments that have active_objects for events.
Note that the
retain_days
config entry has been DEPRECATED. This release includes backwards compatibility, but you should migrate to the new format.Example: Store all segments with motion for 7 days and events with active objects for 14 days.
Stationary objects
Frigate will now continue to track objects after they are stationary. This enables use cases such as presence detection. After an object has been stationary for 10 frames, object detection for the object will be throttled to 1 frame every 10 seconds (this is adjustable with the new
stationary_interval
setting) until there is new movement. An object is determined to be stationary if the bounding box in the current frame overlaps almost entirely with the previous frame. I have been testing this in my home office, and it works quite well.I expect this to disrupt the way a few people are using Frigate. For example, a car that enters the driveway, parks, and then leaves 5 hours later will be one continuous event. The zones will stay with the tracked object over this lifetime, so when the car leaves, it will still have zones associated from when it first arrived. Ensure you use the right retain mode to ensure you only capture the segments you want.
Depending on the specifics of your room, you may need to tune your resolution and motion settings to get the results you want. In my office, I reduced the resolution to 640x360 and increased the
contour_area
setting for motion detection up to 125 to reduce the sensitivity. I recommend watching the debug view and adjusting as needed.fixes #841
In progress events and cache handling
Events are now stored in the database while in progress, so you can expect to see
In progress
for some events under end time in the Events view.Recording segments written to the cache are now only moved to the recordings folder if they overlap with an event (in-progress events too). For those with
retain_days
set to 0, this eliminates disk I/O when there are no events. Frigate will no longer store a minimum of 5 minutes of recording segments for each camera, so now you can enable recording without worrying about SD/SSD wear.Lastly, more proactive cache maintenance was implemented to prevent the cache disk from filling up. You should never see more than 7 segments in the cache for each camera. If the cache maintenance job is too slow, you will get a warning in the logs. You can also see the time it takes to copy to the recordings disk by setting
frigate.record: debug
in the logger config. Additional error handling was also implemented to prevent the cache maintenance thread from stopping on errors.Now that recordings are managed proactively, recordings are expired according to the retention settings once per hour.
fixes #1885
Motion detection improvements
0.9.0 introduced dynamic motion sensitivity which didn't work out well. For many users, this made motion detection too sensitive which increased CPU usage due to more motion causing more object detection. It also increased false positive detections due to the increased frequency for detections on areas without substantial motion.
In this release, motion detection has been reset back to better defaults for
frame_height
andcontour_area
. If you have customized eitherframe_height
orcontour_area
in the past, it is recommended that you remove those for your camera and let them revert back to the new defaults. For most users, the sensitivity can be tuned by adjustingcontour_area
(smaller numbers are more sensitive and larger numbers are less sensitive). For very high resolutions with very small objects, theframe_height
may need to be increased.In addition, this release brings about dynamic contrast adjustment for motion detection. Based on my testing, this substantially improves night time detection with IR lights and other low contrast situations.
Other changes
Fixes
Full Changelog: v0.9.4...v0.10.0-beta6
Images:
blakeblackshear/frigate:0.10.0-beta6-amd64
blakeblackshear/frigate:0.10.0-beta6-amd64nvidia
blakeblackshear/frigate:0.10.0-beta6-armv7
blakeblackshear/frigate:0.10.0-beta6-aarch64
This discussion was created from the release 0.10.0 Beta 6.
Beta Was this translation helpful? Give feedback.
All reactions