0.12.0 Beta 2 #4948
Replies: 29 comments 152 replies
-
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.
-
About tensort container, is there any specific reason to use 22.07-py3? Is better to use the latest avaible tag in this case 22.12-py3? Thanks |
Beta Was this translation helpful? Give feedback.
-
I wanted to react on the Beta1 discussion, but it seems to be closed. I know that my VAAPI is working, but I am wondering if I can get this to work under |
Beta Was this translation helpful? Give feedback.
-
UnRaid betatesters you need to uninstall and install again the beta apps from CA. I tested both nvidia and classic and both are running fine in my system. |
Beta Was this translation helpful? Give feedback.
-
I just modified old template to suit 0.12 needs but I'm struggling with webrtc - everything else works as intended. Do I need to install go2rtc along and if so - it uses 1954 port which your template uses too... |
Beta Was this translation helpful? Give feedback.
-
when setting up the models in the config file for tensorRT how do we know what model to use and its width and height? |
Beta Was this translation helpful? Give feedback.
-
Alright guys I'm back and getting the same error "Address Already in use"
detectors:
cpu1:
type: cpu
num_threads: 3
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#######
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
restream:
enabled: True
############ 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://usernamepassword@10.0.0.2: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://usernamepassword@10.0.0.36: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 I tried changing ports ie 5000 to 5006 or whatever which didn't change anything. |
Beta Was this translation helpful? Give feedback.
-
Stream issue over vpn/cellular I am testing Frigate 0.12.0Beta2 with Home Assistant using the webrtc pointing to go2rtc api included in Frigate. On local lan everything works without any error. When I use cellular connection on my phone and access HA over vpn, I see following errors in HA. 2023-01-07 15:52:09.734 ERROR (MainThread) [frontend.js.latest.202301040] http://192.168.0.10:8123/webrtc/video-rtc.js:563:33 NotFoundError: The object can not be found here 2023-01-07 16:35:06.875 ERROR (MainThread) [frontend.js.latest.202301040] http://srv.home.com:8123/webrtc/video-rtc.js:402:31 Uncaught InvalidStateError: Failed to read the 'buffered' property from 'SourceBuffer': This SourceBuffer has been removed from the parent media source. type: custom:webrtc-camera Anyone else seen this issue? I wonder if this is due to slow network or something else. If I use Frigate card in HA it does show the camera feed over vpn but there is about 18sec latency. Additional update:
|
Beta Was this translation helpful? Give feedback.
-
Just upgraded from 0.11.1 and unfortunately having some issues.
mqtt:
host: 172.16.16.1
user: username
password: password
cameras:
front:
ffmpeg:
inputs:
# - path: rtsp://localhost:8854/front
# roles:
# - detect
- path: rtsp://username:password@172.16.20.1:554/cam/realmonitor?channel=1&subtype=2
roles:
- detect
- restream
- path: rtsp://username:password@172.16.20.1:554/cam/realmonitor?channel=1&subtype=0
roles:
- record
objects:
track:
- person
- vehicle
- animal
record:
events:
required_zones:
- sidewalk
- driveway
snapshots:
required_zones:
- sidewalk
- driveway
zones:
sidewalk:
coordinates: 0,741,1533,339,1359,286,921,350,0,561
driveway:
coordinates: 468,1080,1920,1080,1920,583,1785,519,1620,646,1121,484,304,701
motion:
mask:
- 1510,354,1920,285,1920,0,1324,0
- 0,1080,250,1080,147,675,0,703
side:
ffmpeg:
inputs:
# - path: rtsp://localhost:8854/side
# roles:
# - detect
- path: rtsp://username:password@172.16.20.2:554/cam/realmonitor?channel=1&subtype=2
roles:
- detect
- restream
- path: rtsp://username:password@172.16.20.2:554/cam/realmonitor?channel=1&subtype=0
roles:
- record
objects:
track:
- person
- animal
motion:
mask:
- 244,0,254,285,435,273,430,79,1641,1080,1920,1080,1920,0
improve_contrast: True
threshold: 15
back:
ffmpeg:
inputs:
# - path: rtsp://localhost:8854/back
# roles:
# - detect
- path: rtsp://username:password@172.16.20.3:554/cam/realmonitor?channel=1&subtype=2
roles:
- detect
- restream
- path: rtsp://username:password@172.16.20.3:554/cam/realmonitor?channel=1&subtype=0
roles:
- record
objects:
track:
- person
- animal
motion:
mask:
- 1357,48,1666,101,1920,201,1920,0,0,0,0,79
inside:
ffmpeg:
inputs:
- path: rtsp://localhost:8854/inside
roles:
- detect
- path: rtsp://username:password@172.16.20.4:554/cam/realmonitor?channel=1&subtype=2
roles:
- restream
- path: rtsp://username:password@172.16.20.4:554/cam/realmonitor?channel=1&subtype=0
roles:
- record
motion:
mask:
- 1920,0,1920,74,633,72,637,0
record:
enabled: True
retain:
days: 7
mode: all
events:
retain:
default: 14
mode: active_objects
detect:
width: 1920
height: 1080
model:
labelmap:
2: vehicle
3: vehicle
5: vehicle
7: vehicle
15: animal
16: animal
17: animal
ffmpeg:
# hwaccel_args: -hwaccel vaapi -hwaccel_device /dev/dri/renderD128 -hwaccel_output_format yuv420p
hwaccel_args: preset-vaapi
output_args:
# record: -f segment -segment_time 10 -segment_format mp4 -reset_timestamps 1 -strftime 1 -c copy
record: preset-record-generic-audio
detectors:
coral:
type: edgetpu
device: pci |
Beta Was this translation helpful? Give feedback.
-
Incredible work on this. Thank you very much. Beta 2 running like an absolute champ. I do have one question- I am on an intel 12700k cpu, which comes with the openvino 3.0 compatible Intel GNA; I set Frigate to use openvino AUTO and by golly the cpu is hardly being touched. Is it using the Intel GNA? If so, Frigate and an Alderlake processor make a pretty cool combo. 😎 |
Beta Was this translation helpful? Give feedback.
-
I am helping a friend set his up and he is using the Annke C800 cameras. I noticed in the new config; https://deploy-preview-4055--frigate-docs.netlify.app/configuration/camera_specific It still refers to rtmp and not restream in a few places, is that still correct or does it need to be changed to restream? The link also has H264 when the camera doesn't support that? |
Beta Was this translation helpful? Give feedback.
-
https://deploy-preview-4055--frigate-docs.netlify.app/configuration/camera_specific/ Looking at the Annke C800 on this site is restream in place of rtmp also when viewing from mse no image shows Only see image with jsmpeg with no sound When in mse,webrtc i have image in debug only. |
Beta Was this translation helpful? Give feedback.
-
Any idea why 2 of my cameras are showing as 5fps and are using 7-8% cpu for ffmpeg when I have detect disabled on them? They are both set at 15fps and are only used to record 24/7, detection not neccessary. I didn't think ffmpeg did any converting when only recording?
|
Beta Was this translation helpful? Give feedback.
-
Tried Beta 2 and I'm so impressed - great work! One issue, in the log I see: Any idea why? Running on Ubuntu Linux and using Docker Compose. |
Beta Was this translation helpful? Give feedback.
-
The documentation is a little sparse on Restream at the moment, which is to be expected, but I'd like a little more clarification on maintaining a single connection to the cameras. From what I've read it seems this is the only way to maintain a single connection to the camera:
So would it be correct to assume this will create two connections? And if so, surely there's a way to simplify it or handle it in the background so a new path doesn't have to be manually defined for each one.
|
Beta Was this translation helpful? Give feedback.
-
anyone have a live stream url working via actionable HA notification? what ive been using is this: |
Beta Was this translation helpful? Give feedback.
-
and i'm seeing
|
Beta Was this translation helpful? Give feedback.
-
I get this error when trying to save the config file.. I am sure its an easy fix.. does something need to be added to the docker compose file? |
Beta Was this translation helpful? Give feedback.
-
@yayitazale do you get these errors in your logs?
I am getting 30-40 per day |
Beta Was this translation helpful? Give feedback.
-
Has anyone else noticed increased instances of getting the "No frames have been received, check error logs" error on the 0.12 betas? Seems to happen every night (sometimes randomly during the day) on different camera(s) but can't seem to figure out the cause. Cameras aren't set to restart or anything and it's odd they don't recover like pre-v0.12.0. Restart usually fixes it though. I can't tell if the logs are helpful in this but just turned on debugging to see if that shows anything useful for tonight.
|
Beta Was this translation helpful? Give feedback.
-
after the latest rc.7 release of webrtc in beta2 getting weird stream of reolink camera its a h264 5mp source cam but webrtc seems to be streaming it out at 240FPS. Direct stats from cam:
Direct stats from webrtc
The FFMPEG cmds for this cam is:
|
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
Hello, Running 0.12b2 as HA addon. To enable restream I add to overwrite default network config restream port to 8554 I can't get Webrtc to work. When i hit the button in the Nginx log I have this
but nothing in the go2rtc log
I created a frigate-go2rtc.yaml as described in docs. I port forwarded 8555 in my router. Am I missing something ? A way to "open" API port ? |
Beta Was this translation helpful? Give feedback.
-
Ok looks like I have most of my cameras running, I just need help with using my GPU AMD PCIe card to help.
|
Beta Was this translation helpful? Give feedback.
-
Amazing progress! So much new, great stuff. Would it be possible, at some point, to get an option to set the timezone of the Frigate location? When managing homes on multiple continents or simply traveling, it can get annoying and confusing to have to do a bit of mental arithmetic whenever you're looking at events or recordings. The system timezone is probably not the right option either, since that tends to be set to UTC on most servers. Please let me know if this is the wrong place to discuss this and if I should create a feature request instead. |
Beta Was this translation helpful? Give feedback.
-
Very nice. Those acceleration presets are nice, and something got fixed either in Ubuntu/Linux firmware or ffmpeg or something in the latest few releases acceleration finally works on my Alder lake CPU now. I tried everything before to get it to work but had weird driver issues, it's now cleared up. |
Beta Was this translation helpful? Give feedback.
-
I have not seen this error before... everything has been running great lately. It has not come up again.
|
Beta Was this translation helpful? Give feedback.
-
@yayitazale do i need to select the gpu in the device setup. |
Beta Was this translation helpful? Give feedback.
-
I'm a bit confused, and before I open an issue, I was hoping to get some clarification here. My setup is HassOS with the HassOS addon. Clearly in the minority because all I see is Docker Compose and I have absolutely no clue about Docker. I have 0.12.0 Beta 2 and 4.0.0 beta 2 and WebRTC 3.0-beta 4. Any way, here are my questions:
Is this something that needs to be done for addon users as well? There still are Docker components?
So as an addon user I have to create a go2rtc.yaml somewhere and have frigate-go2rtc.yaml as well?
This seems to concern addon users as it refers to frigate-go2rtc.yaml. I need a nudge in the right direction. I assume I don't have Docker Compose as it's not installed. Docker CLI does, so is this done with docker run? |
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/
Changes Since Beta 1
preset-intel-vaapi
andpreset-amd-vaapi
have been renamed topreset-vaapi
due to there being no differences between themrestream -> video_encoding
option which can be used to re-encode the restreamNone
optionBREAKING CHANGES
./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 the database will need to be deleted to roll-back successfully.live
configuration has been moved torestream -> jsmpeg
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.
See https://deploy-preview-4055--frigate-docs.netlify.app/configuration/ffmpeg_presets for more info on how these should be used.
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-beta2
ghcr.io/blakeblackshear/frigate:0.12.0-beta2
blakeblackshear/frigate:0.12.0-beta2-tensorrt
ghcr.io/blakeblackshear/frigate:0.12.0-beta2-tensorrt
This discussion was created from the release 0.12.0 Beta 2.
Beta Was this translation helpful? Give feedback.
All reactions