-
Good FCPX news for Canon XF100/C300 owners- import plugin released
Canon just released their plugin to enable direct import in FCP X from these cameras: EOS C300 / EOS C300 PL / XF305 / XF300 / XF105 / XF100. Be sure to select OS 10.7 in the popup when you visit this link: https://usa.canon.com/cusa/professional/products/professional_cameras/cinema_eos_cameras/eos_c300#DriversAndSoftware
Noah
Call Box Training.
Featuring the Panasonic GH2 and Panasonic AC160/130. -
10 Replies
-
Wow. Have you tried it?
Jeremy
-
Thanks’ for that Noah,
Been waiting a while for this. Lets hope it works smoothly and allows us to continue importing the files as native.
-
Well I’ve tried it out and . . . .
It’s really buggy, crashes the program, slow . . .
There is no facility for renaming clips prior to ingest . . .
No ability to choose the kind of file you want native, 422L, 422, etc etc
It just brings it in as a 422 file.
So, very disappointed and will continue to use the FCP log and transfer to bring the files onto the computer.
Be interested to see what other people think.
-
I’ve just installed it as well, but actually it won’t let me create optimized media at all. That option is greyed out, probably because it is a MPEG2 codec and FCP X thinks it doesn’t need optimized media for that, same as with HDV footage. Which is fine in most cases, but I would like to have the choice. Anyway that is a FCP X problem, the plugin works fine so far.
-
[Arthur Dobbe] “Anyway that is a FCP X problem, the plugin works fine so far.”
It is not a FCPX “problem” but a feature. FCPX will decide if it needs to transcode or not. If your machine is fast enough and/or the codec is good enough then FCPX will use the native format. Since the XF 422 codec (which FCPX uses) is exactly what you want anyway.
If you absolutely want to make ProResHQ (question is why, because every transcode hurts the material), then you need to export and re-import.
-
[alban egger] “If you absolutely want to make ProResHQ (question is why, because every transcode hurts the material), then you need to export and re-import.”
Or use XfcpX: https://pika.dk/?p=472
Jeremy
-
[Jeremy Garchow] “Or use XfcpX”
huh? but XfcpX only rewraps the codec, it doesn´t transcode, so it basically does the same than the plugin: make FCPX understand the wrapper.
Transcoding any material into HQ won´t make the material better as long as there are no effects involved. And for that FCPX gives the option to work in HQ as render format. But it doesn´t make sense to transcode the original footage just for the sake of transcoding.
-
[alban egger] “huh? but XfcpX only rewraps the codec”
My bad. Thought it transcoded.
I’ll shut up now.
-
[alban egger] ”
If you absolutely want to make ProResHQ (question is why, because every transcode hurts the material), then you need to export and re-import.”For example because I want to grade in Resolve and the footage is in a codec that Resolve can’t handle natively.
(Since last beta Resolve handles also Canon XF300 / C300 codec, but this was a problem until last week)
-
Currently trying to get a FCPX project into Resolve and the only section not behaving is C300 material that I can’t optimize. And optimizing would solve the problem (because it would stick a reel number in the media file). Thanks FCPX!
One workaround to this is to make your c300 footage a multiclip, because you can force FCPX to optimize all mulitclips.
Reply to this Discussion! Login or Sign Up