[FFmpeg-user] Storing scan-type/interlaced in MXF?

[Paul B Mahol]

On 10/31/18, Peter B. <pb at das-werkstatt.com> wrote:
> Hi Carl,
>
> On 31/10/18 13:28, Carl Eugen Hoyos wrote:
>> From a quick look, interlaced mxf is only supported for selected
>> codecs (that support interlaced encoding), not for j2k
>
> Thanks for the quick-look-reply!
> Interesting/good to know. Is this an MXF-specification thing or an
> (ffmpeg) implementation thing?
>
> Hm...
> Might this be the reason why some institutions store J2K-lossless in MXF
> as "field-as-frame" with double framerate?
>

Yes, and that is questionable practice.

>
>> Are you maybe expecting an output file with field encoding? This is
>> generally not supported in FFmpeg, neither for reading nor for writing.
>
> What do you mean by "field encoding"?
>
> The scenario here is as follows:
> Source is uncompressed, interlaced NTSC and shall be stored as
> J2K-lossless in MXF.
> Therefore the intention of having the resulting MXF containing all the
> right metadata to be aware of scan-type and field-order.

MXF muxing support on FFmpeg side lacks such bits.