MXF to FCPX not working? A possible fix

Ingesting C300 rushes using the Canon FCPX plug-in
Ingesting-C300-rushes-using-the-Canon-FCPX-plug-in
Canon provide a free plug-in to enable the C300’s MXF files to import directly into FCPX without the need to transcode to ProRes. Many users report that they have no problems with the installation and it ‘just works’. However, other users with similar setups report that they cannot import C300 rushes in FCPX, though it works through Log and Capture in FCP7, additionally Adobe Premiere successfully imports C300 MXF. Only FCPX seems affected, and for a limted subset of FCPX users.

C300 rushes don’t work
C300-rushes-don-t-work

Here’s the typical scenario: having run the xpfm211 installer. FCPX sees the folder structure, even the MXF files themselves, but does not recognise either. This is as far as some users get. For some reason, the installer has completed successfully, we are seeing files, but nothing imports. De-installing and re-installing brings the user back to this situation. Very frustrating.

After installing
After-installingTrying to track the activity of the installer, we see two new plug-ins highlighted in the MIO/RAD/Plugins folder – CanonE1.RADPlug and CanonXF.RADPlug. The latter would appear to be the ‘magic smoke’ for the MXF format. However, this isn’t working. There’s a second empty RADPlugins folder below – should the plugins be in there?
Moving the plugins
Moving-the-pluginsWhilst it may seem a bit ‘cargo cult’ to shift the contents from a RAD/Plugins heirachy to a RADPlugins, it was worth a shot. No, it didn’t work.
Comparing folders with a working configuration
Comparing-folders-with-a-working-configurationHere’s where it got interesting. I was able to confer with another editor who had a system that did import MXF successfully. The key difference was that he had a CanonXF64.RADPlug folder – not an XF, an XF64. I could not find a similar folder, nor could I make the installer create one. In the end, he just sent me a copy of that folder, and I dragged and dropped it into the same folder I had.
C300 rushes now appear normally
C300-rushes-now-appear-normallyAnd it worked! It’s pretty obvious because you can see the clips, but also note that the MXF folder heirachy has gone, replaced simply with the usual list of clips on a card or archive.
The Secret Sauce of C300 Import
The-Secret-Sauce-of-C300-ImportSo this folder appears to be the missing link. Depending on your system, the installer either creates this folder, or it doesn’t. Both of us had the XDCAMFormat.RADPlugin, removing both did not make my installer create this file, the only way was to use somebody elses copy. It would be useful to provide this folder as a download to those who need it, but license agreements seem to forbid this sort of activity – probably for good reason.
It comes down to an issue with the installer, which isn’t written by Canon staff, and so it’s difficult to work out who to alert to the situation. However, as seen here, access to the CanonXF64.RADplug folder cures the problem for now.

Advertisements

2 thoughts on “MXF to FCPX not working? A possible fix

  1. Hi Matt

    I have exactly this issue…something weird happening with my C300 footage. I’m running FCPX 10.3.1 on OSX 10.9.5 and suddenly my C300 footage shot at 24p drops off the viewer and timeline viewer screens. I can see it in the browser screen to the left, but that’s all. Seems to work for 10-20 minutes on restart, but then drops out again. I’ve never had this problem before and I’ve been accessing the C300 footage successfully through XF utility since the start of the year. This is the first time I’ve shot at 24p, though it seems unlikely that’s connected. It would be amazing if your little link towards the end of the email were working again so that I could add those vital little folders, I seem to have a couple missing…

    Thanks in advance for any advice and help,

    Stu

  2. Pingback: Dreaded Red Screen while playing an imported vi… » Timeclub

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s