Welcome to our community

Be a part of something great, join today!

Log in
  • Hey all, just changed over the backend after 15 years I figured time to give it a bit of an update, its probably gonna be a bit weird for most of you and i am sure there is a few bugs to work out but it should kinda work the same as before... hopefully :)

Why everyone is so painfully wrong about FCPX

Sergio Perez said:
What concerns me is that, and I think I'm reading this right , Red Team didn't know anything and weren't working on anything for FCPX until the day of FCPX release. This contradicts the NYTimes writer. This can also mean all the additional info about future additions of xml, edl, etc. which the same writer said in the article, bogus.
Click to expand...

I had another look at the article and apparently he just had people send him a list of things to ask Apple and he got all the answers from the project managers of final cut pro over a telephone call, if you want to know why he didn't call red to fact check Apple you will have to email Pogue and ask.
 
It does certainly seem like Apple is targeting the *truly* independent filmmaker (and I mean, write/direct/shoot/edit themself) and web video editor audience... so I get why the pros are frustrated. I do.

I don't think it excuses the whining and the bashing, but hey. What do I know.

I guess I'm saying... there are plenty of other platforms out there that are just as capable as FCS, so I think everyone is going to be ok. Transitioning sucks, yeah, but it's inevitible at some point. If this SERIOUSLY means you won't edit with your FCS3 platform anymore, and you were banking your entire production on software you already didn't know much about (meaning X, which not many knew much about)... I don't know what to tell you. But you're all smart, and Adobe and Avid are solid contenders.

Apple is going to lose some customers, sure, but don't think they don't already know that. This isn't the first time a product or software has changed and it's pissed a lot of people off. ;)
 
I've called some friends today to see who is doing what with new tools for FCp X and Im no clearer where this app actually will go or what it may offer in future. Jim is completely right we need to know the road map as Apple see it or most of us will walk.

So far it seems that its up to third parties to build the tools to offer export, colour tools, effects tools, media management and a whole host of other stuff that just isn't there in the app right now or may be Apple have it in mind to build the stuff which I don't believe.

At this time I don't know if FCp X can be a framework to support pro functionality that we need and is essential for all of our work or if Apple have released it to be some sort of advanced iMovie app, which I am finding hard to believe them abandoning the professional community.

There is a difference today from 12 years ago or when ever it was we were testing FCP 1.25. In the intervening years we have all go used to what is mostly a workable and very flexible pipeline. We cant now rewind and start from scratch with this, its better to either jump ship or stick with FCp 7 which as was pointed out is actually FCP 6.5 for all practical purposes.
 
You know what's funny, if people bring out stuff too early, it's no good.... if other people bring stuff out late but perfect, people complain also.... can't make everybody happy :)
And what I never get, is that people will jump ship just because the boat is rocking. I'd rather hold out at least for a short while...
 
albert rudnicki said:
Is there any way to get your money back?
Click to expand...
yes!
i did get it back
although i like the editing style, the missing features to communicate with other programs, the static UI interface, and this media copy stuff are dealbreakers.....
man, steve jobs should fire the crack addicted dslr shooter who said, well thats ok to erase all the pro features. trying to get the crossover discount for avid now.
 
Patrick Grossien said:
And what I never get, is that people will jump ship just because the boat is rocking. I'd rather hold out at least for a short while...
Click to expand...

The boat has been sinking for a long time. And now, Apple finally showed up 'to the rescue', on a jet ski.

If you think giving Apple is going to come to their senses I would point you towards the thriving Shake community... no wait...

Apple wouldn't have blown it like they did if they had acted like a professional tools company and properly communicated/solicited feedback from the professional community. I'm more annoyed with Apple's disregard for the opinions and input of its users than any missing feature. FCP-X is the perfect illustration of why a unilateral closed development environment just doesn't work for professional tools. Apple is making rookie mistakes because they have a culture of secrecy. As long as Apple is Apple they'll keep making those kinds of mistakes over and over and over. Adobe is pretty awful in this regard as well (see 20 page thread of The World v. Adobe on EXR transparency) but they at least have some communication with professional users.

Autodesk used to have a terrible track record in this regard and once they changed their culture their products started to benefit and their users started driving the road-map. The iPhone culture doesn't work for pro-tools. Apple can't dictate a studio's pipeline, they're not irreplaceable.
 
Adobe seems to have done an about-face over the past 18 months. Anyway, they're making some strides in the right direction. I'm so confused about what Apple is trying to do with FCPX, I really don't know what else I can say about it. The omissions and mistakes are truly rookie blunders and total noob decisions. Not only have they failed to solicit suggestions and listen to the desires of the pro community, but they have fallen into the classic large-application-trap where the majority (if not all) of the development team really does not understand the market they're trying to serve. I have a pretty strong feeling that the FCPX development team was completely blind-sided and confused by the industry backlash.
 
Jeff Kilgroe said:
I have a pretty strong feeling that the FCPX development team was completely blind-sided and confused by the industry backlash.
Click to expand...

I'm not so sure, I think that they just assumed that like the imovie community after imovie 08 came out once the next release came out all the anger over the software would just die out.
It seems to me they have quite arrogantly decided to change the way people edit movies which is why older final cut pro files won't be imported into FCP X, they just can't, it wouldn't work because they ditched bins and sequences.
Now you have a project with a single timeline and compound clips to break things up into various sections if you wanted to bring in a legacy FCP project it would have to significantly alter it to get it in and likely break the thing along the way.
 
Craig W. Bickerstaff said:
Actually it sort of did happen with the iphone, when the first iphone was launched there was a ton of noise about how limited it was, why can't we make 3rd party apps as well as many other things it didn't do.
3rd party apps for example Apple kept their mouths shut on Apps and that wasn't introduced until I believe IOS version 2 a full year later, now IOS is considered pretty full featured.
Click to expand...

Paul Nordin said:
Maybe so, but that is not what Apple just did. What Apple just did would be equivalent to shipping the iPhone 5 this fall and no 3rd party apps work because they chose to rewrite the iOS APIs and forgot to tell the 3rd party developer community.
Click to expand...

Apple did all of this this 10 years ago and they even used practically the same name!

OSX

Does any one remember when OS 10.0 came out? No 3rd party software, not even Adobe; classic-9 mode was still a patch or two away (which costed $50!); it crashed all the time. But eventually it became one of the best operating systems and everything was OK!
 
You must log in or register to reply here.
Back
Top