clsid2

Then problem is on driver side. It is possible that they only activate it in x64 processes.

You are scaling to an unusual size. See what happens in fullscreen. I would not be surprised if it only works for certain target resolutions.

Any comparison images? How much extra power does it use?

I don't see much difference. You might need to use PrtScr instead of screenshot function from player, because player image is often before processing.

You have Windows HDR turned on. You should try with that disabled.

Maybe add `SUPERRES_Error` for the case where it attempted to enable superres, but failed? Then in debug overlay you can show a different string. Like "Intel-VPE:err" vs "Intel-VPE:req". @fuchaohan You...

https://patchwork.ffmpeg.org/project/ffmpeg/list/?series=12227

You can click on the commits to see comments from reviewers: https://patchwork.ffmpeg.org/project/ffmpeg/patch/[email protected]/

@Aleksoid1978 Maybe try to re-init one time automatically after a device is lost?

@MistarMuffin Do you have "Default Sound Driver" selected? Test if same problem happens with explicitly selected device. Possibly it is switching device when the HDMI output is temporarily unavailable due...