From: Pierre-Anthony Lemieux <pal@sandflow.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] fate/jpeg2000dec: add support for p0_10.j2k
Date: Tue, 18 Jun 2024 07:59:07 -0700
Message-ID: <CAF_7JxCQJqPtMDRQ0UfnXTuT9CXGfcmHXN=OoHEtnSGM-UNv0Q@mail.gmail.com> (raw)
In-Reply-To: <4083621846eede3997dc08dd93ccb722dc851f58.camel@haerdin.se>
On Tue, Jun 18, 2024 at 7:25 AM Tomas Härdin <git@haerdin.se> wrote:
>
> lör 2024-06-15 klockan 21:47 -0700 skrev pal@sandflow.com:
> > From: Pierre-Anthony Lemieux <pal@palemieux.com>
> >
> > p0_10.j2k is one of the reference codestreams included in Rec. ITU-T
> > T.803 | ISO/IEC 15444-4.
> > ---
> > tests/fate/jpeg2000.mak | 3 +++
> > tests/ref/fate/jpeg2000dec-p0_10 | 6 ++++++
> > 2 files changed, 9 insertions(+)
> > create mode 100644 tests/ref/fate/jpeg2000dec-p0_10
>
> Sounds good, assuming it decodes correctly
>
> If there are more files like this, could we add all of them in one go?
I expect significantly more files to be added once the "Add support
for placeholder passes, CAP, and CPF markers" patch is merged. In the
meantime, I do not see a downside to updating FATE since it addresses
a specific bug in trac.
>
> /Tomas
> _______________________________________________
> 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".
next prev parent reply other threads:[~2024-06-18 14:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-16 4:47 pal
2024-06-18 14:24 ` Tomas Härdin
2024-06-18 14:59 ` Pierre-Anthony Lemieux [this message]
2024-06-19 8:42 ` Tomas Härdin
2024-06-20 20:09 ` Pierre-Anthony Lemieux
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='CAF_7JxCQJqPtMDRQ0UfnXTuT9CXGfcmHXN=OoHEtnSGM-UNv0Q@mail.gmail.com' \
--to=pal@sandflow.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