El mié, 24 jul 2024 a la(s) 4:41 p.m., Rafael Sadowski (raf...@sizeofvoid.org) escribió: > > On Sat Jul 20, 2024 at 11:32:29AM GMT, Rafael Sadowski wrote: > > OK to enable VA-API? It only depends on xenocara libva. Since libva > > builds on almost all arches, I see no reason to restrict it by CPU > > architectures any further. > > > Here is some research from me: > > # Case 1, segmentation fault in intel-media-driver: > > # Files from https://www.elecard.com/videos > $ ffmpeg -hwaccel vaapi -vaapi_device /dev/dri/renderD128 \ > -i AVC-H.264-TheaterSquare_3840x2160.mp4 -vf 'format=nv12,hwupload' -c:v \ > h264_vaapi -f mpegts - | ffplay - >
My case: ffmpeg -hwaccel vaapi -vaapi_device /dev/dri/renderD128 \ -i TheaterSquare_3840x2160.mp4 -vf 'format=nv12,hwupload' \ -c:v h264_vaapi -f mpegts - | ffplay - All ok, encode and decode work fine. Log here: https://pastebin.com/TUNED8gW > > # Case 2 No usable encoding entrypoint found for profile VAProfileVP9Profile0 > > # Files from https://www.elecard.com/videos > $ ffmpeg -hwaccel vaapi -vaapi_device /dev/dri/renderD128 \ > -i VP9_UshaikaRiverEmb_3840x2160.webm -vf 'format=nv12,hwupload' \ > -c:v vp9_vaapi -f mpegts - |ffplay - > ... Second case, not work for me, my card don´t have support for VP9 hwaccel. "Dios en su Cielo, todo bien en la Tierra" ***********************************************
