Using the project Library

[Charlie Austin]

[Jordan Mena] “Has anyone found a good use for this part of FCPX? Does anyone have an idea where Apple will go in future updates for the Project Library?”

Personally I really like the Project Library, I find it much easier to organize the bazillions of versions of all the cuts associated with an event without turning my events into FCP 7-like cluttered nightmares. 🙂

That aside, my guess is that the Event/Project arrangement has something to do with some sort of future shared workflow. A “master” event shared by all with separate projects for each editor. Something like that maybe?

————————————————————-

~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~

[Jeremy Garchow]

Projects also allow sharing in that you can send a Project + used media. This is harder to do with compound clips.

It also creates a backup of sorts since the Project is a separate file form the Event.

I usually do rough cuts in the compounds, and once I get closer to a presentable or final edit, I move to a Project.

Jeremy

[Jeff Kirkland]

I’m pretty much with Jeremy. I use compound clips for rough cuts, sub-projects and version snapshots.

I always have one project timeline that represents my ‘final’ edit i.e. what is going to be delivered to the client. If I’m editing say a narrative with scenes, each scene starts life as a compound clip and moves to the main project when I’m happy.

Otherwise, I’m editing in the project timeline and occasionally create a compound clip of the project as a snapshot for versioning.

Even though I create events for footage and one specifically for compound clips, I find the event library can get too cluttered. I much prefer having a single project timeline that I can find in seconds and I know is the current deliverable version.

Jeff Kirkland | Video Producer | Southern Creative Media | Melbourne Australia
http://www.southerncreative.com.au | G+: https://gplus.to/jeffkirkland | Twitter: @jeffkirkland