[HW Accel Support]: Nuc13, i7-1360P, Proxmox HAOSVM, hwaccel appears to work, but has no effect #16087
Replies: 3 comments 3 replies
-
|
Decoding video does not use much of the GPU. I see similar numbers on my system, and your ffmpeg CPU usage seems reasonable. What makes you think it's not working? |
Beta Was this translation helpful? Give feedback.
-
|
GPU usage never moves from .5%, and I mean NEVER. That seems to be a bit strange to me. Also, if I turn off HW accel in the frigate config, it makes no appreciable difference in CPU usage, which I also found odd. That said, I have found nothing in the logs indicating a problem, once I got it working, so it may very well be doing what it should. It just seems in my case that it might be "not much". I just wanted to check, make sure there was nothing glaring in my config or anything that stood out to someone else. |
Beta Was this translation helpful? Give feedback.
-
This seems like a driver issue, no? Perhaps HAOS does not contain a suitable driver for the GPU in i7-1360p at this time? |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Describe the problem you are having
I'm running the frigate add-on in HAOS, in a proxmox VM. I've fought with hwaccel for a while, eventually getting it "working". However, it appears to have no effect on total CPU usage and GPU usage never leaves .5% according to frigate. Passthrough via proxmox seems to be working fine, as the HAOSVM shows renderD128 as available. I tried numerous config options for hwaccel, all resulting in frigate crashing and reloading, with the exception of the current config. I don't see any ffmpeg related errors in the logs so I'm not sure how to verify or further troubleshoot.
Version
0.14.1-f4f3cfa
Frigate config file
docker-compose file or Docker CLI command
HA add-onRelevant Frigate log output
Relevant go2rtc log output
2025-01-22 17:31:23.924884011 [INFO] Preparing new go2rtc config... 2025-01-22 17:31:23.956977238 [INFO] Got IP address from supervisor: 192.168.19.81 2025-01-22 17:31:23.992482339 [INFO] Got WebRTC port from supervisor: 8555 2025-01-22 17:31:24.322047571 [INFO] Not injecting WebRTC candidates into go2rtc config as it has been set manually 2025-01-22 17:31:24.368531639 [INFO] Starting go2rtc... 2025-01-22 17:31:24.523491571 11:31:24.523 INF go2rtc platform=linux/amd64 revision=b2399f3 version=1.9.2 2025-01-22 17:31:24.523496591 11:31:24.523 INF config path=/dev/shm/go2rtc.yaml 2025-01-22 17:31:24.524199004 11:31:24.524 INF [rtsp] listen addr=:8554 2025-01-22 17:31:24.524203314 11:31:24.524 INF [api] listen addr=:1984 2025-01-22 17:31:24.524552000 11:31:24.524 INF [webrtc] listen addr=:8555 2025-01-22 17:31:33.922765453 [INFO] Starting go2rtc healthcheck service...FFprobe output from your camera
Install method
HassOS Addon
Object Detector
Coral
Network connection
Wired
Camera make and model
Unifi Protect
Screenshots of the Frigate UI's System metrics pages
Any other information that may be helpful
No response
Beta Was this translation helpful? Give feedback.
All reactions