FORUMS: list search recent posts

Too many projects in one library

COW Forums : Apple Final Cut Pro X

<< PREVIOUS   •   VIEW ALL   •   PRINT   •   NEXT >>
Oliver Peters
Too many projects in one library
on Jul 17, 2017 at 5:37:40 pm

Is there a prevailing thought about how many Projects should be in any given Library? I saw a post over at FCPco from a doc editor who had 27 Projects (alternative versions, archived, etc) and this was causing the Library to load very slowly. By moving most of the old ones to an archive Library, it made his main Library more responsive. So is there an ideal number/length before the Library performance is really impacted?

- Oliver

Oliver Peters Post Production Services, LLC
Orlando, FL
http://www.oliverpeters.com


Return to posts index

Jeremy Garchow
Re: Too many projects in one library
on Jul 17, 2017 at 5:58:56 pm

27? That seems really low.

A current library has 113 Projects in it, and it's not even that crazy busy of a library, and yes, that Event takes some time to load sometimes, but that's the way it's always been. And once it's loaded and opened, it doesn't take as long to load the next time. It's the way it is in Pr too, and FCP7, the more sequences the longer it takes to load.

I don't have a hard number, but 27 seems like it shouldn't cause too much harm unless there's something else going on with analyzation or slow plugins.


Return to posts index

Oliver Peters
Re: Too many projects in one library
on Jul 17, 2017 at 6:13:12 pm

[Jeremy Garchow] "I don't have a hard number, but 27 seems like it shouldn't cause too much harm unless there's something else going on with analyzation or slow plugins."

I would image it's a combination of number and length, i.e. total amount of links. 27 commercial Projects would obviously be less than 27 feature-length Projects.

The OP also mentions that the Library is on the Desktop. I wonder if performance would be better if the Library were in the Movies or Documents folder rather than on the Desktop. In my experience macOS has issues with having a ton of files on the Desktop. Since a Library is a container with a ton of files within and not a binary file, that could be a factor, too.

- Oliver

Oliver Peters Post Production Services, LLC
Orlando, FL
http://www.oliverpeters.com


Return to posts index


Jeremy Garchow
Re: Too many projects in one library
on Jul 17, 2017 at 6:21:14 pm

[Oliver Peters] "I would image it's a combination of number and length, i.e. total amount of links. 27 commercial Projects would obviously be less than 27 feature-length Projects."

Of course. I edit more than commercials. 😉

Events with lots of Projects (and longer projects) do take a bit to load, but nothing prohibitive. And, once it's loaded it's usually loaded (unless you restart FCPX).

Not sure on the desktop vs folder. I only run quick test libraries from the desktop. It would be a very easy test to simply move the library to a folder.

Also, cache location does make a difference in speed. I try and keep caches on the internal SSD.


Return to posts index

Claude Lyneis
Re: Too many projects in one library
on Jul 17, 2017 at 6:26:55 pm

The more items on the desktop, the slower the system finishes booting up. This is very noticeable if you don't have some version of an SSD for the internal drive. The system has to treat the desktop differently. So it just a guess, but putting the library on the desktop would not be the best idea.


Return to posts index

Bret Williams
Re: Too many projects in one library
on Jul 17, 2017 at 7:38:29 pm

Putting the library on your system drive seems like a bad idea in general.

_______________________________________________________________________
http://BretFX.com FCP X Plugins & Templates for Editors & Motion Graphics Artists


Return to posts index


Jeremy Garchow
Re: Too many projects in one library
on Jul 17, 2017 at 7:47:48 pm

All my libraries and cache are on my system drive.

They run at nearly 1TB/sec, any system overhead is a blip.


Return to posts index

Bret Williams
Re: Too many projects in one library
on Jul 17, 2017 at 8:17:20 pm

To each their own of course. Speed isn't my worry. Backup would be. And space. I'm not sure aid want to rely on Time Machine for a restore in a system drive crash. And my internal is only 500gigs. But even a 2TB internal is going to fill up quickly. I'm frequently dealing with 500-800gig projects (not including render caches).

