As creative professionals in 2013 we often find ourselves bridging a divide, with Adobe’s products on one side and Apple’s on the other. I spend most of my time switching between Final Cut Pro X and After Effects (with Motion 5 thrown in for good measure). FCPX is by far my NLE of choice, and going back to FCP7 or Premiere feels like a trip back in time. Meanwhile, After Effects is still the reigning champ of the motion graphics world, so learning it is a must. But looking at these two applications side by side illustrates two very different philosophies when it comes to embracing change moving forward.
After Effects is an incredibly deep and useful piece of software with a history and code base that dates back over 20 years. Each successive release has added new features and workflow improvements while retaining practically everything that came before. It is in Adobe’s best interest to keep their customer base happy, and not rocking the boat seems to be their plan to achieve that (Creative Cloud subscription controversies notwithstanding).
The downside is that this strategy may ultimately hold Adobe back. Freelance editor and animator Lou Borella posted an interesting comparison video on Vimeo that highlights the performance differences between After Effects (CS6 and CC) and Apple’s Motion 5- it’s really worth a watch, and make sure you stick around to browse the comments. While both versions of AE struggle to play back a single HD video clip in his demonstration, Motion handles it effortlessly, even after he applies additional layers and filters during real time looping playback. His argument is that the legacy code in After Effects is preventing the program from fully embracing current hardware advances.
Apple, as we know, took a different route when Final Cut Pro was at a crossroads. FCP7 was stuck in 32-bit and could only address a fraction of the RAM installed in high end systems. Most material shot with newer cameras had to be transcoded to ProRes before editing could begin, which took many hours of productivity killing time. Apple responded with version X. Here are a few of my comments on the state of the transition back in September 2011:
I’ve said this before, but FCP X is not finished. It feels like a stable beta release, but one where many features are missing or incomplete. If I was forced to make a decision today to switch from FCP 7 to something else, the answer would be clear: X is not an option. But a year from now? Two years from now? Things could be entirely different. The question is whether or not the pro editing community can hold on that long.
It’s been two years, and things are indeed a lot different. Final Cut Pro has seen a steady march of point release updates (with a major revision coming next month alongside the new Mac Pro) and I’m using it for virtually every broadcast editing job that comes my way. Adobe Premiere and After Effects are great products and will continue to be the go-to tools for a large portion of the market. After Effects in particular is extremely powerful and I use it daily, although the lure of real time playback and a refined interface has me dipping more and more into Motion 5 lately.
I’m a big fan of Alex Gollner’s efforts to dig into Final Cut Pro X (and iMovie) to look for clues about upcoming versions. He’s also kept a close eye on Apple’s support site, and has noticed something interesting:
Although the most release note for Final Cut Server was archived in July, Apple are still making changes to FCS support documents. Hopefully to prepare for a December resurrection.
It’s a (very) long shot, but an intriguing one regardless. Alex has already found clues in iMovie 2013 that point to multi-user editing in FCP X 10.1. December can’t get here fast enough.