[HW Accel Support]: 0.11.0-rc2 HW accel not working #3858
Comments
|
Try running |
|
|
Please try VAAPI instead and see if that works (if not, post the logs): ffmpeg:
hwaccel_args:
- -hwaccel
- vaapi
- -hwaccel_device
- /dev/dri/renderD128
- -hwaccel_output_format
- yuv420p |
|
|
I think something may be wrong on the host side, do you have intel drivers included? Seems that it is able to load the driver included in frigate but the device is immediately failing when trying to decode anything. It's also possible that your iGPU is disabled because no display is plugged in, I've seen some cases where the iGPU is disabled and can't be used for accleration, so maybe try plugging into a monitor, restart, and see if that makes any difference |
|
Tried both a HDMI emulator and monitor didnt work. The graphics card seems to be working on the host |
|
Not sure then honestly, we've had plenty of other 12th gen users running without problems. I will have to look at past issues and see if I can find anything |
|
On my host either or will make use of hardware acceleration. Passing On the host, if I leave off those options to the command it uses about ~30%cpu, but with either of them processing the stream is <5%cpu. Checking with |
|
What version of ffmpeg is running on the host? |
|
Also, what linux distro are you running? |
|
Running Archlinux, ffmpeg is version 5.1.1 |
|
You could try using https://deploy-preview-2829--frigate-docs.netlify.app/configuration/advanced#custom-ffmpeg-build to use your host ffmpeg and see if it works better. Not sure we've had anyone else using ArchLinux with RPi in 0.11 |
|
There's something broken with btbn-ffmpeg. I installed jellyfin-ffmpeg from https://repo.jellyfin.org/releases/server/debian/versions/jellyfin-ffmpeg/5.1.1-1/ in the container and it works with hardware acceleration. No clue how to hack that into the container and get frigate to recognize it btbn-ffmpeg trace output when setting up hwaccel jellyfin-ffmpeg trace: Only thing that stands out is jellyfin-ffmpeg is using a good deal newer libva and intel-media-va-driver. I suspect there may be some kind of ABI compatibility issue |
|
We were using Jellyfin in previous pre-releases but we found a hard-incompatibility with rtsp-simple-server and some other cameras when audio was enabled, so we had to move to btbn. Should be able to patch the jellyfin build in using the instructions described in https://deploy-preview-2829--frigate-docs.netlify.app/configuration/advanced#custom-ffmpeg-build |
|
Also like I said we have other users who have used 12th gen hardware acceleration with this build no problem, so it must be something pretty specific |
|
The software in the container is too old to work with my host (Archlinux). The drivers/libraries are not recent enough to work with a host that has an up to date (most recently released) kernel/driver/library. If I pull in Currently I have to override the PATH and entrypoint in my docker-compose.yml to inject jellyfin-ffmpeg. The mentioned method of overriding ffmpeg in the documents is not usable. It only works if you have a copy of ffmpeg that is statically linked. So you cannot use it to inject something like jellyfin-ffmpeg or the host's ffmpeg. |
|
Hi, I have a similar issue with the NUC6CAYH + Coral USB, where I run my Home Assistant. The first install was the AddOn 3.1 (fFrigate version 10.1) and now I switched to the latest 11.0. How do I change the Addon to use another ffmpeg, if this is the issue? Thank you. |
|
@RaveGun That is not your issue, your issue is your driver. You need to use the |
|
@NickM-27 you are absolutely right. Anyway, I added the environment variable to the frigate.yml, like in the full configuration example, and it went back to the 20%. Thank you and sorry for hijacking this issue. |
This fixed my issue with Unraid 6.11 and Intel 12th Gen CPU not using the GPU. It now works fine! THANK YOU |
Big thanks to you kind sir. Maybe the documentation here (https://docs.frigate.video/configuration/hardware_acceleration) could mention how to set the environment variable. I was unaware of the option in the frigate.yml file and I have been pulling my hair for two days. Now back to 20% cpu and 15% ram from about 50% each. |
I, like many others, have been getting the -17 error when trying to use qsv hw acceleration on my 12th gen cpu running on Ubuntu. Performing the above |
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the problem you are having
The FFMPEG process is unable to start the QSV hardware acceleration. Works if hwaccel is disabled
Version
0.11.0-c461c9e
Frigate config file
docker-compose file or Docker CLI command
Relevant log output
FFprobe output from your camera
Operating system
Other Linux
Install method
Docker Compose
Network connection
Wired
Camera make and model
Dahua IPC-Color4KX
Any other information that may be helpful
12th Gen Intel(R) Core(TM) i5-12400
The text was updated successfully, but these errors were encountered: