[FFmpeg-trac] #9132(ffmpeg:open): Wrong pixel format/output when converting video to yuv444p*
FFmpeg
trac at avcodec.org
Sat Aug 28 23:49:43 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 Balling):
>you could have seen this issue that you are now complaining about was
there even before
I think I did analyse it right, if source file has no BT.709 matrix
libx264rgb sets identity still after your patch, if BT.709 matrix is there
libx264rgb does not set Identity, unspecified is used after your patch.
While '''for ycbcr identity matrix is not needed''', unspecified can work
just as good, for RGB identity is needed and unspecified will lead to
defaulting to ycbcr. I came to this idea to test back from ycbcr back to
rgb today, in the morning. So... I could not have applied patchwork's
patch to test this. Sorry.
Anyway, the problem is that I though that your patch while resetting the
matrix to unspecified will still in the end apply some matrix to VUI. I
was wrong. Sorry about that too. You said so yourself: "Then the color
space information could be reset accordingly (since currently the problem
is that av_frame_copy_props does indeed copy all properties from the
source AVFrame to the output AVFrame, and nothing touches the colorspace
value in the structure)."
--
Ticket URL: <https://trac.ffmpeg.org/ticket/9132#comment:24>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker
More information about the FFmpeg-trac
mailing list