On Fri, 2 Mar 2018 11:14:21 +0100
Timo Rothenpieler wrote:
>
> It's definitely better than the current situation, and I can't think
> of a scenario where it breaks something that's not already broken.
> So LGTM from me.
>
> The other patches also look sensible to me, but I'm not the one to Ok
>
On 02.03.2018 05:26, Philip Langdale wrote:
> nvenc doesn't support P016, but we have two problems today:
>
> 1) We declare support for YUV444P16 which nvenc also doesn't support.
>We do this because it's the only pix_fmt we have that can
>approximate nvenc's internal format that is YUV444
nvenc doesn't support P016, but we have two problems today:
1) We declare support for YUV444P16 which nvenc also doesn't support.
We do this because it's the only pix_fmt we have that can
approximate nvenc's internal format that is YUV444P10 with data in
MSBs instead of LSBs. Because the
