0.12.0 Beta 7 #5329
Replies: 32 comments 194 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.
-
|
I am impressed with the inference performance of the i3/i5/i7 6th gen and newer CPUs in the answers table.. I have a coral now but it would have been a significant savings to just get a good CPU. Affordable used 6th gen CPU based systems are fairly easy to source on ebay / second hand shops. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks again for all the hard work! |
Beta Was this translation helpful? Give feedback.
-
|
Just because this is the last log message, doesn't mean its necessarily the detect process that is the slowest to exit. Those messages are printed when the processes are told to exit, not after they finish exiting. I still think its better to just try and reduce the time it takes for a graceful exit. |
Beta Was this translation helpful? Give feedback.
-
|
So I have been watching |
Beta Was this translation helpful? Give feedback.
-
|
I just tried and can say I am seeing the same thing. Detection processes take ~20 seconds to exit and the last bit of time is all for one camera process |
Beta Was this translation helpful? Give feedback.
-
|
Double checked this. If I have detect disabled on all cameras, shutdown is reliably < 5 seconds. Often I can watch the |
Beta Was this translation helpful? Give feedback.
-
|
Now being looked at in #5368 |
Beta Was this translation helpful? Give feedback.
-
|
Having trouble with HTTPS restream links:
These same links work fine when used directly in frigate. |
Beta Was this translation helpful? Give feedback.
-
|
You'll want to create an issue on go2rtc for this. |
Beta Was this translation helpful? Give feedback.
-
|
What kind of links are these? Reolink FLV? |
Beta Was this translation helpful? Give feedback.
-
|
Here's to hoping the RTC updates fix my yi-hack cams on WebRTC 😁 |
Beta Was this translation helpful? Give feedback.
-
For anyone else having trouble witht he yi cams. You need to use ulaw or alaw audio. yi-hacks aac causes issues with go2rtc been going for 2 days with little to no issue. |
Beta Was this translation helpful? Give feedback.
-
Can you explain how you specify this? I think my DaFang cameras use the same deal. |
Beta Was this translation helpful? Give feedback.
-
|
It's in the web ui for the camera itself. I figured this out because I saw an issue or discussion posted my the author of the hack, i can't seem to find it. It was either on the frigate page or the go2rtc page. The AAC appears to be too unstable as well as the alternative rtsp server for go2rtc to work properly. |
Beta Was this translation helpful? Give feedback.
-
|
Wyze cam v3 stability / repeated errors (the below block of errors has repeated several times in the last few hours) I believe the FPS limit is a recent addition in beta6 to fix frozen frames IIRC, it might be too aggressive? Error: Config snip: |
Beta Was this translation helpful? Give feedback.
-
you may have not known you had an issue since in beta5 frigate would just keep getting the same frame over and over silently being in an errored state without it being obvious |
Beta Was this translation helpful? Give feedback.
-
Interesting, that could be it! Darn, I'm still getting exceeded fps warnings with ffmpeg on single line for all my Wyze Cams. Any recommendations on workarounds to fix? I'd really love to have go2rtc working for them and not have to revert back. Example: |
Beta Was this translation helpful? Give feedback.
-
|
Not really, you could maybe try making an issue on go2rtc and see if by sharing your stream AlexxIt can track down the issue but I don't think there's anything that can be done for a camera like that from frigate side. |
Beta Was this translation helpful? Give feedback.
-
|
You could configure frigate to connect to the rtsp stream directly instead of go2rtc. That may overload the wyzecam though. |
Beta Was this translation helpful? Give feedback.
-
While I really wanted to restream from go2rtc to only have one connection to camera, I had to go with this approach and use two connections per cam - direct RTSP to go2rtc and direct RTSP to frigate for record/detect. We’ll see if it overloads hah. Thanks! |
Beta Was this translation helpful? Give feedback.
-
|
A general feed back / observation issue: After most restarts of frigate I see a large number of frigate.record and frigate.detect errors since switching to internal gotortc streams configuration. These appear to be related to go2rtc not being fully started, or possibly the first time frigate calls the internal url from go2rtc as the stream is slow to load. Most of these errors seem to go away and not repeat after startup. |
Beta Was this translation helpful? Give feedback.
-
|
Just restarted it twice and it came up clean each time lol.. I will wait for the next time it does it.. Was happing fairly frequently with all of the various testing / config changes. |
Beta Was this translation helpful? Give feedback.
-
|
Here is an example of record having some corruption after reboot, a subsequent reboot corrected it. Sometimes there are only a few of these after restart (via GUI)/reboot(via docker), sometimes none. main hall is a tp-link tapo camera |
Beta Was this translation helpful? Give feedback.
-
|
As far as I can tell those are corrupt segments leftover from the previous run in the cache. |
Beta Was this translation helpful? Give feedback.
-
|
Is there a way to avoid that, should it be cleared on restart? At any rate it seems to be a temporary condition during startup intermittently that I mostly ignore but sometimes generates a concerning number of warnings on startup |
Beta Was this translation helpful? Give feedback.
-
|
it's difficult to know without having more info on the corrupted segment. It can be corrupted for any number of reasons. Perhaps the camera sends bad data when it first connects, perhaps it is isolated to the video data or audio data, etc. etc. |
Beta Was this translation helpful? Give feedback.
-
|
This has been very solid with my setup today using settings below. I've only been using Frigate for a couple of weeks and some of that was on Beta 5, so I don't have much experience for comparison with earlier versions. I haven't integrated Home Assistant yet, but everything else is working great and I don't have any errors in the logs. The only thing I'm still trying to figure out is why the FFMPEG process for my WGCC camera is using around twice the CPU as my Reolink cameras using same resolution and FPS. I've played around with encoding profile and bitrate on the camera but haven't found anything with it yet. It runs at 12% vs 6% with the others. Anyway, just wanted to say I appreciate all the work going into this and to let you know it's working well. |
Beta Was this translation helpful? Give feedback.
-
|
not related only to this release, happened to me on beta5 as well, I'm getting this crash atm with beta7: the tail in syslog is the following: now I know googling the above usually points towards a kernel bug but my kernel is Thanks |
Beta Was this translation helpful? Give feedback.
-
|
What hardware are you running on? How do you have the detector configured? |
Beta Was this translation helpful? Give feedback.
-
|
proc: i9 9900 on last unraid OS, kernel 5.19.17 |
Beta Was this translation helpful? Give feedback.
-
|
Not specifically beta 7 specific but any suggestions for the lowest latency way to get frigate 0.12 cameras into homekit? Maybe some new options that go2rtc might have unlocked? I am using the Home Assistant config but the Homekit accessory setup drives me nuts, and does strange things.. I reset my doorbell cam and I am getting lower latency than before however load times are still kind of slow via home assistant. I know frigate and go2rtc don't DIRECTLY support exporting a homekit camera but I am tempted to try homebridge or others in conjunction to get my cameras more reliably into homekit. Main issue however is that I still want to trigger a homekit event to load the camera on people and doorbell press events. Which is the one thing homeassistant does well. |
Beta Was this translation helpful? Give feedback.
-
|
I know exporting to homekit is on the long term list of goals for go2rtc. For now HA is the only way I've seen people do but have no idea what to expect as far as latency goes. I have a similar setup for my android TVs which shows the MSE live stream in the bottom right corner when a person is detected coming to the door. |
Beta Was this translation helpful? Give feedback.
-
|
With frigate 0.11 streams homeassistant would convert to HLS and have about a 15s delay (mostly useless for doorbell cams), with 0.12 after resetting the homekit device, I now get about a 2-3 second delay however home assistant in general / home kit takes way to long to START / load the stream still sometimes more than 10 Seconds. I know homebridge can do RTSP to homekit cams so I was curious if anyone had tried it out. Also home assistant is still doing very random things with the frigate integration cameras, used as homekit cameras:
There are tickets for this in both home assistant and frigate but it seems like it isn't a priority or specific devs can't replicate. Given how fast the new streams are I would love to get that into my apple TVs with lower load times and latency so I can actually catch the person knocking at my door vs seeing them in the feed AFTER they left 20-30s ago. |
Beta Was this translation helpful? Give feedback.
-
|
Clarification on correct value for live_mode for new UI config I have set the following however no formatted example was given for the possible modes in the documentation other than live_mode: mse Is the following correct for webrtc? I don't see any errors but I find my browsers still defaulting to jsmpeg , maybe it remembers individual settings from before the default was set via cookies or something? Also this new UI setting for live mode does not appear to work on a per camera basis, while I have fixed my remaining cameras it might be good to have a per camera default if a user has some some cameras that are not configured in go2rtc for example so you could have a global default but a specific camera override. However I think it auto falls back to jsmpeg anyway. |
Beta Was this translation helpful? Give feedback.
-
Yes that is correct
Yes it does use a cookie to remember what it was before
This is only meant to be a global default. If a camera isn't setup as restream then yes it falls back to jsmpeg |
Beta Was this translation helpful? Give feedback.
-
|
Got to about 3 hours then go2rtc died on me today AlexxIT/go2rtc#237 |
Beta Was this translation helpful? Give feedback.
-
|
This one is the first one where gortc has actually worked (i have not hit the 3hour point as yet as the fellow mentions above) but my attempted config from beta 5 where gortc didn't work was good as a base for beta 7.
I also notice that some h264 streams don't natively play. I have multiple same branded cameras and one is 4MP and another is 5MP and 8MP.. the 4MP will play h264 with no transcoding just fine but the others i need to transcode with FFMPEG as above. Not sure what is go there but it was an interesting thing. I tried reducing their resolution and it made no difference, neither did toggling H264+. Only using the FFMPEG transcode for the gortc stream was the way to get it working for those higher resolution cameras. |
Beta Was this translation helpful? Give feedback.
-
Thst is incorrect, that hardware preset will do nothing, you can check the go2rtc docs to see that. |
Beta Was this translation helpful? Give feedback.
-
i got that from your comment here - #5358 (comment) once i added that into my cameras they worked? hence i said what i said... sigh i'll try take it out again and see |
Beta Was this translation helpful? Give feedback.
-
|
@NickM-27 yep of course you are correct. I'll amend my original comment so as to not confuse people. honestly have no idea why one moment it didn't work, added that it worked, then remove it and it still works... chasing my tail it seems... in any event it is working beta 7 has been the best yet that still remains true |
Beta Was this translation helpful? Give feedback.
-
I'd recommend creating an issue here or on go2rtc with the go2rtc logs for that. There's a lot of different things that could be causing the confusion.
The correct value would be |
Beta Was this translation helpful? Give feedback.
-
|
No worries. |
Beta Was this translation helpful? Give feedback.
-
|
Stuck camera / high FPS go2rtc (also earlier ticket on this AlexxIT/go2rtc#236): frigate last log:
However Frigate UI shows "no frames have been received, check error logs" and the reported FPS of the camera is over 100. The camera mse / webrtc feeds are still viewable and real time so it "looks" like go2trc is recovering over and over but frigate is not. |
Beta Was this translation helpful? Give feedback.
-
|
I'm in similar boat as @bagobones with my Wyze Cams (v2, v3, and pan variants) and couldn't restream without high FPS/CPU and errors above. Currently working with split connections (one for go2rtc, one for detect/record) but hoping to restream and only need 1 connection to camera. @NickM-27 Will be interesting to see what we find here - thanks for looking into it more! |
Beta Was this translation helpful? Give feedback.
-
|
you could try this now by replacing |
Beta Was this translation helpful? Give feedback.
-
|
Changing my 3 problem cameras now and will see what they look like in a few hours |
Beta Was this translation helpful? Give feedback.
-
|
go2rtc died within an hour AlexxIT/go2rtc#213 so going back to the frigate direct config again for these three cameras |
Beta Was this translation helpful? Give feedback.
-
|
@skylarv hasn't been a full day but the following might work, I just get EOF errors instead of corrupt data warnings in go2rtc when the connection breaks. I created a preset that uses the same ffmpeg flags frigate does by default but for go2rtc The order these ffmpeg parameter templates are applied also apparently matters so #frigatedefaults needs to be applied first before the #video=copy etc Frigate like default Video copy (no transcode) Two audio transcodes, aac for recording to match the frigate template, and opus for webrtc compatibility |
Beta Was this translation helpful? Give feedback.
-
|
I am not able to download beta6 or 7 image. any tips how to downloads lates image? |
Beta Was this translation helpful? Give feedback.
-
|
|
Beta Was this translation helpful? Give feedback.
-
|
Is it possible to use intel Quicksync for hardware acceleration in combination with the google coral? I have a intel i5 12600k. If i have hardware acceleration disabled in the config, all logs looks fine: Go2rtc Once I enable hardware acceleration under ffmpeg: I get the following log errors: Go2rtc still looks fine: I have the following mapping in my unraid docker container: What I'm wondering is, do I need hardware acceleration? The main and sub streams from my cameras are already h264 streams. |
Beta Was this translation helpful? Give feedback.
-
|
Like I said I have a similar setup, mapping renderD129 to renderD128 works for me without issue. You could maybe try doing -c:v h264_qsv instead of the preset and see if that works for you |
Beta Was this translation helpful? Give feedback.
-
|
Not working, I'll disable it for now. Thank you for trying to help and your time! |
Beta Was this translation helpful? Give feedback.
-
|
Good news! Got it working! I got the feeling that there could be something wrong with ffmpeg args. So I changed those to defaults. Went from: To this: Now I can see it's working:
Only thing I'm wondering is, are the default "args" okay if everything is working fine? |
Beta Was this translation helpful? Give feedback.
-
|
I'd suggest just removing everything besides the hwaccel_args part as everything else is default and there's no reason to be setting it in your config |
Beta Was this translation helpful? Give feedback.
-
|
The default args are preferred. You shouldn't define them at all if they are the default values so you don't have to modify your config if the default values change in the future. |
Beta Was this translation helpful? Give feedback.
-
|
For anyone having audio sync issues on recordings: In my case, this camera (Hikvision) provides video in |
Beta Was this translation helpful? Give feedback.
-
|
Do we no longer need the output args in beta 7 Reolink camera setup? I don't get audio in my recordings if I don't use the output args https://deploy-preview-4055--frigate-docs.netlify.app/configuration/camera_specific/#reolink-cameras |
Beta Was this translation helpful? Give feedback.
-
|
You will always need the output args for audio no matter the camera. They were removed because that config is not camera specific |
Beta Was this translation helpful? Give feedback.
-
|
This watchdog event should maybe be a a WARNING instead of INFO. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the update. If I am getting the errors "frigate.record WARNING : Unable to keep up with recording segments in cache for Cam1 Keeping the 5 most recent segments out of 8 and discarding the rest..." etc. (This happens for both of my cameras) What should my next action be? I am also having issues with recordings on my H265 camera since the recent 0.12.0 beta releases - the live feed is always stable. The other H264 camera is fine. Sometimes recording works but 95% of the time it doesn't. No errors in any of the logs that I can see apart from the above ones, but they are for both cameras and one works fine. When I try to access an event on that camera with the issues it just says: I will change it back to H264 for now to see if things improve. Strange as it had worked fine before the recent BETAs. |
Beta Was this translation helpful? Give feedback.
-
|
Ok thank you, apologies it must be something else going wrong I just cannot think what, I have all auto updates turned off now. I am now just updating the host Pi and trying some other things. I will report back with my findings, fingers crossed. Thanks again |
Beta Was this translation helpful? Give feedback.
-
|
It's most likely that you were silently losing those segments before and just didn't know. You can try turning on debug logging for the record process for more info: logger:
logs:
frigate.record: debug |
Beta Was this translation helpful? Give feedback.
-
|
Thank you very much, I have added now that and updated the Pi :). |
Beta Was this translation helpful? Give feedback.
-
|
Same issues sadly, this time straight after a reboot even, but I am still looking into it. With that debug info I can see that one camera averages around 4 seconds to copy the clip each time and the other camera averages 10 seconds per a clip to copy (peaks at 13 seconds). I thought that was what the cache was there to help with, but perhaps it thinks the cache is going to fill too soon. It is only 30MB usage out of the 1GB temp file system assigned, I know space is needed for download clips too as Nick kindly explained before. |
Beta Was this translation helpful? Give feedback.
-
|
That is a very long time to move a small file. The files should be 10s long, so that means writes to your disk are too slow to keep up with your camera feeds. I don't think it matters how big the cache is at those speeds. It will eventually fill up if your disk can't write 10s worth of data in 10s. |
Beta Was this translation helpful? Give feedback.
-
|
how is everyone getting audio working on the hass side? I can get it if I create a generic-cam or use the webrtc card. |
Beta Was this translation helpful? Give feedback.
-
That's old you should be in beta 4 |
Beta Was this translation helpful? Give feedback.
-
interesting, it didn't show up as available. |
Beta Was this translation helpful? Give feedback.
-
Been out for a few days, you may need to ping HACS to look manually https://github.com/blakeblackshear/frigate-hass-integration/releases/tag/v4.0.0-beta4 |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the help. I had to delete and re-add my frigate instance as well. It was lagging and/or freezing horribly with a lot of buffering. The stream appears to be the MSE (about 1-2 seconds behind same as vlc and generic-cam) no more buffering but still no sound. hmm. |
Beta Was this translation helpful? Give feedback.
-
probably best if you just make an actual issue so we can see the config |
Beta Was this translation helpful? Give feedback.
-
|
If anyone else runs into the issue, i figured out why my webrtc video windows where offset about an inch down vs the other video modes. I have an ultrawide monitor and I have a extension called Ultrawidify installed. Turns out it was the problem and I just needed to set a page exclusion. |
Beta Was this translation helpful? Give feedback.
-
|
Sometimes HA seems unable to access frigate API, this happens once every 10 min or so, there is no impact in recording, detection etc. but not entirely sure if this has some other underlying meaning I don't know about: Frigate logs: HA logs: if you look closely at the timestamps, HA can't access Frigate for an instant and frigate logs a warning: |
Beta Was this translation helpful? Give feedback.
-
Then your WebRTC card integration isn't setup correctly. I'd suggest removing it and setting it up again pointing at |
Beta Was this translation helpful? Give feedback.
-
|
so I think webrtc doesn't work for me and frigate-card simply falls back to whatever, since clearly I get a stream using but when I try this, it errors out plus.. the webrtc url doesn't work for me |
Beta Was this translation helpful? Give feedback.
-
|
The url: camera1 isn't working because you're currently running 2 different instances of go2rtc. One inside frigate and one inside HA. need to fix that as I described above. |
Beta Was this translation helpful? Give feedback.
-
|
I also just realized that the frigate card is not setup correctly. This is mine which is working perfectly showing MSE and WebRTC (with WebRTC integration setup as I described above) type: custom:frigate-card
live:
webrtc_card:
ui: true
mode: webrtc,mse
muted: true
preload: false
show_image_during_load: false
cameras:
- camera_entity: camera.front_doorbell_cam
live_provider: webrtc-card
webrtc_card:
url: front_doorbell_cam
id: front_doorbell_cam
|
Beta Was this translation helpful? Give feedback.
-
this was the solution, fantastic, thank you so much @NickM-27 , now I've got audio too 👍 |
Beta Was this translation helpful? Give feedback.
-
|
Im having 2 issues with Beta 7:
Would it be best to discuss these in an issue where I can post my log output & config or here? |
Beta Was this translation helpful? Give feedback.
-
Having a screenshot or video of this would be helpful, I don't think I am seeing this issue.
That is incorrect, it is the same player.
It could be a network issue with TCP / UDP packets. It could also be that the camera is sending bad data which makes webrtc choppy. Or it could be that the device is struggling the keep up with the demand. More info is needed |
Beta Was this translation helpful? Give feedback.
-
|
Here is a screenshot of the player I'm given when accessing from the recordings page. You can see a gap at the top of the player that is preventing the buttons along the bottom from being fully accessible. For reference this is on an iPhone 13 Here is a screenshot of the player I'm given when accessing from the events page. Maybe im just being silly but it seems/acts different than what I'm given from the recordings page (with the -10s, play, +10s buttons visible on after single touching the screen, along with a different set of buttons along the bottom row. Less buttons overall than what I see from the recordings page): Regarding the WebRTC issue i will follow up with my full config when i get home this evening. Very well could be a camera or network issue. I know that I just passed the webRTC ports thru to the container (which runs as privalaged). I did not assign the host network mode. |
Beta Was this translation helpful? Give feedback.
-
|
it seems to be due to the way that the browsers have overlays on the bottom along with the fact that the recordings view has the playlist button on the left. |
Beta Was this translation helpful? Give feedback.
-
|
Curious.. how stable is everyone's camera FPS? I enabled the camera fps on each of my cameras in the HA integration to watch for detection failures.. as 0fps or fps much greater than the "detect" FPS are indicators something is wrong. What I wasn't expecting after graphing the data was HOW variable they where. I am curious if anyone else has graphed these values.. While I was spot checking them most of the time they looked fine IE with in .1 FPS of what was set, but according to these graphs drops and reconnects etc are showing a lot of instability in the fps. Two of my cameras are set to detect to 10fps while the rest are set to 5fps. in the config.
|
Beta Was this translation helpful? Give feedback.
-
|
None of my cameras are that stable, 3 of them are technically rebadged dahua but dahua makes a wide range of quality / price cameras. Also all of my cameras are on WiFi which doesn't help (no practical way to run ethernet to most of the needed locations but there is power there. |
Beta Was this translation helpful? Give feedback.
-
|
@bagobones I'd suggest looking into power line Ethernet. I'm going to use that and it's been quite stable in my testing. |
Beta Was this translation helpful? Give feedback.
-
Powerline ethernet is sort of hard wired wifi that tries to use a common ground as an antenna. It is often worse than wifi in condo/townhouse complexes where grounds between units will likely be shared. I have tried to use it in the past but during pairing it tried to connect to a neighbor's house who left all the defaults set to factory including the network ID etc. Performance was worse than my Wifi which is actually quite good as I have 3 APs throughout the house and very good signal strength. THe proboblem is cheap cameras only use 2.4ghz which is always saturated by neighbours. Only three technology's I would suggest are proper ethernet runs , MoCA-Adapters (similar idea to Powerline but uses Coax cable which is shielded and may already been run for TVs through the house), better WiFi devices, 5Ghz capable cameras. MoCA doesn't help me in my current unit however. I may be moving out of the town house within a year so I am not willing to drill and snake the ethernet everywhere it is needed. It is a 3 level townhouse so most cameras in the mid floor so no easy way to run cables as there is a finished floor above and below. At that time I will probably re-do everything with as many direct wired cameras as possible. 4 of my existing cameras support direct ethernet as well as wifi so I will probably just convert them unless I find cheaper / better POE cams. |
Beta Was this translation helpful? Give feedback.
-
|
Yeah, like anything YMMV. I used powerline in a house for years in other non camera applications and it was much more stable than WiFi. Will be curious how it does for cameras but so far bench testing, it has been very solid. |
Beta Was this translation helpful? Give feedback.
-
In a detached home it tends to work better, assuming the home doesn't have any quirky electrical issues. My main problem is low quality 2.4Ghz cameras to start with.. If I am going to get better cameras they will be direct wired or 5Ghz. |
Beta Was this translation helpful? Give feedback.
-
|
birdseye -> restream After playing around with webrtc for all my other camera streams I played around with birdseye -> restream and in all cases the load time over head for restream is substantial vs jsmpeg if no one is consuming the stream then the first client connects.. It is even slower to start than the webrtc feeds as frigate is already always consuming the restream on those so go2rtc will have them loaded. Is there anything that can be done to reduce the startup time (other than leaving a client connected) or is it simply best to leave it jsmpeg / frigate native? |
Beta Was this translation helpful? Give feedback.
-
|
It should be fixed in the next beta, hopefully birdseye performs better for you then |
Beta Was this translation helpful? Give feedback.
-
|
Nice |
Beta Was this translation helpful? Give feedback.
-
|
Actually, it might be good for you to confirm if it's better. You could add your own go2rtc stream called birdseye_test as (Where you just need to fill in the width and height you have set)
|
Beta Was this translation helpful? Give feedback.
-
|
It seems like the update config is instant-2s and the default is instant-5s so there does appears to be an improvement. I logged into the go2RTC dashboard and made sure all streams had gone back to zero and refreshed the client to make sure the card was not preloading. I also tried from the go2RTC dashboard a few times.
Might want to just leave this one be, might not be worth restreaming, it isn't like birdseye has a high framerates. |
Beta Was this translation helpful? Give feedback.
-
|
yeah for your usecase doesn't seem like there will be any advantages. Guess I'm spoiled by my nvidia GPU lol |
Beta Was this translation helpful? Give feedback.
-
|
@blakeblackshear @NickM-27 can we get a new beta now that the new go2rtc has been released with various (vital) fixes? |
Beta Was this translation helpful? Give feedback.
-
|
Out of interest, is it possible to activate a I ask because I have a few cameras that are using H265 with no way to change them to H264. While I'm fine with them recording in H265 it's annoying when trying to watch in browser because you will have some cameras which won't work at all. I tried using The CPU usage increases significantly so I don't really want to run it all the time when it's only needed a few minutes a day. Alternatively, is it possible to get a full resolution snapshot from the restream source? |
Beta Was this translation helpful? Give feedback.
-
|
You probably want |
Beta Was this translation helpful? Give feedback.
-
No GPU available on that server, but thanks for the tip! |
Beta Was this translation helpful? Give feedback.
-
Is that needed anytime I want to use hwaccel? even if I have it it enabled globally via ffmpeg? |
Beta Was this translation helpful? Give feedback.
-
it is for using hwaccel for manual go2rtc streams which is entirely separate from the hwaccel that is configured for frigate itself. it's important to point out that go2rtc only needs hwaccel when it is transcoding streams which is a relatively niche usecase |
Beta Was this translation helpful? Give feedback.
-
Got it thanks. |
Beta Was this translation helpful? Give feedback.
-
|
Are the Frigate / Go2rtc / Nginx logs all just held in memory? I have had a sudden jump in stability and now I am wondering if it is because I suppressed some of the noisy logs. |
Beta Was this translation helpful? Give feedback.
-
|
Yes they are held in memory and they rotate automatically |
Beta Was this translation helpful? Give feedback.
-
|
What is the frequency / trigger? |
Beta Was this translation helpful? Give feedback.
-
|
Each file is rotated individually when it reaches 10MB |
Beta Was this translation helpful? Give feedback.
-
|
I'm running HA on a Bmax b2s along with a Coral USB. Anytime I reboot, Frigate goes to start then crashes because It cant find the coral. It requires me to physically remove it and plug it back in. Anyone run into this issue before? Thanks a lot! |
Beta Was this translation helpful? Give feedback.
-
|
I don't believe anyone else has reported that issue but it was a potential issue, should be fixed in beta 8 |
Beta Was this translation helpful? Give feedback.
-
|
Awesome! I will give beta 8 a try when its released. Thank you! |
Beta Was this translation helpful? Give feedback.
-
With all the updates to errors etc, I have a feeling this warning should be a counter on the system or recording page to help highlight bad cameras.. I was often wondering why I would randomly see skips in my events etc and it probably comes down to corrupt segments being discarded.. This would help weed out bad configs / cameras that should be replaced. |
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 6
Changes Since Beta 5
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.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.
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: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 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-beta6
Images:
ghcr.io/blakeblackshear/frigate:0.12.0-beta6ghcr.io/blakeblackshear/frigate:0.12.0-beta6-tensorrtThis discussion was created from the release 0.12.0 Beta 6.
Beta Was this translation helpful? Give feedback.
All reactions