Using VDPAU with x264 causes visual artefacts when seeking.

Basically what the topic says. Since some time (I can’t pinpoint this exactly since when, but this happened at least on the newest Linux driver and the one before that) I’ve observed that when I seek a VDPAU-accelerated video I get artefacts as if the codec couldn’t find the reference frame and uses the current state of the screen as-is:

This happens for any x264 video that VDPAU can accelerate, for example Hi10P videos are unaffected (since VDPAU cannot accelerate them).

I’ve tried to follow the VDPAU debugging hints and ran mpv with debug envvars:

VDPAU_TRACE=2 VDPAU_NVIDIA_DEBUG=3 VDPAU_TRACE_FILE=mpv-vdpau.log mpv --vo=vdpau --hwdec=vdpau

but this made the error disappear (so it probably is some sort of a synchronisation issue).

Any idea how to fix that (other than runnig VDPAU in debug mode that is)?
nvidia-bug-report.log.gz (111 KB)

Same issue here with Kodi 16 and latest nvidia driver 361.28, as soon as you seek any x264 movie in VDPAU mode, you get artefacts. I had to revert back to 352.79 to fix the problem.

I have artifacts also. I am using 367.35 with vdpau and mpv player :

Hello bug from 3 months ago that Nvidia seems to pretend doesn’t exist and doesn’t give me any feedback for…