View Full Version : What's the deal with MXF on Mac's


Andy Solaini
April 25th, 2011, 08:48 AM
I have always used windows based computers but a friend now works in a computer repair shop and says he might be able to sort me out with a good refurb Macbook pro for a very nice price.

I was just wondering what the deal is with editing Canon MXF files in FCP? I have read a few things saying it's not possible without converting. I assume this would take a long time to do and is not something I would relish given at the present moment I can just load them into my NLE and edit away.

Sorry if this is a stupid question but I have very limited knowledge of anything Mac.

Erik Norgaard
April 25th, 2011, 12:32 PM
It just works.

Canon provides an XF Utility for OSX and a plugin for FCP, by default the FCP plugin converts to ProRes, but you can change that and work in native codec. The only "issue" is that meta data you add with the XF utitlity is not available from FCP, but I find I just use FCP with the plugin, I haven't really found a use for the XF utility.

BR, Erik

Doug Jensen
April 26th, 2011, 05:23 AM
I assume this would take a long time to do and is not something I would relish given at the present moment I can just load them into my NLE and edit away.

Just to add to what Erik has already said, "rewrapping" to .MOV won't slow the importing down if you keep the clips native. In other words, the importing will be just as fast as if you were doing just a straight file transfer, so you don't need to be concerned about that issue.

BTW, if you DO choose to convert to ProRes, then it will take longer to import and the file sizes of the clips will be bigger -- but there will be no benefit. You won't gain anything by converting to ProRes, so just import the clips as "native" and you will love the workflow.

