Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Zhao Zhili <quinkblack-at-foxmail.com@ffmpeg.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: Niklas Haas <git@haasn.dev>
Subject: Re: [FFmpeg-devel] [PATCH v2 1/4] avcodec/h2645_vui: Ensure color primaries/trc/space isn't reserved value
Date: Tue, 27 May 2025 11:07:22 +0800
Message-ID: <tencent_4F803C34CF3FC556A99CB8E1E25A78347F09@qq.com> (raw)
In-Reply-To: <CABGuwEkz20H=RAS+aX79C3BC3NgOVFVzN78UF4Vg=TmuWRgheQ@mail.gmail.com>



> On May 27, 2025, at 02:48, Kieran Kunhya via ffmpeg-devel <ffmpeg-devel@ffmpeg.org> wrote:
> 
> On Mon, May 26, 2025 at 8:13 PM Zhao Zhili
> <quinkblack-at-foxmail.com@ffmpeg.org> wrote:
>> 
>> 
>> 
>>> On May 22, 2025, at 13:06, Zhao Zhili <quinkblack-at-foxmail.com@ffmpeg.org> wrote:
>>> 
>>> From: Zhao Zhili <zhilizhao@tencent.com>
>>> 
>>> Fix error reported by swscaler:
>>> Unsupported input (Operation not supported): fmt:yuv420p csp:unknown prim:reserved trc:bt709 -> fmt:yuv420p csp:bt709 prim:reserved trc:bt709
>>> —
>> 
>> 
>> Will apply soon.
> 
> Surely this should be filtered in swscale?
> I think we need to pass through future reserved values of csp and stuff.

Both of H.264 and H.265 spec says:

> Decoders shall interpret reserved values of colour_primaries as equivalent to the value 2.

The code matches the spec.

There is another similar topic in 2024

https://ffmpeg.org/pipermail/ffmpeg-devel/2024-December/337160.html

cc haasn. This is a regression. Should the fixes go into swscale/avfilter, or the decoder, or both?

Pass through reserved value of csp has its use case. However, it’s more common that those samples are generated by buggy software.

> 
> Kieran
> _______________________________________________
> 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".

_______________________________________________
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:[~2025-05-27  3:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-22  5:06 Zhao Zhili
2025-05-26 12:12 ` Zhao Zhili
2025-05-26 18:48   ` Kieran Kunhya via ffmpeg-devel
2025-05-27  3:07     ` Zhao Zhili [this message]
2025-05-28  7:33       ` Zhao Zhili

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=tencent_4F803C34CF3FC556A99CB8E1E25A78347F09@qq.com \
    --to=quinkblack-at-foxmail.com@ffmpeg.org \
    --cc=ffmpeg-devel@ffmpeg.org \
    --cc=git@haasn.dev \
    /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