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>
Subject: Re: [FFmpeg-devel] [PATCH v2 3/3] tests: Add fate-hevc-color-reserved
Date: Thu, 22 May 2025 13:10:20 +0800
Message-ID: <tencent_C135D13F9156239CB8E0445ACA3459804E09@qq.com> (raw)
In-Reply-To: <AS8P250MB074455281885FAFF0A3016468F9EA@AS8P250MB0744.EURP250.PROD.OUTLOOK.COM>



> On May 21, 2025, at 21:52, Andreas Rheinhardt <andreas.rheinhardt@outlook.com> wrote:
> 
> Zhao Zhili:
>> From: Zhao Zhili <zhilizhao@tencent.com>
>> 
>> ---
>> tests/fate/hevc.mak                | 3 +++
>> tests/ref/fate/hevc-color-reserved | 6 ++++++
>> 2 files changed, 9 insertions(+)
>> create mode 100644 tests/ref/fate/hevc-color-reserved
>> 
>> diff --git a/tests/fate/hevc.mak b/tests/fate/hevc.mak
>> index 390ccf46e2..8113c04300 100644
>> --- a/tests/fate/hevc.mak
>> +++ b/tests/fate/hevc.mak
>> @@ -294,6 +294,9 @@ FATE_HEVC-$(call FRAMECRC, MOV, HEVC) += fate-hevc-mv-position
>> fate-hevc-alpha: CMD = framecrc -i $(TARGET_SAMPLES)/hevc/alpha.mp4
>> FATE_HEVC-$(call FRAMECRC, MOV, HEVC) += fate-hevc-alpha
>> 
>> +fate-hevc-color-reserved: CMD = framecrc -bsf:v hevc_metadata=colour_primaries=0:transfer_characteristics=0:matrix_coefficients=3 -i $(TARGET_SAMPLES)/hevc-conformance/AMP_A_Samsung_4.bit -vf scale,format=nv12 -frames:v 1
>> +FATE_HEVC-$(call FRAMECRC, HEVC, HEVC, HEVC_METADATA_BSF SCALE_FILTER) += fate-hevc-color-reserved
>> +
>> FATE_SAMPLES_AVCONV += $(FATE_HEVC-yes)
>> FATE_SAMPLES_FFPROBE += $(FATE_HEVC_FFPROBE-yes)
>> 
>> diff --git a/tests/ref/fate/hevc-color-reserved b/tests/ref/fate/hevc-color-reserved
>> new file mode 100644
>> index 0000000000..cba6397aa8
>> --- /dev/null
>> +++ b/tests/ref/fate/hevc-color-reserved
>> @@ -0,0 +1,6 @@
>> +#tb 0: 1/25
>> +#media_type 0: video
>> +#codec_id 0: rawvideo
>> +#dimensions 0: 2560x1600
>> +#sar 0: 0/1
>> +0,          0,          0,        1,  6144000, 0x427b9a00
> 
> This seems to simply presume that hevc_metadata does what it is supposed
> to do, but this is not really tested. If hevc_metadata were a no-op for
> this, it would pass the test. Why don't you use something with a hash of
> the output of hevc_metadata?

Added another test. Forgive me for "PATCH v2” which should be "PATCH v3”.

https://ffmpeg.org/pipermail/ffmpeg-devel/2025-May/343927.html

> 
> - Andreas
> 
> _______________________________________________
> 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-22  5:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250521130546.4003-1-quinkblack@foxmail.com>
2025-05-21 13:06 ` [FFmpeg-devel] [PATCH " Zhao Zhili
2025-05-21 13:11   ` Andreas Rheinhardt
2025-05-21 13:26     ` [FFmpeg-devel] [PATCH v2 " Zhao Zhili
2025-05-21 13:52       ` Andreas Rheinhardt
2025-05-22  5:10         ` Zhao Zhili [this message]
2025-05-21 13:28     ` [FFmpeg-devel] [PATCH " Zhao Zhili
2025-05-21 13:37       ` Zhao Zhili
2025-05-21 13:50         ` Andreas Rheinhardt

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_C135D13F9156239CB8E0445ACA3459804E09@qq.com \
    --to=quinkblack-at-foxmail.com@ffmpeg.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