hholst80
commented
6 days ago ffmpeg gives perhaps more details:
root@xps ~/Downloads
# ffmpeg -hwaccel vaapi -hwaccel_device /dev/dri/renderD128 -i castle.mp4 -f null -
ffmpeg version 7.1 Copyright (c) 2000-2024 the FFmpeg developers
built with gcc 13.2.0 (GCC)
configuration: --prefix=/usr --cpu=skylake --enable-gpl --enable-vaapi --enable-libx264
libavutil 59. 39.100 / 59. 39.100
libavcodec 61. 19.100 / 61. 19.100
libavformat 61. 7.100 / 61. 7.100
libavdevice 61. 3.100 / 61. 3.100
libavfilter 10. 4.100 / 10. 4.100
libswscale 8. 3.100 / 8. 3.100
libswresample 5. 3.100 / 5. 3.100
libpostproc 58. 3.100 / 58. 3.100
Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'castle.mp4':
Metadata:
major_brand : mp42
minor_version : 0
compatible_brands: mp42isomavc1
creation_time : 2014-11-27T15:35:09.000000Z
encoder : HandBrake 0.9.9 2013052900
Duration: 00:00:54.57, start: 0.000000, bitrate: 1110 kb/s
Stream #0:0[0x1](und): Video: h264 (Main) (avc1 / 0x31637661), yuv420p(tv, smpte170m/smpte170m/bt709, progressive), 960x540 [SAR 1:1 DAR 16:9], 945 kb/s, 30 fps, 30 tbr, 90k tbn (default)
Metadata:
creation_time : 2014-11-27T15:35:09.000000Z
vendor_id : [0][0][0][0]
encoder : JVT/AVC Coding
Stream #0:1[0x2](eng): Audio: aac (LC) (mp4a / 0x6134706D), 48000 Hz, stereo, fltp, 159 kb/s (default)
Metadata:
creation_time : 2014-11-27T15:35:09.000000Z
vendor_id : [0][0][0][0]
[AVHWDeviceContext @ 0x557d44fc1c00] No VA display found for device /dev/dri/renderD128.
Device creation failed: -22.
[vist#0:0/h264 @ 0x557d44f27480] [dec:h264 @ 0x557d44f73d40] No device available for decoder: device type vaapi needed for codec h264.
[vist#0:0/h264 @ 0x557d44f27480] [dec:h264 @ 0x557d44f73d40] Hardware device setup failed for decoder: Invalid argument
Error opening output file -.
Error opening output files: Invalid argument
root@xps ~/Downloads [234]
#
I tried to run wl-screenrec v0.1.6 on my Intel GPU (dell xps 16 laptop).
I am not sure where it is looking for the vaapi h264 driver though, and wf-recorder seems to be equally unhappy with my vaapi_h264 driver.
I suspect this might be an issue with ffmpeg build (very minimal) but the term 'driver' makes me unsure.