-
With Great Sadness……
-
[Jim Giberti] “Say what you will, but I’ve never experienced this level of damage or instability from any version of any program we’ve ever run.”
Sounds really scary, Jim. I hope after you’ve gotten caught up and rested you’ll call Apple and talk to someone in product support. They need to hear from you directly, not thru the feedback form.
_______________________
David Lawrence
art~media~design~research
propaganda.com
publicmattersgroup.com
facebook.com/dlawrence
twitter.com/dhl -
[Steve Connor] “Absolutely true, Apple’s second biggest mistake after dumping FCS3 was calling it Final Cut Pro 10, but what I’m trying to say is that despite what the marketing schmucks decided to call it, the fact is that it’s well known that it’s a version 1.0 software…”
Heaven knows I’m in emphatic agreement with you there. I get that it’s already a great thing for a lot of people, and I like a lot about what I think it’s trying to do, but goodness, there’s only so hard you can bang your head against the wall before it stops being fun.
Although Bessie would like to thank every single one of you for keeping at it. LOL
But I feel like stopping support of FCS 3 was one of the very smartest things they did. They’re committed to this new direction, so COMMIT. I’m a fan. If I were their business consultant (hah-freaking-hah), that would have been my one strongest bit of advice: all or nothing, boys. Do it or don’t. As Martin Luther said, “Be a sinner, and sin boldly!”
Hey Jeremy, I agree that calling it Final Cut Pro 1 again, so close to the FIRST v.1 of Final Cut Pro, would have been weird. Would have been confusing. So, following the advice of thousands of other people in these forums, maybe they should have called it iMovie Pro v. 1! Hahahaha!
-
[Tim Wilson] “They’re committed to this new direction, so COMMIT. I’m a fan. If I were their business consultant (hah-freaking-hah), that would have been my one strongest bit of advice: all or nothing, boys. Do it or don’t. “
I totally agree Tim, and I want Apple to declare their hand.
Their laissez faire attitude and the “we’re pro” – “no we’re not” – “let’s keep ’em guessing where we’re going” attitude is both crazy and crazy-making.
The marketplace is so confused now that no one knows what to do, and Apple isn’t helping anyone by being so non-committal.
-
[Tim Wilson] “Hey Jeremy, I agree that calling it Final Cut Pro 1 again, so close to the FIRST v.1 of Final Cut Pro, would have been weird. Would have been confusing. So, following the advice of thousands of other people in these forums, maybe they should have called it iMovie Pro v. 1! Hahahaha!”
Good one. I laughed at that one.
—
What’s in a name?
I agree that Apple was right to simply drop 7 and move on, if they are going to rewrite the app from zero and completely change the notion of fcp as we know it. 10.0.3 is a weird release. It enabled a bunch of functionality, but reduced performance. I haven’t experienced the corruption Jim has, but when things started running as slow as they have in this latest release, I stopped using it. You can “feel” that something is wrong, and it’s up to Apple to make it right.
Keeping the Final Cut Pro moniker indicates that they want to stick around in the pro space, in what capacity is kind of unclear, but that is Apple’s m.o. Apple has no fears about letting the pro space go. They’ve done it before, they might do it again. It seems like if they wanted to drop fcp, they would have taken the opportunity to do so rather than create the fanfare that they did, starting at NAB.
The use of multicam, fcpxml, San locations and other “features” seem to signal that there’s more to come, and certainly goes beyond iMovie. Of course if it simply doesn’t work and is unusable due to deplorable performance, the name doesn’t matter.
It’s certainly a rough patch. Fcs3 still works well, even in lion. 😉
A more legit beta program would help, stop me if we’ve heard that one.
—
Jim, did you get that RAM situation fixed? Didn’t all this start happening around then?
-
I think those saying “It’s version 1, remember how buggy the enigma machine was in 1942 etc..” are seriously misrepresenting just how flaky FCPX is.
Software has got steadily better and more reliable over the last 30 years and our standards have risen. It’s still true for me though that FCPX is the buggiest software that I have ever used, by the standards of any era since 1983. That’s pretty amazing.
Admittedly, I haven’t used it since 10.02 but the latest update sounds worse if anything.
On my last job with FCPX, the software slowed to a crawl and had to be restarted every 5 minutes and the titles were all reformatted on every restart.
-
[andy lewis] “I think those saying “It’s version 1, remember how buggy the enigma machine was in 1942 etc..” are seriously misrepresenting just how flaky FCPX is. “
If there’s a positive to this, this is what Beta testing brand new software is like.
Apple is showing the world what it means to beta test.
Color, before Apple bought it, was pretty damn buggy.
Your title bug was supposedly fixed in 10.0.3. Good luck? 🙂
Jeremy
-
[Jim Giberti] “And from a production standpoint, it couldn’t possibly interface with Motion worse than fcpx, so nothing lost there.
“Definitely, Man. Where ever I end up, I want Motion along for the ride. Sorry about the trouble. Our work is hard enough without having those kind of technical nightmares.
-
[Tim Wilson] “They’re committed to this new direction, so COMMIT. I’m a fan. If I were their business consultant (hah-freaking-hah), that would have been my one strongest bit of advice: all or nothing, boys. Do it or don’t. ”
I strongly disagree with this sentiment. It is clear to me after eight months that FCPX is not an upgrade or replacement for FCS3. It is another NLE aimed squarely at a market that is different but has overlaps with FCS3. The EOL without notice and the haste with which they killed and attempted to bury the body has done irreparable damage to many people’s confidence in Apple as a supplier of a reliable professional NLE.
The fact that we are still debating how this NLE can be useful and jokes about beta testing shows that Apple only committed to getting rid of FCS3 without a commitment to building a tool for their customers. All or nothing implies this software is somehow capable of being used professionally and is a worthy replacement. This is still crap after three updates with design paradigms that are hopelessly flawed.
-
[Michael Gissing] “The fact that we are still debating how this NLE can be useful and jokes about beta testing shows that Apple only committed to getting rid of FCS3 without a commitment to building a tool for their customers. All or nothing implies this software is somehow capable of being used professionally and is a worthy replacement. This is still crap after three updates with design paradigms that are hopelessly flawed.”
I’m not sure who you’re addressing specifically, but since I mentioned bera, I’m not joking about beta testing. This is a beta and it feels like it. This isn’t a beta of the next version of a mature program, but rather a beta of a brand new one that was rushed out of the door. It’s not even iMovie Pro as that is more mature and stabke than 10.0.3.
If it was stable, it would be usable for some people. There are no work arounds for instability.
I am curious as to how Lightworks for the Mac is going to be on the first pass.
Jeremy
-
[Jeremy Garchow] “Color, before Apple bought it, was pretty damn buggy. “
We had several seats of “Final Touch” as “Color” was known pre Apple. Paid good money for it. Never regretted it! As I recall, it was quite stable. It was missing some features, but it was predictable.
can’t say the same for “X”.
Mark
Reply to this Discussion! Login or Sign Up