summaryrefslogtreecommitdiffstats
path: root/audio
diff options
context:
space:
mode:
authorwm4 <wm4@nowhere>2019-11-09 23:56:11 +0100
committerwm4 <wm4@nowhere>2019-11-09 23:56:44 +0100
commit35de8ea0a8a665321e814efe5e59b7dd6c237cd1 (patch)
tree016a77dc853db8177a089c94bc0d4d70d70e7f1c /audio
parent05f018b81aa3aec27dc61cbc7308b91cc858dfd8 (diff)
downloadmpv-35de8ea0a8a665321e814efe5e59b7dd6c237cd1.tar.bz2
mpv-35de8ea0a8a665321e814efe5e59b7dd6c237cd1.tar.xz
vo_gpu: yuv alpha is always full range
Probably. It's not like these pixel formats are formally specified - FFmpeg added them because _some_ file format or decoder supports it, and while that format/codec may define it precisely, the pixel format is sort of disconnected and just a FFmpeg thing. In any case, the yuva sample I had at hand uses the full range the component data type can provide. The old code used the same "shifted" range as for Y/U/V components, which must have been wrong. This will not work correctly for packed YUVA formats, but fortunately they matter even less.
Diffstat (limited to 'audio')
0 files changed, 0 insertions, 0 deletions