The customers want to concentrate on their own workflow, and leave the complexity of the MXF to the MXF software. So what the is requirement for the MXF software?
First, an MXF SDK is the infrastructure. It knows every thing in an MXF file.
Next, an MXF De-multiplexer (filter) which can parse an exising MXF file, generate a data structure in the memory which contains all the information of the MXF file, including structural metadata/descriptive metadata/dark metadata, index talbes, all the partitions, except the media essence. But it has the knowledge of what type of the essence the file has, where to get the essence for a given frame.
Then, an MXF Multiplexer (filter) which take the input essence, and generate the MXF file.
The De-multiplexer is easier compare to the Multiplexer, many companies in the market has the similar products. The only problem is that they don't support all the features that the customers need for their work flow. For example, the MainConcept has a De-multiplexer works beautifully with DV and MPEG2, but it doesn't support ANC/VBI track, AVC-Intra, and system item. So it only can be a good tool for demo purpose.
The Multiplexer is the hard part, not too many available products on the market today. It needs a thoroughly understanding on MXF to generate valid MXF files.
If your workflow involves MXF, please put the requirement of your workflow here so that people can share the information.
-- usouthal@hotmail.com