From: James Zern via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: Guangyu Sun <sunguangyucn@gmail.com>, James Zern <jzern@google.com>
Subject: [FFmpeg-devel] Re: [PATCH] avcodec/libvpxenc: fix sRGB colorspace for non-RGB pixel formats
Date: Mon, 23 Feb 2026 13:25:22 -0800
Message-ID: <CABWgkXL3g8=m4j-njEDrA_8-xObqopd3Gcdt5KKtexo9dUVRTQ@mail.gmail.com> (raw)
In-Reply-To: <20260223192155.27035-1-gsun@roblox.com>
Hi,
On Mon, Feb 23, 2026 at 11:22 AM Guangyu Sun via ffmpeg-devel
<ffmpeg-devel@ffmpeg.org> wrote:
>
> When encoding VP9 with a YUV pixel format (e.g. yuv420p) and
> AVCOL_SPC_RGB colorspace metadata, libvpxenc unconditionally set
> VPX_CS_SRGB. This produced a spec-violating bitstream: Profile 0
> (4:2:0) with sRGB colorspace, which is only valid for Profile 1/3
> (4:4:4). The resulting file is undecodable.
>
> RGB pixel formats (GBRP, GBRP10, GBRP12) already correctly set
> ctx->vpx_cs to VPX_CS_SRGB in set_pix_fmt() and bypass the
> colorspace switch in set_colorspace(). So reaching the AVCOL_SPC_RGB
> case means the pixel format is YUV with incorrect RGB metadata.
> Log a warning and fall back to VPX_CS_BT_709.
>
> To reproduce:
>
> # generate a bad source
> ffmpeg -f lavfi -i testsrc=s=64x64:d=1:r=1 -pix_fmt yuv420p -colorspace rgb bad.mp4
> # transcode with default parameters
> ffmpeg -i bad.mp4 bad.webm
> # check decoding
> ffmpeg -i bad.webm -f null -
> # -> 0 frames decoded, error
>
> Signed-off-by: Guangyu Sun <gsun@roblox.com>
> ---
> libavcodec/libvpxenc.c | 12 +++++++++++-
> 1 file changed, 11 insertions(+), 1 deletion(-)
>
> diff --git a/libavcodec/libvpxenc.c b/libavcodec/libvpxenc.c
> index 88c058c403..be731a014f 100644
> --- a/libavcodec/libvpxenc.c
> +++ b/libavcodec/libvpxenc.c
> @@ -902,7 +902,17 @@ static void set_colorspace(AVCodecContext *avctx)
> vpx_cs = ctx->vpx_cs;
> } else {
> switch (avctx->colorspace) {
> - case AVCOL_SPC_RGB: vpx_cs = VPX_CS_SRGB; break;
> + case AVCOL_SPC_RGB:
> + // RGB pixel formats (GBRP, GBRP10, GBRP12) set ctx->vpx_cs
> + // to VPX_CS_SRGB in set_pix_fmt() and take the branch above,
> + // so reaching here means the pixel format is YUV with
> + // incorrect RGB colorspace metadata.
What if the input is yuv444? In that case it could be holding rgb
data. Profile 1 and 3 assume no subsampling when decoding sRGB
content.
> + av_log(avctx, AV_LOG_WARNING,
> + "RGB colorspace is not compatible with pixel format %s, "
> + "using BT.709 instead.\n",
> + av_get_pix_fmt_name(avctx->pix_fmt));
> + vpx_cs = VPX_CS_BT_709;
> + break;
> case AVCOL_SPC_BT709: vpx_cs = VPX_CS_BT_709; break;
> case AVCOL_SPC_UNSPECIFIED: vpx_cs = VPX_CS_UNKNOWN; break;
> case AVCOL_SPC_RESERVED: vpx_cs = VPX_CS_RESERVED; break;
> --
> 2.52.0
>
> _______________________________________________
> ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org
> To unsubscribe send an email to ffmpeg-devel-leave@ffmpeg.org
_______________________________________________
ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org
To unsubscribe send an email to ffmpeg-devel-leave@ffmpeg.org
next prev parent reply other threads:[~2026-02-24 6:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-23 19:21 [FFmpeg-devel] " Guangyu Sun via ffmpeg-devel
2026-02-23 21:25 ` James Zern via ffmpeg-devel [this message]
2026-02-24 0:25 ` [FFmpeg-devel] [PATCH v2] " Guangyu Sun via ffmpeg-devel
2026-02-24 18:33 ` [FFmpeg-devel] " James Zern via ffmpeg-devel
2026-02-24 19:29 ` Guangyu Sun via ffmpeg-devel
2026-02-26 18:05 ` [FFmpeg-devel] [PATCH v3] " Guangyu Sun via ffmpeg-devel
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='CABWgkXL3g8=m4j-njEDrA_8-xObqopd3Gcdt5KKtexo9dUVRTQ@mail.gmail.com' \
--to=ffmpeg-devel@ffmpeg.org \
--cc=jzern@google.com \
--cc=sunguangyucn@gmail.com \
/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