Apple Posts Final Cut Pro X FAQ, Promises Updates

[JasperJanssen]

I don't believe that's true. At least, you can't buy it anymore. So your business can't hire another FCP 7 editor without trying to find a copy on ebay or pirating it.

You can still buy support, just not the application itself, direct from apple. There are as yet options to get NOS of FCS3 licenses, and I suspect if the situation actually gets to the point where people are being forced to pirate it, Apple will reopen phone sales.

http://www.videoguys.com/Item/Apple...cluding+Final+Cut+Pro+7/14F2A523436324D4.aspx

http://cgi.ebay.com/Apple-Final-Cut...ultDomain_0&hash=item1e64c1624e#ht_798wt_1020

 

[manu chao]

Perhaps FCP7 is EOL because it won't run under Lion?

Have you actually read the FAQ? Apple clearly says that FCP 7 will work fine under Lion.

 

[Biolizard]

Apple does not sell it, but authorized distributors and resellers are still selling and I suppose they are making a fortune from all FCP X bad publicity

Will resellers be able to restock, though? If not, then it's not something to be relied upon. The supply of FCP 7 licences could run dry anytime.

I think Apple were right to release FCP X. Clearly software of this complexity needs to be used and have feedback and evolve over time, but the mistake was removing FCP 7 from normal distribution.
They should've said "Here's FCP X, it has about 75% of what FCP 7 does but it does it more efficiently, we're going to be building on this platform for years so start testing with it. We'll begin a transition now and in 12 months time you won't be able to buy FCP 7 anymore as we expect FCP X to be at feature parity by then, so get learning."

Given Apple is normally the master of transitions (OS 9 -> OS X, PPC -> Intel) I'm not sure how they've managed to screw this one up.

 

[manu chao]

I don't believe that's true. At least, you can't buy it anymore. So your business can't hire another FCP 7 editor without trying to find a copy on ebay or pirating it.

And that will change, I am so certain about that I don't think it is even worth getting worked up about. Apple cannot and will not say: 'If you need multicam support now on additional machines, go screw yourself you won't get it from us for the next six to twelve months."

There's no question that Apple should put FCP7 for sale in their Online Store. It's a big mistake and the customers may suffer.

As I said this almost goes without saying.

 

[H. Flower]

Can I hide Events that I am not working on?

Yes. You can hide Events in Final Cut Pro X by moving them out of the Final Cut Events folder. In the Finder, navigate to the /Users/username/Movies folder and create a new folder. Then move the Events you are not using out of the Final Cut Events folder and into your new folder. The moved Events will no longer appear in Final Cut Pro X. If your Events are located on an external drive, you can move the Events to a new folder on that drive, or you can simply unmount the drive.

Why not allow us to choose what we want open, rather than have the program itself dictate it, forcing us to use "workarounds" ?

Like much of this program, it seems so convoluted......

 

[Mrbill317]

Works in my test copy of lion

I am currently running both versions. I installed FCP7 on the 4th developer release of Lion for work without a problem. I also have FCPX working as well (Motion 5 too).
All seem to be fine.

That's the big issue I have. I actually *like* FCPX, for the features it does have and the pure speed it performs with. But the lack of many options that FCP7 folks are used to, make me a bit nervous. I can see pro editors [and even semi-pros] wanting to still be able to use and purchase FCP7 for new machines. If you run a company that is growing and need to buy more FCP7 seats, how can you? Perhaps FCP7 is EOL because it won't run under Lion?

If I were Apple, I would have named this Final Cut Express X. It *does* have some awesome features, but they haven't caught up to what they currently...err..used to offer in FCP7. Keep FCP7 around; lets the Pros play with FCEX knowing that in another year FCEX will become FCPX and be feature complete.

/vjl/

 

[179202]

Your idea is great, market a consumer application as Pro application. A pro application is for professionals, not consumers. If they wanted to make a consumer version, they've should've called it iMovie Pro or something...

