Canon released a firmware update for the venerable Canon EOS-1D X Mark III. Canon EOS-1D…
Some days are gone from June 21, the release date of Final Cut Pro X, and Apple seems still lost in the Clouds.
There has never been a sign of apology or at least an explanation, just an almost embarrassing one way FAQ page.
Just that! and the fundamental questions still not answered.
To the costumer this arrives as “arrogance” and sets a heavy precedent which will be very difficult to retrieve.
Big companies, small business, professionals and ordinary people, all have been disappointed.
This time Apple has left everyone stunned.
Most of us share the same basic, astonished question: why?
I suggest you to read the article by Ken Segall.
It’s very clear, sensible and representative of the collective discontent.
“Well, well. This is something you don’t see every day: an open revolt by some of Apple’s most loyal customers.
It’s not that Final Cut Pro X is a bad product. Quite the opposite. It’s actually a tremendously cool and bold product. (I’ve been playing with it for two days now.) The problem is, for those who make a living with Final Cut Pro, it’s disturbingly incomplete.
Starting with nothing, FCP became the darling of Hollywood and the first choice among pro editors and video hobbyists. An amazing success.
But FCP was seriously due for an upgrade. So when Apple let loose that an all-new 64-bit version of FCP was coming, there was joy across the land.
It was a joy that came to an abrupt halt this week when Final Cut Pro X was released.
FCPX is indeed 64-bit, but it arrived missing features that many pros simply cannot live without. And Apple knows that.
For example, FCPX doesn’t support multiple cameras — which are a standard setup in many productions. It can’t open projects from previous FCP versions. It doesn’t support XML. (See what a big deal Apple made about XML in its own announcement two years ago.)”
To continue the article click on kensegall.com