[HW Accel Support]: Unable to Enable Hardware Acceleration for Video Recording on Intel Celeron J4025 (Frigate on Synology DS220+) #17458
Unanswered
tklkalok
asked this question in
Hardware Acceleration Support
Replies: 1 comment 8 replies
-
You're looking at different things. The warning refers to object detection not hwaccel |
Beta Was this translation helpful? Give feedback.
8 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Describe the problem you are having
Hi,
I am encountering an issue where I am unable to enable hardware acceleration for my cameras in Frigate, despite following the documentation. My setup is as follows:
• Hardware: Synology DS220+ with Intel Celeron J4025 CPU
• Frigate Version: 0.15-1
• Container Management: Synology Container Manager (Docker)
My Goal:
I simply want to have four cameras recording 24/7 without any object detection, filters, or masks—just continuous recording. However, when I set up only one camera, the FFMPEG CPU usage for that camera reaches 100%, which significantly impacts system performance.
Problem:
• When trying to enable hardware acceleration for Intel core (VAAPI), the following warning appears in the logs:
Despite configuring hardware acceleration using VAAPI, I am still unable to lower the CPU usage or enable the hardware acceleration successfully.
Steps Already Taken:
• Tried enabling VAAPI hardware acceleration via both LIBVA_DRIVER_NAME: iHD and FRIGATE_FFMPEG_HWACCEL_ARGS: preset-vaapi.
• Checked the device /dev/dri mappings and ensured they’re correctly passed into the container.
• Reduced the resolution and FPS of the camera (2560x1440, 10 fps), but CPU usage remains high.
I’ve tried troubleshooting using online answers and guides, but I still cannot get the hardware acceleration to work. Could anyone assist with how to properly enable hardware acceleration or help reduce CPU usage while recording? Any help would be appreciated.
Thanks in advance!
Version
0.15.0-cea210d
Frigate config file
docker-compose file or Docker CLI command
Relevant Frigate log output
Relevant go2rtc log output
FFprobe output from your camera
Install method
Docker Compose
Object Detector
CPU (no coral)
Network connection
Wireless
Camera make and model
Tapo C120
Screenshots of the Frigate UI's System metrics pages
Any other information that may be helpful
Sidenote: If I only want to do 247 recording, not detection is needed, can I just disable the detector config?
I also can see from the log that the detector process is with CPU, and there is a warning about it, how can I get rid of it?
Thank you!!
Beta Was this translation helpful? Give feedback.
All reactions