So now that we have Libraries, why do we need Events?

[Bret Williams]

iMoive actually does this. It separates out projects from events. Even amongst all open libraries. It has an “all projects” icon that resides at the same level as libraries. It will show all the projects from within the open libraries. It also has an all events selection.

[Jeremy Garchow]

[Keith Koby] “But if it does go there, it will be sweet, f’n sweet. And it will all make sense. ;)”

It will be real close to (shhhh, avidbinlocking)

Thanks Keith.

I can see reasons why, but I’m just wondering if it’s the *best* reason why. So far, Event locking is the best reson why.

Do we think Apple will go there?

[Keith Koby] ” It is certainly an easier transition for editors to understand coming from fcp7 to x. Is that a good reason to keep it? I don’t know, but we use the separations now anyways. “

But would you use this system now with libraries?

Events where separate Finder elements in FCP 10.0, now, they are bundled in a Library.

So would you use multiple libraries now? Or were the separate Events you were using in 10.0 all per SAN Location? Now that they are no SAN Locations, what would you do?

[Keith Koby] “I don’t see a problem with putting the projects in events. We had compound clips in them before and occasionally there were edits and editors that would make promo versions as compound clips rather than as projects in the old version of x.”

You can always click the top level of the Library and get the birds eye view, it’s true, but it’s all by Event.

I really really liked in FCP 10.0 that the Event was the absolute top level organization. You could view everything. Now, everything is grouped by Event. If I am going to use multiple, Events, I wish I could turn that off, and I then (and only then) would I have the flexibility back.

Now, I am stuck with Event bins. I’m not saying if this is better or worse. It offers another level of organization, but it also takes away a level of sorting.

But I do like the Library system, so at least there’s that.

[Keith Koby] “I think from a program standpoint, database organization under the hood might be cleaner with lib/event organization rather than lib/wild dis-organization.”

I do think that locking off an Event folder (if that is in fact where Apple is going) but I’m not sure if that’s the best way. It seems like having this all done through metadata (collections, user log in, et al) might be more flexible?

Jeremy

[Jeremy Garchow]

[Marcus Moore] “Footage starts coming in for the second block of shooting, maybe lasting several days. At another station on a common network, the assistant goes about importing and logging BLOCK2 in his copy of the Library. When he’s done, he just exports an Event XML of BLOCK2 and the editor can import it into his copy of the Library. Super simple.”

But this wouldn’t have to be the only way. So now, Block 1 has Block 2 in it.

Or now you have two libraries with Block 1 (old) and Block 2. Which is the real Library?

I know exactly what you are saying.

I am just wondering if this is really the best way, or if Apple had to bend to external pressure to make it like everything else.

Jeremy

[Jeremy Garchow]

[John Davidson] “Here’s an example, I had a TON of footage on my home system from random little shoots at family events in Hawaii, Georgia, California, etc. I made a library called ‘Georgia’, and then created events for things like “Thanksgiving 2012, Thanksgiving 2013, and so on.

I also had a library called ‘Random’ for just smaller non-specific shoot elements. On my home system, all media is stored inside libraries instead of leaving in a 3rd location. When I realized that I had put an event in the Random library called ‘Georgia Family visit’, I decided that event would be better served in the “Georgia’ library. Moving that event to a different library (and all associated media with it) was so so easy. I just dragged and copied the event in question to the Georgia library and deleted from the Random library.”

But couldn’t this be done with Collections instead of Events, provided that Apple made it as easy? drag collection to new Library and all the media goes with it (or links to it, or copies it, whatever you want it to do).

Jeremy

[Jeremy Garchow]

[Aindreas Gallagher] “why maintain those kinds of serious – copy only – type canonical event rules within a library?”

I really really liked that in FCP 10.0, that footage can be here AND there (in this collection AND that collection).

Now we are back to here OR there (in this Event OR that Event, even if it’s in the same Library). And if it has to be here AND there, they are two separate annotations in the Browser, so really the same piece of media has two separate instances. This was just like FCP7, really.

[Aindreas Gallagher] “If the event largely exists only as a construct within FCPX – why don’t they just introduce folders and be done with it?

The folders could get the event icon to hide cupertino’s blushes, or, you know, they could just call the folders bins…”

Why have Events at all? Why not just keep the exact same format as 10.0 Events, expect it’s now a Library. You can have folders if you want them, or separate everything by keyword. Add FCP 10.1 Library Media Management to Collections and you’re done.

Jeremy

[Jeremy Garchow]

[Bret Williams] “Why even have libraries? Why not simply rename an event a project, and within such project one has 2 things – organizational structures like keyword collections, smart collections, folders, etc. and sequences.”

Whatever the name of the Library, I do like the Library structure. It is nice to have a file to dupe or move or load, or double click, and now, we can even store media in it.

I think that the Library system, especially towards the Finder is good and works well, I just think we could eliminate Events, add folders to the Library level, and everything would be peachy.

Jeremy

[Bret Williams]

We already have all that with events. Might just be semantics but ditch libraries and make events launchable. I’d like to rename them projects as well, and rename projects sequences.

[Jeremy Garchow]

[Bret Williams] “We already have all that with events. Might just be semantics but ditch libraries and make events launchable. I’d like to rename them projects as well, and rename projects sequences.”

But with events, there’s only “Current Version”.

With Libraries it’s an actual, versionable, modifiable file.

Jeremy

[Andy Neil]

[Jeremy Garchow] “Why have Events at all? Why not just keep the exact same format as 10.0 Events, expect it’s now a Library. You can have folders if you want them, or separate everything by keyword.”

Couldn’t it just be step one in a shared collaborative workflow structure? If you look at how bin locking works in Avid, you have the project which shows up at merely a folder in the finder. The lockable elements are .avb files which exist within the project folder. In MC, the project is merely a window which holds bins only (no sequences) and this allows for all editors to access the same project, but only have writable permissions on the bins they opened first.

Now with libraries in FCPX, you have basically the same structure except that Apple’s used a package instead of a simple folder. This makes it a little more idiot-proof at the finder level. Inside the library, you have event folders with an event file that, presumably, could be locked in much the same way that Avid bins can be locked. The events have a finder level equivalent, something that collections don’t have since they are just meta-data sorting tools.

Perhaps this was just the first organizational hurdle to creating true project sharing. Or perhaps it was to give 3rd parties the structure so they can create project sharing programs

Andy

https://www.timesavertutorials.com

[Alban Egger]

[Jeremy Garchow] “But I can’t figure out why I would need more than one Event in a Library, unless of course I want an Event that is Projects only.”

I have to agree here. Of course their are situations when you need several events, but since keywords are “sticking with” events I will often only have one event per library.

E.g. having a sports-team season in one library. You could make each game one event. But if you then have highlighted (key worded) every players scoring plays it would not make sense to create #80-touchdown in every game. Instead I will follow my “pre 10.1 workflow”: make folders with keywords for a) games b) highlights c) players etc.

For me I believe Events will be a way to share media around. I already used the “Copy Event to Library” command a few times. Works great and allows to put certain parts of jobs into external Disks/Libraries/Events.

But I am sure different workflows will come up as we keep using 10.1 just like they did with 10.0.x