Where we are: No need for debate

[Steve Connor]

Nice summary!

“My Name is Steve and I’m an FCPX user”

[Kevin Patrick]

[Ben Holmes] “I’ll stick to the techniques ones from now on.”

I bet somebody is gonna post something that gets you back here.

Every time you think you’re out, they draw you back in.
(or however the quote went)

[Craig Seeman]

Yes, treating this whole thing like and either/or choice hasn’t made much sense to me.

I think a key issue has been hardware compatibility between the NLEs. I think that’s been going away especially as Avid opens up a bit. Premiere will have CUDA but FCPX is taking advantage of OpenCL and, over time, OSX specific features.

There might be a debate over Mac vs Windows though and that may even intensify when the new MacPros finally happen. It’ll be interesting to see how Thunderbolt is handled over time (even on PC given Acer, Asus, Sony vs HP, Dell, Lenovo).

Actually there was a time when this was a gut wrenching, wallet crying decision when one weighed the exorbitant cost of an Avid upgrade vs an FCP system but those days are long gone.

There’s no reason not to have a diversified tool chest. There’s no reason not to have a primary tool based on one’s own typical workflow.

[Chris Harlan]

[Ben Holmes] “Use FCPX if you want to work quickly in editorial environments “

Oh, yeah. Those of us who choose the others do so because we want to work more slowly. Sorry, I think your analysis is suffering from .0 release bugs.

[Walter Soyka]

[Craig Seeman] “I think a key issue has been hardware compatibility between the NLEs.”

For me, it’s interchange.

FCP was an open system, but Apple has thrown up all kinds of walls around FCPX through the combination of a new data model (which no other apps use) and their lack of interest in supporting existing interchange standards.

There are some brilliant ideas in FCPX that I really like; I just wish it were easier to make it communicate with other systems.

I’d like to see Apple become a better citizen in the post community again. Asking third parties to help them interchange suggests to me that they see it as a low priority, not worth their time.

Walter Soyka
Principal & Designer at Keen Live
Motion Graphics, Widescreen Events, Presentation Design, and Consulting
RenderBreak Blog – What I’m thinking when my workstation’s thinking
Creative Cow Forum Host: Live & Stage Events

[Craig Seeman]

[Walter Soyka] “FCP was an open system, but Apple has thrown up all kinds of walls around FCPX through the combination of a new data model (which no other apps use) and their lack of interest in supporting existing interchange standards.”

I think you’re making an assumption that the current state is the final state. FCPXML is just a first step. It’ll get there. Obviously if it’s not usable at the moment then, that’s where it sites now but that does not indicate that their goal is walled product.

[Rafael Amador]

[Kevin Patrick] “I bet somebody is gonna post something that gets you back here.

Every time you think you’re out, they draw you back in. (or however the quote went)”
Nobody force nobody to come to this Forum.
I guess that you don’t work for Apple and is the very debate which bring you here.
Ben has been long around the FCP forum so his points of views will always be appreciated.
rafael

http://www.nagavideo.com

[Walter Soyka]

[Craig Seeman] “I think you’re making an assumption that the current state is the final state. FCPXML is just a first step. It’ll get there. Obviously if it’s not usable at the moment then, that’s where it sites now but that does not indicate that their goal is walled product.”

I’m not making any assumptions — just sharing my observations on the current state of the product (poor interchange), outline my concerns, and stating my hopes for future versions (improved interchange).

You are making an assumption when you say, “FCPXML is just a first step. It’ll get there.” I’d call that a reasonable assumption, but there have been many reasonable and erroneous assumptions about FCPX so far. I’m trying not to make any more of them myself, and that means not looking beyond things that Apple has explicitly promised. Since they did say in the FAQ that they do not intend to support legacy import, I think my concerns over interchange are well-founded.

I agree that FCPX is still under development and that there’s more to come, but getting back to Simon’s iMovie/FCPX discussion from another thread, they’ve had more than 4 years, and probably closer to 5 or 6, to think about how their new timeline data model can work with the rest of the world. I’m drawing the conclusion that interchange is a very low priority for Apple, since a lot of other development has advanced dramatically in that time — and interchange hasn’t.

Openness wins, and I find it disconcerting that Apple doesn’t seem to be valuing it more highly.

Walter Soyka
Principal & Designer at Keen Live
Motion Graphics, Widescreen Events, Presentation Design, and Consulting
RenderBreak Blog – What I’m thinking when my workstation’s thinking
Creative Cow Forum Host: Live & Stage Events

[Kevin Patrick]

Apparently the point of my post was not obvious. I attempted to make a humorous comment relating to Ben’s statement that he will most likely spend his time discussing FCP X in the FCP X Techniques forum, as opposed to this one. The humorous part was the reference to one of the Godfather movies. (forgot which one)

Honestly, I’m sorry if you didn’t find it humorous. I certainly meant to disrespect to Ben either. But, I can see how someone could take an attempt (especially a poor one) at humor to be disrespectful. Again, sorry.

Although, I’m not sure I understand your comment about whether I work for Apple. Not that I’m offended. I just don’t quite understand it.

[Rob Brandreth-gibbs]

How about if you have no legacy issues but need print-to-tape or numbered audio tracks for post or a fear of sudden EOL?

RBG