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: Wed, 26 Jan 2022 23:30:26 +0100
Message-ID: <CAB0OVGrK1BTyNuhyEJVCRr6m_e2T=C7_pMSD_3bEhK2ri3X1BA@mail.gmail.com> (raw)
In-Reply-To: <32f6de089d7c6c536396970b68089d74dc2d7204.camel@intel.com>

Am Mi., 26. Jan. 2022 um 09:33 Uhr schrieb Xiang, Haihao
<haihao.xiang-at-intel.com@ffmpeg.org>:

> > Did you already explain why you cannot use P016 or in which situation
> > it would create a different output?
>
> $ ffmpeg -hwaccel vaapi -f rawvideo -pix_fmt p016 -s 1920x1080 -i input.yuv
> -vf "hwupload,format=vaapi" -c:v hevc_vaapi -f null -
>
> If using P016, how will we know the input is 12bit indeed

Thank you for explaining this, at least I didn't realize this reason earlier!

I hope we can find another solution than to add an additional pix_fmt.
I believe I had suggested an additional property bit_depth for raw video
a long time ago.

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-26 22:30 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
2022-01-26  8:32             ` Xiang, Haihao
2022-01-26 22:30               ` Carl Eugen Hoyos [this message]

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='CAB0OVGrK1BTyNuhyEJVCRr6m_e2T=C7_pMSD_3bEhK2ri3X1BA@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