From: "Tomas Härdin" <git@haerdin.se>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] avcodec/jpeg2000dec: support of 2 fields in 1 AVPacket
Date: Mon, 19 Feb 2024 12:07:57 +0100
Message-ID: <804a6d5bfa374f4019de4a3d4dce8a0af0613961.camel@haerdin.se> (raw)
In-Reply-To: <e8b5e4046a13cd53ecc3d27a62f4b592d21246d5.camel@haerdin.se>
mån 2024-02-19 klockan 12:05 +0100 skrev Tomas Härdin:
> mån 2024-02-19 klockan 00:43 +0100 skrev Marton Balint:
> >
> >
> > On Fri, 16 Feb 2024, Anton Khirnov wrote:
> >
> > > Quoting Tomas Härdin (2024-02-03 20:58:20)
> > > > I think people with knowledge how interlacing is handled in
> > > > other
> > > > formats and codecs might want to chime in.
> > >
> > > For MPEG codecs our decoders always output (properly signalled)
> > > interlaced content as two interleaved fields in a single AVFrame
> > > flagged
> > > with AV_FRAME_FLAG_INTERLACED. Its height is the height of the
> > > whole
> > > frame, so double the number of lines in each field.
> > >
> > > So IIUC this patch is taking the correct approach.
> >
> > I believe interlaced HEVC has the same issue, the decoder generates
> > field
> > pictures and not frames. Would changing the HEVC decoder be
> > acceptable to
> > generate frames with interleaved fields?
>
> This isn't a J2K thing, but an MXF thing. The same issue will arise
> for
> MJPEG and raw video in MXF using SEPARATE_FIELDS.
To make things worse, encoding SEPARATE_FIELDS using progressive
H.263/4/5/6 in MXF is almost certainly legal. Lawful evil.
/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-02-19 11:08 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-02 15:55 Jerome Martinez
2024-02-03 10:00 ` Tomas Härdin
2024-02-03 10:51 ` Jerome Martinez
2024-02-03 19:58 ` Tomas Härdin
2024-02-03 20:04 ` Tomas Härdin
2024-02-04 0:20 ` Pierre-Anthony Lemieux
2024-02-05 0:19 ` Tomas Härdin
2024-02-15 15:02 ` Jerome Martinez
2024-02-16 0:02 ` Vittorio Giovara
2024-02-16 2:17 ` Kieran Kunhya
2024-02-18 23:14 ` Tomas Härdin
2024-02-19 11:08 ` Tomas Härdin
2024-02-19 11:19 ` Jerome Martinez
2024-02-16 10:32 ` Anton Khirnov
2024-02-18 23:43 ` Marton Balint
2024-02-19 8:22 ` Hendrik Leppkes
2024-02-19 16:14 ` Devin Heitmueller
2024-02-19 11:05 ` Tomas Härdin
2024-02-19 11:07 ` Tomas Härdin [this message]
2024-02-05 2:25 ` James Almer
2024-02-05 14:28 ` Tomas Härdin
2024-02-20 15:07 ` [FFmpeg-devel] [PATCH v2] " Jerome Martinez
2024-02-21 13:11 ` Tomas Härdin
2024-02-21 14:27 ` Jerome Martinez
2024-02-24 12:26 ` Tomas Härdin
2024-02-25 4:14 ` [FFmpeg-devel] [PATCH v3] " Jerome Martinez
2024-03-01 22:29 ` Tomas Härdin
2024-03-03 17:07 ` Jerome Martinez
2024-04-24 11:20 ` [FFmpeg-devel] [PATCH v2] " Jerome Martinez
2024-04-24 22:54 ` Tomas Härdin
2024-04-25 0:59 ` Michael Niedermayer
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=804a6d5bfa374f4019de4a3d4dce8a0af0613961.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