Gear Tags

New FCPX findings after 6 days Peakbreak

After 6 days roadtrip-production we have not as much to report as 2011 when FCPX was new to us.

This year the ingesting, keywording and editing works mostly fine. I am now at almost 3000 clips and while last year my old Macbook (2008) with 4GB started bitching around with 1500 clips in FCPX 10.0.0 I have no problems at all now with FCPX 10.0.5 and the Macbook from 2011 with 16GB RAM.

We got a request to send a few minutes of news rushes of a stage and a few pictures for the stages before.

So after shooting another 450 clips during stage 2 we got back to the hotel, started our ingest plus backup plus basic key wording (day, camera, operator)…..then put some rushes into a timeline (already had some prepared last night) and also adding some interviews.

The problem: I was so fast done with these rushes I am now waiting for FCPX to complete the ingest. As long as clips are not finished ingesting you cannot export the timeline. 

That´s how fast it is. Of course it is only partially good news, because basically the delay during ingest comes from the fact that FCPX stops ingesting in the background while I edit. We were having a discussion if it would be faster to use XDCam Transfer and then import the re-wrapped files at least for some cards. But to me in the long term of the project it makes more sense to stick to the FCPX-only workflow instead of having to keep track which cards got imported how. The question is, if FCPX will ever be able to ingest while I am editing.


After day 4 we had 3 clips that were imported from a camera-archive that showed up as missing media, while the rest of the card was online. To my surprise there is now a "tapeless-batch-capture" feature in FCPX called "re-link Event files from camera /archive" and it is in the File>Import menu 

Now that is a nice addition to the feature set.

We basically have only one issue in our roadtrip-workflow: Since we are two editors it would be nice to share the event on one mobile drive. You can set it up via LAN and SAN and whatnot, but not in a mobile setting. If I have an event I can then also share it and share the projects that I generate in the event. The problem here is that the Event is growing every day. So if I share after 3 do I sync that event with the other one which has only 2 days in it?

Our solution now was to create a new event with the same native media on the second machine; e.g. Stefan makes an event with all "Day 3 footage" and edits a project with that. I can simply copy the project and then RELINK it to my Event, although it has nothing to do with Stefan´s event FCPX relaizes it is the same media behind it. It works amazingly well. But we would prefer to work in the same event on the same thunderbolt drive and edit in it simultanously. That would lift FCPX to another level for these kinds of gigs.

PrintView Printer Friendly Version

EmailEmail Article to Friend

Reader Comments

There are no comments for this journal entry. To create a new comment, use the form below.

PostPost a New Comment

Enter your information below to add a new comment.

My response is on my own website »
Author Email (optional):
Author URL (optional):
Some HTML allowed: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <code> <em> <i> <strike> <strong>
« Wrapping up Peakbreak and getting the C300 wet | Main | The Peakbreak 2012 FCPX initial setup »