Listed below are the currently supported MXF files, many other types of OP1a MXF Files using
AVC-Intra, DV100/DV50/DV25, XDCAM, IMX, DNxHD video compressions should work as well.
If you have a MXF File that is not supported, please contact info@calibratedsoftware.com to see if it can be added.
For further information, workflows or requirements, please see the Calibrated{Q} MXF Import User Guide (PDF)

Panasonic P2 MXF File Formats
AVC-Intra
DVCProHD
DV50
DV25

Panasonic P2 Specific Notes
1.) When opening/importing Video MXF files, the corresponding Audio MXF files will be ‘auto-joined’ when in the proper P2 Folder structure
2.) P2 PullDown Removal and TimeCode conversion for regular PullDown 1080i29.97 and 480i29.97 material is not supported.
3.) P2 PullDown can only be detected and removed thru parsing the P2 XML file data. If the P2 XML for a MXF clip is not present then pulldown cannot be detected or removed.
4.) Auto-assembling of spanned MXF files is not supported. This means that if a shot is ‘spanned’ over multiple MXF files the MXF files will still only be opened or imported as individual MXF files.
5.) AVC-Intra is only supported in Final Cut Pro 7 and is NOT supported in Final Cut Pro 6.
6.) In Final Cut Pro, to import more metadata than just TimeCode/ReelName, please see the Calibrated{Q} Import Assist User Guide (PDF)

Sony XDCAM MXF File Formats
XDCAM HD (35Mb and 25Mb)
XDCAM HD 422 (50Mb)
XDCAM EX (converted to MXF from MP4  via Sony Clip Browser)
IMX
DV25

Sony XDCAM Specific Notes
1.) To work with XDCAM MXF files efficiently in FCP and other applications, Auto-Referencing should be enabled. Please see Chapter: Auto-Referencing for further details.
2.) Auto-assembling of spanned MXF files is not supported. This means that if a shot is ‘spanned’ over multiple MXF files the MXF files will still only be opened or imported as individual MXF files.
3.) XDCAM HD 422 (50Mb) ‘Slow-Mo’ 1920x540 are only supported in Final Cut Pro 7
4.) In Final Cut Pro, to import more metadata than just TimeCode/ReelName, please see the Calibrated{Q} Import Assist User Guide (PDF)
5.) IMX ‘AES3’ Audio requires rendering when imported into a Final Cut Pro sequence and will play back choppy in the FCP 'Viewer' window, and IMX AES3 audio will not play in QT Player X on Lion.
6.) XDCAM Proxy audio will show as needing to be rendered in a FCP Sequence; however when rendering the audio ? FCP will report a 'General Error'.

Ikegami GFCAM MXF File Formats
I-Frame MPEG2 100Mb 1080/720
Long-GOP MPEG2 50Mb 1080/720
I-Frame MPEG2 50/40/30Mb SD

Ikegami GFCAM Specific Notes
1.) To work with GFCAM HD MXF files efficiently in FCP and other applications, Auto-Referencing should be enabled. Please see Chapter: Auto-Referencing for further details.
2.) Auto-assembling of spanned MXF files is not supported. This means that if a shot is ‘spanned’ over multiple MXF files the MXF files will still only be opened or imported as individual MXF files.
3.) In Final Cut Pro, to import more metadata than just TimeCode/ReelName, please see the Calibrated{Q} Import Assist User Guide (PDF) . The Default ReelName of GFCAM MXF files is the 'Bin Title'.
4.) IMX ‘AES3’ Audio requires rendering when imported into a Final Cut Pro sequence and will play back choppy in the FCP 'Viewer' window, and IMX AES3 audio will not play in QT Player X on Lion.

Avid Media Composer MXF File Formats
DNxHD
AVC-Intra
DVCProHD
DV50
DV25
IMX
1-1
1-1-10b
Meridien

Avid Media Composer MXF Specific Notes
1.) The separate Video and Audio MXF Files from Avid Media Composer will NOT be auto-joined, and will open as separate files.
2.) Avid QuickTime Codecs required for DNxHD, 1-1-10b, and Meridien MXF Files.
3.) In Final Cut Pro, the only metadata from MXF files that is currently imported into FCP is TimeCode and ReelName.
4.) IMX ‘AES3’ Audio requires rendering when imported into a Final Cut Pro sequence and will play back choppy in the FCP 'Viewer' window, and IMX AES3 audio will not play in QT Player X on Lion.
5.) AVC-Intra is only supported in Final Cut Pro 7 and is NOT supported in Final Cut Pro 6.
6.) DNxHD MXF files captured by ARRI Alexa, BlackMagic HyperDeck or other hardware devices only have BETA support.
7.) If a DNxHD MXF file was captured or created without a TimeCode Track then a 'fake' when this happens TimeCode is set to 00:00:00:00 (always NDF if 29.97fps or 59.94fps) at the video rate embedded in the MXF file. This was done so that (a) the MXF files would have a UUID ReelName and (b) Audio only MXF files could be identified with the proper video framerate. Please note that Audio only MXF files without any associated video framerate cannot have a TimeCode Track associated with them.
8.) IMPORTANT: Please read the 'DNxHD Options' section in this User Guide for setting up either RGB SMPTE (16-235) or RGB Full (0-255) Color Ranges for DNxHD MXF files