Mastering the Canon XF305/300 Camcorders training DVD (http://www.vortexmedia.com/DVD_XF305.html)

Andy Solaini
April 26th, 2011, 07:55 AM
So it doesn't sound like the pain in the rear I was lead to believe it was by some website...

Anyone have a guess at how well something of this spec would run and edit MXF?
Mid-2010 model with 2.4GHz Core i5, 4GB RAM, 320GB HDD.

My friend is offering an immaculate one for Ģ1100/$1800.

Andrew Strugnell
April 26th, 2011, 08:03 AM
Your editing system will edit the 50Mbps MXF codec just fine. I'm using an older version MBP with FCP 7- it plays back and edits with multiple streams smoothly. I would agree that ingesting your MXF footage in its native format with Log & Transfer in FCP to be the most convenient method over XF Utility.

Josh Dahlberg
April 29th, 2011, 01:27 AM
BTW, if you DO choose to convert to ProRes, then it will take longer to import and the file sizes of the clips will be bigger -- but there will be no benefit. You won't gain anything by converting to ProRes, so just import the clips as "native" and you will love the workflow Mastering the Canon XF305/300 Camcorders training DVD (http://www.vortexmedia.com/DVD_XF305.html)

Hi Doug, I'm curious about this statement and would love your input/wisdom.

Conventional thinking is that if you plan to do a fair amount of grading/colour work on the footage, Prores is more robust to work with and will yield better results, even if the orignal capture was using the camera's native format.

Would you disagree with this? I've been converting to Prores 442 on ingest as a matter of course, but perhaps I should reconsider.

Antony Michael Wilson
April 29th, 2011, 03:13 AM
Doug is correct. Ingesting as a transcode to ProRes will yield no image quality benefits; it will just take up more storage space. Further, it is an unnecessary transcode step. It is a legacy feature from before FCP was able to handle a re-wrap ('native' ingest). The only real use for this would be if you needed to ingest XF footage to .mov for another app/workflow/system which cannot cope with MP2/longGop but can handle ProRes. Since all modern Mac workstations can easily handle MP2 editing overhead, there is no need to ingest to ProRes for an edit directly inside FCP, which will stay inside FCP.

However, for best quality, you should most certainly set your sequence render settings to ProRes or uncompressed. This is where you will see the benefit of ProRes over native MP2. All image manipulation you make should definitely NOT be rendered back to MP2 because then you are re-compressing the images back to a highly compressed acquistion codec. With a few layers/levels of manipulation you will be able to see the difference. We always render to uncompressed where drive space and system speed allows but ProRes on FCP or DNx on Avid are a good second choice.

Doug Jensen
April 29th, 2011, 05:44 AM
Thanks Anthony, for answering the question better than I would have said it myself.

Rajiv Attingal
May 5th, 2011, 07:01 AM
To my understanding is things gets confused when you think about archiving your footage.
You will end up with two versions of footage.One is your Native .MXF Files.The other one is
the re wrapped or Pro Res converted .mov files.It is your choice to keep both, of course at extra cost or choose any one of them depending on the future use.

Rajiv

Reinhard Kungel
May 6th, 2011, 04:17 AM
Hi Rajiv,

good question. I was asking this in this forum last year, too. Also Canon couldnīt answer.
Until now I store both, MXF via XF Utility and native-FC-files. This is not really comfortable and you need double-space, but until nobody really can answer this question I do so.

kind regards,

Reinhard

Nigel Barker
May 6th, 2011, 01:25 PM
Why would you want to keep the files that are converted to ProRes as well as the originals? You can always recreate them if necessary.

Reinhard Kungel
May 7th, 2011, 04:08 PM
First of all: I donīt wanna keep pro-res-files beside MXF-Files - we are talking about native-(Canon/XDCam)-Files. Anyway: the reason why is: in FCP you have the possibility to shorten longer MXF-clips when importing via log-and-transfer. Thats what Iīm doing (as a nature-photographer, who is waiting sometimes for hours). The problem is, that native-FCP-Files and MXF-files are no more identically.

br

Reinhard

Erik Norgaard
May 8th, 2011, 09:54 PM
First of all: I donīt wanna keep pro-res-files beside MXF-Files - we are talking about native-(Canon/XDCam)-Files. Anyway: the reason why is: in FCP you have the possibility to shorten longer MXF-clips when importing via log-and-transfer. Thats what Iīm doing (as a nature-photographer, who is waiting sometimes for hours). The problem is, that native-FCP-Files and MXF-files are no more identically.


That doesn't make much sense to me:

Either you decide that you only need certain clips, the rest is trash, there is no chance that you will ever need it - ever. Or you decide as a precaution or for B-roll whatever, to log and transfer everything.

I'd review that workflow.

BR, Erik

Rajiv Attingal
May 9th, 2011, 04:07 AM
Will the converted .mov or the ProRes keep the original Time code and other Metadata informations?.
If not how you will you re connect your timeline from re converted media?
There are circumstances that you have to keep different versions of your editing. It is where media manager comes into play.You can't trim your timeline to .mxf using media manager.
Will FCP X change this scenario?
Is .mxf supported in FCP X?.

Rajiv

Reinhard Kungel
May 11th, 2011, 01:48 PM
To me, the question is: which datas can I use also in 20 years: original MXF or natively in FCP imported files? As soon as I donīt know I keep both.

Andy Solaini
May 11th, 2011, 05:56 PM
Some good advice in this thread already, thanks for the replies.

I got my Mac the other day but haven't set it up yet. Can someone point me in the right direction for some good tutorials (video or text) on FCP? I am a complete novice in FCP and Macs but have some knowledge of Vegas and Prem Pro.

Philip Lipetz
May 11th, 2011, 06:20 PM
If you do not have FCP yet wait a few weeks and get the new FCP X in June for $299.

Andy Solaini
May 11th, 2011, 06:53 PM
I am wondering how well it will run on my Mac because it's a 2010 Core2Duo one not a new i5/i7. My brother runs the current FCP pretty well on his Mac which is three years old so mine might be ok with FCP X.

Philip Lipetz
May 12th, 2011, 06:19 AM
No one know for sure what the system requirements of FCPX are, but it does use the graphics card for acceleration and early hints are that it will be significantly faster than FCP 7, and will process in the background as you work much more efficently than the current FCP.

Steve Maller
May 14th, 2011, 01:05 PM
BTW, if you DO choose to convert to ProRes, then it will take longer to import and the file sizes of the clips will be bigger -- but there will be no benefit. You won't gain anything by converting to ProRes, so just import the clips as "native" and you will love the workflow.

What I'm seeing with FCP7 is that I can definitely work in the native codec with the nominal re-wrap that Log and Transfer does, but the video on the timeline shows with the green bars, indicating that it's only semi-rendered. It seems to go fast enough, but when I told Log and Transfer to transcode to ProRes, there were no green bars, meaning that FCP7 was working (more) optimally.

Doug Jensen
May 14th, 2011, 03:19 PM
It really depends on your sequence settings, doesn't it? I usually don't have to render when I'm editing an HD timeline because I try to use sequence settings that match my raw footage whenever possible. It sounds like you are using sequence settings that are different than your XDCAM raw footage (Canon files are actually XDCAM), thus FCP needs to do some quick rendering. In either case, I prefer to leave my raw footage in the native codec because the files sizes are a lot smaller and the ingest is faster.

Sam Young
May 14th, 2011, 08:44 PM
What I'm seeing with FCP7 is that I can definitely work in the native codec with the nominal re-wrap that Log and Transfer does, but the video on the timeline shows with the green bars, indicating that it's only semi-rendered. It seems to go fast enough, but when I told Log and Transfer to transcode to ProRes, there were no green bars, meaning that FCP7 was working (more) optimally.

I do not have the green render lines on my footage after log and transfer with the XF plugin, it is gray and ready to go. Maybe your sequence settings need to be changed?

Steve Maller
May 15th, 2011, 12:13 AM
I do not have the green render lines on my footage after log and transfer with the XF plugin, it is gray and ready to go. Maybe your sequence settings need to be changed?

Gaaack. My bad. I had a color corrector filter dropped on the clip.
Apropos, it's interesting that FCP thinks the right compressor for my Sequence is XDCAM 422 24P 50mbps. Is that the same as MXF?

Sam Young
May 15th, 2011, 08:18 AM
My MXF clips also say XDCAM HD422 720p50 at 50Mb/s.

Reinhard Kungel
May 20th, 2011, 06:44 AM
It is where media manager comes into play.You can't trim your timeline to .mxf using media manager.
Will FCP X change this scenario?
Is .mxf supported in FCP X?.

Rajiv


In FCS I and II media manager was working well: I could shorten clips from different sources (DV, analog, Digibeta, etc.). With FCS III media manager doesnīt work well in my setup and it is not possible to shorten DV, HDV, XDCAm-Clips. Has anybody made better experiences?

Reinhard

Doug Jensen
May 20th, 2011, 07:09 AM
Yes, Media Manager on Final Cut Pro 7 does shorten XDCAM clips and Canon clips on my computer.