On 2017-02-02 08:26, wm4 wrote:
Does supporting the nvenc 4:4:4 format even have any advantage? Does it
support encoding something non-4:2:0? If not, then the first option is
probably preferable for now.
With sufficiently new hardware it does. It will output h.264 or hevc
with 4:4:4 by default
On Thu, Feb 02, 2017 at 08:14:00AM -0800, Philip Langdale wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On Thu, 2 Feb 2017 12:08:59 +0100
> Michael Niedermayer wrote:
>
> > On Thu, Feb 02, 2017 at 11:48:49AM +0100, Michael Niedermayer wrote:
> > > On Thu, Feb 02, 2017 at 11:26:26A
On Thu, 2 Feb 2017 08:14:00 -0800
Philip Langdale wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On Thu, 2 Feb 2017 12:08:59 +0100
> Michael Niedermayer wrote:
>
> > On Thu, Feb 02, 2017 at 11:48:49AM +0100, Michael Niedermayer wrote:
> > > On Thu, Feb 02, 2017 at 11:26:26AM +0
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, 2 Feb 2017 12:08:59 +0100
Michael Niedermayer wrote:
> On Thu, Feb 02, 2017 at 11:48:49AM +0100, Michael Niedermayer wrote:
> > On Thu, Feb 02, 2017 at 11:26:26AM +0100, Timo Rothenpieler wrote:
> > > >> In the mean time, common 12 bit cont
On Thu, Feb 02, 2017 at 11:48:49AM +0100, Michael Niedermayer wrote:
> On Thu, Feb 02, 2017 at 11:26:26AM +0100, Timo Rothenpieler wrote:
> > >> In the mean time, common 12 bit content (YUV420P12 or P016) will be
> > >> correctly converted to P010 for nvenc.
> > >
> > > What does this change have
On Thu, Feb 02, 2017 at 11:26:26AM +0100, Timo Rothenpieler wrote:
> >> In the mean time, common 12 bit content (YUV420P12 or P016) will be
> >> correctly converted to P010 for nvenc.
> >
> > What does this change have to do with 4:2:0 content?
>
> Apparently swscale decides that any kind of 12 o
>> In the mean time, common 12 bit content (YUV420P12 or P016) will be
>> correctly converted to P010 for nvenc.
>
> What does this change have to do with 4:2:0 content?
Apparently swscale decides that any kind of 12 or 16 bit content, even
if 4:2:0, whould be converted to YUV444P16 instead of do
On Wed, Feb 1, 2017 at 11:54 PM, Philip Langdale wrote:
> nvenc supports a YUV444P10 format with the same bit layout as P010,
> with the data bits at the MSB end.
>
> Unfortunately, the current YUV444P10 format we have defined puts
> the data bits at the LSB end.
>
> This mismatch led to us introd
nvenc supports a YUV444P10 format with the same bit layout as P010,
with the data bits at the MSB end.
Unfortunately, the current YUV444P10 format we have defined puts
the data bits at the LSB end.
This mismatch led to us introducing a fudge in nvenc where we
mapped their 444P10 format to the ffm
