FCPX offers what advantages over Premiere?

[Steve Connor]

[Bill Davis] “Not sure it makes sense to ask for both simultaneously.”

Why on earth not? The magical FCPX database should give you MORE flexibility not less, as you say it’s an ACTIVE management database, should be easy to change datapoints

[Walter Soyka]

[Bill Davis] “Walter, this also goes to why I suspect the metadata description system in PPro can’t be directly compared to the one in X. Sure they both describe the edit positions via abstraction, but i sispect only one does so as entries in a live evolving SQLite database, rather than the old style of just writing addresses in a fixed code file and referencing them. But I freely admit that I’m no expert on coding nor the guts of this stuff, so I’ll leave it for the programmers to decide whether X and Premier use the same sort of metadata manipulations under the hood – or if that’s a core part if what Apple “re-plumbed” in the X re-imagining.”

Before the revamped relink workflow with Premiere Pro CC, I studied a bunch of my .prproj files, figured out the format, and wrote an in-house re-linking app a couple years back that operated directly on the .prproj file — outside of Premiere entirely. Because of that experience, I think I have about as solid a grasp on the Premiere project data model as you’ll find outside of Adobe.

The Premiere Pro data model is relational, just like the FCP X model. Premiere markers can have durations, not just refer to a single frame; as such, Premiere markers (and subclips) are essentially ranges.

The fact that FCP X runs on CoreData is immaterial here. Both FCP X and Premiere run on relationally-structured databases. One is no more “live” than the other from a data standpoint, though I’d be sympathetic to your argument that FCPX is livelier in how it exposes this data to the user and allows the user to sift and manipulate it.

Walter Soyka
Designer & Mad Scientist at Keen Live [link]
Motion Graphics, Widescreen Events, Presentation Design, and Consulting
@keenlive   |   RenderBreak [blog]   |   Profile [LinkedIn]