[FFmpeg-trac] #9132(ffmpeg:open): Wrong pixel format/output when converting video to yuv444p*

[FFmpeg]

#9132: Wrong pixel format/output when converting video to yuv444p*
------------------------------------+----------------------------------
             Reporter:  viley       |                    Owner:  (none)
                 Type:  defect      |                   Status:  open
             Priority:  important   |                Component:  ffmpeg
              Version:  git-master  |               Resolution:
             Keywords:  regression  |               Blocked By:
             Blocking:              |  Reproduced by developer:  1
Analyzed by developer:  0           |
------------------------------------+----------------------------------
Comment (by Balling):

 You now (after 9dd410c80416197188337e3b7e1600be41d2ea64) set matrix
 unspecified in VUI, which is very bad! Check with ffmpeg -i TESTCASE-
 yuvnew.mp4 -c copy -bsf:v trace_headers -f null -

 this file:
 ffmpeg -i rec.mkv -vf
 scale=out_color_matrix=bt709:flags=accurate_rnd,format=yuv420p -c:v
 libx264 -crf 10 -color_primaries 1 -color_trc 1 TESTCASE-yuvnew.mp4 where
 rec.mkv is rgb from #9374.

 What is worse, not only the problem here is not really fixed, but also the
 opposite problem when you do ffmpeg -i .\TESTCASE-yuvnew.mp4 -vf
 scale=flags=accurate_rnd -c:v libx264rgb -crf 10 -color_primaries 1
 -color_trc 1  rgbsupper.mp4 from YCbCr with -colorspace 0 happens
 (produced with ffmpeg -i rec.mkv -vf
 scale=out_color_matrix=bt709:flags=accurate_rnd,format=yuv420p -c:v
 libx264 -crf 10 -color_primaries 1 -color_trc 1 '''-colorspace 1'''
 TESTCASE-yuvnewer.mp4). It does not happen when -colorspace 1 is not done.
 Oogh.
-- 
Ticket URL: <https://trac.ffmpeg.org/ticket/9132#comment:22>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker