#11457: The order of parsed "Mastering display colour volume SEI message" seems
wrong.
-------------------------------------+-------------------------------------
             Reporter:  SYamaguchi   |                    Owner:  (none)
                 Type:  defect       |                   Status:  closed
             Priority:  normal       |                Component:
                                     |  undetermined
              Version:  unspecified  |               Resolution:  invalid
             Keywords:               |               Blocked By:
             Blocking:               |  Reproduced by developer:  0
Analyzed by developer:  0            |
-------------------------------------+-------------------------------------
Changes (by James):

 * component:  ffprobe => undetermined
 * resolution:   => invalid
 * status:  new => closed
 * version:  6.0 => unspecified

Comment:

 The ordering of values in the mdcv SEI message is GBR as per the spec:
 {{{
 For describing mastering displays that use red, green, and blue colour
 primaries, it is suggested that index value c equal to 0 should correspond
 to the green primary, c equal to 1 should correspond to the blue primary,
 and c equal to 2 should correspond to the red colour primary
 }}}

 And this is what's coded and therefore exported:
 {{{
 [trace_headers @] Mastering Display Colour Volume
 [trace_headers @] 32          display_primaries_x[0]
 1000010001110001 = 33905
 [trace_headers @] 48          display_primaries_y[0]
 0011111001001001 = 15945
 [trace_headers @] 64          display_primaries_x[1]
 0010111000110001 = 11825
 [trace_headers @] 80          display_primaries_y[1]
 1000100110101000 = 35240
 [trace_headers @] 96          display_primaries_x[2]
 0001101110001001 = 7049
 [trace_headers @] 112         display_primaries_y[2]
 0000100110001101 = 2445
 [trace_headers @] 128         white_point_x
 0011110100010010 = 15634
 [trace_headers @] 144         white_point_y
 0100000001000010 = 16450
 [trace_headers @] 160         max_display_mastering_luminance
 00000000100110001001011010000000 = 10000000
 [trace_headers @] 192         min_display_mastering_luminance
 00000000000000000000000000000001 = 1
 }}}

 If the values are wrong, then whatever generated the SEI message for this
 sample is at fault, not ffmpeg's decoder. More so considering that the
 Content Light Level Information SEI message is suspiciously all zeroes.
-- 
Ticket URL: <https://trac.ffmpeg.org/ticket/11457#comment:1>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker
_______________________________________________
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-trac

To unsubscribe, visit link above, or email
ffmpeg-trac-requ...@ffmpeg.org with subject "unsubscribe".

Reply via email to