UPDATE
David Pogue, New York Times, has written an excellent followup article with Apple’s response to missing features in Final Cut Pro X.
Read it here: http://pogue.blogs.nytimes.com/2011/06/23/professional-video-editors-weigh-in-on-final-cut-pro-x/
– – –
Apple released Final Cut Pro X this morning at 5:30 AM LA time. You can read Apple’s announcement here — http://www.apple.com/pr/library/2011/06/21fcp.html
You can visit Apple’s new webpage here: http://www.apple.com/finalcutpro/
In three words – speed, power, cutting-edge.
The first time I saw Final Cut Pro X, back in February, this quote from the title of Stephen Ambrose’s book on the transcontinental railroad flashed into my head.
Just as the transcontinental railroad permanently changed 19th century America – in a wide variety of ways – Final Cut Pro X has the same capability.
During the last several months, I’ve had extensive discussions with engineers and product managers at Apple, read virtually all the Help files and, more recently, been running the software itself.
I’m knee-deep in a long newsletter which will provide a lot more detail when it comes out next week (subscribe for your FREE issue here: larryjordan.biz/newsletter), so here, in this blog, I just want to provide a bigger picture approach.
In every conversation I’ve had with Apple, each person stressed: “The easy thing would be to just create an incremental upgrade. But, we felt that while the current version of Final Cut held up well for the last ten years, it wasn’t ready for the next ten. We needed to design something from the ground up to take us into the next ten years.”
With this release, Apple made four significant changes in direction:
* For the first time, two different versions of FCP can coexist on the same system. I’ve been running FCP 7 and FCP X on the same system for months.
* Maxing out performance to take full advantage of current hardware
* Almost exclusive support for tapeless workflows
* Distribution via the App Store
FINAL CUT PRO 7 IS NOT DEAD
To me, this is one of the highlights!
Installing FCP X does not remove FCP 7. So you can take your own sweet time deciding when to make the switch. And, in fact, you can use FCP 7 where it makes sense and FCP X when that is a better choice. For the first time ever, we can have two different versions of FCP on the same system at the same time, without partitioning hard disks and jumping through hoops.
PERFORMANCE
Its no secret that Final Cut Pro took forever to accomplish some tasks. (I have it on good authority that many families were significantly augmented while waiting for the render bar to complete its measured progress.)
Plus, the 4 GB RAM limit caused projects to corrupt, files to mysteriously disappear and spawned a new breed of tech: the Final Cut guru, who, with an apparent laying on of the hands, could bring nearly dead projects back to life. (That last may be a dramatic overstatement, but I like the allusion.)
This new version flies. Whenever Final Cut needs to think, it does so seamlessly, in the background, with a little indicator that tells you how its doing and a complete dashboard for the curious who want to monitor their system.
It allows editing files natively, but prefers to convert them to ProRes – a decision that I agree with, for both performance and image quality reasons.
Once you edit with the magnetic timeline, you’ll never want to go back. And, while the concept of connected clips is a bit weird initially, the benefits these provide are so well-thought out and obvious that I stopped worrying about them after the first couple of days.
Nesting is improved. Audio filters are amazing and first-rate. There is much tighter integration with Motion and Compressor.
There are as many ways to edit in the new version as the old and more ways to trim. Trimming can even be in real-time or slow-motion. Old barriers such as clips in the Browser, still image sizes, clips in a project, and tracks have all fallen away.
The context-sensitive nature of the Viewer window, and the speed it responds, make me completely comfortable editing with only one image window.
The whole system is designed for speed.
And, when it comes to keyboard shortcuts, there are already hundreds in the system and the new process for creating shortcuts is just amazingly powerful – and easy to use.
NOTE: Remind me to mention how much I like the new audio meters – big, fat, large, readable, and adjustable.
SOME OLD FRIENDS DIDN’T MAKE IT
Soundtrack Pro, DVD Studio Pro, and Color are not in this release. (LiveType was discontinued when FCP 7 came out.)
We all have our favorites, but I will miss Soundtrack Pro the most.
HOWEVER, keep in mind that if you own this software now, you’ll still be able to use it with FCP X. But it is no longer available.
DEALING WITH THE IMOVIE MONKEY
Much ink has been wasted and many pixels have died in the flame debate that FCP X is just a larger form of iMovie.
Yes, they share a similar approach to the interface.
Yes, FCP X imports iMovie projects and media. No, it doesn’t import FCP 7 projects. Yes, Apple should figure out a way to provide an FCP 7 translator. It can’t be that hard.
However, think about this for a minute. iMovie has been out for, what, eight years with ZERO ability to upgrade to Final Cut? Doesn’t it make just a little bit of sense to provide an upgrade option for the millions of future editors out there?
Of course it does.
There’s such in increase in power stepping from iMovie – which I’ve never liked – up to FCP X, that it would be like moving from a bike to a motorcycle. Yes, they both have two wheels and a handlebar, but there’s a huge difference in power in the seat!
APPLE IS MOVING TO TAPELESS
If tapeless media is your life, it will take you a week to stop giggling once you fire up FCP X.
However, FCP X has only limited support for tape. Tape ingest is from FireWire-attached devices, and streaming-only, no timecode controlled positioning of ingest or output to tape.
I’m reminded of the hand-wringing that occurred when Apple dropped floppy disks for optical media “back in the day,” now that Apple has decreed that tape is dead.
In this case, though, I side with the “tapists.” Apple controls the eco-system of the Mac. They don’t control the eco-system of Hollywood; then, again, I’m not sure anyone does. I have clients today that are using 3/4″ Umatic cassettes for sound design and music composition, and EDL lists are used daily for conforming major feature films. Both those formats were declared dead AGES ago!
While FCP X can ingest from a Firewire-attached deck, its output options to tape are limited to live streaming.
This lack of support for layback to video tape using RS-422 control protocol with timecode accuracy gives the perception that Apple is not meeting the needs of professional output. It remains to be seen if companies like AJA, Matrox, or Blackmagic Design will step into the breech. If they do, great. If not, this will cause many of us problems.
However, if you are shooting tapeless, this new software is designed for you. Easy ingest, background transcoding, background rendering, background analysis… Very cool. And, best of all, you can stop or cancel a background process at any time.
Plus, if you are someone that likes to organize their files, FCP X supports that. If you HATE organization, FCP X will organize your files for you. Now, we have a choice.
DISTRIBUTION VIA THE APP STORE
This is a real biggie, as Apple explained it to me. Because no physical media is involved (think packages in an Apple Store), Apple can push out updates faster and at much lower cost because they are using the App Store.
In the past, Apple used a 18 month, or so, cycle between updates. Now, Apple is telling me they are hoping to do an update once or twice a year.
This ability to respond faster to the market and deliver economical updates has already born fruit with the new low prices for Final Cut, Motion, and Compressor.
This gives me lots of hope for the future.
MONKEY #2: APPLE DOESN’T CARE ABOUT THE PRO MARKET
Writing software like this is not easy, not fast, and not cheap. Its taken Apple several years, dozens of millions of dollars, and an engineering crew big enough to fill a small cruise ship.
You don’t go to that effort to meet the needs of a market you aren’t interested in.
Apple tells me they are committed to quickly improving this version and building on it. They tell me they are committed to making changes quickly and bringing them to market. They tell me they are interested in hearing our reactions to the software.
I believe them and look forward to them fulfilling their promises.
THINGS I DON’T LIKE
Final Cut Pro X is very impressive, but it isn’t perfect. There are a variety of design decisions that I disagree with – and I’ve shared these many times with Apple.
There’s no multicam support.
The audio capabilities in FCP X are far superior to FCP 7 in terms of technical specs and filters. But a completely unintuitive method for adding audio cross-dissolves and lack of support for track-based audio mixing leaves me fondly missing the power of Soundtrack Pro.
The process of adding an audio cross-fade is dangerous, unintuitive and dumb.
Worse, there’s no native way to export a project to send it to either Soundtrack Pro or ProTools for sound mixing.
I’ve already mentioned there is no native ability to layback to tape using timecode control.
The autosave is great, but what we need is the ability to freeze specific project builds so that the client can review and approve a version and KNOW that if the project is opened in the future that nothing will be changed.
Preferences need to include the ability to use frames, not just hundredths of a second for all timing decisions.
A clip needs to remember the In and the Out when you deselect it.
There needs to be a way to remove a project from the Project List without having to resort to the Finder.
There needs to be a preference setting so that all new projects default to Stereo vs Surround.
There are others, and I’m sure you’ll have your own list.
SHOULD YOU BUY IT?
Look, you and I both know you’re going to buy it regardless of what I say. So here’s my main point. I think that within the next 18 months virtually all of us will be running FCP X and wondering how we lived without it.
It’s that good.
Is it perfect? No.
Whether this is right for you depends upon what you are doing. Here’s a list to help you decide:
* If you are exclusively shooting tapeless and outputting to the web, this product was designed with you in mind. However, some vendors – Sony comes first to mind – need to update their drivers to work with FCP X. Be sure to check the Sony website for updates before moving to FCP X.
* If you are shooting tape and sending XDCAM SR tapes to the network, you should stay with FCP 7 and complain to Apple to add improved support for video-tape output.
* If you are shooting (H)DSLR cameras, you’ll love the automatic transcoding, auto-image correction, and blinding speed built into the new system.
* If you shoot on DV or HDV and export your files for the web, Final Cut Pro X can make your life a lot simpler.
* If you shoot tapeless and distribute your files on DVD, you can use FCP X for your edit, export your footage, compress on Compressor (either old or new) and use DVD Studio Pro to create your DVD.
* If you simply need to burn your project to either DVD or Blu-ray, the new Final Cut makes this easy. If you need to author a DVD, or Blu-ray, you’ll need to use either DVD Studio Pro or Adobe Encore.
* If you are working in iMovie, you should step up to the new version and put some power in your pictures.
* If you are doing projects with complex audio mixes, stay with FCP 7 until Apple gives us improved audio mixing and audio export support.
* If you live for speed and high image quality, you have a new love in your life.
* If you are in the middle of an FCP 7 project, you should stay there. Don’t even think about trying to port your project into the new system. Finish your project. FCP X will be here when you are done.
* If you are responsible for meeting incredibly tight deadlines, stay with your current system. Buy FCP X – learn it. See what you like and what you don’t. Then, as it makes sense to you, roll it into production.
In other words, consider that your job is telling stories with pictures. Final Cut Pro X is another tool in your toolkit that can help you with your story-telling. For some of us, its perfect now. For others, it needs to mature a bit.
But, when the credits roll, it isn’t the power of the tool, its the power of your story that makes people care.
I’ll have much more in my newsletter next week. In the meantime, let me know what you think.
Larry
P.S. I’ve spent the last six weeks creating training for Final Cut Pro X. 88 movies, over eleven hours of in-depth training. All ready, right now, for you to discover the power and capability of this new software. Visit: larryjordan.biz/fcpx
214 Responses to Ain't Nothing Like It In the World
← Older Comments Newer Comments →As with FCP 7, can you put all your files in an external drive… edit part of the project… eject the drive… move that drive to another Mac… open the project… continue to work exactly where you left off?
Yes, but… it uses a different file structure. You would need to put both the Events folder and the Projects folder on the second drive.
Larry
Omg, everyone, and Larry, you’ve got to lean back and just have a laugh.
The guys at Conan have come through hilariously. Enjoy.
http://www.youtube.com/watch?v=sRzLP0FJ82I
Wow. I don’t think I’ve ever seen a flame war of this magnitude before. People are not just attacking Apple, but anyone with a dissenting opinion, using completely uncivil and insulting rhetoric. How do you keep your composure?
The sad part about this whole mess is: as people raise their pitchforks in response to the missing I/O features, they have completely missed the fact that the actual EDITING engine is amazing–elegant, powerful, and fun. I’ve been testing the program for 3 days now, and your review is pretty darn accurate.
I’m an editing professional, but this week, with all the whining and flaming going on, I’m kinda embarrassed to call myself such.
Larry, last question from me on this topic, please: Are .MOV files still “native” in FCP X? In other words, will a camera like the JVC GY-HM700U shoot files that can simply be dragged and dropped into FCP X?
Based on my experience creating my training, FCP X plays all QuickTime files with no problem – PROVIDED you have the driving installed on your system. For instance, RED and XDCAM EX files require updated drivers from Red, and Sony.
The problem isn’t the QuickTime file, its support for the codec (driver) that the video is encoded with. You’ll need to either check Apple — http://www.apple.com/finalcutpro/resources — or your camera vendor for compatibility and updates.
Larry
Larry,
I have heard conflicting reports on installing FCP X with FCP 7 still on the main OS drive. I read the support document detailed here http://support.apple.com/kb/HT4722. Did you go through these steps before you installed FCP X or did you just install it side by side on the main OS drive. If so are both programs working well?
What do you recommend?
Thanks for all the great info.
Ryan
Ryan:
I just installed it side-by-side. However, I was not installing the release version. I am not a fan of partitioned drives for a wide variety of reasons.
However, as I have not installed the release version yet and I DO need to run FCP 7, I don’t know what really works and what doesn’t. For this reason, I don’t have a recommendation.
Larry
Wow… I can its true what they say that “anyone can be bought”.
Larry, I’m speechless. Just speechless.
I wonder how much did they paid you to back this backwards, pro-sumer-oriented, impotent excuse for a professional NLE ? I watched your videos on Lynda back in the day. No amount of backpedalling can white-wash your bought-and-sold support such a poorly designed contender.
Most people would agree you can’t put a price on professional credibility. I guess you’re not one of them.
Daniel:
I’m sorry you feel that way. FCP X is not yet for everyone and it is not ready for many pros. But it is useful for many others. All I can do is show you how it works and let you decide for yourself.
Larry
Thanks Larry,
Its indeed a very neutral article. I’ve read lots of articles but yours gave the real picture.
Cheers !
Larry,
Do you feel like Atlas with the new world of editing on your shoulders?
Here are 30 more questions:
1. Cannot open both versions at the same time: FCP 7 and FCP X?
2. FCP X media on the applications local drive instead of a stratch disk?
3. Reconnect Media-Media Management?
4. Consolidating projects?
5. Saving different versions?
6. Restore to a saved version?
7. Importing to other software: Pro Tools, After Effects, Resolve, DVD authoring?
8. Red Support?
9. Color correcting on a reference monitor?
10. Checking for interlacing?
11. Mirroring to another monitor?
12. Organizing multiple audio tracks per your previous tutorials?
13. Layered Photoshop import support?
14. Blending modes in video inspector? Limited contextual menu?
15. Custom video presets?
16. Irregular frame rates?
17. No true native editing?
18. Everything is automaticly transcoded and converted to Apple Pro Res in the background?
19. Transcoding storage problem?
20. Every project is locked to the machine?
21. Shared workflow? – Can’t exchange data with other users?
22. Audio export format choices?
23. Who is King of the Hill now for post production software? Adobe?
24. Film based workflows?
25. Apple’s new version release history – 2 years?
26. No volume licencing?
27. Has FCP 7 certification stopped?
28. Baselight color correcting for FCP X coming?
29. Four point, and replace editing gone?
30. Work-space is not customizable?
Thanks for the big shoulder,
David
David:
Take a look at this post from David Pogue of the New York Times: http://pogue.blogs.nytimes.com/2011/06/23/professional-video-editors-weigh-in-on-final-cut-pro-x/
Many of your questions are answered there.
Specifically, the following points in your list are incorrect: 2, 14, 16, 17, 18, 20, 21, 29.
And many answers to more of your questions are answered in the Pogue article.
Larry
larry
Many people here are way out of line with the strong personal attacks against a person who is obviously trying to be very helpful. How many other people are answering all these questions and concerns on a Saturday? I’ve found one. And his name isn’t Steve.
I’ve never met Larry Jordan. However, it’s obvious that Larry is caught in a difficult position. It’s also obvious he’s too civilized to unload against the multiple attacks on his professional credibilty.
He has stated several times that he pointed out certain flaws to Apple.
Look, Larry can lead Apple to water. But he can’t make them drink.
Larry,
First of all, I have to say I am impressed about the way you manage to read all comments and answer to everybody. I command you for that.
And I agree with what everybody as said since my last comment, with the exception of a couple people. And I disagree with most of your positions.
Second of all, you’re answer was beside the point but you’re absolutely right: I am absolutely responsible for my professional choices. But to my defense, Premiere Pro wasn’t considered a viable option up until the past couple of years, and having been lucky enough to work continuously for the past 6 years in an FCP based company, I haven’t had many occasions to flex my Avid muscle memory. But as I said, I’ve been meaning to flex that muscle for a while, and I’m excited to learn Premiere. I needed an incentive to stop procrastinating, I just never thought that that incentive would come from… Apple.
And I’m not angry or in pain, really. I know what I have to do to stay ahead of the game. But I do feel for the fresh out of school and in debt young AE’s I work with who’ve been dedicated to FCP for a couple of years and who are now back to square one.
On that note, you’re telling people that everybody will be working on FCPX 18 months from now. And unless you know something from Apple that we don’t (and I hope you do), you know it is impossible in its actual form. Therefore you are partly responsible of the a choice that some of us are going to make and that is going to impact their professional career. And you become part of the problem.
Also you keep saying to deceived (yes, deceived) FCP professionals that FCPX might not be useful to them, but will be to some. And I just want/need to ask: Who are those people who are working alone and who manages to make a leaving producing single camera shows, not properly color balance (no I/O, no XML, no EDL), not properly sound mix (no Soundtrack and no OMF), and not delivering tapes (again no I/O) to the networks, or to Blue-Ray or DVD (no DVDstudioPro, although there is many alternative for that) to their clients? Who are those people Larry? And why are they so important to Apple that they’re being favored that way?
I want to know because if they are the same people who’ve been telling for the past week to broadcast professionals like me that the missing features were useless anyway, that we don’t see the big picture, I’d like to tell them this:
If you didn’t know how to use any of the now missing features and why they were used… I would seriously re-evaluate your FCP7, AND Post-Production expertise.
If you have problem keeping your FCP7 project in sync… Man, you kinda suck.
Same thing if you can’t move things around in your project quickly and keep everything organized.
FCPX is not a v.1. It would be had Apple not killed FCP7.
And it’s not the interface the problem (although an interface being fully clickable is hardly exciting)
And finally, Larry (and everybody else who triumphantly says so hoping to end the debate), YES, Apple will fix FCP. As they did when they released Imovie X without any of the features of Imovie 6 that were useful to home editor. It took some years but they reluctantly brought back all of those features. Coincidently it was the same team who worked on Imovie X who just committed FCPX. And do we really have to go through that long and painful process with FCP? We waited 10 years to see FCP becoming the tool it became with version 7, only to see it thrown out the widow. Why should we wait another 10 years and maybe take the same risk again? Some Editor at my company have already started to look for Avid jobs once their assignment ends. Why should we keep working on a platform that, even if it will remain useable for few years, is now officially obsolete? And if my boss can’t find experience FCP editors (that he couldn’t find anywhere 10 years ago) he’ll have to switch platform too. Now, are you still sure everybody will be on FCPX 18 months from now?
Again Larry, I hope you know something that we don’t. If not, I suggest you start creating Avid and Premiere Pro tutorials. I’ll buy the Premiere ones.
Have a good day.
Alex.
Alex:
Thanks for writing.
What I’m saying is that if FCP X fits your workflow, use it. If it doesn’t, don’t. I am not using FCP X in my production system because it lacks features that I need. On the other hand, I am using FCP X in my training system so that I can continue to learn it and teach others.
It is up to Apple to decide what features to add or fix. All I can do is provide comments back to Apple and keep everyone informed on what I learn.
For now, I’m urging most people to wait on making a decision on what to do for a while. Let the dust settle. Let’s see what Apple releases. Let’s give the third-party developers time to catch up.
Personally, I think that in 3-4 months the situation will be radically different than it is today. But, in fact, only time will tell.
I’ve been using FCP 7 quite happily since it was released. I plan to continue to do so, to give FCP X time to mature.
Larry