Jeez, somebody got out of bed the wrong side...

Worth sticking with...

I love the end.

What a tosser...

I apologize in advance for my rant. I'm still waiting for coffee to brew... I shouldn't say anything, but, what the hell.

Apple has always said, even during the NAB presentation, that FCP X would be growing and evolving over time, very quickly, in part due to the App Store distribution model. That was never in question. That said...

"Say goodbye to:"
1- Outputing audio track to specific hardware? What does that even mean? And it's coming.

2- Capturing from tape, was never gone. Outputting to tape, Apple always stated free 3rd party apps that do that. AJA's is fantastic. And who outputs to Mini-DV anyway?

3- The support for sharing projects. Again, this guy is a retard as this is plain wrong from day one.

4- Support for multiple timeilnes? Really? What does that even mean? I have all sorts of timeline! It's "timeline" based! Even a "clip" has it's own timeline.

5- Support for RED, which there is a workflow for that is basically the same as it was for FCP 7. AND we know native RED support that 7 never had is in fact coming.

6- Multicam support? We have the best multicam in the industry right now, moron!

7- Specified scratch disks? Thank goodness that's gone! I hated being locked in to one specific media drive. This makes moving, archiving, etc, WAY easier.

8- Limited support for XSAN, and more coming. What a jackwad.

9- External monitors. I'm using my same old AJA LHi with my same old Flanders LM-2452W AND have desktop support so it can even be a second monitor with the click of a button.

10- OMF, there's an app for that.

11- XML, a whole new generation of more powerful than ever XML is here and growing.

12- EDL, a dead format, the few apps using it are changing, it's so freaking outdated and limited, XML blows it away.

13- AAF, another wonky format. Most all recording studios I've ever worked in are strictly OMF and hate touching AAF. Actually OpenTL is the future. But this guy knows nothing about professional audio engineering in a professional recording studio, I guess.

14- 10 years of legacy project, very easily brought into FCP X.

As for the reviews, I can cherry pick the same comments about PPro and MC if I wanted to from various forums. FCP X has a 4.5 start average rating, and 130 4-5 star ratings, and only 31 3-1 star ratings, TODAY.

Yeah, I wonder what that high school kid is doing now. Stealing more copyrighted music for his YouTube movies?

I edit just about every day.

In the past year I've received awards, a raise, a bonus and completed all my work on time and on budget.

I've been using FCP X exclusively since it was released.

What am I doing wrong??

anickt wrote:
Oooohhh anickt! You're not professional! You're using garbage to make garbage! Can't you see how god awful horrible FCP X is? Those awards, that raise, that bonus, those don't really mean anything! Because you're using FCP X, they're meaningless! Oh my, you're just so unprofessional. Just ask anyone on the "Editors Who Hate FCP X" Facebook group!

But don't ask any of us in the "I HONESTLY LOVE FCP X" Facebook group, none of us has a clue as to what we're talking about. None of us are really professionals. And the dozens of working, seasoned pro editors I've trained in classes on FCP X who love it and have switched their studios over also know nothing and are unprofessionals. Oh poor stupid me...

OK, ML just finished downloading, have to log off and reboot!

