Timothy Auld
Forum Replies Created
-
I for one have never been baffled by FCP X. If you stick to the confines of how it wants you to work it is actually quite simple. And I also find that the integration with Motion to by one of the the very positive things about FCP X. However the fact remains that it is at present a very buggy piece of software and one that cannot meet my delivery needs at this time. And I have serious doubts that it is much of a priority at Apple to make it do so. I could be wrong and kind of hope I am.
As a side note I read in one of your previous posts something to the effect that FCP 7 “still works flawlessly.” For the record it never did. If it did I would not have to worry about my project size ballooning and the project file possibly possibly becoming corrupt due to the simple act of placing all my sequences together in one bin. Nor would I have to constantly create new projects for long-form work again to ward off the possibility of corrupt project files. And Soundtrack Pro has never worked for anything over a couple of minutes long. No NLE works flawlessly (all you need is one trip around Avid’s attic to know that) but FCP has more that its share of peccadilloes.
bigpine
-
The marketplace does not now nor has it ever sorted out who gets anything right. It sorts out which product sold the most. And that can happen for a variety of reasons including, but most certainly not limited to, what product is the best at serving its particular need.
bigpine
-
Possibly, Jeremy. But that really wasn’t the phrase with which I would have replaced my ellipsis.
bigpine
-
Interesting. “that old fart” and “insulted me” in the same sentence. Paradox? Irony? Or…
bigpine
-
Yes, with no announcement of support resuming I can only assume this is an attempt to get rid of old inventory and put some more cash in the bank. They are, after all, nip and tuck with Exxon.
bigpine
-
But are they going to support it again, or is it still EOL?
bigpine
-
What you seem to fail to realize is for a good many of us FCP X as it exists now will not serve within our present workflows. It’s not a choice not to use it, it simply won’t work for us in its present state. We couldn’t use it if we wanted to. It’s not yet up to the task. And i personally can’t afford to wait to see if Apple has the intention of making it so.
bigpine
-
duplicate post
-
It’s bad enough that people call this “the Ken Burns effect” as if filmmakers had not been doing it for decades before Mr. Burns was even an a gleam in his father’s eyes, but if there really is a button labelled Ken Burns effect in FCP X it goes more than a little bit further down the road toward confirming my worst fears.
bigpine
-
Like it or not an information vacuum spawns rumors.
bigpine