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

FFmpeg trac at avcodec.org
Sat Jul 24 21:36:19 EEST 2021

#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 jeeb):

 No, that is a separate track :) . libx264 is just the only encoder with
 this sort of separation, and the original bug requested 4:2:0 to be the
 default. I think the separation never really did that, just split off RGB
 from 4:4:4 (so for RGB input you got 4:4:4 instead of RGB by default). So
 as such as far as compatibility is concerned, it never seemed to match the
 requested capability. And it caught my attention since I ended up fixing
 the configure checks related to it :P .

 The real fix will either come with a working version of that swscale check
 (I did poke people about it, but didn't get any response), or when
 elenril's AVFrame based API is merged into swscale, which will come with
 the switch of vf_scale to that API.

 After all, the problem right now is just that when a conversion is done
 (RGB is converted to YCbCr), the given AVFrame field is not reset
 accordingly. You can see an example of that in the `avfilter/vf_scale:
 reset color properties if a conversion was done` commit in my branch.
Ticket URL: <https://trac.ffmpeg.org/ticket/9132#comment:17>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker

More information about the FFmpeg-trac mailing list