0.15.0 Beta 1 #14653
Replies: 55 comments 179 replies
-
|
impressive pace over the last months! Frigate is now the best NVR tool |
Beta Was this translation helpful? Give feedback.
-
|
Thank you so much for the hard work the Frigate team! I just upgraded, yes I've been stalking this upgrade for a while now and see a few issues. Seeing the following errors occasionally in the logs and didn't see anything like this in 0.14.1: When I look at the cameras they are fine. The cameras reporting this are all Amcrests and I run all my cameras through go2rtc and Frigate consumes those of course via go2rtc. Going to the review section when I hover over some of the events, seems to be the most recent ones, I see a blank square but others show the mini preview image. 
Looking forward to helping out and making this best possible. Let me know if you need anything else to help troubleshoot. |
Beta Was this translation helpful? Give feedback.
-
13th Gen Intel(R) Core(TM) i7-13700 |
Beta Was this translation helpful? Give feedback.
-
|
You need to use qsv |
Beta Was this translation helpful? Give feedback.
-
So change: to ? |
Beta Was this translation helpful? Give feedback.
-
|
Depends what codec your detect streams are, but in general yes |
Beta Was this translation helpful? Give feedback.
-
|
Oh see I thought those settings were always related to the record stream not detect. My cameras are configured with main stream as 265 and sub-stream (detect) for 264. I made the qsv 264 tweak and will watch now for issues. |
Beta Was this translation helpful? Give feedback.
-
|
Fantastic progress as ever! One point on Semantic Search - interested as to where the 16GB RAM requirement comes from for the CLIP model. I've been running 0.15 dev builds for a few weeks and my Frigate container (which is set to 16GB max RAM on a 32GB system) has never exceeded 4.5GB memory use. I also only have an Intel 10700 iGPU and don't see any real performance problems (I think it took about 20 minutes to re-encode 7,000 snapshots). Appreciate you might not want to lower the requirement, but just sharing my experience to avoid putting anyone else off... Of course, 0.16 sounds like a GPU could become more mandatory for face recognition, so whether the long term view is that it's necessary would be a fair one. |
Beta Was this translation helpful? Give feedback.
-
This is part of why I see merit in a roadmap of planned features (not a timeline, but a feature list) - so users can make the right hardware choices. I've been pondering this a bit so will make a separate post on the subject. |
Beta Was this translation helpful? Give feedback.
-
|
The thing is it is not really planned, and the supported hardware is also not known. The face recognition / alpr was not planned for 0.16 until we started talking about it literally a week ago. And it was not clear what hardware would be supported until we actually tried it out, found a model, etc. Things could certainly still change with it too. |
Beta Was this translation helpful? Give feedback.
-
|
As we've indicated elsewhere, there is no roadmap, no official development team, and no funding for Frigate beyond what users give via Github Sponsors. Frigate+ is exclusively Blake's project, Nick and I don't contribute or receive benefit from it. Nick and I are just volunteer contributors, and like he said, it was just last week that both of us worked on separate projects (face detection and license plate recognition) and decided to contribute them to the Frigate codebase. For a list of planned features, you can always take a look at the pinned issues. These are things users have requested that we feel are worthwhile to eventually have within Frigate. |
Beta Was this translation helpful? Give feedback.
-
|
I guess I'm as much asking from the perspective that you guys are probably as well-informed as anybody on the deployment of AI models relevant to the security space! Also appreciate that you're not sat there with the equipment or time to test across loads of different hardware configurations. Perhaps I could create a simple "benchmark.py" script that can be run as a non-default docker image command by Frigate, or a UI button, that executes a set of AI activities against some pre-supplied images and outputs the time taken |
Beta Was this translation helpful? Give feedback.
-
|
it's possible things like semantic search can have inference statistics just like the object detectors as a way to gauge how things are running. |
Beta Was this translation helpful? Give feedback.
-
|
Is there an update to https://github.com/blakeblackshear/frigate-hass-integration or https://github.com/dermotduffy/frigate-hass-card required? I can see the clips in the card, but when I click one to play it just shows a loading spinner and doesn't play any clip. |
Beta Was this translation helpful? Give feedback.
-
|
No, nothing has changed in these regards |
Beta Was this translation helpful? Give feedback.
-
|
Do you have plans to accept multiple languages? |
Beta Was this translation helpful? Give feedback.
-
|
It would likely make sense at some point, that would be a very large effort though to be clear |
Beta Was this translation helpful? Give feedback.
-
Thank you to the team's hard work and dedication. |
Beta Was this translation helpful? Give feedback.
-
|
First of all thank you to the team (and contributors) for all the time spent making Frigate so incredible! I was having some issues after upgrading, related to having birdseye enabled with restream. Looks like as I don't have an ffmpeg>hwaccel_args config key, Seems like amending this line to the below (adding
|
Beta Was this translation helpful? Give feedback.
-
|
auto as a default doesn't really make sense because the go2rtc config is created before frigate starts. Realistically you will need to set the hwaccel_args globally to ensure birdseye is restreamed efficiently. But yes setting the default as an empty string there will solve the issue so feel free to put up a PR |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the quick response, raised under #14658 |
Beta Was this translation helpful? Give feedback.
-
|
Found another issue related to Tracked Object Details interface, the left and right arrows at the bottom don't do anything so having to click on the icons in the middle section works but not the left or right:
|
Beta Was this translation helpful? Give feedback.
-
To be honest that is kind of confusing, should they be hidden if large enough or just active them for a more linear progression? |
Beta Was this translation helpful? Give feedback.
-
|
I'm only explaining that the behavior appears to be expected and not a bug in the buttons. Hiding them might be preferable |
Beta Was this translation helpful? Give feedback.
-
|
This is using two carousel UI elements - the first is the one your camera frame is displayed in, which can be dragged on desktop and swiped on mobile. The second carousel is the one with multiple squares/icons. The arrows correspond to that carousel and will be active/not grayed out when there are many steps in the object's life cycle. I can see how this may be confusing. We'll improve it for the next beta. |
Beta Was this translation helpful? Give feedback.
-
|
Just put up a PR to cause the buttons to move through the object lifecycle elements #14662 |
Beta Was this translation helpful? Give feedback.
-
|
I think it might be less confusing if the arrows are right next to the icons, rather than being spread wide. |
Beta Was this translation helpful? Give feedback.
-
|
So upgrading from 0.14.1 to this, for the first 10 minutes or so, the cameras seemed to load and then keep crashing over and over again. It seems to have stopped doing it for the next 10 minutes, so not sure yet if its just a temporary problem on startup/first upgrade, I can keep you updated... here's logs during the issue (we got the old "Unable to keep up with recording segments in cache for . Keeping the 6 most recent segments out of 8 and discarding the rest...": I haven't yet tried the new features, this was just a simple upgrade |
Beta Was this translation helpful? Give feedback.
-
|
I also noticed this with a few cameras. I restarted Frigate after about 10 minutes and it hasn't come back. I've also restarted it a few more times since then and it hasn't happened again. |
Beta Was this translation helpful? Give feedback.
-
|
Spun up my container using the beta and now i don't have the icon for frigate+ any longer on the left side of my screen. |
Beta Was this translation helpful? Give feedback.
-
|
This is expected, use the explore view to submit to Frigate+ |
Beta Was this translation helpful? Give feedback.
-
|
alright, thanks :) Have to say: That new Explore View is awesome, especially as I have quite some zones on my terrace-cam where my gf loves to watch cats strolling by having a midnite snack at night. |
Beta Was this translation helpful? Give feedback.
-
Would it be possible to have an icon or any other visual effect on the explore view to see if an item was already sent to frigate+? We have to open a review item and go to the snapshot to see if it was already sent or if we can send it, could be good to know it without having to open it. |
Beta Was this translation helpful? Give feedback.
-
|
The send to plus button shows on the card if the object has not been sent and has a snapshot. You can also use the 3 dots |
Beta Was this translation helpful? Give feedback.
-
|
great to see new release!!! is it in my main config under each camera stream I need to add? |
Beta Was this translation helpful? Give feedback.
-
|
ok now I get the following error for camera "durys" (reolink doorbell) I double checked streaming from doorbell is using h264 |
Beta Was this translation helpful? Give feedback.
-
|
try using preset-vaapi for that camera |
Beta Was this translation helpful? Give feedback.
-
|
I changed global ffmpeg setting and error is gone. |
Beta Was this translation helpful? Give feedback.
-
|
if there are no errors then there should be no issue |
Beta Was this translation helpful? Give feedback.
-
|
anyway big thanks Nick. You are the best!!! |
Beta Was this translation helpful? Give feedback.
-
|
Hmm, after fixing the birdseye restream ffmpeg config I now hit this: |
Beta Was this translation helpful? Give feedback.
-
|
that would seem to indicate yaml is unable to load your config for some reason, perhaps it is invalid yaml |
Beta Was this translation helpful? Give feedback.
-
|
Fixed! My file was called now a new issue, all streams show perfectly in go2rtc, but not in frigate... |
Beta Was this translation helpful? Give feedback.
-
|
you should create a support discussion, but none of this seems related to the beta |
Beta Was this translation helpful? Give feedback.
-
|
That's weird because everything worked perfectly on 0.14.1 go2rtc:
streams:
tablet1: rtsp://10.9.8.137:8080/h264_pcm.sdp
tablet2: rtsp://10.9.8.109:8080/h264_pcm.sdp
tablet3: rtsp://10.9.8.64:8080/h264_pcm.sdp
tablet4: rtsp://10.9.8.163:8080/h264_pcm.sdp
audio: # <- enable audio events for all camera
enabled: true
snapshots:
enabled: true
cameras:
tablet1:
mqtt:
timestamp: false
bounding_box: false
crop: true
quality: 100
height: 500
ffmpeg:
inputs:
- path: "rtsp://127.0.0.1:8554/tablet1?video&audio"
input_args: preset-rtsp-restream
roles:
- audio
- detect
- record
tablet2:
mqtt:
timestamp: false
bounding_box: false
crop: true
quality: 100
height: 500
ffmpeg:
inputs:
- path: "rtsp://127.0.0.1:8554/tablet2?video&audio"
input_args: preset-rtsp-restream
roles:
- record
- detect
- audio
tablet3:
mqtt:
timestamp: false
bounding_box: false
crop: true
quality: 100
height: 500
ffmpeg:
inputs:
- path: "rtsp://127.0.0.1:8554/tablet3?video&audio"
input_args: preset-rtsp-restream
roles:
- record
- detect
- audio
tablet4:
mqtt:
timestamp: false
bounding_box: false
crop: true
quality: 100
height: 500
ffmpeg:
inputs:
- path: "rtsp://127.0.0.1:8554/tablet4?video&audio"
input_args: preset-rtsp-restream
roles:
- record
- detect
- audio
detectors:
coral:
type: edgetpu
device: usb
database:
path: /media/frigate/frigate.db
birdseye:
enabled: true
restream: true
mode: motion
motion:
threshold: 100
contour_area: 30
objects:
track:
- person
- face
- cat
ffmpeg:
hwaccel_args: preset-intel-qsv-h264
record:
enabled: true
expire_interval: 60
retain:
days: 1
mode: motion
alerts:
retain:
days: 7
detections:
retain:
days: 7
version: 0.15-0 |
Beta Was this translation helpful? Give feedback.
-
|
Fixed by setting ffmpeg section to: ffmpeg:
hwaccel_args: '""' |
Beta Was this translation helpful? Give feedback.
-
|
Impressive update, congratulations! I think I found a bug for the annotation offset. Otherwise, two suggestions:
|
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the report
|
Beta Was this translation helpful? Give feedback.
-
Thanks, fixed in #14667 |
Beta Was this translation helpful? Give feedback.
-
|
Great, thank you for the heads up and the fix! |
Beta Was this translation helpful? Give feedback.
-
|
Was there a breaking change? I did the update and tried to start Frigate and now I'm getting the following within the logs. I update almost every time there is one so I had whatever was the most recent before this morning. |
Beta Was this translation helpful? Give feedback.
-
|
This is a known issue that will be fixed for the next beta. |
Beta Was this translation helpful? Give feedback.
-
|
Ok, I will restore and ignore for now. :) |
Beta Was this translation helpful? Give feedback.
-
|
I had this issue and that was because I had Frigate+ API key configured in both config file and as environment variable. |
Beta Was this translation helpful? Give feedback.
-
|
Ok so semantic search is really cool. |
Beta Was this translation helpful? Give feedback.
-
|
The Home/End keys are bound to the suggestions list that appears below when entering filters through the keyboard. It does seem reasonable to have the keys work in the input when you're typing a normal search term without any filters in the input, though. I'll put up a PR to add this to the next beta. |
Beta Was this translation helpful? Give feedback.
-
|
Ah so they are! I can see why they would be useful there too. Yeah that seems like a good solution, thanks :) |
Beta Was this translation helpful? Give feedback.
-
|
Does Semantic Search detect intel iGPU support automatically or does a detector for OpenVINO need to be configured for ONIX support? If OpenVINO needs to be configured is there a way to specify which tasks to to which accelerator if I have a Coral for normal object detection already configured as well? |
Beta Was this translation helpful? Give feedback.
-
|
it will detect openvino automatically assuming you are using the main build and the GPU device is present. You can check this by using intel_gpu_top |
Beta Was this translation helpful? Give feedback.
-
|
Im not sure what is going on, but Frigate works fine on the on the latest stable version 0.14.1, however on this new beta I can not get it to detect hardware acceleration whatsoever. Exact same docker deployment file other then changing the image tag to the 15 beta. And without the hardware acceleration Im assuming its why go2rtc just crashes code 1 over and over and no camera streams work. 
|
Beta Was this translation helpful? Give feedback.
-
|
That doesn't really make sense, if it's crashing then something else is wrong |
Beta Was this translation helpful? Give feedback.
-
|
Got that fixed, looking in docker logs it was failing the database migration so I just deleted the database and started fresh. 
I see this in the docker logs over and over 2024-11-01 14:09:07.354405696 [INFO] The go2rtc service exited with code 1 (by signal 0) |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
|
That's been fixed for the next version. For now you should just set hwaccel args to preset-intel-qsv-h264 |
Beta Was this translation helpful? Give feedback.
-
O geeze I spent hours last night trying to get it to go and thats all it was. Thanks its running now! |
Beta Was this translation helpful? Give feedback.
-
Ok this is pretty epic that it can do this now! |
Beta Was this translation helpful? Give feedback.
-
|
description is coming from an gen ai ?
El vie, 1 nov 2024 a las 12:02, bigdaddy5414 ***@***.***>)
escribió:
… image.png (view on web)
<https://github.com/user-attachments/assets/08d58bf6-07e3-44aa-b8dc-145ddcf0d09b>
Ok this is pretty epic that it can do this now!
—
Reply to this email directly, view it on GitHub
<#14653 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AIOTKWXVOKPQ6TQJX3J64GDZ6OJX5AVCNFSM6AAAAABQZTB2XGVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCMJSGMYTKMQ>
.
You are receiving this because you commented.Message ID:
***@***.***
com>
--
Andres Roepke Del Solar.
Ingeniero Civil Industrial
Ingeniero Electronico
Mobile 88196932
|
Beta Was this translation helpful? Give feedback.
-
|
yes Google Gemini |
Beta Was this translation helpful? Give feedback.
-
|
anyone here experience this with the last beta? clip view is not working
last stable versions works perfect
{"success":false,"message":"Event not found"}
Andres Roepke Del Solar.
Ingeniero Civil Industrial
Ingeniero Electronico
Mobile 88196932
…On Fri, Nov 1, 2024 at 12:15 bigdaddy5414 ***@***.***> wrote:
yes Google Gemini
—
Reply to this email directly, view it on GitHub
<#14653 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AIOTKWUBYXV33YE34QKUNNTZ6OLIVAVCNFSM6AAAAABQZTB2XGVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCMJSGMZDOOA>
.
You are receiving this because you commented.Message ID:
***@***.***
com>
|
Beta Was this translation helpful? Give feedback.
-
|
Check your record config, like it says in the release notes the config was migrated |
Beta Was this translation helpful? Give feedback.
-
|
Ohh! sorry, i cant find the specific part of the recording migration:(
El vie, 1 nov 2024 a las 12:35, Nicolas Mowen ***@***.***>)
escribió:
… Check your record config, like it says in the release notes the config was
migrated
—
Reply to this email directly, view it on GitHub
<#14653 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AIOTKWSYOZUUGI2HSD3X4CTZ6ONS3AVCNFSM6AAAAABQZTB2XGVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCMJSGM2DKNI>
.
You are receiving this because you commented.Message ID:
***@***.***
com>
--
Andres Roepke Del Solar.
Ingeniero Civil Industrial
Ingeniero Electronico
Mobile 88196932
|
Beta Was this translation helpful? Give feedback.
-
|
record:
enabled: true
retain:
days: 1
mode: all
alerts:
retain:
days: 1
detections:
retain:
days: 1
snapshots:
enabled: true
retain:
default: 500
El vie, 1 nov 2024 a las 12:39, Andres Roepke ***@***.***>) escribió:
… Ohh! sorry, i cant find the specific part of the recording migration:(
El vie, 1 nov 2024 a las 12:35, Nicolas Mowen ***@***.***>)
escribió:
> Check your record config, like it says in the release notes the config
> was migrated
>
> —
> Reply to this email directly, view it on GitHub
> <#14653 (reply in thread)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AIOTKWSYOZUUGI2HSD3X4CTZ6ONS3AVCNFSM6AAAAABQZTB2XGVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCMJSGM2DKNI>
> .
> You are receiving this because you commented.Message ID:
> ***@***.***
> com>
>
--
Andres Roepke Del Solar.
Ingeniero Civil Industrial
Ingeniero Electronico
Mobile 88196932
--
Andres Roepke Del Solar.
Ingeniero Civil Industrial
Ingeniero Electronico
Mobile 88196932
|
Beta Was this translation helpful? Give feedback.
-
|
I'm seeing instability with the birdseye view. Cameras will show as blank but if I click into a camera, the feed shows up. The logs do have a variety of errors too. When I pull up the cameras in other sources like the Reolink client, HomeAssistant, Control4, etc, they show up fine.
|
Beta Was this translation helpful? Give feedback.
-
|
there is no x before the 64 |
Beta Was this translation helpful? Give feedback.
-
|
Ah, sorry. Here is the stream info: [{"return_code":0,"stderr":"","stdout":{"programs":[],"stream_groups":[],"streams":[{"codec_long_name":"H.264 / AVC / MPEG-4 AVC / MPEG-4 part 10","width":2560,"height":1440,"avg_frame_rate":"0/0"},{"codec_long_name":"AAC (Advanced Audio Coding)","avg_frame_rate":"0/0"}]}},{"return_code":0,"stderr":"","stdout":{"programs":[],"stream_groups":[],"streams":[{"codec_long_name":"H.264 / AVC / MPEG-4 AVC / MPEG-4 part 10","width":0,"height":0,"avg_frame_rate":"0/0"},{"codec_long_name":"AAC (Advanced Audio Coding)","avg_frame_rate":"0/0"}]}}] |
Beta Was this translation helpful? Give feedback.
-
|
Maybe try vaapi preset for just that camera |
Beta Was this translation helpful? Give feedback.
-
|
7 of the cameras are the same, the other is a doorbell with similar stream info besides size of the picture: [{"return_code":0,"stderr":"","stdout":{"programs":[],"stream_groups":[],"streams":[{"codec_long_name":"H.264 / AVC / MPEG-4 AVC / MPEG-4 part 10","width":2560,"height":1920,"avg_frame_rate":"20/1"},{"codec_long_name":"AAC (Advanced Audio Coding)","avg_frame_rate":"0/0"}]}},{"return_code":0,"stderr":"","stdout":{"programs":[],"stream_groups":[],"streams":[{"codec_long_name":"H.264 / AVC / MPEG-4 AVC / MPEG-4 part 10","width":896,"height":672,"avg_frame_rate":"0/0"},{"codec_long_name":"AAC (Advanced Audio Coding)","avg_frame_rate":"0/0"}]}}] |
Beta Was this translation helpful? Give feedback.
-
|
I should clarify that it isn't one camera with issues on the birds eye, it appears to be all of them. |
Beta Was this translation helpful? Give feedback.
-
|
Hmm, I seem to be missing the Frigate+ button from the left sidebar. Has it been moved? |
Beta Was this translation helpful? Give feedback.
-
|
It is now integrated into the Explore view |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
|
The same thing just indented at the camera level |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the awesome update - I feel like 0.14 only just came out and now here's another! I'm running using Docker in a Proxmox LXC on a mini-pc with an i7-13700T (4 cpus allocated), 64GB RAM (16GB allocated) and a USB Coral.
Finally, have you considered showing the match details (type and percentage) chip on the Explore Summary view? I like the categories of this view, but appreciate the match details at a glance to know whether to submit that image to Frigate+ |
Beta Was this translation helpful? Give feedback.
-
Glad to hear it's mostly working well for you.
We'll improve the log message on startup for the next beta when shm_size needs to be increased.
Another user running proxmox has reported this as well. It seems like the virtualization happening with proxmox is causing the semantic search model
There's a lack of Since this is only a summary view, there isn't enough space> Thanks for the awesome update - I feel like 0.14 only just came out and now here's another! Glad to hear it's mostly working well for you.
We'll improve the log message on startup for the next beta when shm_size needs to be increased.
Another user running Frigate in Proxmox has reported this as well. It seems like it's related to Proxmox virtualization/threading. The other user didn't report it actually caused any issues, though.
There's not really room for much else on the Summary view, and the goal is really for it to be just a summary. A single click/tap will bring you to the grid view, or you can set the grid view as the default in the Search Settings dialog. |
Beta Was this translation helpful? Give feedback.
-
|
Semantic search is a cool idea, though my results are so-so due to the thumbnails being rather small. Could we add a Thumbnail Snapshot |
Beta Was this translation helpful? Give feedback.
-
|
the problem with using snapshots is it will match on things that don't relate to the object that is being searched, so you can search for a red car but it matches on the red car in the background instead of the car that is driving by. If your neighbor has a blue car that is always parked then every single snapshot would match on that regardless of what was going on. In my experience, searching has brought relevant results to what is in the thumbnail, so it would be better to understand specifics of what you are seeing, expecting, but not getting in the search results |
Beta Was this translation helpful? Give feedback.
-
I don't see any detail that would meaningfully change the search results, we need more information on what is not working correctly |
Beta Was this translation helpful? Give feedback.
-
|
I agree with @NickM-27, there is not anything more significant about the snapshot vs. the thumbnail that would cause search results to improve. As suggested in the beta docs and the semantic search tip, search results dramatically improve with an "image caption approach". For example, "person walking" will likely return more irrelevant results than "man with a hat on walking next to a car on a sunny day". This is due to the model being trained on many things. Narrow it down with a more descriptive search, and you'll likely get much better results. |
Beta Was this translation helpful? Give feedback.
-
|
I am very new to Frigate, Models, and Home Assistant, in fact it was only yesterday that I finally got Frigate up and running for the first time...felt amazing. My question: I noticed that the Hailo detector is using mobile net v1 (0.15 beta), will it be able to use other models as well? I apologize if this is not the right place to ask, I am struggling to understand all the aspects of how models / integrating them work, and I do not understand how to "compile" them. I was able to download the yolov8s.hef from Hailo, but when I put it into Frigate it was running, but I wasn't getting detections from people or any of my "objects" and I know I am missing something but I don't understand enough to know what I am missing. Any help would be greatly appreciated :) |
Beta Was this translation helpful? Give feedback.
-
|
Other model types have to be supported but yes there's nothing stopping other models from working. All SSD models are supported currently |
Beta Was this translation helpful? Give feedback.
-
|
I got the yolov8s model running on Hailo8L using frigate 0.15-0 beta 1! 640x640, nhwc, rgb, yolox. 30ms inference note: the current documents (config reference) note that “model type” are only used for openvino, though it’s used with Hailo now :) |
Beta Was this translation helpful? Give feedback.
-
|
I've done that too. All HA does is send me a link to the MP4 clip. Link plays fine on Edge in Windows just not at all in Safari on iPhone. It has to be an encoding thing again, just can't figure out the correct args for 0.15.
John Miles Lento Jr.
| - gpg public key: https://lento.io/08EB5F22.txt
| - Sent via RFC 1149...
…________________________________
From: Nicolas Mowen ***@***.***>
Sent: Saturday, November 2, 2024 10:56
To: blakeblackshear/frigate ***@***.***>
Cc: johnlento ***@***.***>; Comment ***@***.***>
Subject: Re: [blakeblackshear/frigate] 0.15.0 Beta 1 (Discussion #14653)
I mean testing directly on the iPhone in the browser without HA
—
Reply to this email directly, view it on GitHub<#14653 (reply in thread)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AGHSRT2DQQ2ULCDWGXCN4VDZ6TR2HAVCNFSM6AAAAABQZTB2XGVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCMJSHE4DSMA>.
You are receiving this because you commented.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
If you're using ffmpeg 5.0 there's no reason there would be any difference. Nothing else has changed in this regard |
Beta Was this translation helpful? Give feedback.
-
|
I’ve done both 5 and 7 and it still doesn’t work in 0.15 with the args that did work on 0.14. It has to be something with clip storage or conversion in the beta
Sent via RFC 1149
Get some Carrier Pigeons<https://en.m.wikipedia.org/wiki/IP_over_Avian_Carriers>...
…________________________________
From: Nicolas Mowen ***@***.***>
Sent: Saturday, November 2, 2024 11:01:39 AM
To: blakeblackshear/frigate ***@***.***>
Cc: johnlento ***@***.***>; Comment ***@***.***>
Subject: Re: [blakeblackshear/frigate] 0.15.0 Beta 1 (Discussion #14653)
If you're using ffmpeg 5.0 there's no reason there would be any difference. Nothing else has changed in this regard
—
Reply to this email directly, view it on GitHub<#14653 (reply in thread)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AGHSRT64SB7RSCVIJTHSHJ3Z6TSNHAVCNFSM6AAAAABQZTB2XGVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCMJSHE4TANY>.
You are receiving this because you commented.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
Nothing has changed with that so I'm not sure |
Beta Was this translation helpful? Give feedback.
-
|
I cant see anything in the docs but the UI > Order seems to be ignored and cameras are shown in the order they appear in the config file, |
Beta Was this translation helpful? Give feedback.
-
|
Depends what dashboard you are using, works fine for me with the default dashboard |
Beta Was this translation helpful? Give feedback.
-
|
I was using the default dash but you are correct there is nothing wrong. What was wrong was I have two cameras set to order 6 when they should have been 6 and 7. Odd thing was in V14 it displayed them in (what for me was) the desired order so I hadn't noticed the error but when I used the same config file on the beta they were flipped. Because I was using the same config file on identical hardware between live and test I put it down to an error with the beta. Sorry about that and all fixed now. Thanks again for all your hard work |
Beta Was this translation helpful? Give feedback.
and others
-
Beta Documentation: https://deploy-preview-13787--frigate-docs.netlify.app/
Images
ghcr.io/blakeblackshear/frigate:0.15.0-beta1ghcr.io/blakeblackshear/frigate:0.15.0-beta1-standard-arm64ghcr.io/blakeblackshear/frigate:0.15.0-beta1-tensorrtghcr.io/blakeblackshear/frigate:0.15.0-beta1-tensorrt-jp4ghcr.io/blakeblackshear/frigate:0.15.0-beta1-tensorrt-jp5ghcr.io/blakeblackshear/frigate:0.15.0-beta1-rkghcr.io/blakeblackshear/frigate:0.15.0-beta1-rocmghcr.io/blakeblackshear/frigate:0.15.0-beta1-h8lMajor Changes for 0.15.0
Breaking Changes
There are several breaking changes in this release, Frigate will attempt to update the configuration automatically. In some cases manual changes may be required. It is always recommended to back up your current config and database before upgrading:
frigate.dbfileshm_sizeis too low then a warning will be printed in the log stating that it needs to be increased.recordconfig has been refactored to allow for direct control of how longalertsanddetectionsare retained. These values will be automatically populated from your current config, but you may want to adjust the values that are set after updating. See the updated docs here.hwaccelpreset they are using (preset-vaapimay need to now bepreset-intel-qsv-h264orpreset-intel-qsv-h265).ffmpegis no longer part of$PATH. In most cases this is handled automatically, but go2rtcexecstreams will need to add the full path for ffmpeg which in most cases will be/usr/lib/ffmpeg/7.0/bin/ffmpegExplore
The new Explore pane in Frigate 0.15 makes it easy to explore every object tracked by Frigate. It offers a variety of filters and supports keyword and phrase-based text search, searching for similar images, and searching through descriptive text generated by AI models.
AI/ML Search
Frigate 0.15 introduces two powerful search features: Semantic Search and GenAI Search. Semantic Search can be enabled on its own, while GenAI Search works in addition to Semantic Search.
Semantic Search
Semantic Search uses a CLIP model to generate embeddings (numerical representations of images) for the thumbnails of your tracked objects, enabling searches based on text descriptions or visual similarity. This is all done locally.
For instance, if Frigate detects and tracks a car, you can use similarity search to see other instances where Frigate detected and tracked that same car. You can also quickly search your tracked objects using an "image caption" approach. Searching for "red car driving on a residential street" or "person in a blue shirt walking on the sidewalk at dawn" or even "a person wearing a black t-shirt with the word 'SPORT' on it" will produce some stunning results.
Semantic Search works by running an AI model locally on your system. Small or underpowered systems like a Raspberry Pi will not run Semantic Search reliably or at all. A dedicated GPU and 16GB of RAM is recommended for best performance.
See the Semantic Search docs for system requirements, setup instructions, and usage tips.
Generative AI
GenAI Search employs generative AI models to create descriptive text for the thumbnails of your tracked objects, which are stored in the Frigate database to enhance future searches. Supported providers include Google Gemini, Ollama, and OpenAI, so you can choose whether you want to send data to the cloud or use a locally hosted provider.
See the GenAI docs for setup instructions and use case suggestions.
Improved Tools for Debugging
Review Item Details Pane
A new Review Item Details pane can be viewed by clicking / tapping on the gray chip on a review item in the Review pane. This shows more information about the review item as well as thumbnails or snapshots for individual objects (if enabled). The pane also provides links to share the review item, download it, submit images to Frigate+, view object lifecycles, and more.
Object Lifecycle Pane
The Recordings Timeline from Frigate 0.13 has been improved upon and returns to 0.15 as the
Object Lifecycle, viewable in the Review Details pane as well as the new Explore page. The new pane shows the significant moments during the object's lifecycle: when it was first seen, when it entered a zone, became stationary, etc. It also provides information about the object's area and size ratio to assist in configuring Frigate to tune out false positives.Native Notifications
Frigate now supports notifications using the WebPush protocol. This allows Frigate to deliver notifications to devices that have registered to receive notifications in the Frigate settings, delivering them in a timely and secure manner. Currently, notifications will be delivered for all review items marked as alerts. More options for native notifications will be supported in the future.
See the notifications docs.
New Object Detectors
ONNX
ONNX is an open model standard which allows for a single model format that can run on different types of GPUs. The
default,tensorrt, androcmFrigate build variants include GPU support for efficient object detection via ONNX models, simplifying configuration and support more models. There are no default included ONNX models for object detection.AMD MiGraphX
Support has been added for AMD GPUs via ROCm and MiGraphX. Currently there is no default included model for this detector.
Hailo-8
Support has been added for the Hailo8 and Hailo-8L hardware for object detection on both arm64 and amd64 platforms.
Other UI Changes
Other Backend Changes
This discussion was created from the release 0.15.0 Beta 1.
Beta Was this translation helpful? Give feedback.
All reactions