FCP Producer is pushing a web petition

FCP Producer is pushing the web petition to get us a 64 bit FCP 8. I have signed, but as of now there are only 147 signatures though!

Apple recently introduced a completely new version of Final Cut Pro that immediately replaced the previous one. Although modern and revolutionary in many ways, this new version X lacks at least 10 main features required by any professional who uses Final Cut on TV studios, Feature Film editing, Production and Post-Production houses. In order to keep expanding the numbers of Final Cut Pro editing suites on these places we request that the Final Cut Pro 7 application should be temporally available for free as a download to all of those who bought Final Cut Pro X, while these 10 features are not addressed in the X release. They are: Add ability to import and export XML files natively;Add ability to import previous Final Cut Pro projects natively;Add ability to export OMF files natively;Add ability to change a project’s frame rate after it’s been created; Add ability to read and write projects stored on an network or SAN volumes; Add ability to switch the Final Cut Pro X layout to a more traditional 2-monitor setup; Add ability to preview true video signal, independent from the 2-monitor setup; Add support for Multicam editing; Add support from capturing and recording to tape, not only via capture now but also via batch capture and print to tape natively; Add support for importing image sequence files such as DPX and OpenEXR;

Some very true facts.

Planet 5D rings in on FCP X

Planet 5D has a good article on the whole FCP X fiasco, though to me they are still a little too positive on the whole thing, while I am basically thinking this program will never be for pros!

Apple/Steve Jobs also realize that there will be a group of editors who leave and go to Adobe Premiere Pro or over to Avid – but they believe that the video editing market is going to be huge in the future and they have positioned iMovie to be the basic editor – and FCPX is the pro editor (which by the way imports iMovie assets – get the hint?).They will sell tons of copies of FCPX in the next 10 years and are not afraid to lose a few old fans along the way. They would have sold even more if they were to have gotten ownership from the editing community instead of taking it away. They’re going to have to go into major recovery mode or they’re going to lose a big hunk of the community – bigger than they were willing to lose in the first place.But I still believe that in the long run, in a year or so, FCPX will rock. I’m certainly using it now and will continue to explore and learn from those who have tutorials ready (more on that shortly too).


I still just don’t believe it can ever get as good as people think it will, too many fundamental problems!

It was to be a companion to FCP

If this article at MacRumors is to be believed what became iMovie 08 and later FCP X was supposed to be an app to quickly make rough cuts that would export to finishing in FCP. I wish that was all it was!

From that experience, First Cut was born which would let you import your raw footage and quickly skip through, organizing and building a rough edit. The intention originally was to then export to Final Cut Pro. At some point, Apple officially latched onto the project and turned it into the new iMovie ’08.

I just wish it had stayed that way!

High Definition has an article on FCP X

At times I find the article to be too positive, but it does have some choice things to say.

Which brings us on to the timeline – another massive bone-of-contention in the FCP community.  The notion of tracks has completely disappeared, principally because of the new ‘magnetic timeline’. Instead of FCP 7’s old ‘Clip Collision…’ message that either drove you mad, or was a useful warning (depending on your point-of-view) clips now move themselves out of the way – essentially creating new tracks as they go. There is no track routing so, for instance, you can’t control where your audio goes when you insert a clip. This is pretty horrible – for example, if you want to mute your sound effects you need to hunt through the timeline and disable each one individually, rather than just muting the track you put them all on – you can’t even rely on them being where you last saw them, as editing in the magnetic timeline may have moved them somewhere else. I’m not sure that the benefits of losing the Clip Collision dialog outweigh the problems the magnetic timeline causes though Apple says it’s working on a solution – I suspect this may just be a way of assigning audio to output tracks which won’t solve the layout problem I’ve just described. They also claim that Automatic Duck Pro Export will allow you to create and assign output tracks as a workaround, but I’m not sure that’s true…Editing is a little weird too, if you are used to the standard 3 point edit paradigm. It sort of still exists, but only as the illegitimate offspring of iMovie and FCP.


and

It feels, somehow, like Apple have taken the iMovie code and grafted three point editing onto it. I can see the point of the magnetic timeline, and it’s arguably better than a tracked timeline, but there was no need to replace the FCP 7 three (and four) point paradigm. FCP X’s implementation isn’t better – it seems to be a bit of a mess.

and

At the moment, you can’t set the start timecode of the timeline, so the usual broadcast requirement of programme material starting at 10:00:00:00 isn’t possible. Similarly, audio track assignment is a real problem until Apple releases an update that solves the issue. You can’t use a broadcast monitor or audio PPMs until there is a professional I/O unit supported and you’ll need the Automatic Duck software to interface to ProTools/SADiE for audio work and, potentially, your finishing solution (if you don’t finish picture in FCP X)

And the final thoughts.

The funny thing is, if Apple had released this as a replacement for Final Cut Express (which has also been discontinued) then the reviews would be glowing. They could have continued to sell FCP 7, and then release a ‘Pro’ version, with all these problems solved, in a year or so. I would certainly be surprised if any of next year’s Oscar nominees will be cut on FCP X.

Personally I think I like the program less, but I do agree with most points, and the should have saved some of this tech for a true pro Final Cut Pro instead of making it completely prosumer.

More on Final Cut Pro X

Larry Jordan has written a scathing article about the new Final Cut Pro X, and it really echoes what I feel about the program.

In FCP X, Apple got some things amazingly right. But they also got key features amazingly wrong. And if they don’t change course, this software, which has significant potential, is going to spin further and further out of control. At which point, its feature set is irrelevant, its reputation will be set. We’ll be looking at another Mac Cube.

And what they need to do immediately

1. Immediately return Final Cut Studio (3) to the market. If it is not compatible with Lion (and I don’t know whether it is or not) label it so. But put it back on store shelves so consumers have the ability to work with the existing version until FCP X is ready for prime time.2. Fund the development of a conversion utility – either at Apple or thru a 3rd-party – and announce the development with a tentative release date.3. Publicly announce a road-map for FCP X that just covers the next 3-4 months. Apple needs to be in damage control mode and the best way to defuse the situation is to communicate. Answering the question: “What features will Apple add to FCP X, and when?” will go a long way to calming people down.


And his conclusion:

This launch has been compared to Coca-Cola launching New Coke – resulting in a humiliating loss of market share.With Final Cut Pro X, however, the situation is worse — with New Coke, only our ability to sip soda was affected. With Final Cut Pro X, we are talking losing livelihoods.

Thanks for getting this out there Larry, I really appreciate you saying what needs to be said.