Interestingly, I followed to actual merge request from 2024 and https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/27810 Cr channel not encoded As problem in h264 encode case. So, may be this bug was not fixed, or re-surfaced at some point in time? I also do not know how to set those encode modes, via avcodec params ?
On 2/15/26 2:14 PM, Andrew Randrianasulu wrote:
Interestingly, I followed to actual merge request from 2024 and
https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/27810
Cr channel not encoded
As problem in h264 encode case.
So, may be this bug was not fixed, or re-surfaced at some point in time?
Yeah, this seems to be the case as Andrea had no color issue.
I also do not know how to set those encode modes, via avcodec params ?
I'll try to express my opinion, even though I know nothing about the issue and it would be better to keep quiet. ;) Could it be the “planar” or “semi-planar” pixel format? Yuv420 is planar. That is, the three “planes” Y, Cb, and Cr are taken into account. I have read that Vulkan poorly supports YUV420, while it is more compatible with NV12, which is semi-planar, i.e., it considers the Y plane and a second plane that includes Cb and Cr together. Perhaps the problem with Intel drivers is that they use a planar format, but Vulkan only reads two planes instead of three?
participants (3)
-
Andrea paz -
Andrew Randrianasulu -
Terje J. Hanssen