When was this video done? As BenB states, most of these issues (along with it's 2star rating) were left behind almost 6 months ago with the release of 10.0.3.

More sour grapes.

Some factual errors in there as well. The video seems to believe that FCP7 shipped with FCS2...

If you go over to Vimeo you can see 'Bangshock's note on his/her video:

I choose to see it as a satire on the knee-jerk reaction to Final Cut Pro X. It was melodramatic enough!

What Ben said.


Also, the "bad reviews" he had in quotes were all nobodies from the appstore board, not industry professionals, many of whom have now got behind supporting FCPX.

Everybody's take on how they like or don't like FCPX depends on what they done with legacy FCP/FCS, meaning what they have done with it professionally. I edit video as a "professional" working in local TV news. So many still say FCPX is NOT a pro program. Well just speaking for me, I use it professionally, therefore to me it's a pro program.

Working in TV news, our editing has to be quick and expedited for a same day show.

In my "professional work capacity" we don't care about XML, EDL's, Red Cameras/DSLR video (no time to do cine style shooting at breaking news, messing with a follow focus when a fireman is coming out of burning building, can't yell cut tell em to go back in and redo it! LOL!)... We shoot P2 on HPX370's. So what I do professionally, FCPX has been great! It works for what we do. Its quick and edits smoothly, and lets us meet show deadline which comes up on you very fast. The event system is great where we can pull up file video by keyword very easily. We need the "improvements" we have been teased about, dual viewers, paste attributes(this should have been done in 10.0 - no brainer, don't get me started!), scrolling timeline etc...Apple needs to come up more frequently on these updates, over a year and the program is still developing, is still too slow for me. My only gripe...

So when somebody says "FCPX is not a pro application" be careful because that persons perspective of pro is different from person to person, professional to professional, depending on what they do. I can see the others point of view as it might effect what they do more drastically than it does others like me.

-Been editing TV news on FCPX since 10.0.3....Prior to that it was FCP6
Peace

VideoJounalistGB wrote:
The program will be continuing to develop over the next ten years (Apple has publicly stated that, I didn't make it up). All software continues to develop. Just Apple does it faster and better. Sometimes too fast for some folks to be comfortable with. Not us, I mean the other folks who have no clue what FCP X really is.

So, every 3 months is too slow? What's fast enough? Just setting the record straight that expecting faster is IMHO unreasonable. Software development is a painfully slow process. I was in that industry in my former career. I'm amazed at how fast Apple is giving us very significant updates.

Remember, FCP 8 (64-bit FCP 7) was in development, quite a way in to it. Then Apple decided to take a different direction WAY earlier than expected with the underlying frameworks of OS X. The FCP dev team was caught off guard, so to speak. So, they could begin re-writing all of that 64-bit code for the same-old-same-old, or do something different. At this point they decided it was best to just start from scratch. After all, we were all bitching about the outdated GUI and such. Not to mention the stuff FCP X has from Final Cut Server, Color, Cinema Tools, etc was all 32-bit and had to be totally re-written.

So they started from scratch, totally new, GUI design, function design, new AVframework, new technologies. It's amazing they got so much done so fast.

How far along has PPro or MC come in the past 12 months? How many new features have they given users? How often? How much do they still charge for every update/upgrade that has new features?

Truth is FCP X is coming along faster, more often, for less money, and with features more advanced than anything anyone has ever seen to date.

Just had to set the record straight. If you want faster, well, I guess microwave ovens boiling water in 3 minutes is too slow.

Nothing personal, I'm just saying, keep a realistic perspective, that's all.

And over the next few months, and years, you're going to be blown away. It will all be worth it. Good bye Media Composer, be happy in second place Premier Pro.

I'm just saying...

I've been saying this for a year and I honestly believe it. It was a conflation of 3 things that I think has, and will continue to, cause a lot of the negativity from a certain sector of the legacy crowd-

1. They changed things, radically.
2. The software wasn't feature comparable to FCP7 at launch.
3. Apple's messaging at launch was to cut off FCP7 sales- prompting people to think they had to make a quick decision on what to do.

If they'd only done any 2 of these 3 things, there probably wouldn't have been this level of backlash.

If they'd launched "FCP8" and stopped selling 7, no one would have said anything. Faster horse.

If they'd launched FCPX with it's radical changes, except with comparable feature-set to FCP7, then there would have been no question about "who is this for?". But as we're not quite there even now (maybe 10.0.6) that would have meant the software would have been delayed for at least another 18 months. So MC6 and CS6 would have launched with nothing from Apple until at least this Fall or maybe even next Spring. They couldn't wait.

They had to launch with what they had to show their cards, and get it in the hands of those who could start using it. But for this scenario to work, you have to be ABSOLUTELY CLEAR to your user base that this is a transition period to a product that isn't ready for all markets yet. Keep selling FCP7. Lots of workshops on FCPX features. Get people excited about using it without them thinking they've just had the rug pulled out from under them. That's how you get people on board for change.

But what happened... happened. So those of us who can see the longer game here are going to have to put up with the stigma on FCPX for a while longer.

"This video brought to you by your friends at ADOBE!"

Disproportionate Pictures wrote: Good points - agree. Think they should have maybe called it something different.

BenB wrote

...
11- XML, a whole new generation of more powerful than ever XML is here and growing.
...

Ben then you obviously must have a very special version of FCPX.

Andreas

I have the version that is updated and evolving faster than any other NLE on the market. So I never speak of it as a static entity, but as the swiftly growing and expanding application it is. FCPXML at present is the foundation for what it will be over the next several months and years. Which will be the most powerful version of XML to date. Simply being realistic.

BenB:
... FCPXML at present is the foundation for what it will be over the next several months and years. Which will be the most powerful version of XML to date. Simply being realistic.

What means "realistic" ? Shouldn't you say: "optimistic" ?

FCPXML at it's current state is even far behind the state of XMEML version 1 with FCP 4.1.
Probably some day FCPXML will be powerful (which I doubt will happen in the next several months) — right now it's just a poor simple implementation of XML. Simply being realistic.

Anyway — most of the users don't/won't use XML. Therefore it's at the end of the "what to do list". Most users even wouldn't notice when changes are implemented.

-Andreas

mistermattsmith wrote:
I don't think the name is a problem. If Apple is to be believed, in the end Apple want to be serving the same markets with X as they did with 7, even if it isn't ready yet. So it should definitely be called Final Cut Pro.

In fact, I find the name perfectly apt. FCPX is not an iterative step forward; they aren't building on the old foundations anymore, they tore down the house and are starting from scratch.

When has Apple done this before? Well, anyone who's been around for a while will remember the launch of OSX. It faced many of the same criticisms in it's early days as FCPX. Software had to be rewritten to run on it, so the programs you needed to get work done probably didn't run on it. It was riddled with bugs and the UI was called "overly flashy". So the solution for a lot of users was running OS9 and OSX in parallel for several years for different tasks.

With such a clear example from their own recent past, it amazes me that Apple didn't pitch the FCP7 to FCPX transition in the same way.

Yeah, you're right, they just make a right pig's ear of the launch. Think they're still stunned at the backlash. The earlier point about keeping FCP7 alive and giving this a softer launch would have been better. People are already cutting beautiful stuff on FCPX and natural curiousity/jealousy would have wooed people across. It was also a bit half-baked at launch, which didn't help.

FCPX was ALWAYS going to be a tough sell to the professional market. New UI, several new editorial methodologies that throw out some very ingrained NLE concepts...

In my mind, the migration strategy for high-end users should have been almost as important to Apple as the software itself. I personally believe that Apple has made some incredibly keen breaks with FCP7. But you can be as innovative as you want, but you put a stigma on those ideas when you screw up the launch this badly.

AVID and Adobe had the easy job. All they had to say was they weren't changing things and that they listen to their Pro client base.

I really do hope the FCPX team puts in another appearance at NAB next year to introduce a 10.1 product. To show editors that they don't think they were wrong, and to quote Tim Cook, they're "doubling down" on FCPX.