0.12.0 Beta 4 #5131
Replies: 19 comments 110 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 be seen here |
Beta Was this translation helpful? Give feedback.
-
|
As I wrote before: great change: much simpler solution and elegant configuration of cameras and streams. After separating both everything works perfectly the last 4 hours. And most of it will be copy/paste and only changing the name of the stream/camera. Especially the birdseye stream is perfect now and very fast. Thanks! |
Beta Was this translation helpful? Give feedback.
-
|
I just updated and everything appears fine in the frigate UI, however home assistant has all the cameras as unavailable. Here is the changes I made from beta3 to beta4: Is there something obvious I missed during the config migration? |
Beta Was this translation helpful? Give feedback.
-
|
@onedr0p yes and then we changed stuff, so there will need to be a new beta for the integration |
Beta Was this translation helpful? Give feedback.
-
|
Thanks @NickM-27, that was not clear on the release notes. I'll wait for the update to come thru in hass. |
Beta Was this translation helpful? Give feedback.
-
|
updated the release notes accordingly |
Beta Was this translation helpful? Give feedback.
-
No, but recommended. :) |
Beta Was this translation helpful? Give feedback.
-
I'll have to tinker with it a bit because I know there's some custom stuff I'm doing to get audio working with unifi protect. |
Beta Was this translation helpful? Give feedback.
-
|
(I'm loving the changes) I've tried the sub-stream config, but it doesn't seem to be using it for the live view in Frigate: go2rtc:
streams:
front: ffmpeg:rtsp:https://192.168.0.42/ISAPI/Streaming/channels/101/
front_low: ffmpeg:rtsp:https://192.168.0.42/ISAPI/Streaming/channels/102/
cameras:
front:
ffmpeg:
output_args:
record: preset-record-generic-audio-copy
inputs:
- path: rtsp:https://localhost:8554/front?video=copy&audio=copy # <--- the name here must match the name of the camera
input_args: preset-rtsp-restream
roles:
- record
- detect
live:
stream_name: front_lowThe live view in Frigate however is still the main stream, not the sub-stream (the camera overlays a date/time that's quite visibly different in the different streams). I even tried pointing it at an entirely different camera feed to be sure. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks, looks like I was checking for the name but failed to use it. Will fix. |
Beta Was this translation helpful? Give feedback.
-
|
Is there anything special that needs to be done for HTTP based Reolink cameras? I'm using this: and the following camera config: I don't get the video and see the following errors. |
Beta Was this translation helpful? Give feedback.
-
|
And it was working with beta3 right? I'd suggest making an issue on go2rtc repo with those logs and noting it worked on the previous beta. |
Beta Was this translation helpful? Give feedback.
-
|
Okay. One question on your Reolink cameras, what do you have set for the Max Bitrate and H.264 profile? |
Beta Was this translation helpful? Give feedback.
-
|
I have the 511WA, Doorbell WiFi, and the E1 Zoom. All are high profile. The first two have max bitrate set to 6000kbps and the e1 zoom is 3000kbps (or whatever the closest option is) |
Beta Was this translation helpful? Give feedback.
-
|
What's the downside of using the Reolink RTSP or RTMP feed? |
Beta Was this translation helpful? Give feedback.
-
|
Reolink rtsp is known to have smearing of pixels due to bad compression. Rtmp is exactly the same as http just different protocol |
Beta Was this translation helpful? Give feedback.
-
|
I'm trying to update to beta 4, but I can't get it to work. I have the following config: This results in the following error: Does the {FRIGATE_RTSP_PASSWORD} still work with the go2rtc? Or is there something else I'm doing wrong? |
Beta Was this translation helpful? Give feedback.
-
|
Like it says at the release notes, variable substitution is not currently supported |
Beta Was this translation helpful? Give feedback.
-
|
I've changed it, now I get the following error: |
Beta Was this translation helpful? Give feedback.
-
|
try removing the |
Beta Was this translation helpful? Give feedback.
-
|
Thanks that worked. Current config looks like this: If I delete: It's still working. So can I leave it out? Or does this affect performance? |
Beta Was this translation helpful? Give feedback.
-
there's a reason we recommend it, otherwise there is a good chance your recordings will be stuttery / have hitching |
Beta Was this translation helpful? Give feedback.
-
|
Can't start up with my previous config, I don't want to use the restream stuff yet, is there something I need to disable somehow for go2rtc? |
Beta Was this translation helpful? Give feedback.
-
|
I disagree. After all, Frigate needs go2rtc even if user hasn't set anything on it. |
Beta Was this translation helpful? Give feedback.
-
|
For live view... for birdseye restream... actually I'm almost giving up this idea of allowing users to disable go2rtc entirely. :) |
Beta Was this translation helpful? Give feedback.
-
If camera stream isn't defined under go2rtc streams then jsmpeg is the only option for live view. |
Beta Was this translation helpful? Give feedback.
-
|
Interesting, but there's still the birdseye. Users don't need to have anything set under go2rtc for using birdseye rtsp. |
Beta Was this translation helpful? Give feedback.
-
|
Correct, probably better to always have go2rtc running. |
Beta Was this translation helpful? Give feedback.
-
|
I'm having a bit of trouble understanding the roadmap. How close to "done" is this beta? is there a list of things that need to be addressed before it goes to release? Or a plan for how many Betas? |
Beta Was this translation helpful? Give feedback.
-
|
There's no plan for how many betas, it's basically "ready when it's ready" sort of approach (from my perspective anyway). I believe it is considered ready when the confidence is high that all known issues have been dealt with. With beta3 it became clear that the restream approach was causing too much complexity so it was rewritten. After the betas there will be release candidates and then stable. |
Beta Was this translation helpful? Give feedback.
-
|
Is there somewhere to see where the blocking bugs are? When I look at the issues page it's hard to tell what's Beta4 vs the current release, vs something else. Is there a tag to search for? |
Beta Was this translation helpful? Give feedback.
-
|
I'm doing my best to tag issues related to the beta as beta. |
Beta Was this translation helpful? Give feedback.
-
|
Something that can help is Projects: https://github.com/blakeblackshear/frigate/projects But honestly I'd rather spend time in fixing the issues rather than organizing them. :P |
Beta Was this translation helpful? Give feedback.
-
|
Beautiful. Definitely an improvement. Everything seems to be working great including WebRTC externally. My Reolink RLC-810A is behaving great so far without the previous input args like so: This is with the resolution set to the one below 4K. @themoosman |
Beta Was this translation helpful? Give feedback.
-
|
I am getting following error when starting beta 4 in docker with or without streams config in go2rtc |
Beta Was this translation helpful? Give feedback.
-
|
this will be fixed, but you need to include the go2rtc config inside of the frigate config file. |
Beta Was this translation helpful? Give feedback.
-
|
Ok, and I see the instruction - always read it 3 times :) |
Beta Was this translation helpful? Give feedback.
-
|
So I'm getting the same error "Address already in use netstat -tulpn (while frigate is running) config.yml
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
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
############ Cameras!!!##############
######Driveway Camera!!##########
go2rtc:
streams:
driveway: rtsp:https://username:[email protected]:2600/media/ch0/stream0
backroom: rtsp:https://username:[email protected]:88/videoMain
cameras:
driveway:
ffmpeg:
output_args:
record: preset-record-generic-audio-aac
hwaccel_args: preset-vaapi
inputs:
- path: rtsp:https://127.0.0.1:8554/driveway
input_args: preset-rtsp-restream
roles:
- record
- detect
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: preset-record-generic-audio-aac
hwaccel_args: preset-vaapi
inputs:
- path: rtsp:https://127.0.0.1:8554/backroom
input_args: preset-rtsp-restream
roles:
- record
- detect
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.
-
|
Did you try removing the ports section in your docker compose and running? |
Beta Was this translation helpful? Give feedback.
-
Yes, same error |
Beta Was this translation helpful? Give feedback.
-
|
I'm honestly stumped on this one. It's like Frigate is somehow trying to run multiple things on the same port in it's own container somehow. I really don't understand how it's possible that only you are experiencing this. You are on synology, right? Maybe there is something special about that I am not aware of. |
Beta Was this translation helpful? Give feedback.
-
|
Have you tried running with the smallest config possible? Try to eliminate as much as you can to try and narrow it down further. |
Beta Was this translation helpful? Give feedback.
-
|
You can use go2rtc config to disable all those ports internally |
Beta Was this translation helpful? Give feedback.
-
|
went on beta3, everything works just fine, after beta4, i had some issues with two cameras, i've got 5 cameras same brand and model and one in frigate is having problems, no recording and no displaying, even if with vlc and imou app is working. Also i have 2 cameras that are recordin with no video only audio but in beta3 was ok. im receiving this error if i wait long, camera looks online and ok but no recordings dormitorio: ffmpeg:rtsp:https://admin:[email protected]:554/cam/realmonitor?channel=1&subtype=0
dormitorio_sub: ffmpeg:rtsp:https://admin:[email protected]:554/cam/realmonitor?channel=1&subtype=1
dormitorio:
ffmpeg:
output_args:
record: preset-record-generic-audio-copy
inputs:
- path: rtsp:https://127.0.0.1:8554/dormitorio_sub?video=copy&audio=aac
input_args: preset-rtsp-restream
roles:
- detect
- path: rtsp:https://127.0.0.1:8554/dormitorio?video=copy&audio=aac
input_args: preset-rtsp-restream
roles:
- record
detect:
width: 640
height: 360
fps: 5
record:
retain:
days: 18
mode: motion
events:
retain:
default: 18
mode: active_objects
objects:
track:
- person
mqtt:
height: 500
# Optional: jpeg encode quality (default: shown below)
quality: 99
live:
stream_name: dormitorio_subUpdate!! Also two cameras ezviz have the same issue and recording without video only audio the error is but if i use normal input preset not the restream is working, must be something with the presets |
Beta Was this translation helpful? Give feedback.
-
|
For your go2rtc streams you're not defining extra values so there's no reason to use Also there is no stream limit. |
Beta Was this translation helpful? Give feedback.
-
Hi , do i need to define extra parameters? i assume video and audio is copied |
Beta Was this translation helpful? Give feedback.
-
|
if you supply nothing then video and audio is copied. If you put |
Beta Was this translation helpful? Give feedback.
-
thanks i will try now and come bak to you. |
Beta Was this translation helpful? Give feedback.
-
it works!! thanks for your help |
Beta Was this translation helpful? Give feedback.
-
|
guess i found a bug, 0.12.0-beta4 create config.yml as a directory, not as a file. docker: error log: |
Beta Was this translation helpful? Give feedback.
-
|
BTW, if we change the recommendation from
|
Beta Was this translation helpful? Give feedback.
-
|
Hm... they gave up on deprecating it. The latest docs says: Even though there is no plan to deprecate --volume, usage of --mount is recommended. |
Beta Was this translation helpful? Give feedback.
-
|
i upgraded from beta3 to beta4 and i tried to start up with the old valid config.yml wich was surely present in this directory, but i leaved it with :ro in the beginning. i fall back now to where i started, here the result (only removed the :ro from docker): log: so, does go2rtc become a must? frigate doesnt rewrite the config, isnt it? |
Beta Was this translation helpful? Give feedback.
-
|
this is a bug that has already been fixed, but for now you can just add go2rtc:
enabled: falseand it will solve the issue |
Beta Was this translation helpful? Give feedback.
-
|
Or just: go2rtc: {} |
Beta Was this translation helpful? Give feedback.
-
|
Updated to beta 4. Everything seems to work, except the live view. When click on a camera image, nothing happens. I see this in the console on Chrome:
Birdsey is working as expected. For every camera I have a config like this: Also tried to add this, but no result: Any thoughts? |
Beta Was this translation helpful? Give feedback.
-
|
That change fixed it! Thank you very much for your help! |
Beta Was this translation helpful? Give feedback.
-
I would suggest mentioning this at the top of this thread under "Changes Since Beta 3" given that Frigate won't start without this, so it's a pretty breaking change. |
Beta Was this translation helpful? Give feedback.
-
|
It's a bug and it was corrected already. This is why this is still beta :) |
Beta Was this translation helpful? Give feedback.
-
|
I'm aware of that. I just think that if you're going to go to the trouble of highlighting to us beta testers "changes since the previous beta", it's probably worth highlighting that the application won't even start unless you add a missing piece of (previously optional) config. |
Beta Was this translation helpful? Give feedback.
-
|
Yeah, I think it won't hurt mentioning the "known issues" in the beginning. |
Beta Was this translation helpful? Give feedback.
-
|
The WebRTC live view in Frigate is not working with following in beta 4 (it was working in beta 3). Anything I am missing? |
Beta Was this translation helpful? Give feedback.
-
|
easier to read |
Beta Was this translation helpful? Give feedback.
-
|
Can you try using |
Beta Was this translation helpful? Give feedback.
-
|
Doesn't apper to be any difference |
Beta Was this translation helpful? Give feedback.
-
|
there's a typo in your config. You have |
Beta Was this translation helpful? Give feedback.
-
|
ugh! sorry about that - that fixed it. Thanks for finding my mistake and appreciate your help again @NickM-27 |
Beta Was this translation helpful? Give feedback.
-
|
I was stuggleing with my no name cams, which worked perfect in beta3 but not reliable in beta4. ProblemAfter starting frigate i got may errors in go2rtc and frigate. Then after a while (3-6 min.) all camaeras find their way to operate and the errors disappear ..). frigate log: ffprobe: frigate config: Solution:I tried many things, but what helped was to add "#backchannel=0" to the stream! Maybe this helps others too! I have one additional question: I do not use the ffmpeg:rtsp audio enhancement, but in Frigate I can use both, MSE (a little bit slower) and Webrtc (really fast) too. My camera seems to provide audio PCM only. Why does both work? In the readme there is noticed that aac and pcm/opus needs to be there... |
Beta Was this translation helpful? Give feedback.
-
|
MSE requires AAC for audio, are you saying audio works in both? That wouldn't make sense, but video working does make sense for both. |
Beta Was this translation helpful? Give feedback.
-
|
Ah got it! |
Beta Was this translation helpful? Give feedback.
-
Correct, although webRTC doesn't support h265 so that's a different conversation for video |
Beta Was this translation helpful? Give feedback.
-
|
Regards go2rtc logging: |
Beta Was this translation helpful? Give feedback.
-
|
this is a bug that has already been fixed |
Beta Was this translation helpful? Give feedback.
-
|
AMD GPU usage.
Does the H264 in the profile mean its trying to only use GPU on 264. Also do you have knowlwdge about the drivers for AMD GPUs in Unraid. using |
Beta Was this translation helpful? Give feedback.
-
|
|
Beta Was this translation helpful? Give feedback.
-
|
What are the logs? |
Beta Was this translation helpful? Give feedback.
-
|
|
Beta Was this translation helpful? Give feedback.
-
|
would you like me to post my config?? |
Beta Was this translation helpful? Give feedback.
-
|
That error has nothing to do with your hwaccel. You need to update your recording preset to |
Beta Was this translation helpful? Give feedback.
-
|
Seeing a couple different errors since updating to beta 4.. `2023-01-18 11:39:21.012920612 [2023-01-18 11:39:21] frigate.watchdog INFO : Detection appears to be stuck. Restarting detection process... and `2023-01-18 19:34:54.766814696 [2023-01-18 19:34:54] ws4py INFO : Managing websocket [Local => 127.0.0.1:8082 | Remote => 127.0.0.1:42020] Here is my config... `mqtt: Global Image Storage Settingsnapshots: go2rtc configgo2rtc: Global Camera Settingsdetect: Camera SettingsFront Camera - Facing Northcameras: Front Camera - Facing Southfrontsouth: Carport Cameracarport: Backporch Camerabackporch: Backyard Camerabackyard: |
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 3
go2rtcconfig. We realized it didn't make sense to have restream under the ffmpeg config and the cross referencing between inputs was difficult to understand.So your existing config which looks like:
will now look like
NOTE: The go2rtc config does not currently support env var substitution.
NOTE: An update to the integration will be required for live to work.
live -> stream_namepreset-record-generic-audiohas been renamed topreset-record-generic-audio-aacrestream -> jsmpeghas been moved back toliveui -> timezoneandui -> live_modeconfigurations127.0.0.1should be used instead oflocalhostfor restream streamsBREAKING 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.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. The restream of a camera can be accessed at
rtsp:https://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:https://frigate_ip:8554/birdseyeNOTE: Port
8554will 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
MSEandWebRTClive 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
Debugpage has been renamed toSystem. It now includes much more information and links to easily getvainfoandffprobedata.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
VAINFObutton 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
FFPROBEbutton 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
:roor 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.mp4to/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_agentforrtmpstreams by @felipecrs in Do not apply-user_agentforrtmpstreams #4596New Contributors
Full Changelog: v0.11.1...v0.12.0-beta4
Images:
ghcr.io/blakeblackshear/frigate:0.12.0-beta4ghcr.io/blakeblackshear/frigate:0.12.0-beta4-tensorrtThis discussion was created from the release 0.12.0 Beta 4.
Beta Was this translation helpful? Give feedback.
All reactions