The editing of feature films is a small niche of the overall market for editing software, yet companies continue to highlight features edited with their software as a form of aspirational marketing to attract new users. Avid Technology has had plenty of competition since the start of the company, but the majority of mainstream feature films are still edited using Avid Media Composer software. Lightworks and Final Cut Pro “legacy” have their champions (soon to be joined by FCP X and Premiere Pro CC), but Media Composer has held the lead – at least in North America – as the preferred software for feature film editors.
Detractors of Avid like to characterize these film editors as luddites who are resistant to change. They like to suggest that the interface is stodgy and rigid and just not modern enough. I would suggest that change for change’s sake is not always a good thing. Originally Final Cut Pro got a foothold, because it did well with file-based workflows and was very cheap compared to turnkey workstations running Media Composer or Film Composer. Those days are long gone, so trying to make the argument based on cost alone doesn’t go very far.
Editing speed is gained through familiarity and muscle memory. When you hire a top-notch feature editor, you aren’t hiring them for their software prowess. Instead, you are hiring them for their mind, ideas and creativity. As such, there is no benefit to one of these editors in changing to another piece of software, just because it’s the cool kid on the block. Most know how they need to manipulate the software tools so well, that thinking about what to do in the interface just disappears.
Change is attractive to new users, with no preconceived preferences. FCP X acolytes like to say how much easier it is to teach new users FCP X than a track-based system, like FCP 7, Premiere Pro or Media Composer. As someone who’s taught film student editing workshops, my opinion is that it simply isn’t true. It’s all in what you teach, how you teach it and what you expect them to accomplish. In fact, I’ve had many who are eager to learn Media Composer, precisely because they know that it continues to be the “gold standard” for feature film editing software.
There are some concrete reasons why film editors prefer Media Composer. For many, it’s because Avid was their first NLE and it felt logical to them. For others, it’s because Avid has historically incorporated a lot of user input into the product. Here are a dozen factors that I believe keep the equation in favor of Avid Media Composer.
1. Film metadata – At the start of the NLE area, Avid was an offline editing system, designed to do the creative cut electronically. The actual final cut for release was done by physically conforming (cutting) camera negative to match the rough cut. Avid built in tools to cut at 24fps and to track the metadata back to film for frame-accurate lists that went to the lab and the negative cutter. Although negative cutting is all but dead today, this core tracking of metadata benefits modern versions of Media Composer and is still applicable to file-based workflows.
2. Trimming – Avid editors rave about the trim mode in Media Composer. It continues to be the best there is and has been augmented by Smart Tools for FCP-style contextual timeline editing. Many editors spend a lot of time trimming and nothing matches Media Composer.
3. Logical layout – When Avid started out, they sought the direct input from many working editors and this helped the interface evolve into something totally logical. For example, the keyboard position of JKL (transport controls) or mark/clear/go-to in/out is based on hand positions when placed on the keyboard and not an arbitrary choice by a software designer. If you look at the default keyboard map in Media Composer, there are fewer layers than the other apps. I would argue that Media Composer’s inherent design makes more layers unnecessary. In fact, more layers become more confusing.
4. Script integration – Early on, Avid’s designers looked at how an actual written script might be used within the software. This is completely different than simply attaching copied-and-pasted text to a clip. With Media Composer, you can set up the bin with the actual script pages and link clips to the text of the dialogue. This is included with the base software as a manual process, but if you want to automate the linking, then the optional ScriptSync add-on will lighten the load. A second dialogue-driven option, PhraseFind, is great for documentary filmmakers. Some editors never use these features, but those that do, wouldn’t want to work any other way.
5. Built-in effect tools – The editorial team on most features gets involved in creating temporary visual effects. These are placeholders and style ideas meant to help the director and others visualize the effects. Sometimes these are editorial tricks, like an invisible split screen to combine different takes. The actual, final effect is done by the visual effects compositors. Avid’s internal tools, however, allow a talented film editor or assistant editor, to temp in an effect at a very high quality level. While Media Composer is certainly not a finishing tool equal to Avid DS (now EOL’ed) or Autodesk Smoke, the internal tools surpass all other desktop offline editors. FCP X requires third-party plug-ins or Motion 5 and Premiere Pro CC requires After Effects. With Media Composer, you have built-in rotosplining, tracking, one of the better keyers, stabilization and more. All without leaving the primary editing interface.
6. Surround mixing – Often film editors will build their rough cut with LCR (left-center-right) or full 5.1 surround panning. This helps to give a better idea of the theatrical mix and preps a sequence for early screenings with a preview or focus group audience. Other systems let you work in surround, too, but none as easily as with Media Composer, assuming you have the right i/o hardware.
7. Project sharing – You simply cannot share the EXACT SAME project file among simultaneous, collaborative users with any other editing application in the same way as you can with Media Composer and Avid’s Unity or Isis shared storage networks. Not every user needs that and there are certainly functional alternatives for FCP and Premiere Pro, as well as Media Composer. For film editors, the beauty of the Avid approach, is that everyone on the team can be looking at the exact same project. When changes are made to a sequence for a scene and the associated bin is saved, that updated info ripples to everyone else’s view. Large films may have as many as 15 to 20 connected users, once you tally editors, assistants and visual effects editors. This function is hard to duplicate with any alternative software.
8. Cross-platform and easy authorization – Media Composer runs under both Mac OS X and Windows on a wide range of machines. This makes it easy for editors on location to shift between a desktop workstation and a laptop, which may be of differing OS platforms. In the past, software licensing was via a USB license key (dongle), but newer versions use software authorization to activate the application. The software may be installed on any number of machines, with one active and authorized at any given time. De-activation and re-activation only takes a few seconds if you are connected to the Internet.
9. Portability of projects and media – Thanks to Avid’s solid media management with internal media databases, it’s easy to move drives between machines with no linking issues. Keep a common and updated project file on two machines and you can easily move a media drive back and forth between them. The software will instantly find all the correct media when Media Composer is launched. In addition, Avid has held one of the best track records for project interchange among older and newer versions.
10. Interoperability with lists – Feature film workflows are all about “playing well with others”. This means industry-standard list formats, like EDLs, AAFs and OMFs. I wish Media Composer would also natively read and write XMLs, but that’s a moving target and generally not as widely accepted in the facilities that do studio-level work. The other standards are all there and built into the tools. So sending lists to a colorist or audio editor/mixer requires no special third-party software.
11. Flexible media architecture – Avid has moved forward from the days when it only handled proprietary Avid media formats. Thanks to AMA, many native camera file formats and QuickTime codecs are supported. Through a licensing deal with Apple, even ProRes is natively supported, including writing ProRes MXF files on Apple workstations. This gives Media Composer wider support for professional codecs than nearly every other editing application. On top of that, you still have Avid’s own DNxHD, one of the best compression schemes currently in professional film and video use.
12. Robust – In most cases, Media Composer is a rock-solid application, with minimal hiccups and crashes. Avid editors have become very used to reliability and will definitely pipe up when that doesn’t happen. Generally Avid editors do not experience the sorts of RAM leaks that seem to plaque other editing software.
For the sake of full disclosure, I am a member of one of the advisory councils that are part of the Avid Customer Association. Obviously, you might feel that this taints what I’ve written above. It does not.
I’ve edited with Avid software since the early 90s, but I’ve edited for years with other applications, too. Most of the last decade leading up to Apple’s launch of Final Cut Pro X was spent on FCP “legacy”. The last couple of years have been spent trying to work the kinks out of FCP X. I’ve cut feature films on Media Composer, FCP 4-7, FCP X and even a Sony BVE-9100. I take a critical view towards all of them and go with what is best for the project.
Even though I don’t use many of the Avid-specific features mentioned above, like ScriptSync, I do see the strengths and why other film editors wouldn’t want to use anything else. My main goal here was to answer the question I hear so often, which is, “Why do they still use Avid?” I hope I’ve been able to offer a few answers.
For some more thoughts, take a look at these videos about DigitalFilm Tree’s transition from FCP to Media Composer and Alan Bell’s approach to using Avid products for cutting films like “The Hunger Games: Catching Fire”.
©2014 Oliver Peters