Talk:Material Exchange Format
From Wikipedia, the free encyclopedia
[edit] Conversion
I am very concerned about the text suggesting that MXF can be "converted into AVI". Many MXF files do not contain video (or even any linear media at all). Even then there are effectively as many video compression codecs in MXF files as there devices which create MXF files and no software can support arbitrary codecs. These are two good reasons why this line is NG, and I've nixed it. —Preceding unsigned comment added by 82.152.178.6 (talk) 15:54, 4 December 2007 (UTC)
[edit] Avid / Sony incompatibility
This is just something that bugs me, but Avid's implementation of MXF cannot be read in Sony Vegas.
[edit] MXF issues
It may be enlightening to add information on why there are several different flavours of MXF. If anyone has a copy of the SMPTE journal, the information should be there... i.e. I recall skimming over an article about MPEG2 essence in MXF. AFAIK, there are issues such as:
A- Audio interleaving.
B- MPEG2 indexing for fast random access. Important for real-time editing of HDV and XDCAM material (the XDCAM type that uses MPEG2 compression).
C- Performance issues. (My knowledge is vague here.)
D- Other reasons why there needs to be several flavours of MXF.
Glennchan 06:44, 7 October 2006 (UTC)
I'd say: MXF is a wide standard for the wrapping of a range of essence types with a range of metadata schemes for a range of use cases. This is why there are so many "flavors."
Gwsyzygy 17:28, 11 May 2007 (UTC)
I believe the references to "naming convention which relies on randomly generated filenames" are UMIDs, which are not ramdomly generated but are specially crafted filenames intended to be universally unique (UUID).

