[HW Accel Support]: How to ensure VAAPI is actually used for hardware acceleration (AMD APU + LXC + Docker) #19396
Replies: 4 comments 3 replies
-
| 
         For AMD/ATI GPU hardware acceleration with VAAPI, you need to ensure the correct driver configuration. Based on your setup, there are several issues to address: Configuration IssuesYour current configuration uses manual VAAPI arguments, but for AMD GPUs, you should use the  You need to change the driver to  Recommended ConfigurationReplace your current manual hwaccel_args with the preset: ffmpeg:
  hwaccel_args: preset-vaapiVerification MethodsTo verify hardware acceleration is working, the documentation provides specific testing commands. For VAAPI, you can test inside the container with: Hardware DetectionThe hwaccel presets not only replace longer arguments but also give Frigate hints about available hardware, allowing Frigate to make other optimizations using the GPU such as when encoding the birdseye restream or scaling streams (3). TroubleshootingBased on a similar case with AMD GPU in Docker, ensure you have the correct devices mapped and that  The high CPU usage you're experiencing suggests hardware acceleration may not be active. Switch to  📚 Sources: 
 Have another question? Just tag @inkeep.  | 
  
Beta Was this translation helpful? Give feedback.
-
| 
         Tests performed: 
 /usr/lib/ffmpeg/7.0/bin/ffmpeg -loglevel verbose  Confirms radeonsi_drv_video.so is loaded correctly. pix_fmt: vaapi is being set. 
 Video Decode stays near 0% even with active RTSP streams. Overall GPU Load is very low. 
 cat /sys/kernel/debug/dri/0/amdgpu_pm_info Output: GPU Load: 1 % Indicates that VCN is powered up but apparently not handling video decoding. Even though VAAPI seems configured, the CPU cores assigned to Frigate remain in constant boost, with CPU temperature fixed between 80 °C and 90 °C. LIBVA_DRIVER_NAME=radeonsi is already set. ffmpeg preset changed to preset-vaapi as recommended in the docs. {"return_code":0,"stderr":"","stdout":"vainfo: VA-API version: 1.22 (libva 2.10.0)  | 
  
Beta Was this translation helpful? Give feedback.
-
| 
         Following as I am having a similar problem, not on proxmox running bare metal but same issue in my docker compose that my CPU is being hit hard and GPU is not really much at all but have a similar configs and all match the provided documentation  | 
  
Beta Was this translation helpful? Give feedback.
-
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
Hi everyone 👋
I'm running Frigate inside a Docker container, hosted in a Proxmox LXC, on a system using an AMD Ryzen 7 5800U APU. I've passed through the GPU using the following devices to the LXC:
/dev/dri/card0 /dev/dri/renderD128
Inside the container:
vainfoworks and reports supported VAAPI profiles for H.264, HEVC, VP9, etc./dev/driis visible inside the Docker container.docker-compose file or Docker CLI command
Relevant Frigate log output
Relevant go2rtc log output
FFprobe output from your camera
Install method
Proxmox via Docker
Object Detector
Coral
Network connection
Wired
Camera make and model
Reolink and Ctronics
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