Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Araz <primeadvice@gmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH 1/4, v2] avcodec/amfenc: Fixes the color information in the output.
Date: Thu, 1 Aug 2024 16:58:28 +0200
Message-ID: <CAGT-SYV2HdSOpvK=ASD1jK7P+TcPyWGNvq2gm1Z2vcf-St1-7g@mail.gmail.com> (raw)
In-Reply-To: <AS8P250MB0744AF439D00253778302F6D8FB22@AS8P250MB0744.EURP250.PROD.OUTLOOK.COM>

> > +    AV_PIX_FMT_P010,
> >      AV_PIX_FMT_NONE
> >    };
> >
> >   @@ -72,6 +73,7 @@ static const FormatMap format_map[] =
> >    {
> >        { AV_PIX_FMT_NONE,       AMF_SURFACE_UNKNOWN },
> >        { AV_PIX_FMT_NV12,       AMF_SURFACE_NV12 },
> >   +    { AV_PIX_FMT_P010,       AMF_SURFACE_P010 },

>  Why is this in this commit?

This patch mostly fixes color information.
10-bit pixel format update is too small to make a separate patch for it.
I can rename that patch or split it on 2 patches.
_______________________________________________
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:[~2024-08-01 14:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-01 11:13 Araz Iusubov
2024-08-01 11:13 ` [FFmpeg-devel] [PATCH 2/4,v2] avcodec/amfenc: HDR metadata Araz Iusubov
2024-08-01 11:13 ` [FFmpeg-devel] [PATCH 3/4, v2] avcodec/amfenc: add 10 bit encoding in av1_amf Araz Iusubov
2024-08-01 11:13 ` [FFmpeg-devel] [PATCH 4/4, v2] avcodec/amfenc: GPU driver version check Araz Iusubov
2024-08-01 13:17 ` [FFmpeg-devel] [PATCH 1/4, v2] avcodec/amfenc: Fixes the color information in the output Andreas Rheinhardt
2024-08-01 14:58   ` Araz [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='CAGT-SYV2HdSOpvK=ASD1jK7P+TcPyWGNvq2gm1Z2vcf-St1-7g@mail.gmail.com' \
    --to=primeadvice@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