0.12.0 Beta 1 #4859
Replies: 51 comments 231 replies
-
|
I read through everything but feel like I missed something...getting a nginx and go2rtc error on starting the container...I can open issue if needed |
Beta Was this translation helpful? Give feedback.
-
|
What does your docker compose look like? Seems like something is being overwritten |
Beta Was this translation helpful? Give feedback.
-
|
Didn't think about that. I am currently going through the config file to kind of reconcile with the new docs. But here is my current docker compose: |
Beta Was this translation helpful? Give feedback.
-
|
got the same problem
```json
{
"AppArmorProfile": "docker-default",
"Args": [
"python3",
"-u",
"-m",
"frigate"
],
"Config": {
"AttachStderr": false,
"AttachStdin": false,
"AttachStdout": false,
"Cmd": [
"python3",
"-u",
"-m",
"frigate"
],
"Domainname": "",
"Entrypoint": [
"/init"
],
"Env": [
"DEBIAN_FRONTEND=noninteractive",
"FLASK_ENV=development",
"FRIGATE_RTSP_PASSWORD=Flyer001",
"LIBVA_DRIVER_NAME=i965",
"NVIDIA_DRIVER_CAPABILITIES=compute,video,utility",
"LIBVA_DRIVER_NAME_JELLYFIN=i965",
"PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/lib/btbn-ffmpeg/bin",
"NVIDIA_VISIBLE_DEVICES=all",
"S6_BEHAVIOUR_IF_STAGE2_FAILS=2",
"S6_CMD_WAIT_FOR_SERVICES=1",
"S6_CMD_WAIT_FOR_SERVICES_MAXTIME=0",
"S6_SERVICES_GRACETIME=30000",
"S6_LOGGING_SCRIPT=T 1 n0 s10000000 T",
"S6_SERVICES_READYTIME=50"
],
"ExposedPorts": {
"1935/tcp": {},
"5000/tcp": {},
"8554/tcp": {},
"8555/tcp": {}
},
"Hostname": "835202f40a93",
"Image": "blakeblackshear/frigate:0.12.0-beta1",
"Labels": {
"maintainer": "blakeb@blakeshome.com"
},
"OnBuild": null,
"OpenStdin": false,
"StdinOnce": false,
"Tty": false,
"User": "",
"Volumes": {
"/config": {},
"/etc/localtime": {},
"/media/frigate": {}
},
"WorkingDir": "/opt/frigate"
},
"Created": "2023-01-02T20:35:52.430110033Z",
"Driver": "overlay2",
"ExecIDs": null,
"GraphDriver": {
"Data": {
"LowerDir": "/var/lib/docker/overlay2/54634e2e246098fb6b4e2616c6d9b88e6ff11596c903679a27a5d475024fd633-init/diff:/var/lib/docker/overlay2/83ad2fba893d0faf4e3c6c1e576e03eca35d0db821349dc1d8dc70b3f4b49d74/diff:/var/lib/docker/overlay2/49b7f8e5fb62eea219a818b2e77717f308b55b2776bed280dd6571e9d915bab7/diff:/var/lib/docker/overlay2/f2a9c75f8746aa4221d03124909472bbc26296478ed233f56abb5b0c30f98312/diff:/var/lib/docker/overlay2/7683d1cca14d1e60131876aa6a64b419ca38c2e901bb9127f4e3a48f8616e568/diff:/var/lib/docker/overlay2/62d8e10a9136c6f0057ee0ce9579c2df0834f56f908cf99b18dbdc115fb0818c/diff:/var/lib/docker/overlay2/c2f30f7b9f7843fab1e329e75201654c2f380fb6b84afd744880ded0ca171d00/diff:/var/lib/docker/overlay2/323137c5b4f63fa3ede5e99efbc9bcb4141bb346a3933c1988c6f49610fd1c0a/diff",
"MergedDir": "/var/lib/docker/overlay2/54634e2e246098fb6b4e2616c6d9b88e6ff11596c903679a27a5d475024fd633/merged",
"UpperDir": "/var/lib/docker/overlay2/54634e2e246098fb6b4e2616c6d9b88e6ff11596c903679a27a5d475024fd633/diff",
"WorkDir": "/var/lib/docker/overlay2/54634e2e246098fb6b4e2616c6d9b88e6ff11596c903679a27a5d475024fd633/work"
},
"Name": "overlay2"
},
"HostConfig": {
"AutoRemove": false,
"Binds": [
"/usr/share/hassio/homeassistant:/config",
"/etc/localtime:/etc/localtime:ro",
"/media/scooper1/frigate/frigate:/media/frigate"
],
"BlkioDeviceReadBps": null,
"BlkioDeviceReadIOps": null,
"BlkioDeviceWriteBps": null,
"BlkioDeviceWriteIOps": null,
"BlkioWeight": 0,
"BlkioWeightDevice": [],
"CapAdd": [
"AUDIT_WRITE",
"CHOWN",
"DAC_OVERRIDE",
"FOWNER",
"FSETID",
"KILL",
"MKNOD",
"NET_BIND_SERVICE",
"NET_RAW",
"SETFCAP",
"SETGID",
"SETPCAP",
"SETUID",
"SYS_CHROOT"
],
"CapDrop": [
"AUDIT_CONTROL",
"BLOCK_SUSPEND",
"DAC_READ_SEARCH",
"IPC_LOCK",
"IPC_OWNER",
"LEASE",
"LINUX_IMMUTABLE",
"MAC_ADMIN",
"MAC_OVERRIDE",
"NET_ADMIN",
"NET_BROADCAST",
"SYSLOG",
"SYS_ADMIN",
"SYS_BOOT",
"SYS_MODULE",
"SYS_NICE",
"SYS_PACCT",
"SYS_PTRACE",
"SYS_RAWIO",
"SYS_RESOURCE",
"SYS_TIME",
"SYS_TTY_CONFIG",
"WAKE_ALARM"
],
"Cgroup": "",
"CgroupParent": "",
"CgroupnsMode": "host",
"ConsoleSize": [
0,
0
],
"ContainerIDFile": "",
"CpuCount": 0,
"CpuPercent": 0,
"CpuPeriod": 0,
"CpuQuota": 0,
"CpuRealtimePeriod": 0,
"CpuRealtimeRuntime": 0,
"CpuShares": 0,
"CpusetCpus": "",
"CpusetMems": "",
"DeviceCgroupRules": null,
"DeviceRequests": null,
"Devices": [
{
"CgroupPermissions": "rwm",
"PathInContainer": "/dev/bus/usb",
"PathOnHost": "/dev/bus/usb"
},
{
"CgroupPermissions": "rwm",
"PathInContainer": "/dev/apex_0",
"PathOnHost": "/dev/apex_0"
},
{
"CgroupPermissions": "rwm",
"PathInContainer": "/dev/dri/renderD128",
"PathOnHost": "/dev/dri/renderD128"
}
],
"Dns": [],
"DnsOptions": [],
"DnsSearch": [],
"ExtraHosts": null,
"GroupAdd": null,
"IOMaximumBandwidth": 0,
"IOMaximumIOps": 0,
"IpcMode": "private",
"Isolation": "",
"KernelMemory": 0,
"KernelMemoryTCP": 0,
"Links": null,
"LogConfig": {
"Config": {},
"Type": "json-file"
},
"MaskedPaths": [
"/proc/asound",
"/proc/acpi",
"/proc/kcore",
"/proc/keys",
"/proc/latency_stats",
"/proc/timer_list",
"/proc/timer_stats",
"/proc/sched_debug",
"/proc/scsi",
"/sys/firmware"
],
"Memory": 0,
"MemoryReservation": 0,
"MemorySwap": 0,
"MemorySwappiness": null,
"Mounts": [
{
"Target": "/tmp/cache",
"TmpfsOptions": {
"SizeBytes": 1000000000
},
"Type": "tmpfs"
}
],
"NanoCpus": 0,
"NetworkMode": "bridge",
"OomKillDisable": false,
"OomScoreAdj": 0,
"PidMode": "",
"PidsLimit": null,
"PortBindings": {
"1935/tcp": [
{
"HostIp": "",
"HostPort": "1935"
}
],
"5000/tcp": [
{
"HostIp": "",
"HostPort": "5000"
}
]
},
"Privileged": false,
"PublishAllPorts": false,
"ReadonlyPaths": [
"/proc/bus",
"/proc/fs",
"/proc/irq",
"/proc/sys",
"/proc/sysrq-trigger"
],
"ReadonlyRootfs": false,
"RestartPolicy": {
"MaximumRetryCount": 0,
"Name": "unless-stopped"
},
"Runtime": "runc",
"SecurityOpt": null,
"ShmSize": 67108864,
"UTSMode": "",
"Ulimits": null,
"UsernsMode": "",
"VolumeDriver": "",
"VolumesFrom": null
},
"HostnamePath": "/var/lib/docker/containers/37c74824d27ea13e0ce3ab1da6f6d3b81edcf9962e5531f8b4657b8fc2f1ab85/hostname",
"HostsPath": "/var/lib/docker/containers/37c74824d27ea13e0ce3ab1da6f6d3b81edcf9962e5531f8b4657b8fc2f1ab85/hosts",
"Id": "37c74824d27ea13e0ce3ab1da6f6d3b81edcf9962e5531f8b4657b8fc2f1ab85",
"Image": "sha256:da6e753a2bfc16d6f01cf645bb249349518c9419703a3bc735480b2f6f0fbd64",
"LogPath": "/var/lib/docker/containers/37c74824d27ea13e0ce3ab1da6f6d3b81edcf9962e5531f8b4657b8fc2f1ab85/37c74824d27ea13e0ce3ab1da6f6d3b81edcf9962e5531f8b4657b8fc2f1ab85-json.log",
"MountLabel": "",
"Mounts": [
{
"Destination": "/tmp/cache",
"Mode": "",
"Propagation": "",
"RW": true,
"Source": "",
"Type": "tmpfs"
},
{
"Destination": "/config",
"Mode": "",
"Propagation": "rprivate",
"RW": true,
"Source": "/usr/share/hassio/homeassistant",
"Type": "bind"
},
{
"Destination": "/etc/localtime",
"Mode": "ro",
"Propagation": "rprivate",
"RW": false,
"Source": "/etc/localtime",
"Type": "bind"
},
{
"Destination": "/media/frigate",
"Mode": "",
"Propagation": "rprivate",
"RW": true,
"Source": "/media/scooper1/frigate/frigate",
"Type": "bind"
}
],
"Name": "/frigate",
"NetworkSettings": {
"Bridge": "",
"EndpointID": "",
"Gateway": "",
"GlobalIPv6Address": "",
"GlobalIPv6PrefixLen": 0,
"HairpinMode": false,
"IPAddress": "",
"IPPrefixLen": 0,
"IPv6Gateway": "",
"LinkLocalIPv6Address": "",
"LinkLocalIPv6PrefixLen": 0,
"MacAddress": "",
"Networks": {
"bridge": {
"Aliases": null,
"DriverOpts": null,
"EndpointID": "",
"Gateway": "",
"GlobalIPv6Address": "",
"GlobalIPv6PrefixLen": 0,
"IPAMConfig": {},
"IPAddress": "",
"IPPrefixLen": 0,
"IPv6Gateway": "",
"Links": null,
"MacAddress": "",
"NetworkID": "8b9af2a02f7903d0afeba3ceb4c3d9b59eec55817c6e2a7e857324eefb421669"
}
},
"Ports": {},
"SandboxID": "ce7f3838173e31705e33c62e735352b0f5da06a60948ad0389dba00ba9f4cbc3",
"SandboxKey": "/var/run/docker/netns/ce7f3838173e",
"SecondaryIPAddresses": null,
"SecondaryIPv6Addresses": null
},
"Path": "/init",
"Platform": "linux",
"Portainer": {
"ResourceControl": {
"Id": 85,
"ResourceId": "37c74824d27ea13e0ce3ab1da6f6d3b81edcf9962e5531f8b4657b8fc2f1ab85",
"SubResourceIds": [],
"Type": 1,
"UserAccesses": [
{
"UserId": 0,
"AccessLevel": 1
}
],
"TeamAccesses": [],
"Public": false,
"AdministratorsOnly": false,
"System": false
}
},
"ProcessLabel": "",
"ResolvConfPath": "/var/lib/docker/containers/37c74824d27ea13e0ce3ab1da6f6d3b81edcf9962e5531f8b4657b8fc2f1ab85/resolv.conf",
"RestartCount": 12,
"State": {
"Dead": false,
"Error": "",
"ExitCode": 143,
"FinishedAt": "2023-01-02T20:39:41.07059288Z",
"OOMKilled": false,
"Paused": false,
"Pid": 0,
"Restarting": true,
"Running": true,
"StartedAt": "2023-01-02T20:39:35.883861303Z",
"Status": "restarting"
}
}
```
|
Beta Was this translation helpful? Give feedback.
-
|
@esmoyer out of curiosity, can you try the ghcr image instead and see if it has the same? |
Beta Was this translation helpful? Give feedback.
-
|
Turned on debug logging and got a couple extra lines about readiness notification; not sure if that is helpful or not |
Beta Was this translation helpful? Give feedback.
-
|
Hopefully it's not wrong but I typically just edit the container and update the Image Name to the new release and redeploy. If I would have remembered to delete the PATH variable, it would have worked just fine. Is there a better way to go about it? |
Beta Was this translation helpful? Give feedback.
-
|
Delete the PATH from portainer and recreate the container, you have to do it with every new release - strange portainer "feature". Easy fix once you know the issue! Thanks Nick for adding it to the release notes as a reminder :). |
Beta Was this translation helpful? Give feedback.
-
|
How did you get the initial configuration into portainer? |
Beta Was this translation helpful? Give feedback.
-
|
When I first setup Frigate in Docker, I used the docker compose, but once the container was setup I make adjustments and config changes for the container from within Portainer. |
Beta Was this translation helpful? Give feedback.
-
|
Well, this seems weird to me. If you use docker compose you should not make changes to the containers somewhere else, you should make the changes in the docker compose file. But I have never used Portainer. |
Beta Was this translation helpful? Give feedback.
-
|
looks like path setting may need deleting again on my redeploy via portainer |
Beta Was this translation helpful? Give feedback.
-
|
Yep, good call @felipecrs...I forgot I have to delete the PATH variable and have it auto create again when re-deploying the container! Need to add that to my tech notes so I don't forget it! @NickM-27 thanks for the quick response..seems like things are working now! |
Beta Was this translation helpful? Give feedback.
-
|
This new release is awesome. It seems I will have to re-learn how to use Frigate with all these good stuff! |
Beta Was this translation helpful? Give feedback.
-
|
Agreed! Gonna use it as a good opportunity to refine and clean my config and all that up. |
Beta Was this translation helpful? Give feedback.
-
|
have another problem - address in use 5 lines from end of log |
Beta Was this translation helpful? Give feedback.
-
|
i have the same problem on two independent systems one ubentu and the other on debran two different networks |
Beta Was this translation helpful? Give feedback.
-
|
any hints? |
Beta Was this translation helpful? Give feedback.
-
|
It's getting an exit signal. Maybe make sure MQTT doesn't have /restart set and besides that not totally sure. |
Beta Was this translation helpful? Give feedback.
-
|
turned off the mqtt broker made no difference is there any extra logging I can do help diag |
Beta Was this translation helpful? Give feedback.
-
|
I have solved the crash issue I had when updating with portainer |
Beta Was this translation helpful? Give feedback.
-
|
docker image not found for me, strange |
Beta Was this translation helpful? Give feedback.
-
|
Where did you enter the image name? Seems like it was put in the wrong field, a screenshot of it might be helpful. |
Beta Was this translation helpful? Give feedback.
-
|
I think there was a typo in the post...should be blakeblackshear/frigate:0.12.0-beta1 vs. blakeblackshear/frigate:0.12-beta1 |
Beta Was this translation helpful? Give feedback.
-
Thanks so much @esmoyer , that fixed it. I just copy/pasted from the release notes. Thanks also @NickM-27 for your quick reply and all the work you have been doing. Maybe someone can update the notes ;) |
Beta Was this translation helpful? Give feedback.
-
|
Fixed for me as well. Thanks |
Beta Was this translation helpful? Give feedback.
-
|
Updated |
Beta Was this translation helpful? Give feedback.
-
|
Is the beta also available with the addon? |
Beta Was this translation helpful? Give feedback.
-
|
It will be but not yet |
Beta Was this translation helpful? Give feedback.
-
|
I have noticed how great of a job @NickM-27 does (hackernews, reddit, here, he seems to be everywhere helping whenever frigate is mentioned). Donated, appreciate all the frigate team does! |
Beta Was this translation helpful? Give feedback.
-
|
Two issues so far for me.
I’m going to continue to investigate but thought I would post here in case anyone else was having the same issues. |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
|
Thanks. Yes, for number 2 if I exec into the Frigate container and run intel_gpu_top it prints that same error. It works on the host and I’m running the container in privileged mode and passing through the VAAPI device so not sure why it thinks it doesn’t have permissions. I’ll continue to poke at it. |
Beta Was this translation helpful? Give feedback.
-
|
The intel_gpu_top is very sensitive, you'll find lots of issues on GitHub about it. Running rootless docker may be another reason it doesn't work |
Beta Was this translation helpful? Give feedback.
-
|
None of my RTMP cameras are working. Here is the errors I am getting in the logs: Here is the config for the camera: Camera is the Reolink RLC-410-5MP My other non Reolink non RTMP input cameras appear fine |
Beta Was this translation helpful? Give feedback.
-
|
That's odd, can you try using the hwaccel preset for nvidia too and see if that still happens. |
Beta Was this translation helpful? Give feedback.
-
I've swapped over to the preset for those cameras as well as all of my non Reolink cameras and looks like that did the trick, so far it is working. Thanks @NickM-27 |
Beta Was this translation helpful? Give feedback.
-
|
Looks like that's a bug then |
Beta Was this translation helpful? Give feedback.
-
|
Fixed in #4864 |
Beta Was this translation helpful? Give feedback.
-
|
Also for those using Unraid, make sure you pass through port 8554 if you want to do any restream |
Beta Was this translation helpful? Give feedback.
-
|
I'll add that port to the template. I'll test the beta ASAP to make the needed changes. |
Beta Was this translation helpful? Give feedback.
-
|
I adjusted my config and updated to the latest container, no issues so far. Thanks! |
Beta Was this translation helpful? Give feedback.
-
|
Does the experimental UI not work with this release? I couldn't view the live feed pages when it was enabled. |
Beta Was this translation helpful? Give feedback.
-
|
The experimental UI has not been updated to support the new live views if that's what you're asking |
Beta Was this translation helpful? Give feedback.
-
|
Ah okay gotcha, when I had experimental enabled nothing was showing up in any of the camera's live view pages |
Beta Was this translation helpful? Give feedback.
-
|
Oh, that's unexpected |
Beta Was this translation helpful? Give feedback.
-
|
I had the same issue, just turned off experimental view and works fine now |
Beta Was this translation helpful? Give feedback.
-
|
@NickM-27 did the filtering by time end up making it? I can't really understand the way the pull system works: |
Beta Was this translation helpful? Give feedback.
-
|
No that's still in draft |
Beta Was this translation helpful? Give feedback.
-
Thanks, I will wait |
Beta Was this translation helpful? Give feedback.
-
|
I'm having some issues using intel hardware acc: I'm passing the unit to the container: On config file I have this: |
Beta Was this translation helpful? Give feedback.
-
|
Is something weird, I tested the regular beta without any problem at from from yesterday to today. Then I have testing and preparing the nvidia version without any issue, and when I stop that container and started the regual one again with no modificacions from yesteday it started to have this issues. And it is constant, the container crashes even with only 1 camera configured. |
Beta Was this translation helpful? Give feedback.
-
NVIDIA GeForce GTX 1060 3GB |
Beta Was this translation helpful? Give feedback.
-
|
Can you give more logs then? |
Beta Was this translation helpful? Give feedback.
-
|
I restarted the host again and now is working fine again. I had similar issues on the past with same solution, reboot few times... |
Beta Was this translation helpful? Give feedback.
-
|
Interesting, 🤞 that's good then |
Beta Was this translation helpful? Give feedback.
-
|
I get following error when I try to use the restream url as record role |
Beta Was this translation helpful? Give feedback.
-
|
I saw this issue as well. For some reason, it does not like the |
Beta Was this translation helpful? Give feedback.
-
|
Here is the preset value: https://github.com/blakeblackshear/frigate/blob/dev/frigate/ffmpeg_presets.py#L218 |
Beta Was this translation helpful? Give feedback.
-
|
rw_timeout is for http streams only, if you try to use it with an rtsp stream then it will have problems. You need to set the input_args at the camera level cameras:
garage:
ffmpeg:
output_args:
record: preset-record-generic-audio
inputs:
- path: http://192.168.0.139/flv?port=1935&app=bcs&stream=channel0_ext.bcs&user=admin&password={FRIGATE_CAM_PASSWORD}
input_args: preset-http-reolink
roles:
- detect
- path: http://192.168.0.139/flv?port=1935&app=bcs&stream=channel0_main.bcs&user=admin&password={FRIGATE_CAM_PASSWORD}
roles:
- restream
#- record
- path: rtsp://192.168.0.10:8554/garage
input_args: preset-rtsp-generic
roles:
- record |
Beta Was this translation helpful? Give feedback.
-
|
@themoosman we highly recommend using the timeout arg in all cases |
Beta Was this translation helpful? Give feedback.
-
|
Ah, even better. Thanks, I'll test that out. |
Beta Was this translation helpful? Give feedback.
-
|
How much tmpfs cache are you guys using in the stats / storage section? Of my 1GB assigned I see only 6-12MB used, is that expected? I honestly thought it would have been closer to the 1GB mark! |
Beta Was this translation helpful? Give feedback.
-
|
|
Beta Was this translation helpful? Give feedback.
-
Depends how you have frigate installed and what the config is
No, as soon as each 10 second segment is done processing frigate will decide to keep it (move it to storage) or discard it. This way if you shut the container down or the device loses power, no data besides (at most) the last 10 second will be lost. |
Beta Was this translation helpful? Give feedback.
-
|
It's installed as a docker container using Portainer to manage it. The only other thing running is Home Assistant and that uses hardly any RAM. Thanks for explaining how it works. So I think that works out to around 6-10MB for every 10 seconds. I wonder why the recommendation is just a flat out 1GB volume of tmpfs/RAM in that case. Your cameras must be pushing some large bandwidth! Or is yours shared with other containers or something? |
Beta Was this translation helpful? Give feedback.
-
My cameras have bandwidth of ~ 2200 MB/hr, so the total for their mp4 files in /tmp/cache is only ~30MB. It is just because the way my container is setup
Because when you download a recording clip it is saved in /tmp/cache before downloading, if you had a small /tmp/cache then frigate would crash |
Beta Was this translation helpful? Give feedback.
-
|
Thanks very much Nick, ok that makes sense. I could only get hold of the 2GB Raspberry Pi so if I want to run any other containers I just need to be cautious of the RAM usage :). I have already solved my weekly crashing by increasing the disk swap file size from the really low default on Raspberry OS of approx only 100MB to a much better 2GB. |
Beta Was this translation helpful? Give feedback.
-
|
I've just had a bit of an odd one, I had a notification - a person on one of the cameras as usual, it wasn't an in progress event, but a completed event. I went to view it and it wouldn't load on any device. A few minutes later and the event has gone! I thought that wasn't possible unless it was an "in progress" event or was a duplicate event? I don't think I have seen this before. |
Beta Was this translation helpful? Give feedback.
-
|
I have seen this error a few times in the console, after I view the camera images in the debug or live view. Not sure where to begin looking for the issue... any ideas?
for what its worth.. I am running the 0.12.0-beta1-tensorrt version on a dell 7050 Intel i7-6700T |
Beta Was this translation helpful? Give feedback.
-
|
This usually is due to a camera stream disconnecting. Not a concern if it is only occasional |
Beta Was this translation helpful? Give feedback.
-
|
It is only occasional. Thanks!! |
Beta Was this translation helpful? Give feedback.
-
|
Hi Team, running AMD 3800x CPU, Google TPU & AMD 390X GPU. |
Beta Was this translation helpful? Give feedback.
-
|
I'd recommend reading a lot of the docs, but especially the recordings, hwaccel, ffmpeg preset, & restream docs. |
Beta Was this translation helpful? Give feedback.
-
|
Will i need to uninstall the current version before installing 0.12.0? working through the config will just be a thing that never ends. I worked hard on getting my Annke H265 camera's working well with 4k streaming. |
Beta Was this translation helpful? Give feedback.
-
|
Not necessarily, you could duplicate the folders and run both at the same time I think. Only issue is that only one will be able to use the coral, both can't access it at the same time. |
Beta Was this translation helpful? Give feedback.
-
|
I don't suppose AMD GPU can be used like NVIDIA GPU for Detection can they? |
Beta Was this translation helpful? Give feedback.
-
|
I don't think so https://deploy-preview-4055--frigate-docs.netlify.app/configuration/detectors |
Beta Was this translation helpful? Give feedback.
-
|
No, AMD GPUs don't have any AI accelerators built in except in their newest cards. |
Beta Was this translation helpful? Give feedback.
-
|
Not sure what I've done wrong with this, but no matter what I do I keep getting the following error. 2023-01-06 08:40:56.839103659 ************************************************************* ##############################config.yml database: logger: ffmpeg: input_args:- -analyzeduration- 1024- -probesize- 1024############ Cameras!!!############## ############Backroom Camera####### |
Beta Was this translation helpful? Give feedback.
-
|
Like it says you defined |
Beta Was this translation helpful? Give feedback.
-
|
Thats crazy, it didn't give me a problem in the previous version! |
Beta Was this translation helpful? Give feedback.
-
|
Yes because it was a silent bug. We have now added a check for it to make sure it doesn't happen. |
Beta Was this translation helpful? Give feedback.
-
|
Trying to migrate from beta 11 to beta 12. Can't start it due to this error: I'm on Unraid. PGUI 100, PGID 99. |
Beta Was this translation helpful? Give feedback.
-
Just a stupid suggestion because I was having the same exact problem for no reason.. copy this section exactly. |
Beta Was this translation helpful? Give feedback.
-
|
OK I have to check with the driver plugin maintainer as we have more user with similar gpus facing this same issue. |
Beta Was this translation helpful? Give feedback.
-
|
Can you confirm that the command Can you post screenshots from the templates with Advanced View enabled? |
Beta Was this translation helpful? Give feedback.
-
|
I had this issue using yolo7, fixed once i changed to yolo4. |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
Home Assistant custom webrtc card pointing to Go2rtc api works from PC browser but from mobile browser/app, causes above error. |
Beta Was this translation helpful? Give feedback.
-
|
I've not seen that error, you should make an issue with https://github.com/AlexxIT/go2rtc |
Beta Was this translation helpful? Give feedback.
-
|
ok. and also seem to cause the cpu usages to increase |
Beta Was this translation helpful? Give feedback.
-
|
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 bee seen here |
Beta Was this translation helpful? Give feedback.
-
|
the results should now be viewable after filling in the info, not sure if there is a way to view the results without entering it again though |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
|
It looks like that doc is outdated, clicking on the links just brings me to this https://support.google.com/surveys/answer/12626240 |
Beta Was this translation helpful? Give feedback.
-
|
Sorry - was on mobile and verifying everything wasn't easy. I've tested it now, here's how to do it:
|
Beta Was this translation helpful? Give feedback.
-
|
Thanks, added to the top post header |
Beta Was this translation helpful? Give feedback.
-
|
Would there be any disadvantages to running the cameras to go2rtc (in unraid) then running those feeds to Frigate? I am trying to get the lowest possible latency to a feed I have set up and currently use the restream from Frigate. I was wondering if this would reduce the latency if I get that feed before Frigate does.. |
Beta Was this translation helpful? Give feedback.
-
|
This setup is covered in the restream docs. Personally I run this way because I want to reduce connections to the camera which I think should make it work less hard. For me watching the restream in frigate with WebRTC compared to the original camera in VLC the streams are basically identical |
Beta Was this translation helpful? Give feedback.
-
|
Thanks @NickM-27, I currently run all the cameras into Frigate then restream using MPV/VLC from the Frigate restream (now RTSP). I was just wondering I guess if it made any difference running the cameras directly to go2rtc, then Frigate. But, maybe it won't |
Beta Was this translation helpful? Give feedback.
-
|
Doesn't restream reduce connections to the camera anyway? I've got my AD410 added as below and then I use the restream of that for recording, detection and also as the rtsp feed for my HA Frigate card. |
Beta Was this translation helpful? Give feedback.
-
|
@conorlap yes, it does. Frigate has go2rtc embedded and that's exactly what's used for restream. I can't think of a good reason to use go2rtc outside of frigate too since you can customize the go2rtc config running in frigate however you want. |
Beta Was this translation helpful? Give feedback.
-
|
@blakeblackshear Excellent, that's what I figured but was a little confused by the comments above! Frigate just gets better and better - thanks to you all for all your great work 😄 |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the help earlier. Like I had said I didn't even have a problem from the last version. Anyway, I changed some things around with my config and now I get this. Even when i leave out the model path the s6 still fails. ######Config.yml Change detectors:
cpu1:
type: cpu
num_threads: 3
model:
path: /custom_model.tflite <---no matter if I have it "" or in '' I get the same error.
cpu2:
type: cpu
num_threads: 3
mqtt:
enabled: True
host: 10.0.0.26
database:
path: /media/frigate/frigate.db
logger:
default: info
logs:
frigate.event: debug
#######Global Camera Settings#######
#live:
# height: 720
# quality: 1
detect:
width: 1920
height: 1080
fps: 15
record:
enabled: True
events:
pre_capture: 15
post_capture: 15
retain:
default: 5
mode: active_objects
objects:
dog: 2
cat: 2
#rtmp:
# enabled: False
restream:
enabled: True
#ffmpeg:
# hwaccel_args:
# -hwaccel vaapi
# -hwaccel_device /dev/dri/renderD128
# -hwaccel_output_format vaapi
#ffmpeg:
# input_args:
# - -analyzeduration
# - 1024
# - -probesize
# - 1024
############ Cameras!!!##############
######Driveway Camera!!##########
cameras:
driveway:
ffmpeg:
output_args:
record:
-f segment
-segment_time 45
-segment_format mp4
-reset_timestamps 1
-strftime 1
-codec:v h264_vaapi
-global_quality 25
-acodec aac
-max_interleave_delta 0
-fps_mode passthrough
hwaccel_args:
-hwaccel vaapi
-hwaccel_device /dev/dri/renderD128
-hwaccel_output_format yuv420p
inputs:
- path: rtsp://10.0.0.35:8554/driveway
roles:
- detect
- record
- path: rtsp://username password@10.0.0.2:2600/media/ch0/stream0
roles:
- restream
objects:
track:
- person
- cat
- dog
filters:
person:
min_area: 5000
max_area: 100000
min_score: 0.5
threshold: 0.75
mask:
- 523,1080,897,0,0,0,0,1080
cat:
min_area: 5000
max_area: 100000
min_score: 0.5
threshold: 0.8
mask:
- 523,1080,897,0,0,0,0,1080
dog:
min_area: 5000
max_area: 100000
min_score: 0.5
threshold: 0.8
mask:
- 523,1080,897,0,0,0,0,1080
############Backroom Camera#######
backroom:
ffmpeg:
output_args:
record:
-f segment
-segment_time 45
-segment_format mp4
-reset_timestamps 1
-strftime 1
-codec:v h264_vaapi
-global_quality 25
-acodec aac
-fps_mode passthrough
hwaccel_args:
-hwaccel vaapi
-hwaccel_device /dev/dri/renderD128
-hwaccel_output_format vaapi
inputs:
- path: rtsp://10.0.0.36:8554/backroom
roles:
- detect
- record
- path: rtsp://username password@10.0.0.36:88/videoMain
roles:
- restream
objects:
track:
- person
- cat
- dog
filters:
person:
min_area: 5000
max_area: 100000
min_score: 0.5
threshold: 0.75
mask:
- 1920,330,1920,0,0,0,0,343
cat:
min_area: 5000
max_area: 100000
min_score: 0.5
threshold: 0.8
mask:
- 1920,330,1920,0,0,0,0,343
dog:
min_area: 5000
max_area: 100000
min_score: 0.5
threshold: 0.8
mask:
- 1920,330,1920,0,0,0,0,343 |
Beta Was this translation helpful? Give feedback.
-
|
You don't have a config error. Your error message is |
Beta Was this translation helpful? Give feedback.
-
|
you shouldn't need to set |
Beta Was this translation helpful? Give feedback.
-
|
I am running it succesfully on a Synology with the Also just tested Anyone knows how to solve this |
Beta Was this translation helpful? Give feedback.
-
|
That vainfo output is not an error, it is working as expected. |
Beta Was this translation helpful? Give feedback.
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/
BREAKING CHANGES
liveconfiguration has been moved torestream -> jsmpeg./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)Retention limited by available storage
Frigate now limits its recordings to available storage, if the storage for recordings gets below 1 hour left then Frigate will delete the oldest recording segments to make room for newer ones. Frigate will also not fail if there is no space to save recordings.
RTSP restreaming
Due to many issues with RTMP based restream, RTMP is now deprecated in favor of a new RTSP restream. This also comes with a new
restreamrole which is enabled by default. The restream of a camera can be accessed atrtsp://frigate_ip:8554/config_camera_name. The restream can also be used inside Frigate to reduce connections to the camera, see the restream docs for more info.Birdseye restreaming is also now supported at
rtsp://frigate_ip:8554/birdseyeNOTE: Port
8554will need to be mapped in the docker run or docker compose file for the restream to be accessed outside the container.New live stream options
The new RTSP restream also enables new
MSEandWebRTClive view options in the frontend which enable low-latency full-framerate live views that support audio.NOTES:
The live view options are set in the Frigate WebUI for each camera individually.
New detector types
Frigate now supports new detector types along with the Google Coral TPU.
OpenVINO
The OpenVINO detector type runs an OpenVINO IR model on Intel CPU, GPU and VPU hardware. OpenVINO is supported on 6th Gen Intel platforms (Skylake) and newer. A supported Intel platform is required to use the GPU device with OpenVINO. The MYRIAD device may be run on any platform, including Arm devices. For detailed system requirements, see OpenVINO System Requirements
TensorRT
NVidia GPUs may be used for object detection using the TensorRT libraries. Due to the size of the additional libraries, this detector is only provided in images with the -tensorrt tag suffix. The TensortRT detector is able to run on x86 hosts that have an Nvidia GPU which supports the 11.x series of CUDA libraries. The minimum driver version on the host system must be >=450.80.02. Also the GPU must support a Compute Capability of 5.0 or greater. This generally correlates to a Maxwell-era GPU or newer, check the TensorRT docs for more info.
NOTE: The link in the docs is for the final release location, for the beta the script is located at https://raw.githubusercontent.com/blakeblackshear/frigate/dev/docker/tensorrt_models.sh
New system page
The
Debugpage has been renamed toSystem. It now includes much more information and links to easily getvainfoandffprobedata.The GPUs section will show each GPU based on the hwaccel args, depending on the type of GPU different information is supported. For example Nvidia GPUs will have the name while others will be generic, also intel does not support memory usage. There is also a
VAINFObutton which will make it easier to diagnose hwaccel issues and verify that the hwaccel driver is being used correctly.Each camera will have their own process CPU & memory usage so it will be easier to see which process is using those resources. There is also an
FFPROBEbutton which will be helpful to understand what each stream is presenting and make it easier to include that in support issues.The debug config has also been removed, the config can be copied using the config page in the WebUI.
New storage page
Frigate WebUI now has a built in storage page which shows the general usage for both storage and memory. It also shows a per-camera storage usage and stream bandwidth. This should make it a lot easier to have a general idea how much storage is being used by each camera.
New logs page
Frigate WebUI now has built in logs, this will make copying and viewing logs much easier. Currently the logs are static meaning the page must be refreshed to view new logs.
New config editor
Frigate WebUI now has a built in config editor with syntax highlighting and schema validation. This means that the config will be validated before it can be saved which will make yaml config much easier to manage.
NOTE: The previous docker-compose or docker CLI may have had the /config.yml set to
:roor read-only. That will need to be removed for the config editor to be able to save the new file.MQTT is now optional
Frigate no longer requires MQTT to function, MQTT is also setup asynchronously so errors will be more clear and frigate won't stop when mqtt is enabled but not setup correctly.
NOTE: MQTT is still required for the Frigate-HomeAssistant Integration
No changes are needed for existing users.
FFMpeg presets
FFMPEG presets for common configurations are now added, making the config cleaner and allowing the underlying args to be changed between releases without being a breaking change. It is highly recommended to update the configuration to use these presets.
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-beta1
Images:
blakeblackshear/frigate:0.12.0-beta1ghcr.io/blakeblackshear/frigate:0.12.0-beta1blakeblackshear/frigate:0.12-beta1-tensorrtghcr.io/blakeblackshear/frigate:0.12.0-beta1-tensorrtThis discussion was created from the release 0.12.0 Beta 1.
Beta Was this translation helpful? Give feedback.
All reactions