Apple's rationale for calling projects 'Events' and sequences 'projects'?

E

eco_bach

Well-known member
Can anyone possibly explain Apple's rationale for calling projects 'Events' and sequences 'projects'?
And why they are saved separately?
 
Apple have a history of railroading over standards if they feel that there's a "better" way of doing things...

I can't see the rationale behind it except maybe it locks people into their NLE a bit more?
 
I think they explained it when they initially introduced it at the supermeet, but I can't remember what they said.
 
it seems to make more sense archiving footage.

you can store source files from an 'event', and use the files in multiple projects. for example, if your working on a dvd or blu ray, you might create multiple projects for the main movie, and then a couple more projects for extras and behind the scene footage.

or if your creating different versions of the movie in different projects, or if your using footage from a live concert in a concert project and a music video with the concert footage.
 
I like it. It means media filmed at an event is related to that place and point in time. Different projects can then draw from that event
 
Dave © said:
What he said.
Click to expand...

Of course it makes sense for very small 'projects'(in the old sense), weddings, concerts, corporate events. But what about anything that requires multiple shooting dates and or times? Like most any short film or documentary.

To me at least this 'event' metaphor breaks down and is simply not intuitive for organizing your assets.

Perhaps it will make more sense after working with it a while
 
I would not consider Projects to be the same as Sequences. They don't do what Sequences did. But "Compound Clips" do exactly what Sequences did.
 
They told it indeed somewhere in the introduction; It's also because that 2 data sets are kept seperate, they are harder to corrupt. And in that case, you can have an Event for instance, where you have media that you use a lot in projects (Bumpers, Music Ques, ...) so you can always reference to that event without always importing it into every project.
So it does make sense, but you really have to re-adjust. There are times where I'm not a big fan of the system, but it has more to do with my adjusting then the system itself, I think. (yes, I don't like the name Events, but hey... It's more of a Media Pool)
 
BenB said:
I would not consider Projects to be the same as Sequences. They don't do what Sequences did. But "Compound Clips" do exactly what Sequences did.
Click to expand...

Which is exactly why I create compound clips in my Event and build a lot of things right inside there without making a whole new project for everything. I just create a Compound Clip and treat it as a sequence. Hasn't failed me yet... :) It also lets me treat my Events like you could an old .fcp where everything's sorta in there. Projects have their place but they're not always necessary.
 
How about if you are cutting 3 trailers and a short from the same event/shoot ?
Or cutting a 15 sec, 30 sec and 1 minute spot from the same event/shoot ?
 
eco_bach said:
Of course it makes sense for very small 'projects'(in the old sense), weddings, concerts, corporate events. But what about anything that requires multiple shooting dates and or times? Like most any short film or documentary.

To me at least this 'event' metaphor breaks down and is simply not intuitive for organizing your assets.

Perhaps it will make more sense after working with it a while
Click to expand...

I don't see how the metaphor breaks down. You can either treat them all as one event or treat them all as separate events.
 
You can continue to add to a specific event, or you can set up new events. The event media can then be used in an infinite number of ways to make a project. I find this much easier than previous versions of FCP and I have been using the program since 1.25. I see no downside, and in fact, I found it much easier to keep things nice and tight.
 
I say if you don't get how to use the library, you look into some online training. No matter how long you've been editing. It might even be a good idea to look at some training even if you think you understand the library.
 
Projects are not events. A helpful metaphor is that an event is an instance of media assets grouped together that can be used across multiple projects.
 
I think an Event comes from Iphoto or something

Event: Grannies Birthday

Event: Joe Plays soccer filmed by doting mum.

S
 
J Davis said:
event = collection of media connected to date + location
Click to expand...

Perhaps I misunderstand you. But an Event can contain anything you want in it without any connection, although you would want to create an Event that has clips related in some fashion. It's how you sort those clips into to various folders and sub folders that makes the whole thing hum along.
 
yes, it's like a smart folder or smart collection or smart object.

now, you can associate the event to a date, location, client, project, film, short film, ...etc. if you normally organize source data in folders in a specific manner, it can be translated into the software. imagine a small user friendly database management software that looks more appealing than the older fcp version, and includes keywords, clip data, ...etc.
 
You must log in or register to reply here.
Back
Top