EVS "MXF" Documentation

EVS "MXF" structure

Unfortunately the EVS MXF files do not follow the specification of MXF files in SMPTE 377M. To begin with, the Operational Pattern has the following unknown value:
06.0e.2b.34.02.05.01.01.0d.01.02.01.01.01.01.00
However, the absence of a SourcePackage makes the file non-compliant and restricts interoperability, which defeats the aim of the MXF standard. At best, the EVS file can be described only as KLV compliant (SMPTE 336M).

When attempting interoperability in practice, the most difficult problem is the invalid EssenceContainer label:
06.0e.2b.34.02.05.01.01.0d.01.03.01.18.01.02.01
This "dark" EssenceContainer contains JPEG and uncompressed audio in an undocumented interleaved fashion. Fields of video are compressed as JPEG images and arranged in "clumps" of 18 fields, followed by uncompressed audio data, followed by the next clump of JPEGs and so on.

All EVS "MXF" files have the following KLV layout, with offsets being constant for the first 5 KLV triplets i.e. up to the Footer.

  K = OpenIncompleteHeader ( 0000000000000000 )
                     1 Invalid EssenceContainer listed
  K = Primer ( 000000000000007d )
  K = [ Dark - clip metadata which uses tags defined in Primer ]
      06 0e 2b 34 04 01 01 01 0d 01 04 01 01 01 02 00
  K = KLVFill ( 000000000000073a )
  K = [ Dark - essence in the form of blobs of 18 JPEG images, one JPEG per field ]
      06 0e 2b 34 02 05 01 01 0d 01 03 01 18 01 02 01
  K = IncompleteFooter ( [varies] )
                     1 Invalid EssenceContainer listed
  K = Primer ( [varies] )
  K = [ Dark - repeat of clip metadata plus 3 true-color RGB thumbnails ]
      06 0e 2b 34 04 01 01 01 0d 01 04 01 01 01 02 00