On Wed, Apr 24, 2024 at 01:20:02PM +0200, Jerome Martinez wrote:
> Hi, I'm bumping this patch proposal for avoiding a situation where FFmpeg
> skips half the visual content when 2 jpeg2000 codestreams are present in one
> frame. I re-reviewed this discussion and think I answered all concerns. I'm
ons 2024-04-24 klockan 13:20 +0200 skrev Jerome Martinez:
> Hi, I'm bumping this patch proposal for avoiding a situation where
> FFmpeg skips half the visual content when 2 jpeg2000 codestreams are
> present in one frame. I re-reviewed this discussion and think I
> answered
> all concerns. I'm
Hi, I'm bumping this patch proposal for avoiding a situation where
FFmpeg skips half the visual content when 2 jpeg2000 codestreams are
present in one frame. I re-reviewed this discussion and think I answered
all concerns. I'm hesitant with patch v3 because I consider that
touching
ons 2024-02-21 klockan 15:27 +0100 skrev Jerome Martinez:
> On 21/02/2024 14:11, Tomas Härdin wrote:
>
> > mxfdec can detect cases where there will be two separate fields in
> > one
> > KLV,
>
> In practice the issue is not to detect I2 case in mxfdec (it saves us
> only a little during probing
On 21/02/2024 14:11, Tomas Härdin wrote:
mxfdec can detect cases where there will be two separate fields in one
KLV,
In practice the issue is not to detect I2 case in mxfdec (it saves us
only a little during probing of the first frame, but I could add such
signaling in a patch after this
This is still J2K specific rather than handling it properly for all
codecs all at once.
mxfdec can detect cases where there will be two separate fields in one
KLV, and the decoder(s) can if I'm not mistaken be instructed to decode
into an AVFrame with stride and offset set up for interlaced
Attached is an updated version of the patch proposal.
About the idea to keep separate fields in the output AVFrame, I note
from the discussion that it is commonly accepted that up to now it is
expected that the AVPacket contains what is in the MXF element and that
the AVFrame contains a frame
