mpv icon indicating copy to clipboard operation
mpv copied to clipboard

vo_gpu-next: vapoursynth filter seems could not receive dolbyvision's metadata

Open hooke007 opened this issue 3 years ago • 1 comments

Important Information

Provide following Information:

  • mpv version https://github.com/shinchiro/mpv-winbuild-cmake/releases/tag/20220723
  • Windows Version win11 release
  • Source of the mpv binary https://github.com/shinchiro/mpv-winbuild-cmake/releases/tag/20220723
  • If known which version of mpv introduced the problem N/A
  • Possible screenshot or video of visual glitches

Reproduction steps

# mpv.conf
vo=gpu-next
  1. run mpv.exe and play a dv file, and then activate any vapoursynth filter.

  2. vf toggle vapoursynth="~~/test0.vpy"

# test0.vpy
video_in.set_output()

Expected behavior

correct color

Actual behavior

mpv-shot0001

Log file

mpv-test.log

hooke007 avatar Jul 23 '22 14:07 hooke007

The side data doesn't propagate through the vapoursynth vf. Not sure if it would be easily doable, but from my perspective it isn't.

quietvoid avatar Jul 26 '22 23:07 quietvoid

Not 100% sure about the patch cause there's strange color blinking sometimes (not always, just in some scenes) when the filter increases frame rate. Maybe I'm missing something important here o_O

chainikdn avatar Nov 17 '22 14:11 chainikdn

https://github.com/mpv-player/mpv/issues/10390#issuecomment-1179725841

when the filter increases frame rate

Probably there is the loss of luminace info in the extra frames created by vs.

hooke007 avatar Nov 17 '22 14:11 hooke007

it doesn't happen on every inserted frame more like some frames occasionally lose this DoVi data

chainikdn avatar Nov 17 '22 15:11 chainikdn

same for me

Durden-T avatar Sep 14 '23 15:09 Durden-T