I keep all libraries / media on my raid 5. By default the libraries get backed up to the system drive. By default all the caches stay on the raid. And no need to pay Apple tax on large internal system drive.

That said, I kinda wish I had a larger internal on the laptop for the occasional road edit. But I'd rather have a SSD raid 5. Looking at the one from OWC so I can have a more portable raid with the same insane speed as the MBPro internal, but with raid 5 protection.

_______________________________________________________________________
http://BretFX.com FCP X Plugins & Templates for Editors & Motion Graphics Artists


Return to posts index

Jeremy Garchow
Re: Too many projects in one library
on Jul 17, 2017 at 8:38:04 pm

[Bret Williams] "To each their own of course. "

But of course!

[Bret Williams] "I'm frequently dealing with 500-800gig projects (not including render caches). "

I keep my media on separate storage (all media in libraries are external, and not managed).

I have constant backups going, and the FCPX backup folder is automagically uploaded to the cloud.

Space is a consideration, but since I rarely render, it's manageable. Libraries are usually pretty small, and the cache can grow, but it's easy to delete unneeded render media out of it.

My backup folders do NOT include my cache folder and I keep all caches external to the library, and all going to one "FCPX_Cache" folder on my SSD system drives for easy browsing, trashing, and selective deleting.


Return to posts index


Bret Williams
Re: Too many projects in one library
on Jul 17, 2017 at 9:01:41 pm

That's exactly all the work I avoid by simply putting the library on the raid 5. Copy media to raid from card. Then create library on raid. Automatically backed up on raid plus a separate drive (system) for the library. No worry about where the caches are or where the media is. Which means no accidental files on the system drive. I can also consolidate projects instantly because the media is on the same drive, creating a consolidated, no-relinking library to hand off or archive. Everything is also in one single folder on the raid.

_______________________________________________________________________
http://BretFX.com FCP X Plugins & Templates for Editors & Motion Graphics Artists


Return to posts index

Mark Suszko
Re: Too many projects in one library
on Jul 18, 2017 at 3:49:48 pm

Am I doing it wrong? I make a new library for every new job that comes in, and keep all related media and projects together with it. It just seemed more intuitive to me that way, but I'm willing to be schooled.


Return to posts index

Bret Williams
Re: Too many projects in one library
on Jul 18, 2017 at 4:56:35 pm

You're doing it the way the majority of us do it. I think Jeremy was just saying having 27 projects in a library isn't that many. For example, I'm currently on a job that is a set of 8 videos. On some of the videos we're up to v5, 8, even v10. So that's easily 40+ projects. One for each version. Lots and lots of compounds too. And since each version, except the current, is a snapshot, all those compounds exist alone. I would think that each compound counts as a little mini project in the eyes of FCPX as well. There certainly isn't any magic number. Just like any edit, the more sequences, clips, fx, compounds, etc the more space and memory you'll need.

_______________________________________________________________________
http://BretFX.com FCP X Plugins & Templates for Editors & Motion Graphics Artists


Return to posts index


Jeremy Garchow
Re: Too many projects in one library
on Jul 19, 2017 at 2:33:49 am

[Mark Suszko] "Am I doing it wrong? I make a new library for every new job that comes in, and keep all related media and projects together with it. It just seemed more intuitive to me that way, but I'm willing to be schooled."

As Bret alludes to, there is no right or wrong, only what's right for you.

We have shared storage and keeping libraries on there would allow any one person to open the same library. We choose to run our storage this way (there are ways to lock folders and files) but it's just easier to keep libraries local and share XMLs or whole libraries.

Also, the cache runs faster on our local drives than it does over the shared storage, so we keep that local too.

We do not keep media in libraries because it makes moving them around very cumbersome, especially when our projects are currently running in the 1-3 TB range on average. Having managed libraries could be very beneficial if you don't need to move them around very much as you'd only have the one library file and all of the resultant media will go with. It just doesn't work as well for our needs since people need access to the same media, it's better to have it stored once, as opposed to stored many times in individual libraries.


Return to posts index

<< PREVIOUS   •   VIEW ALL   •   PRINT   •   NEXT >>
© 2017 CreativeCOW.net All Rights Reserved
[TOP]