From: Andreas Rheinhardt <andreas.rheinhardt@outlook.com>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH 0/1] fate/jpegxl: add multiframe permuted TOC image parser
Date: Sun, 10 Dec 2023 15:07:05 +0100
Message-ID: <DU0P250MB0747A4F32A7ED364640465208F88A@DU0P250MB0747.EURP250.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <20231209194938.308992-1-leo.izen@gmail.com>
Leo Izen:
> This patch requires a sample that hasn't been uploaded yet. It can be found
> at [1] and it should be placed at jxl/orange.jxl once uploaded. It's 262k,
> which is not very large, but large enough that I did not want to attach it
> to this email.
>
> [1]: https://buzo.us/O.jxl
>
> sample sha256sum: 9288337dc0d37effd1f539d4e20083a8ffed757e486f4098121520c74e8de6f6
> sample signature: https://buzo.us/A.asc
>
> Leo Izen (1):
> fate/jpegxl: add multiframe permuted TOC image parser test
>
> tests/fate/jxl.mak | 3 +++
> tests/ref/fate/jxl-multiframe-permuted-toc | 11 +++++++++++
> 2 files changed, 14 insertions(+)
> create mode 100644 tests/ref/fate/jxl-multiframe-permuted-toc
>
I disagree with your assertion that 262k is not very large. Why do you
use a 2400x2400 sample?
- 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".
next prev parent reply other threads:[~2023-12-10 14:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-09 19:49 Leo Izen
2023-12-09 19:49 ` [FFmpeg-devel] [PATCH 1/1] fate/jpegxl: add multiframe permuted TOC image parser test Leo Izen
2023-12-09 20:25 ` [FFmpeg-devel] [PATCH 0/1] fate/jpegxl: add multiframe permuted TOC image parser Thilo Borgmann via ffmpeg-devel
2023-12-10 14:07 ` Andreas Rheinhardt [this message]
2023-12-10 14:47 ` Leo Izen
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=DU0P250MB0747A4F32A7ED364640465208F88A@DU0P250MB0747.EURP250.PROD.OUTLOOK.COM \
--to=andreas.rheinhardt@outlook.com \
--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