check-va-api should only attempt modes that are in the profile list
The following discussion from !587 (merged) should be addressed:
-
@xexaxo started a discussion: Looking at the current test - it fetches the profiles only to ignore them. Where the h264 decode should be used only if
VAProfileH264Main
is supported, same for mpeg2 and post-processing. Would also need to fetch (see vaQueryConfigEntrypoints) and check match the entrypoint - we're usingVAEntrypointVLD
for decode andVAEntrypointVideoProc
for post-processing.Wouldn't hurt to explicitly try the tests, even if the first one is successful - an error if they all fail is fine. If none are supported, perhaps we should also throw an error. Distros have can have Mesa drivers built without h264 or vc1 and h265 (licensing is fun), but at least one should be there.