Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Carl Eugen Hoyos <ceffmpeg@gmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH v1 1/9] lavu/pix_fmt: add P012 pixel format
Date: Sun, 23 Jan 2022 01:06:05 +0100
Message-ID: <CAB0OVGpK0-5O-GAQ3v=pvxbzwoTLmb8ic_bZMhtgpFoy2T8XVA@mail.gmail.com> (raw)
In-Reply-To: <BN9PR11MB5515A418A100567B1FBDB6BA9E5B9@BN9PR11MB5515.namprd11.prod.outlook.com>

Am Fr., 21. Jan. 2022 um 06:56 Uhr schrieb Xiang, Haihao
<haihao.xiang-at-intel.com@ffmpeg.org>:
>
> > -----Original Message-----
> > From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of Xiang,
> > Haihao
> > Sent: Tuesday, June 30, 2020 15:34
> > To: ffmpeg-devel@ffmpeg.org
> > Subject: Re: [FFmpeg-devel] [PATCH v1 1/9] lavu/pix_fmt: add P012 pixel
> > format
> >
> > > Am So., 28. Juni 2020 um 23:01 Uhr schrieb Mark Thompson <sw@jkqxz.net>:
> > >
> > > > FFmpeg has always used pixfmt as defining both the memory layout
> > > > and which bits are used in that (so, for example, ARGB and 0RGB
> > > > are not the same thing)
> > >
> > > But they have the same bitdepth per component...
>
> > Agree with Mark. P012 and P016 have different significant bits, we should use
> > different pixfmts, otherwise an extra field in AVFrame is needed for bit depth.
> >
> > BTW there are the YUV420P variants for 10 / 12 / 14 / 16 bit in FFmpeg, it
> > would be better to follow FFmpeg's style to introduce P012 format instead
> > of reusing P016.

I was under the impression that YUV420P12 is much more different from
YUV420P16 than P012 from P016: Did I misunderstand?
(Reading the thread again, I don't think I did)

> Sorry for picking up this old thread.
>
> We'd like to add the support for 12bit decoding / encoding in VAAPI and QSV.
> Is there any other concern if adding P012 in FFmpeg ?

Did you already explain why you cannot use P016 or in which situation
it would create a different output?

Carl Eugen
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".

  reply	other threads:[~2022-01-23  0:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20200619015248.21873-1-fei.w.wang@intel.com>
     [not found] ` <CA+anqdyoVCxv+cbq3Jv3b12sNzPTV4Q97x48LfFzRUy+3Sko0A@mail.gmail.com>
     [not found]   ` <3655b2de-b1b4-7bd6-6b5d-40fd7e1022a3@jkqxz.net>
     [not found]     ` <CAB0OVGoUrUORFimsZ65a6qExHWtsLwvYtTJM5DoFxWaQ4U9F_w@mail.gmail.com>
     [not found]       ` <3c400dee9fc251dd1c35864952ead7c91d90bee5.camel@intel.com>
2022-01-21  5:56         ` Xiang, Haihao
2022-01-23  0:06           ` Carl Eugen Hoyos [this message]
2022-01-26  8:32             ` Xiang, Haihao
2022-01-26 22:30               ` Carl Eugen Hoyos

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAB0OVGpK0-5O-GAQ3v=pvxbzwoTLmb8ic_bZMhtgpFoy2T8XVA@mail.gmail.com' \
    --to=ceffmpeg@gmail.com \
    --cc=ffmpeg-devel@ffmpeg.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
		ffmpegdev@gitmailbox.com
	public-inbox-index ffmpegdev

Example config snippet for mirrors.


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git