Linked by Thom Holwerda on Wed 29th Jun 2011 15:04 UTC
Thread beginning with comment 479220
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 06/18/13 22:33 UTC
Linked by Anonymous on 06/18/13 22:26 UTC
Linked by Thom Holwerda on 06/18/13 22:25 UTC
Linked by Thom Holwerda on 06/18/13 17:45 UTC
Linked by Thom Holwerda on 06/18/13 17:32 UTC, submitted by poundsmack
Linked by Thom Holwerda on 06/17/13 17:58 UTC
Linked by Thom Holwerda on 06/17/13 17:52 UTC
Linked by Thom Holwerda on 06/14/13 21:03 UTC
Linked by Thom Holwerda on 06/14/13 20:46 UTC
Linked by Thom Holwerda on 06/14/13 17:32 UTC
More News »
Sponsored Links



Member since:
2006-06-09
I didn't remember QuickTime X dropping backward compatibility or not supporting earlier versions features of QuickTime. Do you?
New codebase is neither a selling feature neither an valid excuse.
They also know that MacOS X provides backward compatibility with previous MacOS version, that QuickTime X provides backward compatibility with previous version. Even if they were new codebase.
So, how one could know by himself that FCP X wont be backward compatible or wont support at least the set of Pro features that does previous version of FCP?
By reading on the box?
Nope, nothing there.
By reading the press release?
Nope, nothing there.
FCP X "preview" was demoed at NAB. It was not released in store yet then. It is now.
And nothing inform buyers about the broken backward compatibility or the features set which don't cover Pro ones. It was not said during NAB either.
You can twist it as much as you want, the facts are that they present it as the *new* Final Cut Pro version without saying it's not backward compatible.
Then give it a completly different name, for god sake!
Now. But could you bet that Mac App Store won't ever do that when upgrading a product?
What would happened if the Mac App Store upgrade process had remove FCP 7 to replace with FCP X?
Oh, sure, Apple will have fixed it a few days or weeks, but until that, no access to existing FCP projects!?
That's money loss.
I'm sorry, but maybe that a risk consumers could accept, but pros really can't. There is enough stuff that could jeopardize your business, you don't need some software provider to screw your workstation.
And Apple just send the signal this risk is increasing with their FCP product.
The least pros can do is sending back the signal that they won't accept it.