Charlie Austin
Forum Replies Created
-
[Jeremy Garchow] “makes X so much faster”
Choose your words carefully Jeremy. If you use terms like “faster” or “better”, you will be attacked from one camp. Words like “destroying” or “killing” will provoke attack from another. Best not to use any adjectives or verbs at all when discussing FCP X. 😉
————————————————————-
~ My FCPX Babbling blog ~
~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~ -
[David Lawrence] “[Chris Harlan] “And the Source Timeline–that’s probably my favorite Avid exclusive. In fact, yes, that’s the thing I miss when I’m using Pr.”
Have a tasty pancake! 😉
“So, just to be clear… In FCP X, if I create a compound clip rough cut of all my selects, and use that as the source… Isn’t that essentially the same thing as a source timeline (MC) or pancake timeline (Pr). I guess I can’t drag clips from one sequence to another. And at some point I have to break the clips apart. Other than that, what’s the diff? 3 NLE’s, 3 different ways to accomplish the same thing.
————————————————————-
~ My FCPX Babbling blog ~
~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~ -
[Franz Bieberkopf] “a couple hundred million dollars per year in 2010 for FCP7, and something like sixty million in 2013 for FCPX.”
Not that it matters, but add in Compressor, Motion, and maybe Logic to that FCP X total. Rcp 7 wasn’t sold alone.
————————————————————-
~ My FCPX Babbling blog ~
~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~ -
[Michael Aranyshev] “[Charlie Austin] “I really think that if people spent time actually working in X, they’d be just as fast as they are in anything else.”
Did they put Replace on Playhead into one of the updates? If they did I might consider spending time learning it.”
Yeah, that’s still missing. Also, reading my quote above it sounds like an admonishment, and it wasn’t meant to be at all. As some other threads here show, I guess wee need to choose our words as carefully as politicians now, lest we be misunderstood. 😉
————————————————————-
~ My FCPX Babbling blog ~
~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~ -
[David Roth Weiss] “but if you’re a good driver and are comfortable operating a Volkswagen, you’ll get to your destination a lot faster in your Volkswagen that you would in a Raptor if you first have to learn how to fly.
So, while the continued evolution of X over the last three years may be wonderful for some users, for many others whose primary focus is creative decision making and storytelling, the evolution of the product has meant a continuous and arduous learning curve, one that interferes with their creative process instead of speeding it up.”
Absolutely true, at least the good driver part. I really think that if people spent time actually working in X, they’d be just as fast as they are in anything else. Having been cutting in FCP “classic” since version 1, I can work ridiculously quickly, and I put the same effort into learning X as I did 7. (or MC before FCP or Pr when FCP X (which I didn’t like very much at the time) appeared…) As a result, I can cut in it just as I do in 7. Fast.
The X “evolution” hasn’t really affected the fundamental way the timeline works, that’s been pretty much the same since it came out. It’s a complex NLE. Learn it, and you’re good to go. The same learning curve argument applies to people moving from FCP 7 to MC. That’s why Pr is popular with switchers I think. It’s the closest approximation of FCP classic there is. 😉
————————————————————-
~ My FCPX Babbling blog ~
~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~ -
[David Roth Weiss] “n any case, if an editor feels they can spend of their time making creative decisions with any particular application, and that app is most likely going to get them to the finish-line faster, regardless of all other considerations, then that’s the fastest NLE for them.”
True. For me that’s FCP X, and I work in mostly short form. Anecdotally X is great and or not so great for long form, there’s evidence for both results. I do still use others, mostly 7, some Pr. But as you say, whatever you feel best working in… use that. 😉
————————————————————-
~ My FCPX Babbling blog ~
~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~ -
[Franz Bieberkopf] “Congratulations to Apple. End-of-Life has never been so good.
“FWIW, you’ll probably be able to update to the latest greatest OS if you like, and still use FCP 7. After that… ???
————————————————————-
~ My FCPX Babbling blog ~
~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~ -
[Alex Gollner] “as well as features that would help implement dynamic trimming.”
That would be kind of cool. I’d prefer a “hot key” to switching modes…
————————————————————-
~ My FCPX Babbling blog ~
~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~ -
[Franz Bieberkopf] “… “shaping and controlling the discussion of its products”.”
Interesting read. The quote above is pretty much a textbook definition of marketing. Most companies wish they were as good at it as Apple. 🙂
————————————————————-
~ My FCPX Babbling blog ~
~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~ -
[Oliver Peters] “Sounds plausible.”
It kinda does huh? That would be nice…
————————————————————-
~ My FCPX Babbling blog ~
~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~