> sudo vainfo > sudo ffmpeg -hwaccel vaapi -hwaccel_output_format vaapi -i input.mp4 -c:v > h264_vaapi output.mp4
It's weird to be running these commands as root; I would actually expect that could make them fail (as they need to talk to the user's display server, and sudo will strip a bunch of necessary environment). Is there a particular reason these are being run as root? I wouldn't expect *users* to run these as root. The test plan does not make it entirely obvious what “pass” means; I think from context that “pass” means that log lines like > vaInitialize failed with error code -1 (unknown libva error),exit are not emitted, but it would be good to make it more clear. Since we're enabling code-paths that are currently unused - as mentioned in “what could go wrong” - I think the test plan should include some functional testing of a few high-impact scenarios. Something like “playing a video in the default video player still works” and “Google Meet in Firefox still works”. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to intel-media-driver in Ubuntu. https://bugs.launchpad.net/bugs/2116923 Title: [SRU] video hardware acceleration codec fails for Intel Arrow lake To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-media-driver/+bug/2116923/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
