How to manage huge events? (4TB of HD material --really sloooow )

Would you mind explaining me why Events need to be shared. NO CRITISISM I'm keen to understand, I work mainly in Reality Docs and TV. I can understand editors having access to the same footage but I can't figure out the need to "share".

I can't say for sure but I would say it is the hardware.
We have 3 pimped out Mac Pro that are beeing used for FCPX which are hooked up to 14TB fiber raid. No slowness here, i would break the events down to scenes or sections.
We share to have two or three editors to work on a project the sometime.

Seanus wrote: Would you mind explaining me why Events need to be shared. NO CRITISISM I'm keen to understand, I work mainly in Reality Docs and TV. I can understand editors having access to the same footage but I can't figure out the need to "share".

"Having access to the same footage" is "sharing". You can only access media assets via an Event. If multiple editors need to access the same library of media assets, they need to "share" the same Events.

It was a Final Cut Server feature that I am very sure we'll see more and more of in FCP X over time as it continues to mature.

BenB wrote:
"Having access to the same footage" is "sharing". You can only access media assets via an Event. If multiple editors need to access the same library of media assets, they need to "share" the same Events.

Great thanks. I guess what I find a little strange is that you would have two editors working from the one Event. If there were common assets then I would definitely put them in their own folder and get each editor to add them to their own events but not copy media.

This is the thing that has me a little confused as it's easy to have your media anywhere you like then just create your own Event and don't copy the media. Am I missing something?

Sharing projects is another thing entirely obviously.

Right now, on a network, that is how you do it. Each editor has his own Events on a drive. If it's a network shared drive, Disk Images on that one drive for each editor. Their Events link to the originals in a central storage directory on that drive.

marchyman wrote: T. Payton reported a drastic processing slowdown when doing this back in August. His guess for the cause was constant updates to a very large event database. Has that changed in current versions of FCPX? And T. Payton, did I characterize your complaint correctly?

Unfortunately this is still very much an issue with 10.0.3. It is a problem that occurs with a large complicated database and is reproducible on every machine I have tried it on. From my older Macs to the latest and greatest at my local Apple store. I've got another large project (been working on it since August) that has the same type of "database bloat" slowdowns. However, I've been working with Apple on this issue since December, so I hoping for a fix soon.

I'm thrilled that not everyone has encountered this problem.

I've been moving clips from the main huge event to another one. The Idea is to split the making of material in pre production, production, intervews etc..

I'll let you know if after this time consuming process it will be faster. I hope Apple manages to fix this, because being able to tag clips in one single event was the main reason I decided to use FCPX.