Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: "Tomas Härdin" <git@haerdin.se>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] [MXF] - Set aspect ratio for jpeg2000 images
Date: Tue, 30 Jan 2024 11:36:48 +0100
Message-ID: <cb6b4a164ffb734b5df2aca7a76e55db4bc6723b.camel@haerdin.se> (raw)
In-Reply-To: <83b8f2bdddae30daac8f3a067ebb1874ab7a7293.camel@haerdin.se>

tis 2024-01-30 klockan 10:47 +0100 skrev Tomas Härdin:
> fre 2024-01-26 klockan 10:12 -0800 skrev Pierre-Anthony Lemieux:
> > On Fri, Jan 26, 2024 at 10:02 AM Cédric Le Barz
> > <clebarz@ektacom.com>
> > wrote:
> > > 
> > > Set aspect ratio for jpeg2000 images.
> > 
> > "The image area on the reference grid is defined by its upper left
> > hand reference grid point at location (XOsiz, YOsiz), and its lower
> > right hand reference grid point at location (Xsiz – 1, Ysiz – 1)"
> > (15444-1, 8.2)
> > 
> > AFAIK setting the MXF aspect ratio item to the ratio of the image
> > pixel dimensions only works if (a) the pixel aspect ratio is 1 and
> > (b)
> > the video is not interlaced -- see 6.2.1.2 and Annex H at
> > https://pub.smpte.org/doc/st2067-21/20221124-pub/.
> 
> You also need to know the display rectangle. If for example VBI lines
> are present then these might also need be cropped, in addition to the
> cropping done at the J2K level. Sometimes container and essence
> disagree on what SAR is, which affects the DAR. Which value is the
> correct one typically depends on business logic
> 
> A demuxer is the wrong place to put logic like this

Wups, missed that this is a muxer patch, not a demuxer one.

Anyway, this patch is very wrong. DAR is a container level thing. We
shouldn't take it from the essence unless there is overwhelming reason
to do so. My point about VBI still stands, in modified form: if VBI
lines are present then this patch would write a bogus DAR

Much of the logic currently in mxfenc.c should probably live somewhere
higher up since MOV also supports some of these things

/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".

      reply	other threads:[~2024-01-30 10:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-26 18:02 Cédric Le Barz
2024-01-26 18:12 ` Pierre-Anthony Lemieux
2024-01-30  9:47   ` Tomas Härdin
2024-01-30 10:36     ` Tomas Härdin [this message]

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=cb6b4a164ffb734b5df2aca7a76e55db4bc6723b.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