FCPX v10.4.9 Updated Proxy Workflow

I watched the Ripple Training rundown of the new features in the FCPX v10.4.9 update and am stoked on the update to the proxy workflow- namely being able to move a "proxy only" version of a Library (and it's corresponding un-proxy-able media) over to a travel drive/laptop to take on the road.

They only demo'd how to reintegrate an updated project back into the original Library though, not a changed event with maybe new ranges applied to existing footage, new keywords or even new assets added to the event in the travel library.

Does anybody know how this workflow would work? Do you drag the updated events from the travel Library onto the corresponding events in the original Library? Would that replace the old versions of clips? Double them? Would I just drag the updated events into the original Library and delete the old versions? Would that cause any problems then trying to view the original (non-proxy) versions of the media in the updated events considering they've never themselves been connected to the original media?

Thanks

-Morgan

You give the proxy event and project a distinct name. When you bring the proxy library back you copy the event and project into the main library. That will keep the old version and the new edit. You can go from here. ct b

What I still haven't worked out how to do is send the edit the proxy files recorded in camera (say FX9) and then when they get hold of the original material add that in.

What would actually be more useful is to send the client the proxies out of the camera. They do the edit and then send you an EDL to upload just the clips they need.

Would be majorly helpful in news and fast turnaround docs.

Currently the FX9 doesn't work with FCP, so we can't test it. It may be possible to work if the FX9 proxies follow the requirements the application. The proxies have to be exactly the same length, the same frame rate, and have the same audio channel configuration.

I know! I'm an FX9 owner and have been shouting about it since I first discovered it on Tuesday.

It looks like its some kind of metadata issue. FS7 clips load fine and they are the same codec XAVC-I as the FX9.

I tried loading some material from a card I shot yesterday and FCPX didn't read it. But taking the clips into Sony's Catalyst Browse and re-exporting them as XAVC seems to work. Apparently this rebuilds the metadata.

Thanks for the quick reply, Tom.

Tom Wolsky wrote: You give the proxy event and project a distinct name. When you bring the proxy library back you copy the event and project into the main library. That will keep the old version and the new edit. You can go from here. ct b

So in the workflow you describe, it sounds like I'll end up with basically two versions of the same event- the older/original and the updated/proxy version. Can I delete the older or do I now have to keep both around? If I delete the older will I have any problems with the updated version of the event relinking to the original media? How does the proxy version know to relink to the original proxies on my desktop work drive instead of the proxies on my travel drive (which won't always be attached to my desktop computer)?

Sorry, I'm still trying to wrap my head around this.

For this to work you need to always work with external media rather than managed media inside the library bundle. Assuming that you can relink proxies if you have to, but you should never need to because the media on your computer while already see proxies in the correctly location.

Thanks for the info. I think I’m just going to have to test it out myself to fully understand it.