APPLE FINAL CUT PRO: Apple Final Cut Pro X FCPX Debates FCP Legacy FCP Tutorials

Re: Cutting a major Hollywood Feature on FCPX

COW Forums : Apple Final Cut Pro X Debates

Respond to this post   •   Return to posts index   •   Read entire thread

Charlie Austin
Re: Cutting a major Hollywood Feature on FCPX
on Oct 8, 2014 at 6:48:52 pm

[Bill Davis] "And then note that what I'm pushing back against in this thread is public discussions with an editor who doesn't use X indicating that the very REASON he doesn't use it is because it "fails" in a necessary operation - that I then pointed out that it actually handles that specific operation rather brilliantly."

And that's fine Bill, even pushing hard. I think what people react to in your posts are statements like:

"...and therefore make editing much, MUCH easier for those who understand the new system."

"And the nomenclature had to change because the CONCEPTS behind the program had to change. Starting with a clean slate lets you start from scratch and use names that have meaning in the new system. Timelines were FIXED with a zero point and an unbreakable progression in time."

"the whine of "But I already KNOW words for this kind of stuff - don't make me learn any new terms." which is simply kinda LAZY IMO. "

Here's my opinion, feel free to reject it, :-) ...

There's no reason to insult people, (even if they deserve it lol). Facts help change minds, and you often present great facts. But when they're wrapped in indirect insults it hurts your argument.

And you sometimes offer your opinions, - such as the part above about names changing because concepts change - as facts. They're not. The names more likely changed because Apple's other apps use terms like Library and Project and Event. iPhoto, Logic, Motion. And sometimes you're even wrong... For example, timelines still are fixed with a zero point, and are still called timelines in X.. ;-)

I don't say this to pile on, but to maybe shed light on why people react to some of your posts the way they do. The high horse approach isn't necessary, and doesn't work. IMO of course. There are plenty of people who will never like X. Whether for a legitimate reason like it doesn't suit their workflow, or a dumb reason like they're mad at Apple for killing off older products. BFD.

Presenting info, as you have in this thread, about how X can work for someone is great. Pontificating about the inner workings of software you didn't write, and denigrating anyone who "doesn't get it" is counterproductive. Again... my opinion...


~ My FCPX Babbling blog ~
~"It is a poor craftsman who blames his tools."~
~"The function you just attempted is not yet implemented"~

Posts IndexRead Thread 

Current Message Thread:

© 2019 All Rights Reserved