If an application can be used by people to edit, it doesn't matter if it's 'pro' or 'consumer'. A great piece of software empowers the user. It doesn't matter whether they're 'pro' or 'consumer'. Sure, there are some features that a pro would need and a consumer wouldn't, but that's all to do with personal workflow. That differs from person to person.

Apple are right to provide basics and let third parties handle specialised, niche features and provide support for their own hardware. They haven't dropped the ball here. They've simply released a solid editing app that many people, for some bizarre reason, thought they could switch to right away.

 

[H. Flower]

If an application can be used by people to edit, it doesn't matter if it's 'pro' or 'consumer'. A great piece of software empowers the user. It doesn't matter whether they're 'pro' or 'consumer'. Sure, there are some features that a pro would need and a consumer wouldn't, but that's all to do with personal workflow. That differs from person to person.

Apple are right to provide basics and let third parties handle specialised, niche features and provide support for their own hardware. They haven't dropped the ball here. They've simply released a solid editing app that many people, for some bizarre reason, thought they could switch to right away.

Why is the timeline closed architecture, though?

Do you remember that's what drove people away from AVID to the old Final Cut?

 

[pubwvj]

"Regarding importing from Final Cut Pro 7, Apple says that due to the many changes there was no way to "translate" old projects without losing or changing data. So, Apple suggests that users continue to use Final Cut Pro 7 for existing projects."

That is really BAD because the next thing is Apple will of course stop supporting FCP7 and then when they upgrade their hardware you won't be able to run FCP7 on the new machines and your projects become so much trash.

Apple should be maintaining compatibility for all applications all the way back. The computers, even an iPodTouch, have the computing power necessary to emulate all the previous machines. There is a tremendous amount of software that was never upgraded to PowerPC and then to Intel. Developers went out of business. But many users, especially in small businesses and education, still use that software. This is a great resource. It is a shame for Apple to abandon it. If they're doing this for Quicken they should do it for all applications.

Some people say upgrade to alternative software but are no alternative titles for a lot of the software. Apple should not be abandoning Rosetta and they should not have abandoned Classic. They are an enormous company with tremendous resources. They could easily keep emulation for these older systems going.

It is irresponsible of Apple to create obsolescence of hardware by discontinuing operating system and technical support for older systems. This policy of Apple's creates more trash filling the landfills and is a waste of resources.

The solution is for Apple to make new software intelligently scaleable such that it recognizes the hardware it is being installed on and adjusts to fit within the memory footprint and hardware's capabilities. Yes, certain new features like transparent window shadows will not be available but there are many improvements which can be continued to offer for older hardware such as the folders in the new iOS which do not need any advanced hardware capability.

The benefit to Apple is they can continue getting sales of operating systems each year as they offer new versions of the OS with new features. Additionally Apple will gain more market penetration as the old hardware is kept active and passed down in families resulting in a larger user installed base. Charge for the technical support - obviously. Just keep offering AppleCare.

Apple should also encourage developers to support the furthest back operating systems and hardware possible.

 

[tatonka]

Are people really still amazed that Apple doesn't give two ribs about the pro market? Some people must be in deep denial to still not see that.
Apple wants to cater the ambitous amateures .. there just is not enough money in the pro market alone.

I love my MBP, but I wouldn't trust Apple with my business, as in base a coporate decision on an Apple product much less one that could eventually, maybe, potentially be released. I am fine with buying it for private purposes.

T.

 

[dethmaShine]

Will resellers be able to restock, though? If not, then it's not something to be relied upon. The supply of FCP 7 licences could run dry anytime.

I think Apple were right to release FCP X. Clearly software of this complexity needs to be used and have feedback and evolve over time, but the mistake was removing FCP 7 from normal distribution.
They should've said "Here's FCP X, it has about 75% of what FCP 7 does but it does it more efficiently, we're going to be building on this platform for years so start testing with it. We'll begin a transition now and in 12 months time you won't be able to buy FCP 7 anymore as we expect FCP X to be at feature parity by then, so get learning."

