Let get one thing striaght…

[Peter Blumenstock]

You cannot separate audio tracks.

[Greg Burke]

Really? No there has to be a way.

[J Hussar]

I like final cut 7 – it was just getting long in the tooth and not taking advantage of the 12 processors and 24 GB of RAM I have in my MacPro (which was well over $7k).

They sold FCP as a tool for pros. They lied and said the new version was for pros. A lie.

Basically they lied, they continue to lie – even knocking the negative comments off the app store until they got caught doing it.

It’s a PR disaster for Apple – much bad mouthing going on in the real world. This is real negative word of mouth from people who love really always loved Apple.

Randy Ubillos should resign over this fiasco. Simple.

[Peter Blumenstock]

What exactly do you mean with separating audio? Assigning channels, outputting for example four channels of audio instead of stereo? All that can’t be done.

[Phil Hoppes]

There will never be a FCP8. What you see is what you will get. There is no hidden meaning. If FCPX fails, and actually, once the dust settles, I don’t think it will fail. But if it did fail, its gone and in the grand scheme of Apple Corporate Revenue it will be a footnote on a back page of an annual report. Seriously, how big do you believe that $300 a pop software product makes for a 100B/yr company? Do the math. Go crazy. 2 million units at 300each. That is 0.6% of their annual revenue.

In fact I think it will be wildly successful, just not the mainstay of 90% on this board. They may use it for sure, but it is not intended for the top 10% nor will it ever be pushed to that arena. No need.

[Craig Seeman]

[Greg Burke] “I really want it to fail, mainly because if it does apple will make Fcp 8 faster.”

It’s incomplete. That’s not a fail. There can be no FCP8 because FCP was based on Quicktime which is 32 bit. In order to make a 64 bit program they had do use a new base and that’s AV Foundation. Then it would be a challenge to mimic an old paradigm when AV Foundation’s media handling is very different.

It makes more sense to have productive feature requests and improvements than to clamor for an improved “old” way when there simply wasn’t anything to build that on.

In fact one of FCP’s biggest disadvantages was it’s tie to Quicktime and the need to rewrap or transcode or otherwise trick it into seeing things as Quicktime wrapped. Sometimes there’s no prettying up a pile of decaying matter.

Apple wanted, rightly fully so I think, more direct and clean tie ins to the new technologies they’re using.

[James Carey]

[Craig Seeman] “In fact one of FCP’s biggest disadvantages was it’s tie to Quicktime and the need to rewrap or transcode or otherwise trick it into seeing things as Quicktime wrapped. Sometimes there’s no prettying up a pile of decaying matter.”

wow, that’s quite a statement, Quicktime a pile of decaying matter.

Jim Carey
Director of Video, Radical Entertainment
linkedin: https://ca.linkedin.com/in/jcarey256
mobygames: https://www.mobygames.com/developer/sheet/view/developerId,17212/

[Herb Sevush]

Craig –

Premiere Pro is 64 bit and yet, guess what, it looks and acts like a NLE.

The fact that Quicktime was a problem and the code had to be re-written has nothing to do with the fact that this product was re-targeted for a different audience. They killed the Viewer window (which eliminates Multi-Cam)– was this necessitated because of AV Foundation or because it’s now a simpler program for Youtubers to navigate?

Herb Sevush
Zebra Productions

[Ted Levy]

Unfortunately this can’t actually be a PR disaster, because most Apple customers will never use and don’t care about Final Cut Pro.

[J Hussar]

You nailed it Herb… all the misdirection that they ‘can’t’ do something is simply nonsense.

Programming is NOT impossible. They chose not to support pros.