0.12.0 Beta 1 #4859
Replies: 51 comments 231 replies
-
I read through everything but feel like I missed something...getting a nginx and go2rtc error on starting the container...I can open issue if needed
|
Beta Was this translation helpful? Give feedback.
-
Turned on debug logging and got a couple extra lines about readiness notification; not sure if that is helpful or not
|
Beta Was this translation helpful? Give feedback.
-
looks like path setting may need deleting again on my redeploy via portainer |
Beta Was this translation helpful? Give feedback.
-
Yep, good call @felipecrs...I forgot I have to delete the PATH variable and have it auto create again when re-deploying the container! Need to add that to my tech notes so I don't forget it! @NickM-27 thanks for the quick response..seems like things are working now! |
Beta Was this translation helpful? Give feedback.
-
This new release is awesome. It seems I will have to re-learn how to use Frigate with all these good stuff! |
Beta Was this translation helpful? Give feedback.
-
have another problem - address in use 5 lines from end of log
|
Beta Was this translation helpful? Give feedback.
-
docker image not found for me, strange |
Beta Was this translation helpful? Give feedback.
-
Is the beta also available with the addon? |
Beta Was this translation helpful? Give feedback.
-
I have noticed how great of a job @NickM-27 does (hackernews, reddit, here, he seems to be everywhere helping whenever frigate is mentioned). Donated, appreciate all the frigate team does! |
Beta Was this translation helpful? Give feedback.
-
Two issues so far for me.
I’m going to continue to investigate but thought I would post here in case anyone else was having the same issues. |
Beta Was this translation helpful? Give feedback.
-
None of my RTMP cameras are working. Here is the errors I am getting in the logs:
Here is the config for the camera:
Camera is the Reolink RLC-410-5MP My other non Reolink non RTMP input cameras appear fine |
Beta Was this translation helpful? Give feedback.
-
Also for those using Unraid, make sure you pass through port 8554 if you want to do any restream |
Beta Was this translation helpful? Give feedback.
-
I adjusted my config and updated to the latest container, no issues so far. Thanks! |
Beta Was this translation helpful? Give feedback.
-
Does the experimental UI not work with this release? I couldn't view the live feed pages when it was enabled. |
Beta Was this translation helpful? Give feedback.
-
@NickM-27 did the filtering by time end up making it? I can't really understand the way the pull system works: |
Beta Was this translation helpful? Give feedback.
-
For unRaid users, I have created 3 new beta Apps to test this beta.
Please if anyone can test them to be sure that everything works. At the moment they point to v12-beta1, but I will update the tags to point to the next betas as they are released. I separated the nvidia and not nvidia version for installation template simplicity. @DrSpaldo fyi |
Beta Was this translation helpful? Give feedback.
-
I'm having some issues using intel hardware acc:
I'm passing the unit to the container: On config file I have this:
|
Beta Was this translation helpful? Give feedback.
-
I get following error when I try to use the restream url as record role
|
Beta Was this translation helpful? Give feedback.
-
How much tmpfs cache are you guys using in the stats / storage section? Of my 1GB assigned I see only 6-12MB used, is that expected? I honestly thought it would have been closer to the 1GB mark! |
Beta Was this translation helpful? Give feedback.
-
I've just had a bit of an odd one, I had a notification - a person on one of the cameras as usual, it wasn't an in progress event, but a completed event. I went to view it and it wouldn't load on any device. A few minutes later and the event has gone! I thought that wasn't possible unless it was an "in progress" event or was a duplicate event? I don't think I have seen this before. |
Beta Was this translation helpful? Give feedback.
-
I have seen this error a few times in the console, after I view the camera images in the debug or live view. Not sure where to begin looking for the issue... any ideas?
for what its worth.. I am running the 0.12.0-beta1-tensorrt version on a dell 7050 Intel i7-6700T |
Beta Was this translation helpful? Give feedback.
-
Hi Team, running AMD 3800x CPU, Google TPU & AMD 390X GPU. |
Beta Was this translation helpful? Give feedback.
-
I don't suppose AMD GPU can be used like NVIDIA GPU for Detection can they? |
Beta Was this translation helpful? Give feedback.
-
Not sure what I've done wrong with this, but no matter what I do I keep getting the following error. 2023-01-06 08:40:56.839103659 ************************************************************* ##############################config.yml database: logger: ffmpeg: input_args:- -analyzeduration- 1024- -probesize- 1024############ Cameras!!!##############
############Backroom Camera#######
|
Beta Was this translation helpful? Give feedback.
-
Trying to migrate from beta 11 to beta 12. Can't start it due to this error:
I'm on Unraid. PGUI 100, PGID 99. |
Beta Was this translation helpful? Give feedback.
-
Home Assistant custom webrtc card pointing to Go2rtc api works from PC browser but from mobile browser/app, causes above error. |
Beta Was this translation helpful? Give feedback.
-
I have created a short survey for those that are using the new OpenVINO and TensorRT detectors. It will aid in understanding the expected performance for different devices and help identify other issues that may be occurring. Thanks! Answers can bee seen here |
Beta Was this translation helpful? Give feedback.
-
Would there be any disadvantages to running the cameras to go2rtc (in unraid) then running those feeds to Frigate? I am trying to get the lowest possible latency to a feed I have set up and currently use the restream from Frigate. I was wondering if this would reduce the latency if I get that feed before Frigate does.. |
Beta Was this translation helpful? Give feedback.
-
Thanks for the help earlier. Like I had said I didn't even have a problem from the last version. Anyway, I changed some things around with my config and now I get this. Even when i leave out the model path the s6 still fails.
######Config.yml Change detectors:
cpu1:
type: cpu
num_threads: 3
model:
path: /custom_model.tflite <---no matter if I have it "" or in '' I get the same error.
cpu2:
type: cpu
num_threads: 3
mqtt:
enabled: True
host: 10.0.0.26
database:
path: /media/frigate/frigate.db
logger:
default: info
logs:
frigate.event: debug
#######Global Camera Settings#######
#live:
# height: 720
# quality: 1
detect:
width: 1920
height: 1080
fps: 15
record:
enabled: True
events:
pre_capture: 15
post_capture: 15
retain:
default: 5
mode: active_objects
objects:
dog: 2
cat: 2
#rtmp:
# enabled: False
restream:
enabled: True
#ffmpeg:
# hwaccel_args:
# -hwaccel vaapi
# -hwaccel_device /dev/dri/renderD128
# -hwaccel_output_format vaapi
#ffmpeg:
# input_args:
# - -analyzeduration
# - 1024
# - -probesize
# - 1024
############ Cameras!!!##############
######Driveway Camera!!##########
cameras:
driveway:
ffmpeg:
output_args:
record:
-f segment
-segment_time 45
-segment_format mp4
-reset_timestamps 1
-strftime 1
-codec:v h264_vaapi
-global_quality 25
-acodec aac
-max_interleave_delta 0
-fps_mode passthrough
hwaccel_args:
-hwaccel vaapi
-hwaccel_device /dev/dri/renderD128
-hwaccel_output_format yuv420p
inputs:
- path: rtsp://10.0.0.35:8554/driveway
roles:
- detect
- record
- path: rtsp://username [email protected]:2600/media/ch0/stream0
roles:
- restream
objects:
track:
- person
- cat
- dog
filters:
person:
min_area: 5000
max_area: 100000
min_score: 0.5
threshold: 0.75
mask:
- 523,1080,897,0,0,0,0,1080
cat:
min_area: 5000
max_area: 100000
min_score: 0.5
threshold: 0.8
mask:
- 523,1080,897,0,0,0,0,1080
dog:
min_area: 5000
max_area: 100000
min_score: 0.5
threshold: 0.8
mask:
- 523,1080,897,0,0,0,0,1080
############Backroom Camera#######
backroom:
ffmpeg:
output_args:
record:
-f segment
-segment_time 45
-segment_format mp4
-reset_timestamps 1
-strftime 1
-codec:v h264_vaapi
-global_quality 25
-acodec aac
-fps_mode passthrough
hwaccel_args:
-hwaccel vaapi
-hwaccel_device /dev/dri/renderD128
-hwaccel_output_format vaapi
inputs:
- path: rtsp://10.0.0.36:8554/backroom
roles:
- detect
- record
- path: rtsp://username [email protected]:88/videoMain
roles:
- restream
objects:
track:
- person
- cat
- dog
filters:
person:
min_area: 5000
max_area: 100000
min_score: 0.5
threshold: 0.75
mask:
- 1920,330,1920,0,0,0,0,343
cat:
min_area: 5000
max_area: 100000
min_score: 0.5
threshold: 0.8
mask:
- 1920,330,1920,0,0,0,0,343
dog:
min_area: 5000
max_area: 100000
min_score: 0.5
threshold: 0.8
mask:
- 1920,330,1920,0,0,0,0,343 |
Beta Was this translation helpful? Give feedback.
-
I am running it succesfully on a Synology with the Also just tested
Anyone knows how to solve this |
Beta Was this translation helpful? Give feedback.
-
Major Changes for 0.12.0
❗❗Notice❗❗
I want to recognize @NickM-27 for all the contributions he made on this release and all the support he helps provide in the issues. If you have been considering sponsoring this project with either a one time contribution or a recurring contribution, I would request that you do so at his sponsors page.
Link to updated docs: https://deploy-preview-4055--frigate-docs.netlify.app/
BREAKING CHANGES
live
configuration has been moved torestream -> jsmpeg
./run: line 7: exec: nginx: not found
, then you need to stop overriding your PATH. This happens with both Proxmox LXC and Portainer ([Support]: Beta11 Can't Find FFMPEG #3223)Retention limited by available storage
Frigate now limits its recordings to available storage, if the storage for recordings gets below 1 hour left then Frigate will delete the oldest recording segments to make room for newer ones. Frigate will also not fail if there is no space to save recordings.
RTSP restreaming
Due to many issues with RTMP based restream, RTMP is now deprecated in favor of a new RTSP restream. This also comes with a new
restream
role which is enabled by default. The restream of a camera can be accessed atrtsp://frigate_ip:8554/config_camera_name
. The restream can also be used inside Frigate to reduce connections to the camera, see the restream docs for more info.Birdseye restreaming is also now supported at
rtsp://frigate_ip:8554/birdseye
NOTE: Port
8554
will need to be mapped in the docker run or docker compose file for the restream to be accessed outside the container.New live stream options
The new RTSP restream also enables new
MSE
andWebRTC
live view options in the frontend which enable low-latency full-framerate live views that support audio.NOTES:
The live view options are set in the Frigate WebUI for each camera individually.
New detector types
Frigate now supports new detector types along with the Google Coral TPU.
OpenVINO
The OpenVINO detector type runs an OpenVINO IR model on Intel CPU, GPU and VPU hardware. OpenVINO is supported on 6th Gen Intel platforms (Skylake) and newer. A supported Intel platform is required to use the GPU device with OpenVINO. The MYRIAD device may be run on any platform, including Arm devices. For detailed system requirements, see OpenVINO System Requirements
TensorRT
NVidia GPUs may be used for object detection using the TensorRT libraries. Due to the size of the additional libraries, this detector is only provided in images with the -tensorrt tag suffix. The TensortRT detector is able to run on x86 hosts that have an Nvidia GPU which supports the 11.x series of CUDA libraries. The minimum driver version on the host system must be >=450.80.02. Also the GPU must support a Compute Capability of 5.0 or greater. This generally correlates to a Maxwell-era GPU or newer, check the TensorRT docs for more info.
NOTE: The link in the docs is for the final release location, for the beta the script is located at https://raw.githubusercontent.com/blakeblackshear/frigate/dev/docker/tensorrt_models.sh
New system page
The
Debug
page has been renamed toSystem
. It now includes much more information and links to easily getvainfo
andffprobe
data.The GPUs section will show each GPU based on the hwaccel args, depending on the type of GPU different information is supported. For example Nvidia GPUs will have the name while others will be generic, also intel does not support memory usage. There is also a
VAINFO
button which will make it easier to diagnose hwaccel issues and verify that the hwaccel driver is being used correctly.Each camera will have their own process CPU & memory usage so it will be easier to see which process is using those resources. There is also an
FFPROBE
button which will be helpful to understand what each stream is presenting and make it easier to include that in support issues.The debug config has also been removed, the config can be copied using the config page in the WebUI.
New storage page
Frigate WebUI now has a built in storage page which shows the general usage for both storage and memory. It also shows a per-camera storage usage and stream bandwidth. This should make it a lot easier to have a general idea how much storage is being used by each camera.
New logs page
Frigate WebUI now has built in logs, this will make copying and viewing logs much easier. Currently the logs are static meaning the page must be refreshed to view new logs.
New config editor
Frigate WebUI now has a built in config editor with syntax highlighting and schema validation. This means that the config will be validated before it can be saved which will make yaml config much easier to manage.
NOTE: The previous docker-compose or docker CLI may have had the /config.yml set to
:ro
or read-only. That will need to be removed for the config editor to be able to save the new file.MQTT is now optional
Frigate no longer requires MQTT to function, MQTT is also setup asynchronously so errors will be more clear and frigate won't stop when mqtt is enabled but not setup correctly.
NOTE: MQTT is still required for the Frigate-HomeAssistant Integration
No changes are needed for existing users.
FFMpeg presets
FFMPEG presets for common configurations are now added, making the config cleaner and allowing the underlying args to be changed between releases without being a breaking change. It is highly recommended to update the configuration to use these presets.
Example: Enabling Audio In Recordings
before:
after:
This also enables presets for hardware acceleration which will be used to further reduce CPU usage by using the GPU to optimize scaling and other workloads.
Improved events filters
Recordings updates
Recording segments are now stored in UTC to avoid issues with DST. In order to avoid a breaking change, the path of the stored segments has changed from
/media/frigate/recordings/%Y-%m/%d/%H-%s.mp4
to/media/frigate/recordings/%Y-%m-%d/%H-%s.mp4
.Recordings in the frontend are now shown in the timezone of the device viewing frigate, so the timezone set on the server running frigate is irrelevant.
No changes are needed for existing users.
What's Changed
-user_agent
forrtmp
streams by @felipecrs in Do not apply-user_agent
forrtmp
streams #4596New Contributors
Full Changelog: v0.11.1...v0.12.0-beta1
Images:
blakeblackshear/frigate:0.12.0-beta1
ghcr.io/blakeblackshear/frigate:0.12.0-beta1
blakeblackshear/frigate:0.12-beta1-tensorrt
ghcr.io/blakeblackshear/frigate:0.12.0-beta1-tensorrt
This discussion was created from the release 0.12.0 Beta 1.
Beta Was this translation helpful? Give feedback.
All reactions