Support for Canon MXF from xf100 in FCP X?

What do you do with the MPEG-2 file in FCP? Is it QuickTime in XDCAM or something else?

FCP will recocknize the MPEG2 just fine after XfcpX rewraps it in the .mov container. So you simply just import the mov files directly into FCP.

PikaFoto wrote:

XF utility and other imports are assembling these to one big clip for you on import - so will XfcpX in the near future.

That's good news! Was actually waiting for a plugin from Canon, but I bet you'll be faster.

Thank you.

The newest version of FCP X came out today. Are we good yet for support for Canon XF100 cameras? Was a new plugin included?

I installed the new version this morning. Seems to be no change in XF100 support. Same errors.

You won't see XF100 support natively in FCPX... same deal as in FCP7. Canon has to supply a plug-in "ingester" the same way they did with FCP7. Given that Magic Bullet just released Looks for FCPX (which I'm downloading now) I would assume that the FCPX SDK now has the API's to support the ingester.

Finger's crossed, but heck.. Pikafoto's utility has made this whole issue moot for me anyway.

I'd assume the APIs have been out quite while. It is rather Canon being slow as molasses as usual.

Nope. Sony totally blew it on publishing a usable SDK. FCPX 10.0.3 is the first version that is capable of supporting effects plugins, and _hopefully_ it can support ingest plugins as well. I don't have a copy of the SDK but heck... it's been 6 months so...

That said, thanks to XFcpX we're all functional here. It's been a lifesaver for me.

Are you sure? Noise Factory effects have been working from day one.

Hey, talk to the folks at Red Giant about it. They were able to squeek Mojo out the door, but there were so many broken pieces of the API that anything remotely complex was impossible. I'm just assuming that the ingest API components were just as broken as the rest of it, but hey... without the SDK it's impossible to make any educated statements. These are just guesses.

I just did a little googling and found that Noise Factory's effects are not implemented as plugins in FCPX... they are simply Motion templates. (Motion does have a relatively robust API.) Here's a little snippet about it I pulled off of Larry Jordan's blog:

(BTW, in a post from earlier today I mentioned "Sony" blowing it when I meant "Apple" of course.)

Recently, I installed the FX Factory Pro update. Upon doing so, “all” Noise Industry plugins are showing up in final cut pro x…by all, I mean ones that I don’t own and therefore can’t use, so I find it cumbersome. Is there a way to turn those off?

So, I contacted the folks at FX Factory and here is their reply:

“At the moment there is no way to hide our effects from Final Cut Pro X. Contrary to all other hosts, Final Cut Pro X does not support plug-ins “natively”, so the only way to remove an effect is to delete the Motion Template on disc.

Until we can improve FxFactory to do this for you, the only option is to navigate to the following directory on disc:

/Library/Application Support/Final Cut Pro/Effects

And manually locate and remove any effects you do not need.”

Thnaks for the clarification.

This is thje answer I just got from canon:

Op 30 jan. 2012, om 19:59 heeft Canon Support het volgende geschreven:

Dear R.Bruce:

We appreciate your continued correspondence regarding XF100.

Regrettably, you would need to use Final Cut 7 or 6 which we have a plug in for to import to, from there you can import it into Final Cut X. This is the only work around that we can offer on this issue. We do apologize for any inconvenience this may cause.

Please let us know if we can be of any further assistance with your XF100.

Thank you for choosing Canon.

Sincerely,

Nathan
Technical Support Representative

No hope boys... it does interest them nothing if you are planning to buy a canon cam or not.

by now it's quite apparent that we're all foolish to hold our collective breath waiting for a plugin from Canon.

and, if a common pedestrian user like Pika (no disresptect intended) can create an appropriate transcode utility from scratch, then Canon deserves all the critism we can muster...

"...we're on the luxury liner SS Canon, but it appears the captain is allowing us to crash upon the rocks!"

in this case, public opinion would have Canon confined to house-arrest (at least), and Pika makes the triumphant parade upon the shoulders of XF100 and 105 users.

I say to the victor go the spoils.

It was just a short letter to Canon from me and i got this answer within 3 days. I advised them in a reply on this disappointing policy my mail to send to that stupid marketing- en management department who ignore there clients that pay there second limo, 3e home and private airplane.

If we all do the same me be it will help??

So, mail all of you to CareCenter@cits.canon.com

bruce