On 06/10/16 13:21, Yogender Gupta wrote:
>>> I'd fold it in the current check for ctx->data_pix_fmt that is
>>> already present.
> I kept it separate to maintain consistency as it is set for HEVC
>
I see what you mean, I guess the patch can go in as is then.
lu
>> I'd fold it in the current check for ctx->data_pix_fmt that is already
>> present.
I kept it separate to maintain consistency as it is set for HEVC
>> Currently we are setting FF_PROFILE_H264_HIGH_444 should it be changed to
>> FF_PROFILE_H264_HIGH_444_PREDICTIVE as well?
On 06/10/16 11:10, Yogender Gupta wrote:
> +if (ctx->data_pix_fmt == AV_PIX_FMT_YUV444P) {
> +cc->profileGUID = NV_ENC_H264_PROFILE_HIGH_444_GUID;
> +avctx->profile = FF_PROFILE_H264_HIGH_444_PREDICTIVE;
> +}
I'd fold it in the current check for ctx->data_pix_fmt that is
This patches forces high_444 profile selection for yuv444p inputs for
nvenc_h264.
Thanks,
Yogender
---
This email message is for the sole use of the intended recipient(s) and may
contain
confidential information.
