MXF interchange specification
This specification applies to MXF file transfer, import, and export on K2 Summit, Solo, and SAN systems.
MXF supports simple clips with a single video track only.
The following are not supported:
- Complex movies
- Multiple video tracks, such as 3D/Video + Key
- Lists of mixed formats or containing empty tracks, such as empty ancillary data or empty audio tracks
- Long GoP
Formats are supported are as follows:
| Supported formats | Notes | ||
|---|---|---|---|
| Video | DVCPRO25 | — | |
| DVCPRO50 | — | ||
| DVCPRO HD | Super Slo-Mo requires software version 7.1. x or higher | ||
| DVCAM | — | ||
| D10 | See MXF export behavior for eVTR style D10AES3. | ||
| MPEG-2 | Includes all MPEG-2 formats (IMX, XDCAM, etc.) that can be stored on a K2 system | ||
| AVC-Intra | — | ||
| Avid DNxHD | Playable on K2 Summit 3G system only. Can transfer to systems with K2 software version 8.x and higher. | ||
| Audio | 48 kHz | — | |
| 16 bit, 24 bit | — | ||
| PCM, Dolby-E, AC-3 | — | ||
| Data | VBI | MXF supports either ancillary data packets or VBI lines in the data track but not both, so if ancillary data packets and VBI lines have been recorded into the K2 clip’s data track, then the VBI lines will be dropped from the MXF data track on an MXF export. | |
| Ancillary | — | ||
Interchange mechanisms are supported as follows:
With a special export option, you can export a completed continuous (loop) record clip as MXF or QuickTime, with the result being a flattened stream file. Recording must be complete before you export the clip, however you can make sub-clips while record is underway and export the sub-clips. For this feature, MPEG-2 long GoP is not supported.