search

AlexxIT / go2rtc

Ultimate camera streaming application with support RTSP, RTMP, HTTP-FLV, WebRTC, MSE, HLS, MP4, MJPEG, HomeKit, FFmpeg, etc.
https://github.com/AlexxIT/Blog
MIT License
4.89k stars 395 forks source link

Question : how to use hardware decode/endcore for intel Raptor Lake-U in FFmpeg #1405

Open vigeland opened 3 days ago

vigeland commented 3 days ago

I did not found the parameter for ffmeg ?

vainfo returns:

error: can't connect to X server! libva info: VA-API version 1.17.0 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so libva info: Found init function __vaDriverInit_1_17 libva error: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed libva info: va_openDriver() returns 1 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so libva info: Found init function __vaDriverInit_1_8 libva error: /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init failed libva info: va_openDriver() returns -1 vaInitialize failed with error code -1 (unknown libva error),exit

Thanks for support.

NickM-27 commented 3 days ago

Looks like you don't have the driver installed on the host or don't have the device mapped in docker

vigeland commented 2 days ago

Both so files are installed on base system, render128 exits. The container is copied from a system with a Intel HD Graphics 4000. Hardware decoding works.

So, I think the driver is installed, or which driver did you mean. Using debian 11. But came the driver (so) file not with the docker ?

vigeland commented 22 hours ago

I use frigate, it's based on Debian 11 with bookworm Intel_media_driver [intel-media-driver 22.3.1+dfsg1-1] The chipset need a newer driver. The U120 has the Vendor ID 0xA7AC the 22.3.1 does not contain intel chip.