Why is there a project library?

[John Heagy]

[Jeremy Garchow] “Where is the XML generated from?
“

We have a custom app that links disparate media based on Reel ID and TC. We use this to generate an xml that links to media on the San.

[Jeremy Garchow] ” An empty FCP7 won’t relink to anything. An empty Event won’t relink to anything either.”

Sure it can, FCP7 never looks at media in the project to link to, it links directly via path. I can open an empty FCP7 project… import the xml I describe above, and Wa La! a 100% linked seq! The only item in the project is the seq created from the xml import.

[Jeremy Garchow] “I guess I am having trouble seeing how this doesn’t work for FCPX in an almost identical way to FCP7”

If by identical you mean now needing a San Location for every project, an Event filled with aliases, and separate projects for every seq… then yes, identical 😉 You’ll agree that not using Events to assist in some way makes it an obstacle to work around and not an asset in this case? Can we make it work?… Yes… but it’s no improvement.

[Jeremy Garchow] “I do see a problem if you need to “online” though as reconnecting to other media in FCPX is terribly non-existent. “

That’s the least of my concerns because we can use FCPX xmls like we do today with FCP7 and produce a linked project. Of course we first need to create a folder point FCPX to it as a San Location then create a Event then point the xml media to it and then.. Wa La! a linked project along with 100s of pointless alias files.

Yes, I know we are in the minority here, but FCP7 flourished across the entire gamut of production from pajama editors to 100 seat collaborative productions. Apple seemed to intentionally truncate the productions FCPX could serve – or even worse – thought it would just pick up where FCP7 left off which means they were simply out of touch with reality.

John

[Jeremy Garchow]

[John Heagy] “We have a custom app that links disparate media based on Reel ID and TC. We use this to generate an xml that links to media on the San.”

OK, then in FCPX you’d create a new set of criteria for FCPXML purposes, and set the path to this same media, no?

[John Heagy] “Sure it can, FCP7 never looks at media in the project to link to, it links directly via path. I can open an empty FCP7 project… import the xml I describe above, and Wa La! a 100% linked seq! The only item in the project is the seq created from the xml import.”

Right, so you are left with a project with a sequence in it.

Although it looks different, this is exactly what happens in FCPX, but there’s an alias file created if one isn’t present. When you “reveal source” in FCPX, it points you to the hard media, not the alias file. Importing the XML also does creates an Event, so it’s similar to an FCP7 project.

[John Heagy] “If by identical you mean now needing a San Location for every project, an Event filled with aliases, and separate projects for every seq… then yes, identical 😉 “

You don’t HAVE to have a SAN Location for every Project, though. You can import an XML anywhere.

As far as multiple sequences, there would be ways to make them all one Project if you really wanted to.

When using an XML, an Event is a consequence just like an FCP7 project is a consequence of importing a sequence. It is there, but its not going to get in the way anymore than an FCP7 project.

[John Heagy] “You’ll agree that not using Events to assist in some way makes it an obstacle to work around and not an asset in this case? Can we make it work?… Yes… but it’s no improvement.
“

I guess I don’t see it as any much different, even though it might not look like an FCP7 workflow. in FCP7, the project held info that points to the files, in FCPX, the Event holds that info, as well as the Project. And, as this thread states, you can skip Projects all together if you’d like and go back to “one file” just like FCP7.

[John Heagy] “a linked project along with 100s of pointless alias files.”

That’s really what it is isn’t it? The alias files are what sends the workflow over the edge. I can appreciate that, but since everything started aliasing itself on a SAN, I think about them much less than I used to.

[John Heagy] “Yes, I know we are in the minority here, but FCP7 flourished across the entire gamut of production from pajama editors to 100 seat collaborative productions. Apple seemed to intentionally truncate the productions FCPX could serve – or even worse – thought it would just pick up where FCP7 left off which means they were simply out of touch with reality.”

Clearly, the only big operations they had in mind were theirs. I think they are smart enough to know that.