0.12.0 Beta 5 #5156
Locked
blakeblackshear
started this conversation in
General
0.12.0 Beta 5
#5156
Replies: 53 comments 283 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.
6 replies
-
This is incorrect and doesn't exist so it will 100% cause errors |
Beta Was this translation helpful? Give feedback.
-
|
Also can't help without logs |
Beta Was this translation helpful? Give feedback.
-
|
whats the new config?? when is use the, record: preset-record-generic-audio I have no issues & errors PS I'm trying not to flood this channel have made a new AMD GPU chat. not sure if this is the right way to resolve my issue. |
Beta Was this translation helpful? Give feedback.
-
Yes
It doesn't exist so it will cause errors, no question about it |
Beta Was this translation helpful? Give feedback.
-
|
above is my current config using the record: preset-record-generic-audio but my GPU is not doing much, looks like CPU has the load. logs are. |
Beta Was this translation helpful? Give feedback.
-
|
I was running it on Synology NAS (11.0), but then switched to custom build hardware running Ubuntu Server and CasaOS on top. I had switched because the custom build had a gpu to assist in the hardware accel. Nickm you said I could use the go2rtc function to by pass the ports? By the way, thank you both for helping and suggesting everything you have. I would like to keep on using CasaOS on top of ubuntu server, but if I can't figure it out I may have to switch and install ubuntu and install docker. |
Beta Was this translation helpful? Give feedback.
2 replies
-
Will disable listening on those ports |
Beta Was this translation helpful? Give feedback.
-
Same error |
Beta Was this translation helpful? Give feedback.
-
|
Hello, I've been experiencing some issues with the new betas I started with beta2 and it has persisted throughout. Firstly frigate takes a good long time to initialize. they come after go2rtc loads up (streams are available via VLC) I am also losing the JSMPEG stream as well as the stillframes on the dashboard and HASS camera entities. intermittently once this happens I need to restart frigate: This is mostly on cameras 4 and 5 but it can happen to any of the others as well, sometimes all of them. config items in "<>" are not acutal names etc: Lastly, I stopped getting sound on the HASS cameras with beta4, I assume that has to do with the go2RTC changes and I need to wait for the HACS version to be updated? any help or advice would be appreciated. TIA |
Beta Was this translation helpful? Give feedback.
10 replies
-
That was the first code line. all that shows in the log is: It looks like it may be hanging on peewee migrate? take notice of the log times even on the line for "there is nothing to migrate" there is a 2 1/2 minute difference in this case. (fortunately a 'short' one this time.) It used to only take about 30seconds for frigate to do a full restart. |
Beta Was this translation helpful? Give feedback.
-
|
is your database file kept on a hard drive or something? I see no reason for that to be the case |
Beta Was this translation helpful? Give feedback.
-
The I have not altered the db location. so it should be on my boot drive which is a 1TB NVME. |
Beta Was this translation helpful? Give feedback.
-
that is incorrect, the default location of the DB is right next to the recordings in the /media folder, so this might be your issue |
Beta Was this translation helpful? Give feedback.
-
Well that may do it. =) |
Beta Was this translation helpful? Give feedback.
-
|
I run my Frigate in the docker/portainer (Privileged mode) alongside HA on a laptop with installed Debian on it. I can see in the go2rtc logs a lot of lines like this: AND sometimes line like this(for Reolink POE RLC-510A): AND sometimes line like this(for NEDIS): Any ideas to what this error is referring? I can provide more info/logs if needed. I have 6 cameras. 4 Reolink (2xRLC-510WA and 2xRLC-510A) and 2 Nedis ones. In general my setup works. I have also a question about birds-eye view. Looks like it always uses detect stream. I have Reolink cameras. I would like to use main stream for recording and live view and ext stream for detect. We can point live view to main stream and it works. But birds-eye and cameras view uses detect stream. Are you planning to implement a possibility to choose which stream is used in the birds-eye/cameras view also? |
Beta Was this translation helpful? Give feedback.
12 replies
-
|
So you are saying I have set it up not properly? |
Beta Was this translation helpful? Give feedback.
-
|
Are you certain that you haven't set a retain mode at the camera level? You should only ever see that message if you are using |
Beta Was this translation helpful? Give feedback.
-
|
Here is the whole config: |
Beta Was this translation helpful? Give feedback.
-
|
I think I see how/why this is happening. You can ignore the messages. It's not working any differently than it did before. It's just logging a warning that I don't think is valid. |
Beta Was this translation helpful? Give feedback.
-
|
Ok, thank you. Apart from these warnings Frigate has been working pretty well. Great work guys. |
Beta Was this translation helpful? Give feedback.
-
|
Beta 5 available shortly in Unraid. |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
|
Beta Was this translation helpful? Give feedback.
-
|
I see this error for all the cameras:
The got2rtc config: And the cameras config: The FFMPEG config: I'm not sure if it is related to this error, but I can hear the audio on the frontend ui also in the home assistant, but when an event occurs, the recorded clip doesn't have any audio. |
Beta Was this translation helpful? Give feedback.
19 replies
-
|
Ok, I deleted all the second ffmpeg streams and records still are saved with no audio... |
Beta Was this translation helpful? Give feedback.
-
I correct myself, now clips are not even beeing saved. |
Beta Was this translation helpful? Give feedback.
-
in that case there should be logs |
Beta Was this translation helpful? Give feedback.
-
Added this and also aac as audio input path and now works. This new way of defining streams is so confusing for me... |
Beta Was this translation helpful? Give feedback.
-
|
we are going to write a migration guide, in the meantime hopefully this helps clear things up a bit go2rtc:
streams:
balcon:
- rtsp:https://user:[email protected]:554/stream1 # <- this is a copy of your stream
- ffmpeg:rtsp_cam#audio=opus # <- this creates an extra audio track in opus format (along with the existing video and audio formats from the original stream)then rtsp:https://127.0.0.1:8554/balcon?video=copy&audio=aac tells go2rtc to return the video as is and return the audio track in aac format. If there is no track with aac format then there will be blank audio. |
Beta Was this translation helpful? Give feedback.
-
|
Any ideas why my logs are filling with these: Otherwise everything seems to be working. |
Beta Was this translation helpful? Give feedback.
7 replies
-
|
Seems like AlexxIT/go2rtc#144 maybe due to an issue coming back up or perhaps your network has ports blocked which shouldn't be |
Beta Was this translation helpful? Give feedback.
-
|
I don't think that there even can be blocked ports in the LAN ? Well.. maybe HAOS blocks ? |
Beta Was this translation helpful? Give feedback.
-
there absolutely can, VLANs and sectioned off local network are not uncommon in the HA crowd
okay, if that's the case then perhaps it's just camera issues and you can let it continue on as is. |
Beta Was this translation helpful? Give feedback.
-
|
Weird but flooding stopped when I made this change: to this: |
Beta Was this translation helpful? Give feedback.
-
|
So your recordings are now being saved in native audio (I am guessing it is not AAC). If the audio in recordings still works then it is no issue |
Beta Was this translation helpful? Give feedback.
-
|
Wow, I'm gone for a week and miss 2 betas! Trying to play catch-up and read all the comments. I think I have all my config updated after comparing to the new docs and a few of the posts here and on Beta 4 discussion but for some reason my live view dropdown only has jsmpeg available, no mse or webrtc. I'm sure I overlooked or am misinterpreting the docs or something but can't seem to figure it out; no errors or anything. |
Beta Was this translation helpful? Give feedback.
2 replies
-
|
your camera in |
Beta Was this translation helpful? Give feedback.
-
|
Dang it! I knew it was something dumb I was overlooking. I should know better than to use capital letters in the first place! Appreciate it! |
Beta Was this translation helpful? Give feedback.
-
|
Using tensorrt, ffmpeg is not working for me. Example config: I got this error at startup: And few seconds later the container crashes. |
Beta Was this translation helpful? Give feedback.
7 replies
-
|
looks like you don't have the correct nvidia runtime set or something, it's working as expected for me in Unraid |
Beta Was this translation helpful? Give feedback.
-
|
to be clear this is happening on the tensorrt image? |
Beta Was this translation helpful? Give feedback.
-
|
Sorry, I'm so stupid that I didn't follow my own instructions and indeed, I was missing the addition of the --runtime=nvidia extra parameter... It's working perfectly. |
Beta Was this translation helpful? Give feedback.
-
I can't imagine all that you're juggling keeping those templates up to date haha I wouldn't sweat it. Thanks for confirming |
Beta Was this translation helpful? Give feedback.
-
|
I also see a CPU usage reduction from beta3:
|
Beta Was this translation helpful? Give feedback.
-
|
running beta4 the last couple of days and its been great. i successfully setup webrtc for live view and confirmed it is working on iOS. i did not have to change network mode to host or bridge, just passed the tcp/udp ports thru docker-compose. however ive noticed when i set the live view mode to webrtc, i have to click on the big play button to actually start the stream which is a minor annoyance. just thought i would point that out |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
I have noticed since since moving from Beta 3 to 5, my CPU is pegged at 100%; I know it's been mentioned on and off in issues; but can't figure out what would have changed from 3 to 5 to have my CPU go from 60-70% to 99.9%. I have tried turning off Birdseye and a trying a few other settings but nothing makes a difference. Did something change between 3 and 5? |
Beta Was this translation helpful? Give feedback.
5 replies
-
|
Actually, a number of users have reported reduced CPU usage as we have tuned the presets. We do of course have the system page which is helpful for these sorts of things. I'd also suggest trying |
Beta Was this translation helpful? Give feedback.
-
|
Thanks, good to know it wasn't another thing I overlooked! I indeed tried the |
Beta Was this translation helpful? Give feedback.
-
|
Dropped back to Beta3, CPU hanging at 67%, which is the best it's ever been. I'll have to tinker with my config in Beta5 to see if I maybe missed something. |
Beta Was this translation helpful? Give feedback.
-
|
The only reason you would see performance differences between beta 3 and 5 would be configuration based. Nothing would have changed in Frigate itself that would cause a change here. The way streams are specified in go2rtc is a little different, but it should be possible to match the performance of beta3 in beta5 with the right configuration. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for confirming. I am going to revisit the docs and make sure I am setting things up correctly with the changes to the restream setup in the config from 3 to 5. |
Beta Was this translation helpful? Give feedback.
-
|
what is "VAINFO" supposed to return on the System page? I've been running beta 4 for a few days and not having any issues but noticed this error when selecting that button:
I can post my config and or logs if needed. |
Beta Was this translation helpful? Give feedback.
2 replies
-
|
Depends on what GPU / iGPU you have. Looks like you're using nvidia so that's not a concern, it's mainly for AMD / intel |
Beta Was this translation helpful? Give feedback.
-
|
understood, thanks for the reply. and yes i am using nvidia. |
Beta Was this translation helpful? Give feedback.
-
|
Hello, Can some one tell me the reason why when I view the camera info in go2rtc it shows like this the stream with localhost does not work in VLC but the one with the Ip address does. PS. How do I post my frigate.yml without it looking weird? Thanks in advance! |
Beta Was this translation helpful? Give feedback.
1 reply
-
that is just the URL of the producer, which in this case is ffmpeg.
localhost means from inside the device that is running so that is 100% expected
use three backticks ``` |
Beta Was this translation helpful? Give feedback.
-
|
@NickM-27 Got it, Thanks for the help. |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
seems to be crashing more now with beta 5. have to restart a few time. can you see anything obvious in my config or logs. |
Beta Was this translation helpful? Give feedback.
5 replies
-
How much tmp cache do you have set? I'd recommend increasing it |
Beta Was this translation helpful? Give feedback.
-
|
@NickM-27 how do i increase size. ??? is that in the docker ?? |
Beta Was this translation helpful? Give feedback.
-
|
You're running Unraid so go to the extra args section and edit |
Beta Was this translation helpful? Give feedback.
-
|
copy in the docker edit under extra parameters in advance mode. addedan extra 0 to the -
|
Beta Was this translation helpful? Give feedback.
-
|
|
Beta Was this translation helpful? Give feedback.
-
|
Any thoughts on if there is or will be a way to have no hw_accel_scale preset applied when defining custom args on the detect output? The "default" preset that always gets applied in this case may cause a conflict with any hardware scaling filters in the custom args. My use case below is surely atypical/hacky, but I imagine others may be doing something more basic that would include hardware scaling. At the moment, I'm just modifying the presets in a fork, so not a big deal. My camera's sub streams are poor quality, so I was taking the main stream, dropping the FPS to 10, scaling, and then reencoding to publish for live viewing at the same time as dropping the FPS to 5 before outputting for detection. |
Beta Was this translation helpful? Give feedback.
4 replies
-
|
If you use a hwaccel preset it will use the scaling / vf output and this important even in cases no scaling is done as it still reduces GPU usage compared to the previous approach. If you're going to use custom output args like that I'd suggest just not using a hwaccel preset either. |
Beta Was this translation helpful? Give feedback.
-
|
I wasn't clear on that part, but I was not using a hwaccel preset either... (those args were defined globally in the config, and are the same as the vaapi preset). From the ffmpeg presets, it applies the "default" scaling preset even when using custom hwaccel args. Is that on purpose? |
Beta Was this translation helpful? Give feedback.
-
|
Yea that's on purpose, same behavior as 0.11 |
Beta Was this translation helpful? Give feedback.
-
|
Got it. Yeah playing with it a bit more it's the fps filter (not the scaling filter) in the default preset that caused the problem for me... but mine is definitely a weird use case, so all good. |
Beta Was this translation helpful? Give feedback.
-
|
Hello! I have 5 cameras that output only 15 FPS each, I have go2rtc restreaming configured and seeing intermittent high CPU usage (95%+) on frigate host (debian lxc on proxmox with openvino and hw accel pass through - no google coral). Didn't make any changes to FPS in configs so it'll be using default of 5 for detect. When looking at system page, camera FPS varies from 5 to 100+? Trying to figure out why the FPS is spiking and CPU is high. This wasn't an issue with v0.11 so seems specific to v0.12?
|
Beta Was this translation helpful? Give feedback.
1 reply
-
|
This is an issue with qsv, has already been fixed for the next beta |
Beta Was this translation helpful? Give feedback.
-
|
To post something positive frigate + go2rtc + RTSPtoWebRTC in home assistant is a complete game changer for low latency camera viewing... Once you sort out all of the new configuration needed. I was completely shocked when I saw the near real time webrtc view in frigate, then after some struggles was AGAIN blown away when I got it working on HA even outside my network (after NAT / firewall / STUN config was corrected). I have an indoor cam that can see me at my desk and waving at myself was really groundbreaking when I was used to at least 1 second delay at best or 5-15 at worst. I hope I can get my last two cameras working with restream and webrtc in the next beta! |
Beta Was this translation helpful? Give feedback.
10 replies
-
That's probably because you're using the camera.entity instead of url with the name of the camera in your go2rtc config. The WebRTC card is built on top of go2rtc directly. Another advantage is that it can also use MSE (not just WebRTC). type: custom:webrtc-camera
url: backyard_camAlso, you can see AlexxIT/go2rtc#218 (comment) for an example of what I'm talking about. If you don't have issues that's great, I'm just simply saying what is recommended. |
Beta Was this translation helpful? Give feedback.
-
|
The go2rtc documentation has been updated at https://github.com/AlexxIT/go2rtc#module-hass to cover the installation and benefits of WebRTC Camera vs RTSPtoWebRTC and talks about using the customer camera card. Still seems a bit more confusing to setup.. also adding another layer I am currently using the custom frigate-hass-card which has some webrtc support which seems like it can stack on top using the AlexxITs card when installed.. Sort of gets complicated at that point but I might go that route. |
Beta Was this translation helpful? Give feedback.
-
|
I use webrtc-card inside of the frigate card already so happy to help out however. Has been working great for me and setting up the webrtc card integration is super easy if HA and frigate are on the same docker network |
Beta Was this translation helpful? Give feedback.
-
I have frigate split out on a dedicated machine now as overhead from restream / doube-take etc was getting too high and unresponsive as well as interrupting other dockers I had on my HA host. It also let me bundle up and separate frigate storage which still has no configurable limit. |
Beta Was this translation helpful? Give feedback.
-
|
Gotcha, in that case you'll need to specify |
Beta Was this translation helpful? Give feedback.
-
|
Small visual issue on desktop chrome in the frigate web UI, both the mse and webrtc video modes leave a large blank / gap area under the live / debug text. The jsmpeg player does not do this. The video shifts down the screen about an inch vs the jsmpeg mode. |
Beta Was this translation helpful? Give feedback.
2 replies
-
|
Can you show a screenshot? I have not seen this. |
Beta Was this translation helpful? Give feedback.
-
|
Hmm Interesting.. This may only be happening on my main home PC it isn't happening on my work PC or mobile.. I will do more testing.. Maybe adblock or something is messing with the page |
Beta Was this translation helpful? Give feedback.
-
|
I'm having an issue trying to get beta5 running. I built the docker container from |
Beta Was this translation helpful? Give feedback.
4 replies
-
|
You should not be building the container. Just use the prebuilt images. |
Beta Was this translation helpful? Give feedback.
-
|
The only reason I built it is I don't see beta5 on dockerhub. It only goes up to beta2. Should I be using a different container repo? |
Beta Was this translation helpful? Give feedback.
-
Recommend reading the header on dockerhub
|
Beta Was this translation helpful? Give feedback.
-
|
I'm sorry, I totally looked for a package on GitHub too. Thank you for pointing that out for me as I did miss that previously 🙂 |
Beta Was this translation helpful? Give feedback.
-
|
Quick question - this is unique to my single Wyze Cam running wz_mini_hacks custom firmware, can't get the audio to work via go2rtc. Looks like it uses pcm_s16le? Any suggestions on what to use for go2rtc ffmpeg and frigate input path to get audio working? |
Beta Was this translation helpful? Give feedback.
4 replies
-
go2rtc:
streams:
wyze:
- rtsp:https://camera-ip-here:8554/video6_unicast/
- ffmpeg:wyze#audio=aac |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the quick reply! I tried aac and no audio on webrtc player https://frigate-ip-here/live/webrtc/stream.html?src=wyze-minihacks. aac works for regular wyze firmware but not for wz_mini_hacks firmware? I do get audio when hitting the rtsp of camera directly though so I know the camera's audio is working. Hmm... |
Beta Was this translation helpful? Give feedback.
-
|
webrtc doesn't support AAC so, if you are using the setup above exactly then it should be working. If not then you'd want to use go2rtc:
streams:
wyze:
- ffmpeg:rtsp:https://camera-ip-here:8554/video6_unicast/#video=copy#audio=aac#audio=opus |
Beta Was this translation helpful? Give feedback.
-
This fixed it and audio works now - you're the best! Thanks! |
Beta Was this translation helpful? Give feedback.
-
|
Appreciate all the work on Frigate and the ability to utilize Home Assistant. The added features on ver 0.12 beta especially the cleaning for storage enhances its stability. Can I suggest that instead of the disk capacity, that a max storage setting to used to limit the space disk used. |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
Right now it's just there to ensure frigate's stability. In future versions there may be additional customization for its behavior. |
Beta Was this translation helpful? Give feedback.
-
|
Anyone using the Amcrest AD110 with restream? Seems like it is randomly failing "No frames received..." and not recovering with the restream config a few hours after config. (probably another just wait till beta 6 and newer go2rtc build item) I have 8 cameras and my results with restream so far are:
All of these cameras work under a legacy style direct config in frigate 11.1 or 12 without go2rtc restreaming I will also note from a stability point of view that ALL of my cameras fail (no frames errors) if I even configure the reolink cameras at all with restream, they take all of the recording and detection processes offline however webrtc viewing seems to continue to work. ONly noting this because a one bad camera I would hope would not take down the whole system |
Beta Was this translation helpful? Give feedback.
11 replies
-
I have updated the release notes
This seems like a good way to go, I think this can be done. |
Beta Was this translation helpful? Give feedback.
-
|
I just realized that DEV SHM is already displayed on the storage page.. seems like it would be very simply to do the calc of detection resolutions and camera number and add it to the UI. |
Beta Was this translation helpful? Give feedback.
-
|
@bagobones yes, I also think so. PRs are always welcome as well! :) |
Beta Was this translation helpful? Give feedback.
-
You probably don't want me submitting code with my current skill level in those areas. Just observing a likely reliability and support issue that can probably be fixed with data already on hand |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
|
Small note on Recordings & Snapshots it appears to show the total space used on the mount and the total size of the drive which is more important to the app to find when it will run out. It doesn't actually show how much space is used for JUST Recordings & Snapshots.. It might be useful to display that as well. I am currently moving my install to a dedicated host and when I checked the actual space on disk the the Recordings & Snapshots actually only took up about 750GB but the frigate value was over 2TB. |
Beta Was this translation helpful? Give feedback.
5 replies
-
Displaying the specific size used just for recordings & snapshots would require spinning the drive up for every stats check which is not acceptable. |
Beta Was this translation helpful? Give feedback.
-
|
Due to motion recording my drive is almost always spun up anyway but I understand it would not be good for those doing pure object recording. Seem like frigate will have to poll the drive for free space anyway will it not as part of the drive space run out feature? knowing the size of the DB / recordings / snapshots would be useful info for the user Alternate option might be to get it at startup (display the time stamp), then have a refresh button on the storage page so the user could optionally check the current state? It's just a nice to have.. |
Beta Was this translation helpful? Give feedback.
-
It's not that simple. For example I personally have a fuse file system which means I have an HDD and an SSD which appear as one drive to frigate. Frigate writes to the SSD and the only time the HDD is spun up is when the SSD is full and recordings are being moved or when recordings are being deleted (which happens twice a day due to my config). Setups like this will spin up much less frequently.
No, checking the current free space of the entire file system (as opposed to the used space of a specific part of the file system) does not cause the drive to spin up.
That is potentially a different approach |
Beta Was this translation helpful? Give feedback.
-
|
Again all a nice to have, but if the end goal of frigate is to be an easy to use addon for home assistant (not just a super techy system) some of this info would be good to surface.. The current changes of the info on the System and Storage pages are already huge improvements to make it easier to troubleshoot from the UI vs digging through the docker files. Only highlighted it since I was trying to size up a separate system to run frigate on and questioned the number displayed and had to validate it manually via the filesystem. |
Beta Was this translation helpful? Give feedback.
-
|
I'm of course not arguing against the idea only saying it's a complicated problem to solve in an efficient way. |
Beta Was this translation helpful? Give feedback.
-
|
0.12 new camera event filter multi select has not quick single select option? There does not appear to be a way to quickly unselect all cameras / select one camera. (greater problem when you have a larger number of cameras) A lot of filter systems with a similar UI will select one camera if you click on the item label instead of the check mark.. Or the select all will act as a toggle and unselect all. |
Beta Was this translation helpful? Give feedback.
2 replies
-
|
You click the camera icon to the right of the label to quickly select just that one. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks, I swear I tried that.. Maybe I just didn't hit the right hit box when I was on mobile with my finger. |
Beta Was this translation helpful? Give feedback.
-
|
Question when do stills previews update in frigate? This may not be a specific to 0.12 question but it just seems like I have had a larger number of cases of the thumbnail always showing something very out of date or corrupt, but recordings / events or live view work fine and sometimes the thumbnail updates after viewing a camera? In particular I find it strange when I see a person in the still, I would think at least the image would update at the start AND end of a motion event? |
Beta Was this translation helpful? Give feedback.
8 replies
-
|
Shift + refresh should be killing any client side caching, same images appear on alternate browsers and clients like my phone.. is there anything I should check in regard to latest.jpg not updating? Going back through my logs I have quite a few warnings like this. 2023-01-30 13:42:25.168644826 [2023-01-30 13:42:25] frigate.object_processing WARNING : Unable to create jpg because frame 1675114942.305174 is not in the cache |
Beta Was this translation helpful? Give feedback.
-
A number of users have confirmed that this didn't help when viewing frigate via ingress inside HA. Frigate tells the browser not to cache Line 871 in 7a7e30e
That usually has to do with snapshot not latest.jpg. Something to look into but I am not sure if it would cause this or not. |
Beta Was this translation helpful? Give feedback.
-
|
To be clear I am accessing Frigate directly in chrome for windows and it is running as a separate docker. All of the clients and alternative browsers where also direct. I am intimately aware of how client server cache control works, I deal with proxy and caching solutions professionally. Hence why I ask as the source image does appear to not be updating. The cameras in question are using restream / pointing to go2rtc. One is the stuck person at the fridge, another was a camera persistently showing a slightly corrupt image. |
Beta Was this translation helpful? Give feedback.
-
|
Are the cameras working if you view the debug view? If you go to the system page do you see any cameras with really high FPS values? Seems like it could be totally unrelated to caching and instead related to #5280 |
Beta Was this translation helpful? Give feedback.
-
|
Not seeing crazy high fps on the system page but switching to debug view it is clearly running detect repeatedly on a still / stuck frame so that does appear to be the issue. Guess it is all the same bug..... wait till beta 6 jsmpeg liveview is also frozen but mse and webrtc are working so that is probably why I didn't notice as I just deployed the webrtc config for most of my cameras and switched the live views to use that. |
Beta Was this translation helpful? Give feedback.
-
|
does anyone know why recordings only have an FPS of 12.5 while the rtsp stream is more then 20? |
Beta Was this translation helpful? Give feedback.
3 replies
-
|
I'm not seeing that, mine are correct. Perhaps you're not using the correct input args but in any case I'd suggest making an issue. |
Beta Was this translation helpful? Give feedback.
-
|
My cameras provide 15 FPS and recordings also have correct 15 FPS. |
Beta Was this translation helpful? Give feedback.
-
|
sorry guys, bit of pebkac here... rebooted container and camera and now it's all well. |
Beta Was this translation helpful? Give feedback.
-
|
Awaiting beta 6 and newer go2rtc.. However I see 11hrs ago go2trc also released a 1.1.0 release with even more improvements for codec handling, hope that makes it in. |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
I am noticing that restarts seem to take longer and longer. Previously a restart would complete in < 5s, now it seems to be more like 40s. A relatively minor complaint but when you're adjusting config it's slightly frustrating, as well as meaning detection / recording is lost during that period. Is that expected behaviour or worth debugging? Potentially something to do with the leaked shared_memory objects referenced below? |
Beta Was this translation helpful? Give feedback.
9 replies
-
|
We're hoping to do it this evening or tomorrow morning. |
Beta Was this translation helpful? Give feedback.
-
You can always connect frigate directly to the camera and bypass go2rtc. Then go2rtc will only be used for live view and not as an intermediary for frigate's connection. |
Beta Was this translation helpful? Give feedback.
-
|
A little confused as to whether we're saying a 40 second restart time is expected or not. But one observation is that if I disable detection on all cameras in the UI, the restart is <5s again. I'm using go2rtc for WebRTC in Frigate, WebRTC in HomeAssistant and Frigate record/detct feeds. |
Beta Was this translation helpful? Give feedback.
-
Previously it would just stop but now frigate (as it was meant to all along) waits until the processes stop so the existing recording segments can be moved, events can be ended, etc. The bug in beta5 is that if it's stopped from the UI it'll never actually stop. That is fixed in beta6 |
Beta Was this translation helpful? Give feedback.
-
|
I don't know too. I'd say that the detection libraries aren't very good at finishing their processes. But nevertheless Frigate should give enough time for all processes to exit gracefully, which wasn't happening in earlier versions. |
Beta Was this translation helpful? Give feedback.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
and others
-
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 4
FRIGATE_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 restreaming
go2rtc has been bundled inside Frigate. The configuration can be set directly inside Frigate's config file nested under the
go2rtcsection.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-beta5
Images:
ghcr.io/blakeblackshear/frigate:0.12.0-beta5ghcr.io/blakeblackshear/frigate:0.12.0-beta5-tensorrtThis discussion was created from the release 0.12.0 Beta 5.
Beta Was this translation helpful? Give feedback.
All reactions