Bjoern Adamski
Forum Replies Created
-
Antony,
“…because the ClipBrowser software I am using (v2.0.0.0) will only convert the MP4s to MXF, and because I believe the format was specifically developed to include all of the meta data captured on the shoot (time/date, etc) or added to the clips in the EX whilst reviewing them in camera before exporting/converting onto the Mac.”
Well, yes and no. The main idea behind MXF is to have a manufacturer independent, full documented, open and SMPTE standardized file container format. MXF is very open and quite generic so for cross plattform and cross system compatibility it really requires to review which sub-standards/variation is supported.
XDCAM EX/XDCAM HD is quite challenging for a direct and fast NLE integration due to the internal MXF file structure. We provide a PDF documentation regarding this: https://mxf4mac.com/images/stories/downloads/principles_of_cbr_and_vbr.pdf
In terms of metadata with Sony XDCAM you’re correct. The XML file from XDCAM gets embedded into the MXF file. However the question is which system parses this metadata and how about editing? Editing metadata in a separate XML file is much easier than within the MXF. A XML can be opened in any text editor, for MXF metadata editing you need a dedicated MXF aware software. Also, since the embedded metadata within the MXF uses a fixed data size the editing capabilities are limited. Having metadata stored externally isn’t a bad thing.
“I guess I was hoping somebody would reply, “No FCP won’t import MXFs” or “Yes FCP will but you have to do x”…?”
FCP by nature does not import native MXF assets, they get re-wrapped to MOV either by using Log and Transfer for P2 or XDCAM Transfer by Sony or other third party applications. Our integrated MXF solutions work perfectly with XDCAM but not yet with XDCAM HD and EX. The file and index structure of XDCAM (I-Frame Only, CBR, IMX, DV) and XDCAM HD and EX (Long-GOP, VBR, MPEG-2) is completely different and the file access is too slow when accessing large amounts of files, large files, or when dealing with video live feeds. The PDF document mentioned above shows the reason.
Accessing the native MP4s from EX however is not really a challenge as MP4 is based on MOV, it uses the same file container structure. For some testings I just changed one header entry in the MP4 files to open them natively in QuickTime without using any 3rd party software, so basically it’s possible. Also the index and essence structure is the same like with MOV so the situation is very different to the XDCAM HD and EX MXF files. Files can be opened and accessed fast. The pure MP4 however does not contain the metadata you ask for and it even does not contain any timecode information. Therefore you need to keep the entire MP4 folder structure to have XML metadata including timecode. Based on many tests I did with huge amounts of footage and large projects I would consider to use the standard workflow with Sony XDCAM Transfer and re-wrap to MOV. Timecode and metadata gets included into the MOV with this workflow. You can review the metadata in FC Server, not in FCP or QuickTime Player.
———————
Product Manager
MXF4mac
https://mxf4mac.com -
HDV is tape.
XDCAM and XDCAM HD are MXF
XDCAM EX on card is MP4, it can be re-wrapped to MXF.
My AE CS4 on the Mac only imports XDCAM EX wrapped in MP4. I don’t get any XDCAM MXF files imported, only Panasonic P2.
———————
Product Manager
MXF4mac
https://mxf4mac.com -
Shane,
basically it’s not FCP that installs Apple’s pro codecs, it’s Compressor. Any installation of Compressor will do it, it’s part of FC Studio, FC Server and Logic Pro.
———————
Product Manager
MXF4mac
https://mxf4mac.com -
Depending the compression format AD provides QuickTime Reference Movie files that point to the native MXF.
———————
Product Manager
MXF4mac
https://mxf4mac.com -
FCP and other FCS applications can be enabled to import native MXF.
What is the format you’re dealing with here, P2?
———————
Product Manager
MXF4mac
https://mxf4mac.com -
There is an issue currently with P2 MXF files created with Premiere, please see here:
https://mxf4mac.com/compatibility
———————
Product Manager
MXF4mac
https://mxf4mac.com -
Hi Jay,
the UMID is equal for P2 video and audio clips that belong together, as well as for spanned clips. Our importer reads the UMID and maps it to QuickTime. A little tool could merge the clips and send them to FCP similar to P2 Flow/P2 Flow CM. We didn’t do this yet by ourselves, it will maybe become a feature within P2 Flow but I am not sure if we can make it for v1.0. However it can be done. You might contact us regarding your issue.
Thanks
Bjoern———————
Product Manager
MXF4mac
https://mxf4mac.com -
We don’t compete. Automatic Duck focuses on project exchange, we focus on MXF media exchange and we cooperate to provide an even better integration in the future.
———————
Product Manager
MXF4mac
https://mxf4mac.com -
You need the Panasonic P2CMS application to get a dedicated P2 component installed. Watch out for the additional codecs it installs, if you have FCP then you should remove the DVCPRO HD codecs from Panasonic as they might conflict with those from FCP. You can review a PDF from us regarding this:
https://mxf4mac.com/images/stories/downloads/p2cms_workflow.pdf
Also you can try our MXF Import QT component, it supports much more MXF then just P2. Also we support timecode for P2 MXFs, something the P2CMS component doesn’t, maybe just have a look here:
https://mxf4mac.com/images/stories/downloads/fcp_fast_p2_workflow.pdf
https://mxf4mac.com/mxfimportBest
Bjoern———————
Product Manager
MXF4mac
https://mxf4mac.com -
It seems to work on PC but maybe not on the Mac CS4?
https://www.dvinfo.net/conf/digital-compositing-effects/145296-after-effects-xdcam-hd-mxf-files.html
———————
Product Manager
MXF4mac
https://mxf4mac.com