there are many cases that suffer psnr decline with gst-vaapi encode vp8/vp9
It have been verified that the issue of VP8e is caused by gst-plugin-base(660b5e4a9864).
for example,
case1
cmd-line:
gst-launch-1.0 -vf filesrc location=input num-buffers=10 ! rawvideoparse format=i420 width=352 height=288 ! videoconvert dither=0 ! video/x-raw,format=NV12 ! vaapivp8enc rate-control=cqp keyframe-period=30 yac-qi=14 quality-level=4 tune=none sharpness-level=0 loop-filter-level=0 ! video/x-vp8 ! matroskamux ! filesink location=output
result:
DETAIL:drv.iHD.psnr:expect=[39.0419,41.4528,41.0753,39.1498,41.8009,41.4039]
DETAIL:drv.iHD.psnr:expect=[39.0419,39.6182,38.3811,39.1498,39.7459,38.533]
case2
cmd-line:
gst-launch-1.0 -vf filesrc location=input num-buffers=75 ! rawvideoparse format=i420 width=3840 height=2160 framerate=30 ! videoconvert dither=0 ! video/x-raw,format=NV12 ! vaapivp9enc rate-control=cbr keyframe-period=30 bitrate=20000 ref-pic-mode=0 tune=low-power sharpness-level=4 loop-filter-level=16 ! video/x-vp9 ! matroskamux ! filesink location=output
result:
DETAIL:drv.iHD.psnr:expect=[38.2037,47.3138,48.0854,43.8056,51.0044,51.76]
DETAIL:drv.iHD.psnr:expect=[38.2037,47.2478,47.8169,43.8056,50.7294,51.2088]