From: Philip Langdale <philipl@overt.org>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH 0/3] v2: vaapi: switch 8bit 444 format to VUYX
Date: Tue, 23 Aug 2022 14:45:37 -0700
Message-ID: <20220823144537.77435456@fido7> (raw)
In-Reply-To: <20220820043146.398996-1-philipl@overt.org>
On Fri, 19 Aug 2022 21:31:43 -0700
Philip Langdale <philipl@overt.org> wrote:
> After discussion with Mark, I'm switching the preferred format for
> 8bit 444 content in vaapi to VUYX, which is the alpha-less variant of
> VUYA.
>
> This format is formally supported by the driver, so we don't even need
> to do any fudging.
>
> I am not removing VUYA because we found another use for it, replacing
> the previous requirement to use v408[enc|dec] to work with it.
>
> * v2: Fix test update in wrong change
> * v3: Remove incorrect alpha flag from pix_fmt
>
> Philip Langdale (3):
> lavu/pixfmt: Introduce VUYX format
> libswscale: add support for VUYX format
> lavc/vaapi: Switch preferred 8bit 444 format to VUYX
I will push this in a few days if there are no comments.
--phil
_______________________________________________
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".
next prev parent reply other threads:[~2022-08-23 21:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-20 4:31 Philip Langdale
2022-08-20 4:31 ` [FFmpeg-devel] [PATCH 1/3] lavu/pixfmt: Introduce VUYX format Philip Langdale
2022-08-20 4:31 ` [FFmpeg-devel] [PATCH 2/3] libswscale: add support for " Philip Langdale
2022-08-20 4:31 ` [FFmpeg-devel] [PATCH 3/3] lavc/vaapi: Switch preferred 8bit 444 format to VUYX Philip Langdale
2022-08-23 21:45 ` Philip Langdale [this message]
2022-08-26 2:13 ` [FFmpeg-devel] [PATCH 0/3] v2: vaapi: switch " Philip Langdale
-- strict thread matches above, loose matches on Subject: below --
2022-08-20 2:14 Philip Langdale
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=20220823144537.77435456@fido7 \
--to=philipl@overt.org \
--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