Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Pierre-Anthony Lemieux <pal@sandflow.com>
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, 12 Jul 2024 12:51:30 -0700
Message-ID: <CAF_7JxCzwQw77Dw_oS1Pu5oxktmM=q35Jj17XiNtO=P5P_MwHQ@mail.gmail.com> (raw)
In-Reply-To: <48919b7f5cd52dbcdbe0a18469c9d2202eee5bfd.camel@haerdin.se>

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.

This condition may impact downstream decoders and might signal
something deeply wrong with the codestream.

In any case, maybe the case ought to be clarified to something along
the lines of: "Non-conformant codestream: a COD marker is present in a
tile-part header even though the codestream is marked as HOMOGENEOUS."

> Should we perhaps error out?
>
> /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".

  reply	other threads:[~2024-07-12 19:51 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 [this message]
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
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='CAF_7JxCzwQw77Dw_oS1Pu5oxktmM=q35Jj17XiNtO=P5P_MwHQ@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