Given Apple is normally the master of transitions (OS 9 -> OS X, PPC -> Intel) I'm not sure how they've managed to screw this one up.

Wonderfully said. Probably the best post overall in this final cut pro tragedy.

Truly, Apple has been a master of a number of transitions but this was way too rude and rough. Unfortunately, this involved thousands of professionals who have invested hundreds of thousands or maybe millions of $s in their business which is more or less FCP dependant.

Not good Apple. You have learnt so much over the years, but still? FCP7 needs to come back.

 

[Popeye206]

Developer Cycles and Product releases for features don't always coincide.

It's a clear indication that they had a choice: Release in June or extend several Betas to key developers for the next 2 quarters and then release it, and still receive complaints for change.

They chose to release the new architecture and in a few weeks will come the Developer APIs to extend support so by the end of this quarter and entering the next quarter both 3rd parties and Apple will release plugins and major updates to this new flag ship editing software.

This ends the several years complaint that FCP is dead,etc., and opens a new can of worms on it not being feature perfect.

Guess what? List the number of major areas Apple is simultaneously competing on and then compare what Apple was doing back in 1998. Night and Day.

Apple is spewing out store after store, market after market for major target markets at a rate never seen in this corporation but it's never fast enough for some very vocal customers.

In 1998 Apple [as a former employee so I know wherefore I speak] had 3 months of capital to keep the doors open and now they have $70 Billion in the bank and have leap frog'd Microsoft in valuation. And all during one of the worst global recessions since The Great Depression.

Take a long pause and think about exactly what Apple has accomplished, all during Steve fighting for his own life.

Yet people continue to whine that this 1.0 product isn't the greatest solution for present and future approaches to NLE.

And all for $299. Truly pathetic.

I paid $299 in 1996 for Openstep User/Developer as a student before working at NeXT Inc.

Seriously, get some perspective folks.

Wow... do you have to be so realistic and level thinking?

I think you're dead on with this comment. I'm sure the tradeoff was wait forever to bring it all, or release what was ready, get feedback and continue adding the features.

Plus, since the Lean development process is a big deal now, they could be using that development methodology and it makes it easy to make these sort of decisions in order to hit deadlines.

It does suck they could not get it all in, but with all these changes, I'm sure in the long run it will work out and given the feedback, I'm sure they're in overdrive.

 

[tatonka]

Your idea is great, market a consumer application as Pro application. A pro application is for professionals, not consumers. If they wanted to make a consumer version, they've should've called it iMovie Pro or something...

Actually it is an ingenious marketing scheme to charge more. iMovie is what 19.99$ on the app store? iMovie Pro would go for maybe 99$. But an ambitous amateuer that wants to play with the big boys tools (and there is ton of those, amateuer, not tools) would find a way to justify 299$ as well.
In order to get those guys though, you need to create a pro image around the software (whether it acutally is pro level or not).

T.

 

[macsmurf]

Are people really still amazed that Apple doesn't give two ribs about the pro market? Some people must be in deep denial to still not see that.
Apple wants to cater the ambitous amateures .. there just is not enough money in the pro market alone.

I love my MBP, but I wouldn't trust Apple with my business, as in base a coporate decision on an Apple product much less one that could eventually, maybe, potentially be released. I am fine with buying it for private purposes.

T.

The funny thing is that when Apple make a statement, such as this FAQ, people will readily believe that this time they really mean it

It's all about risk vs. benefit. There seem to be a great deal of risk involved in taking Apple's public statements at face value.

 

[jmpnop]

If an application can be used by people to edit, it doesn't matter if it's 'pro' or 'consumer'. A great piece of software empowers the user. It doesn't matter whether they're 'pro' or 'consumer'. Sure, there are some features that a pro would need and a consumer wouldn't, but that's all to do with personal workflow. That differs from person to person.

Apple are right to provide basics and let third parties handle specialised, niche features and provide support for their own hardware. They haven't dropped the ball here. They've simply released a solid editing app that many people, for some bizarre reason, thought they could switch to right away.

