Couldn’t they have automated the projects/events to libraries process?

[Marcus Moore]

I think there’s WAY to many ways for this to go horribly wrong as automation. Especially with lots of project/event crossover.

[Glenn Grant]

It seems to me that this is a good way of clean up and organizing material. I wouldn’t upgrade in the middle of a project anyway. Unless there is some new feature (Or new MacPro) that you just have to have.

I have a few clients that I have ongoing projects, I will update there stuff to a new library and I think the little bit of extra work to update seems well worth it in the long run.

If all your files are online and you only have the events and projects your want combined available, then the process is automatic.

[Charlie Austin]

[Ron Hurtibise] “I have a huge project comprised of 20 projects and dozens of events spread across two external drives. I’m scared to death of the tedium that awaits”

You can just make sure your external drives are mounted and choose Update All. It’ll make one Library for each Drive, containing the existing Events on the drive, and any projects associated with those Events. You can organize stuff, (If you even need to) after the fact.

Make sure you have good, *working* backups of everything, including a zipped copy of your urgent FCP X 10.0.

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

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

[Mark Dobson]

Hi Ron,

Ripple Training have a set of three free instructional videos about the switchover. I watched these before I downloaded 10.1

https://www.rippletraining.com/fcpx-features.html

I also followed the advice of Philip Hodgetts – he is even supplying free software to assist people!

https://www.philiphodgetts.com/2013/12/upgrade-your-events-and-project-to-fcp-x-10-1-libraries-the-better-way/

So It’s really not a hassle – you can transfer Events / Projects on a need to basis rather than getting swamped with everything you’ve ever produced.

Whilst being initially a bit nervous – it all went very smoothly – and that’s when the fun starts.

And Alex4d has generously posted a really useful list of FCPX resources

https://alex4d.com/notes

Good luck

[Bret Williams]

But that’s not what you want. If you have multiple events and projects open, then it’s going to lop them all into one big library. To open any project, you’ll be forced to mount the whole library with all the events and projects within. This completely defeats the purpose of the library.

Apple really should have been more clear. But beyond telling everyone to muck about in the finder or get event manager and admit their own system of managing media was a mess, how could they?

Check out Mark’s link above.

[Bret Williams]

There’s no way for it to do it automated, unless somehow it knew what projects and events should be lopped together in what library automagically. It could perhaps bring up a screen asking you, which would have been nice, and create multiple libraries from the resulting query. But that wouldn’t exactly be automated.

[Ron Hurtibise]

Thanks for the responses. No, I don’t want to lop everything in one big library. And Bret, you’re right when you say there’s no true automated process. What I think would have been nicer would have been a simple option to have FCPX 10.1 create a new library with all connected events for each project in a mounted drive. Some events might be copied into more than one project library, but so what? Using Event Manager X to organize which projects and events are moved into new libraries still requires me to have a prior listing of which events are tied to each project. It doesn’t appear that Event Manager X detects which events are tied to each project, or am I missing something?

[Ron Hurtibise]

Why would knowing which events are associated with which project have to be automagical? In 10.0.9, you click on the project in the project library and the properties box lists the events tied to that project. Is this still true in 10.1 when all projects and events are lumped into one big library?

[Charlie Austin]

[Bret Williams] ” then it’s going to lop them all into one big library. To open any project, you’ll be forced to mount the whole library with all the events and projects within. This completely defeats the purpose of the library.”

Yes and no. It makes one big library for each mounted drive, The projects associated with the events on drive A will move to Library A etc. If a Project references media across multiple drives, it will figure that out and copy/move/link to that media. Once it’s all updated you can re-organize as you see fit.

If you had Drive A,B, and C mounted you’ll end up with Library A,B and C.

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

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

[Ron Hurtibise]

OK guys, I watched the first three videos in the Ripple Training package, plus the Working with Libraries video. And I’m still not wrapping my head around it. (I never worked extensively in Legacy, so I’m not familiar with Bins). In 10.1, I get that we’re creating Libraries, ostensibly to serve as holding containers for all elements associated with what we used to call Projects. And we can move those Libraries across drives or store them on network drives to enable shared access. Within those Libraries are Events. Events are created to store distinctive types of clips (Interview A, Interview B, B-roll, Exteriors, Music, Animations, Photos, etc.). Why, then, is it recommended that we locate Projects (or timelines) inside individual Events when Projects typically consist of clips from all of the Events? Why would I want to go into Event folders to access my Projects/Timelines? Shouldn’t Projects be renamed Timelines and placed in a Timeline folder inside a Library, separate from the Events? And shouldn’t Libraries have been called Projects, so that within each “Project” (Library) folder, we would have Timelines and Events?