From: Anton Khirnov <anton@khirnov.net>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] add HDR image format test coverage
Date: Mon, 18 Jul 2022 13:16:23 +0200
Message-ID: <165814298357.25016.14142188982130160036@lain.khirnov.net> (raw)
In-Reply-To: <CAPYw7P6rFFeibEmZLb+j65TOZ4HWfYWejm6zmZsJa347e3WBbg@mail.gmail.com>
Quoting Paul B Mahol (2022-07-17 16:51:20)
> Patch attached.
>
> From 7080795a572f8f741d4a00b2db02c8e00ce6aaf2 Mon Sep 17 00:00:00 2001
> From: Paul B Mahol <onemda@gmail.com>
> Date: Sun, 17 Jul 2022 15:12:12 +0200
> Subject: [PATCH] fate: add Radiance HDR image test
>
> Signed-off-by: Paul B Mahol <onemda@gmail.com>
> ---
> tests/fate/lavf-image.mak | 1 +
> tests/ref/lavf/hdr | 3 +++
> 2 files changed, 4 insertions(+)
> create mode 100644 tests/ref/lavf/hdr
>
> diff --git a/tests/fate/lavf-image.mak b/tests/fate/lavf-image.mak
> index 38d3689abf..6a87ad25a4 100644
> --- a/tests/fate/lavf-image.mak
> +++ b/tests/fate/lavf-image.mak
> @@ -52,6 +52,7 @@ FATE_LAVF_IMAGES-$(call LAVF_IMAGES, XWD) += rgb8.xwd
> FATE_LAVF_IMAGES-$(call LAVF_IMAGES, XWD) += rgb4_byte.xwd
> FATE_LAVF_IMAGES-$(call LAVF_IMAGES, XWD) += gray.xwd
> FATE_LAVF_IMAGES-$(call LAVF_IMAGES, XWD) += monow.xwd
> +FATE_LAVF_IMAGES-$(call LAVF_IMAGES, HDR) += hdr
>
> FATE_LAVF_IMAGES = $(FATE_LAVF_IMAGES-yes:%=fate-lavf-%)
>
> diff --git a/tests/ref/lavf/hdr b/tests/ref/lavf/hdr
> new file mode 100644
> index 0000000000..129c309197
> --- /dev/null
> +++ b/tests/ref/lavf/hdr
> @@ -0,0 +1,3 @@
> +95961d2136160b39d71858305226f5f2 *tests/data/images/hdr/02.hdr
> +tests/data/images/hdr/%02d.hdr CRC=0x1a5ee73b
> +326788 tests/data/images/hdr/02.hdr
> --
> 2.36.1
The codec seems to be floating point, will this be bitexact everywhere?
--
Anton Khirnov
_______________________________________________
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-07-18 11:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-17 14:51 Paul B Mahol
2022-07-18 11:16 ` Anton Khirnov [this message]
2022-07-18 11:50 ` Paul B Mahol
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=165814298357.25016.14142188982130160036@lain.khirnov.net \
--to=anton@khirnov.net \
--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