It may be good for you but for 'pros' it isn't sufficient. Calling consumer application 'professional application' is just ridiculous. Remember 'pro' isn't a term added to make a name sound cooler like Apple's prefix 'i'.

 

[xStep]

FCPX is downgrade from FCP7. I don't really see the point of calling it Final Cut Pro since it no long caters the pro market which previous versions did.

What I got out the FAQ is that it will cater to the pro market, in the future, and for the added price of third party software. I wonder what it will cost to bring this 'Pro' software up to pro usability.

Does Final Cut Pro X support OMF, AAF, and EDLs?
Not yet. When the APIs for XML export are available, third-party developers will be able to create tools to support OMF, AAF, EDL, and other exchange formats. We have already worked with Automatic Duck to allow you to export OMF and AAF from Final Cut Pro X using Automatic Duck Pro Export FCP 5.0.

 

[linuxcooldude]

It may be good for you but for 'pros' it isn't sufficient. Calling consumer application 'professional application' is just ridiculous. Remember 'pro' isn't a term added to make a name sound cooler like Apple's prefix 'i'.

I'm sure changing the name will make all the difference in the world.

 

[iBug2]

Why is the timeline closed architecture, though?

Do you remember that's what drove people away from AVID to the old Final Cut?

What drove people away from AVID to the old Final Cut was the price.

"Regarding importing from Final Cut Pro 7, Apple says that due to the many changes there was no way to "translate" old projects without losing or changing data. So, Apple suggests that users continue to use Final Cut Pro 7 for existing projects."

That is really BAD because the next thing is Apple will of course stop supporting FCP7 and then when they upgrade their hardware you won't be able to run FCP7 on the new machines and your projects become so much trash.

That's what happens when an app is discontinued. But there are some ways to keep the old projects alive. FCP 7 works with Lion, so that means it'll work for 2 more years at least. If After Lion Apple switches to 64bit only mode, then it'll keep working on Lion and any hardware Lion supports, that means any hardware released in the next 2 years. That hardware will be able to work for at least 4-5 years without issues. So FCP 7 will be used in the next 6 years.

After that, one would need to run Lion on new hardware through virtual machines etc, to keep FCP 7 running.

 

[Skika]

FAQ summary:

Q: Does it have X/ Can i do X?

A:Not yet.

 

[JesterJJZ]

huh? class action lawsuit over what?

False marketing, advertisement? Something to that end. This product is not Final Cut Pro and they are selling it under that brand.

 

[Gareth-H]

Any thoughts on whether FCP6 is likely to be stuck with using Snow Leopard? We hadn't upgraded earlier (since it pretty much does everything we need it to) but since FCP X is a no-go due to missing features, I'm concerned that there's no way we can keep the OS up-to-date now we can't upgrade to FCP7.

 

[gkpm]

So the whole world knows FCP X doesn't yet have all the advanced pro features of previous versions.
Apple refunded those who complained.
There is now a FAQ saying what people should expect next.

But now the complaints are all about the name? Because they call it Pro?

Next people will be complaining that the MacBook Pro doesn't come with Fibre Channel interfaces or 10GbE...

 

[SirHaakon]

This product is not Final Cut Pro and they are selling it under that brand.

Lol. This product IS Final Cut Pro, because they own the name and can slap it on whatever they want. Just because you don't like the direction the software is going doesn't mean you can sue over it.

 

[toxotis70]

I am a PRO user and i prefer FCPX philosophy , speed and easy of use !

For my main job i wiil continue to work with old one, for a short period, but then i will go for the newer .

It is extremely fast, versatile and easy to use.

In a while, we will have support for extra hardware (video cards - external monitor) from AJa and other companies , there is already plugin for importing-exporting FCP 7 projetcs from automatic duck.

More plugins are near, at no cost (if you upgrade) ...

No one forced you to buy the new one...

 

[MrNomNoms]

And funny enough this whole fiasco could have been avoided had they provided the FAQ at the time the product was put on the AppStore so that customers knew what they were getting - a product that was very much work in progress.