On Sun, Aug 29, 2021 at 9:21 PM Paul B Mahol <one...@gmail.com> wrote: > > probably fine if fate passes
Yea, FATE passes :) . I think this stuff not being noticed until now is due to nothing checking the metadata values returned by vf_scale (since pix_fmt and actual logic is not changed at all with these output AVFrame metadata changes): - The first fix I did was for RGB->YCbCr still being flagged as RGB (and thus encoders like the libx264 wrapper would gladly comply, leading to bugs like issue #9132 ) - This one fixes the opposite conversion where your YCbCr input has matrix coefficients configured, and the RGB output still has that value as-is from the av_frame_copy_props call (and once again, encoder complies). Jan _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
