0.12.0 Beta 9 #5652
Replies: 14 comments 38 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.
-
|
Missed spelled word, 'sort' should be 'short' , configuration file Optional: Set the date style for a specified length.Options are: full, long, medium, sort <----date_style: short Optional: Set the time style for a specified length.Options are: full, long, medium, sort <---- |
Beta Was this translation helpful? Give feedback.
-
|
Finally made the jump from 0.11.1 to 0.12.0-beta9, and it was a pretty painless process despite all of the major changes between 0.11 and 0.12. Great work! I have a brief question for you @NickM-27 - in this commit for the frontend you changed code that set the max-width of the containing div of the birdseye stream. Since the early days of birdseye, I've been used to it taking up the full width of my window, and I usually have the window open all the time on a second high-res monitor on my desk. But it looks like you set the container to have the Tailwind class of Thanks! |
Beta Was this translation helpful? Give feedback.
-
|
Yes, because you can Fullscreen by clicking on the live view and in 0.13 there will be other controls next to birdseye when not Fullscreened |
Beta Was this translation helpful? Give feedback.
-
|
Gotcha. I'll just tweak the code for myself for 0.12 then until the controls appear later in 0.13. Thanks! |
Beta Was this translation helpful? Give feedback.
-
I think you misunderstood what I meant. The size will always be that way when not Fullscreened. By controls I meant PTZ and two way talk controls |
Beta Was this translation helpful? Give feedback.
-
|
Cool. If the PTZ controls aren't coming until 0.13 and there's just empty space in the meantime, I'll tweak it for myself to take up the full width (as it always has been for me) until then. |
Beta Was this translation helpful? Give feedback.
-
|
Hey guys, I need some help. I just installed a Tesla K80 I've also installed the nvidia runtime docker, nvidia the other suggested installs by you guys from this link you guys had linked in the instructions: https://docs.nvidia.com/datacenter/cloud-native/container-toolkit/install-guide.html I'm able to use sudo nvidia-smi and it shows. up, however no matter what I do I can't get Frigate to utilize it. I intend to use it with TensorRT, but I understand that they and two others will no longer be able to support TensorRT sometime in the future. I know that I have drivers installed. I'm able to reach /dev/driv/ and have cards: card0, card1, renderD128, and renderD29. I keep getting the error Not able to find libcuda.so.1. Hardware may not support this function. Any help would be appreciate. Thanks in advance. |
Beta Was this translation helpful? Give feedback.
-
|
You'll want to pass both GPUs using the count config probably https://deploy-preview-4055--frigate-docs.netlify.app/configuration/hardware_acceleration#nvidia-gpus |
Beta Was this translation helpful? Give feedback.
-
Ok thanks, Ill change that. I would rather give you more information than too little. When I installed the drivers I used the suggestion https://linuxconfig.org/how-to-install-the-nvidia-drivers-on-ubuntu-22-04 and then I ran sudo apt-get cuda-toolkit. Then I followed the guide for Nvidia Run-time that is posted in the frigate guide. When run nvidia-smi I get the following +-----------------------------------------------------------------------------+ +-----------------------------------------------------------------------------+ |
Beta Was this translation helpful? Give feedback.
-
|
@NickM-27 By the way, thanks for always willing to be helpful. Now, I made the changes and this is what I got. 0 - b'[mov,mp4,m4a,3gp,3g2,mj2 @ 0x55997ea976c0] moov atom not found\n/tmp/cache/back_yard-20230307131054.mp4: Invalid data found when processing input\n' |
Beta Was this translation helpful? Give feedback.
-
|
This is the same when I was getting when I was using device_ids |
Beta Was this translation helpful? Give feedback.
-
|
Was there any further suggestions on this issue? Also, while I'm this issue situated I switched to installing it on my synology nas. I keep getting the following error from go2rtc 2023-03-09 22:46:05.446962965 [INFO] Preparing go2rtc config... |
Beta Was this translation helpful? Give feedback.
-
|
Hello, |
Beta Was this translation helpful? Give feedback.
-
|
Set docker to pull from the images that are shown at the bottom of the release notes |
Beta Was this translation helpful? Give feedback.
-
|
Images: ghcr.io/blakeblackshear/frigate:0.12.0-beta9 |
Beta Was this translation helpful? Give feedback.
-
|
Ok. |
Beta Was this translation helpful? Give feedback.
-
|
Since moving to beta 9 I'm not getting video clips recorded for some of my cameras. Some work and some don't. Everything worked fine in beta 8 and rolling back to beta 8 restores functionality Cameras are a mix of cheap no name stuff using rtsp feeds I'm using exactly the same config.yml file as my V11 installation (except I've moved to openvino from coral) so not using go2trc I see some other similar issues here but none directly related to the shift from beta 8 to 9 so is this unknown behaviour or something you are aware of? |
Beta Was this translation helpful? Give feedback.
-
|
If the recording file in cache keeps growing and never stops that's usually due to a timestamp issue from the camera. I don't know any change that would have caused this. I'd suggest making an issue. |
Beta Was this translation helpful? Give feedback.
-
|
raised on #5677 |
Beta Was this translation helpful? Give feedback.
-
|
looks like using the below, which was 'working' before, at least for being able to view it as I've had recording broken for a while now, removing it seems to have fixed the viewing of the streams again: and on the bright side, it looks like frigate is able to store recordings again... |
Beta Was this translation helpful? Give feedback.
-
|
That's an entirely incorrect preset for detect so makes sense that there were issues |
Beta Was this translation helpful? Give feedback.
-
|
pretty sure I took that from the docs for global ffmpeg section :'D |
Beta Was this translation helpful? Give feedback.
-
|
Definitely not for detect
|
Beta Was this translation helpful? Give feedback.
-
|
yh I checked too :) not sure where exactly but was from docs somewhere.. but then i've been trying soo many things to get recording working again who knows, might of inadvertently copy'd from else where :S beta9 seems to have fixed whatever my recording issues were tho. either way was just an in case someone had that.. it did work before with it :'D |
Beta Was this translation helpful? Give feedback.
-
|
@NickM-27 quick question, what exactly is meant in the config docs by "clean" snapshot copy? |
Beta Was this translation helpful? Give feedback.
-
|
There is a png created which doesn't have the annotations (bounding box, timestamp, etc) of the snapshot.jpg |
Beta Was this translation helpful? Give feedback.
-
|
gotcha. it would be nice to be given the option from the web UI download feature on which to download (clean vs processed). but for now i can just manually grab what I need. |
Beta Was this translation helpful? Give feedback.
-
|
I'm getting I tried with a few different methods and they all end up with the same error. Can it be a configuration error? http://homeassistant.local:8123/ccab4aaf_frigate-fa-beta/dashboard https://lettersandnumbers.ui.nabu.casa/ccab4aaf_frigate-fa-beta/dashboard http://192.168.XXX.XXX:8123/ccab4aaf_frigate-fa-beta/dashboard My install method is HAOS and the diagnostic file will be in the next comment. |
Beta Was this translation helpful? Give feedback.
-
|
config_entry-frigate-c874780b45cc0c8fec26c9c4e9a102a1.json.txt |
Beta Was this translation helpful? Give feedback.
-
|
Me too. But that's expected for the current implementation. To be able to access it from within nabu casa, go2rtc would need to be embedded in Frigate's page. |
Beta Was this translation helpful? Give feedback.
-
|
Mee too, but this works. |
Beta Was this translation helpful? Give feedback.
-
|
The link won't work via ingress because it requires a bunch of path rewriting. I'm not sure we can do anything about it and it's just for debugging purposes anyway. |
Beta Was this translation helpful? Give feedback.
-
|
I just want to mention that same issue is still with this beta: Problem is that it is impossible to get logs, because it is HAOS ja complete machine hangs. So my point of view that go2rtc is totally experimental. |
Beta Was this translation helpful? Give feedback.
-
|
As probably you are the only one who can reproduce this error, I would suggest you open an issue in go2rtc itself. |
Beta Was this translation helpful? Give feedback.
-
|
I understand, but for now this direct connection to the camera is a good way for me. Testing is difficult because I operate in a production environment. So it's unfortunate when home automation systems suddenly get stuck. Well, this is my own choice, and I don't blame anyone for it. Frigate is awesome and it will be even better !! Keep up the good work. |
Beta Was this translation helpful? Give feedback.
-
|
Well, it's good that you have a workaround. I'm just trying to say that, if you don't report the issue, chances are that it's not going to be fixed. |
Beta Was this translation helpful? Give feedback.
-
|
go2rtc seems to be a bit more stable in beta9 but I just had a crash after several hours of running restream on most of my cameras AlexxIT/go2rtc#259 The new watchdog on go2rtc kicked in and recovered it.. Thanks for adding it. |
Beta Was this translation helpful? Give feedback.
-
|
Sounds like this bug will be fixed in the next go2rtc release.. I was seeing up to two crashes of go2rtc a day but the watchdog was gracefully recovering. |
Beta Was this translation helpful? Give feedback.
-
|
Is anyone having an issue where some events play but some don't (same camera), with the below error? No error logs apart from the below, it's in the recordings when manually checked. The camera time appears to be accurate to the second. No config changes made. "2023-03-14 21:49:23.096722125 [2023-03-14 21:49:23] frigate.http ERROR : No recordings found for the requested time range |
Beta Was this translation helpful? Give feedback.
-
|
Check earlier in your logs for discarded corrupt segments / recordings. I believe the check for corrupt segments is more aggressive in 0.12 than 0.11. I also get more of them when I restream via go2rtc for detection / recordings. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks Bagobones, there were no errors reported at least for a couple of hours before the event, I'll keep monitoring, at least it was still recorded, that is the main thing :). The errors a few hours before Unable to keep up with recording segments in cache for cam1. Keeping the 5 most recent segments out of 7 and discarding the rest... but I get them daily ever since these warnings were enabled... |
Beta Was this translation helpful? Give feedback.
-
|
Hmm I just noticed that all my recordings for two of my cameras come back as no recording / bad format.. These are reolink cameras I had setup to restream via go2rtc.. I have reverted their config to be direct.. My other cameras seem to be fine so I wonder if something odd is happing with these ones not set to have audio and the parameters I had set. |
Beta Was this translation helpful? Give feedback.
-
|
Hello! I have the old version of frigate v0.10 (stable) installed and I would like to upgrade to 0.12 beta 9. Can I upgrade the addon directly? I ask because in the addon it only shows the upgrade to 0.11.1 as an option. I can install version 0.12 beta 9 by selecting the addon from the addon's store but it proceeds as a new addon installation and not as an upgrade of the already installed one. |
Beta Was this translation helpful? Give feedback.
-
|
There is a different addon in the same repo for the beta. You will need to remove the existing addon and install the beta addon instead. Note that the database migrations are reversible and you will not be able to revert to 0.10 or 0.11 after upgrading. |
Beta Was this translation helpful? Give feedback.
-
|
What is the deal with the package repo? Is there a GitHub issue or did all the packages really get removed? Edit: To answer my own question. GitHub has an outage that is effecting packages. https://www.githubstatus.com/ |
Beta Was this translation helpful? Give feedback.
-
|
BTW, it was erroring with 503 Service Unavailable, which seems a reasonable and intuitive response (I don't see how this could led to the understanding that the package was removed). |
Beta Was this translation helpful? Give feedback.
-
When doing a docker pull it was timing out and going to the packages list it was empty. |
Beta Was this translation helpful? Give feedback.
-
|
I see. Maybe it was behaving differently depending on the time or location. For me, docker pull was returning 503. |
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 8
BREAKING 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.[Errno 98] Address already in uswhich need to be set back to default to work [Support]: [Errno 98] Address already in use #5444Retention 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.
go2rtc
go2rtc has been bundled inside Frigate. The configuration can be set directly inside Frigate's config file nested under the
go2rtcsection. You can follow the guide to setup go2rtc.Due to many issues with RTMP, it is now deprecated in favor of using the bundled go2rtc to provide an RTSP stream. Streams configured in go2rtc can also be used by 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/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 bundled go2rtc 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-beta9
Images:
ghcr.io/blakeblackshear/frigate:0.12.0-beta9ghcr.io/blakeblackshear/frigate:0.12.0-beta9-tensorrtThis discussion was created from the release 0.12.0 Beta 9.
Beta Was this translation helpful? Give feedback.
All reactions