[FFmpeg-trac] #7978(undetermined:reopened): inaccurate conversion from YCbCr Narrow range to RGB Full range

FFmpeg trac at avcodec.org
Fri Sep 10 09:36:14 EEST 2021


#7978: inaccurate conversion from YCbCr Narrow range to RGB Full range
-------------------------------------+-------------------------------------
             Reporter:  cepesh       |                    Owner:  (none)
                 Type:  defect       |                   Status:  reopened
             Priority:  normal       |                Component:
                                     |  undetermined
              Version:  unspecified  |               Resolution:
             Keywords:               |               Blocked By:
             Blocking:               |  Reproduced by developer:  0
Analyzed by developer:  0            |
-------------------------------------+-------------------------------------
Comment (by Balling):

 So, yes. I was able to confirm the bug:

 ffmpeg.exe -video_size 3840x2160 -vcodec v210 -i YUV_pattern-2fr.v210
  -vf scale=in_color_matrix=bt2020:in_range=tv,format=gbrp10le -f rawvideo
 rawle.rgb

 (Do not use gbrp10be, since YUVview does not support BE.)

 Open in YUVview, first select it being GBR ('''not''' RGB, select it is
 planar, select it is 10 bit) then select it is 3840x2160, it '''will'''
 crash at least once. They if you will activate hex viewer in settings and
 zoom in you will get the hex values. Indeed white is 1020 10 bit, just
 like in 16 bit png (65283 / 64 =1020). Now, as described in ITU docs it is
 normal to use 1020 instead of 1023 since that is what naïve implementation
 will give. WOW.
-- 
Ticket URL: <https://trac.ffmpeg.org/ticket/7978#comment:8>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker


More information about the FFmpeg-trac mailing list