Re: Working with material on existing projects

I was told that the source media size did not matter and that it was just the quantity of compound clips within a project, that should be restricted. 35 compound clips added to a project from event browser keywords, was enough to bloat and bring my specific project to a crawl. I still suspect that the original source media length can play a role, as does the use of nested clips.

I'm starting to think that the people that are using fcpx with no problems, are simply not using compound clips as organizational units, but just maybe as containers for a few special situations. I have worked on simple projects with absolutely no issues at all.

For the record, I have seen my project file get way above 200 MB at times, almost a gig once, but usually with a force quit ending. I really don't understand what they are trying to store in that project file to make it so big, if the media and render files are located in their own locations. Whatever it is, that file size or the processing that is going on within it, has been the source of my woes and slow performance that I spent a huge amount of time trying to diagnose. I've only been able to remedy it by breaking apart all my compound clips that originally came from the EB via keywords. Interestingly, if I turn them back into compound clips, the project file size does not expand and my system does not slow, but by then, I've lost all the useful linkages back to the EB.