From: "Tomas Härdin" <git@haerdin.se>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH v4 1/3] avcodec/jpeg2000dec: Add support for CAP and CPF markers
Date: Fri, 26 Jul 2024 10:04:31 +0200
Message-ID: <f3ad4134d4ff61f7460c37b9b411df4886e65851.camel@haerdin.se> (raw)
In-Reply-To: <CAF_7JxA3fHtOEE7YqFNzYbFx9E7bxWXwqLhqai88u-WASw3VEw@mail.gmail.com>
tor 2024-07-25 klockan 17:06 -0700 skrev Pierre-Anthony Lemieux:
> On Thu, Jul 25, 2024 at 2:17 AM Tomas Härdin <git@haerdin.se> wrote:
> >
> > sön 2024-07-21 klockan 14:07 +0900 skrev Pierre-Anthony Lemieux:
> > > On Sat, Jul 20, 2024 at 5:12 PM Tomas Härdin <git@haerdin.se>
> > > wrote:
> > > >
> > > > tor 2024-07-18 klockan 23:10 +0900 skrev Pierre-Anthony
> > > > Lemieux:
> > > > > On Mon, Jul 15, 2024 at 10:33 PM Tomas Härdin
> > > > > <git@haerdin.se>
> > > > > wrote:
> > > > > >
> > > > > > fre 2024-07-12 klockan 12:51 -0700 skrev Pierre-Anthony
> > > > > > Lemieux:
> > > > > > > On Thu, Jul 11, 2024 at 10:28 PM Tomas Härdin
> > > > > > > <git@haerdin.se>
> > > > > > > wrote:
> > > > > > > >
> > > > > > > > > + if (s->in_tile_headers == 1 && s->isHT
> > > > > > > > > &&
> > > > > > > > > (!s-
> > > > > > > > > > Ccap15_b11))
> > > > > > > > > + av_log(s->avctx, AV_LOG_WARNING,
> > > > > > > > > "COD
> > > > > > > > > marker
> > > > > > > > > is
> > > > > > > > > found in HOMOGENEOUS HT set\n");
> > > > > > > >
> > > > > > > > How bad is this and the other markers being present in
> > > > > > > > this
> > > > > > > > case?
> > > > > > >
> > > > > > > At the very least, it means that signaling is
> > > > > > > inconsistent
> > > > > > > within
> > > > > > > the
> > > > > > > codestream since the standard states that:
> > > > > > > """
> > > > > > > The HOMOGENEOUS set is the set of HTJ2K codestreams
> > > > > > > where:
> > > > > > > • none of the functional marker segments, e.g., COD, COC,
> > > > > > > RGN,
> > > > > > > QCD,
> > > > > > > QCC, and POC, are present in any
> > > > > > > tile-part header; and
> > > > > > > • no PPT marker segment is present.
> > > > > > > """
> > > > > > >
> > > > > > > The point of signalling that a codestream is
> > > > > > > "HOMOGENEOUS" is
> > > > > > > to
> > > > > > > allow
> > > > > > > decoders to configure themselves solely based on
> > > > > > > information
> > > > > > > retrieved
> > > > > > > entirely from the main header.
> > > > > > >
> > > > > > > Since, AFAIK, FFMPEG does not rely on the HOMOGENEOUS to
> > > > > > > short-
> > > > > > > circuit
> > > > > > > configuration, incorrect HOMOGENEOUS signalling will
> > > > > > > likely
> > > > > > > not
> > > > > > > impact
> > > > > > > FFMPEG.
> > > > > >
> > > > > > It could happen that information in tile headers contradict
> > > > > > information
> > > > > > in the main header, right? In such a case it sounds like we
> > > > > > can't
> > > > > > be
> > > > > > sure which decode is the correct one.
> > > > >
> > > > > Per the spec, the decoder uses the COD information in tile-
> > > > > parts
> > > > > over
> > > > > the COD information in the header.
> > > > >
> > > > > The issue here is that a decoder, upon seeing HOMOGENEOUS,
> > > > > simply
> > > > > does
> > > > > not bother with looking for COD information in tile-parts,
> > > > > thereby
> > > > > missing critical information.
> > > >
> > > > So it is actually perfectly legal? Then it seems this patch is
> > > > wrong
> > >
> > > What is not "illegal": the HOMOGENEOUS flag being equal to true
> > > *and*
> > > having COD marker segments in tile-parts.
> > >
> > > This is what the patch detects.
> > >
> > > FFMPEG can decode such illegal codestream. Other decoders might
> > > not.
> > >
> > > The question is: what should FFMPEG do? Should FFMPEG exit or
> > > warn
> > > and continue.
> >
> > If the spec allows it but it's perhaps unadviced then warning about
> > it
> > seems reasonable
>
> (I totally messed up my double negative. Repeat below. Sorry for the
> confusion.)
>
> What is "illegal": the HOMOGENEOUS flag being equal to true *and*
> having COD marker segments in tile-parts.
>
> This is what the patch detects.
>
> FFMPEG can decode such illegal codestream. Other decoders might not.
>
> The question is: what should FFMPEG do? Should FFMPEG exit or warn
> and continue.
Since it's illegal then we should complain and bail out. Users that
*really* want it to keep going can change the code.
/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".
next prev parent reply other threads:[~2024-07-26 8:04 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-24 13:37 Osamu Watanabe
2024-06-24 13:37 ` [FFmpeg-devel] [PATCH v4 2/3] avcodec/jpeg2000dec: Add support for placeholder passes Osamu Watanabe
2024-06-24 13:37 ` [FFmpeg-devel] [PATCH v4 3/3] avcodec/jpeg2000dec: Fix HT decoding Osamu Watanabe
2024-07-12 4:57 ` [FFmpeg-devel] [PATCH v4 1/3] avcodec/jpeg2000dec: Add support for CAP and CPF markers Pierre-Anthony Lemieux
2024-07-13 10:31 ` WATANABE Osamu
2024-07-12 5:27 ` Tomas Härdin
2024-07-12 19:51 ` Pierre-Anthony Lemieux
2024-07-15 13:32 ` Tomas Härdin
2024-07-18 14:10 ` Pierre-Anthony Lemieux
2024-07-20 8:12 ` Tomas Härdin
2024-07-21 5:07 ` Pierre-Anthony Lemieux
2024-07-25 9:16 ` Tomas Härdin
2024-07-26 0:06 ` Pierre-Anthony Lemieux
2024-07-26 8:04 ` Tomas Härdin [this message]
2024-07-26 21:11 ` Pierre-Anthony Lemieux
2024-07-29 7:46 ` WATANABE Osamu
2024-07-26 21:29 ` Michael Niedermayer
2024-07-26 21:32 ` Pierre-Anthony Lemieux
2024-07-30 20:22 ` Tomas Härdin
2024-07-30 21:39 ` Michael Niedermayer
2024-08-01 1:58 ` WATANABE Osamu
2024-08-01 2:40 ` WATANABE Osamu
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=f3ad4134d4ff61f7460c37b9b411df4886e65851.camel@haerdin.se \
--to=git@haerdin.se \
--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