The Hobbit

df_hobbit_1Peter Jackson’s The Hobbit: An Unexpected Journey was one of the most anticipated films of 2012. It broke new technological boundaries and presented many creative challenges to its editor. After working as a television editor, Jabez Olssen started his own odyssey with Jackson in 2000 as an assistant editor and operator on The Lord of the Rings trilogy. After assisting again on King Kong, he next cut Jackson’s Lovely Bones as the first feature film on which he was the sole editor. The director tapped Olssen again for The Hobbit trilogy, where unlike the Rings trilogy, he will be the sole editor on all three films.

Much like the Rings films, all production for the three Hobbit films was shoot in a single eighteen month stretch. Jackson employed as many as 60 RED Digital Cinema EPIC cameras rigged for stereoscopic acquisition at 48fps – double the standard rate of traditional feature photography. Olssen was editing the first film in parallel with the principal photography phase. He had a very tight schedule that only allowed about five months after the production wrapped to lock the cut and get the film ready for release.

To get The Hobbit out on such an aggressive schedule, Olssen leaned hard on a post production infrastructure built around Avid’s technology, including 13 Media Composers (10 with Nitris DX hardware) and an ISIS 7000 with 128TB of storage. Peter Jackson’s production facilities are located in Wellington, New Zealand, where active fibre channel connections tie Stone Street Studio, Weta Digital, Park Road Post Production and the cutting rooms to the Avid ISIS storage. The three films combined, total 2200 hours (1100 x two eyes) of footage, which is the equivalent of 24 million feet of film. In addition, an Apace active backup solution with 72TB of storage was also installed, which could immediately switch over if ISIS failed.

The editorial team – headed up by first assistant editor Dan Best – consisted of eight assistant editors, including three visual effects editors. According to Olssen, “We mimicked a similar pipeline to a film project. Think of the RED camera .r3d media files as a digital negative. Peter’s facility, Park Road Post Production, functioned as the digital lab. They took the RED media from the set and generated one-light, color-corrected dailies for the editors. 24fps 2D DNxHD36 files were created by dropping every second frame from the files of one ‘eye’ of a stereo recording. For example, we used 24fps timecode with the difference between the 48fps frames being a period instead of a colon. Frame A would be 11.22.21.13 and frame B would be 11:22:21:13. This was a very natural solution for editing and a lot like working with single-field media files on interlaced television projects. The DNxHD files were then delivered to the assistant editors, who synced, subclipped and organized clips into the Avid projects. Since we were all on ISIS shared storage, once they were done, I could access the bins and the footage was ready to edit, even if I were on set. For me, working with RED files was no different than a standard film production.”

df_hobbit_2Olssen continued, “A big change for the team since the Rings movies is that the Avid systems have become more portable. Plus the fibre channel connection to ISIS allows us to run much longer distances. This enabled me to have a mobile cart on the set with a portable Media Composer system connected to the ISIS storage in the main editing building. In addition, we also had a camper van outfitted as a more comfortable mobile editing room with its own Media Composer; we called it the EMC – ‘Editorial Mobile Command’. So, I could cut on set while Peter was shooting, using the cart and, as needed, use the EMC for some quick screening of edits during a break in production. I was also on location around New Zealand for three months and during that time I cut on a laptop with mirrored media on external drives.”

The main editing room was set up with a full-blown Nitris DX system connected to a 103” plasma screen for Jackson. The original plan was to cut in 2D and then periodically consolidate scenes to conform a stereo version for screening in the Media Composer suite. Instead they took a different approach. Olssen explained, “We didn’t have enough storage to have all three films’ worth of footage loaded as stereo media, but Peter was comfortable cutting the film in 2D. This was equally important, since more theaters displayed this version of the film. Every few weeks, Park Road Post Production would conform a 48fps stereo version so we could screen the cut. They used an SGO Mistika system for the DI, because it could handle the frame rate and had very good stereo adjustment tools. Although you often have to tweak the cuts after you see the film in a stereo screening, I found we had to do far less of that than I’d expected. We were cognizant of stereo-related concerns during editing. It also helped that we could judge a cut straight from the Avid on the 103” plasma, instead of relying on a small TV screen.”

df_hobbit_3The editorial team was working with what amounted to 24fps high-definition proxy files for stereo 48fps RED .r3d camera masters. Edit decision lists were shared with Weta Digital and Park Road Post Production for visual effects, conform and digital intermediate color correction/finishing at a 2K resolution. Based on these EDLs, each unit would retrieve the specific footage needed from the camera masters, which had been archived onto LTO data tape.

The Hobbit trilogy is a heavy visual effects production, which had Olssen tapping into the Media Composer toolkit. Olssen said, “We started with a lot of low resolution, pre-visualization animations as placeholders for the effects shots. As the real effects started coming in, we would replace the pre-vis footage with the correct effects shots. With the Gollum scenes we were lucky enough to have Andy Serkis in the actual live action footage from set, so they were easy to visualize how the scene would look. But other CG characters, like Azog, were captured separately on a Performance Capture stage. That meant we had to layer separately-shot material into a single shot. We were cutting vertically in the timeline, as well as horizontally. In the early stages, many of the scenes were a patchwork of live action and pre-vis, so I used PIP effects to overlay elements to determine the scene timing. Naturally, I had to do a lot of temp green-screen composites. The dwarves are full-size actors and for many of the scenes, we had to scale them down and reposition them in the shot so we could see how the shots were coming together.”

As with most feature film editors, Jabez Olssen likes to fill out his cut with temporary sound effects and music, so that in-progress screenings feel like a complete film. He continued, “We were lucky to use some of Howard Shore’s music from the Rings films for character themes that tie The Hobbit back into The Lord of the Rings. He wrote some nice ‘Hobbity’ music for those. We couldn’t use too much of it, though, because it was so familiar to us! The sound department at Park Road Post Production uses Avid Pro Tools systems. They also have a Media Composer connected to the same ISIS storage, which enabled the sound editors to screen the cut there. From it, they generated QuickTime files for picture reference and audio files so the sound editors could work locally on their own Pro Tools workstations.”

Audiences are looking forward to the next two films in the series, which means the adventure continues for Jabez Olssen. On such a long term production many editors would be reluctant to update software, but not this time. Olssen concluded, “I actually like to upgrade, because I look forward to the new features. Although, I usually wait a few weeks until everyone knows it’s safe. We ended up on version 6.0 at the end of the first film and are on 6.5 now. Other nonlinear editing software packages are more designed for one-man bands, but Media Composer is really the only software that works for a huge visual effects film. You can’t underestimate how valuable it is to have all of the assistant editors be able to open the same projects and bins. The stability and reliability is the best. It means that we can deliver challenging films like The Hobbit trilogy on a tight post production schedule and know the system won’t let us down.”

Originally written for Avid Technology, Inc.

©2013 Oliver Peters

Phil Spector

df_philspector_3Phil Spector became famous as a music industry icon. The legendary producer, who originated the “wall of sound” production technique of densely-layered arrangements, worked with a wide range of acts, including the Ronettes, the Righteous Brothers and the Beatles. Unfortunately, fame can also have its infamous side. Spector abruptly came back into public notice through the circumstances of the 2003 death of actress Lana Clarkson and his subsequent criminal trials, culminating in a 2009 conviction for second-degree murder.

The story of his first murder trial and the relationship between Spector (Al Pacino) and defense attorney Linda Kenney Baden (Helen Mirren) form the basis for the new film by HBO Films. Phil Spector, which is executive produced by Barry Levinson (Rain Man), was directed by celebrated screenwriter/director David Mamet (The Unit, The Shield, Hannibal, Wag the Dog). Rather than treat it as a biopic or news story, Mamet chose to take a fictionalized approach that chronicles Spector’s legal troubles as a fall from grace.

One key member of the production team was editor Barbara Tulliver (Too Big to Fail, Lady in the Water, Signs), who has previously collaborated with Mamet. She started as a film editor working on commercials in New York, but quickly transitioned into features. According to Tulliver, “I assisted on David’s first two films and then cut my first feature as an editor with him, so we have established a relationship. I also cut Too Big to Fail for HBO and brought a lot of the same editorial crew for this one, so it was like a big family.”

df_philspector_4As with most television schedules, Phil Spector was shot and completed in a time frame and with a budget more akin to a well-funded independent feature, rather than a typical studio film. Tulliver explained, “Our schedule to complete this film was between that of a standard TV project and a feature. If a studio film has six weeks to complete a mix, a film like this would have three. The steps are the same, but the schedule is shrunk. I was cutting during the thirty-day production phase, so I had a cut ready for David a week after he wrapped. HBO likes to see things early, so David had his initial cut done after five weeks, instead of the typical ten-week time frame. Like any studio, HBO will give us notes, but they are very respectful of the filmmakers, which is why they can attract the caliber of talent that they do for these films. At that point we went into a bit of a hold, because David wanted some additional photography and that took awhile until HBO approved it.”

The production itself was handled like a film shoot using ARRI Alexa cameras in a single-camera style. An on-set DIT generated the dailies used for the edit. Although you wouldn’t consider this a visual effects film, it still had its share of shots. Tulliver said, “There were a lot of comps that are meat-and-potatoes effects these days. For instance, the film was shot in New York, so in scenes when Spector arrives at the courthouse in Los Angeles, the visual effects department had to build up all of the exteriors to look like LA. There are a number of TV and computer screens, which were all completed in post. Plus a certain amount of frame clean-ups, like removing unwanted elements from a shot.”

df_philspector_2Mamet wrote a very lean screenplay, so the length of the cut didn’t present any creative challenges for Tulliver. She continued, “David’s scripts are beautifully crafted, so there was no need to re-arrange scenes. We might have deleted one scene. David makes decisions quickly and doesn’t overshoot. Like any director, he is open to changes in performance; but, the actors have such respect for his script, that there isn’t a lot of embellishment that might pose editing challenges in another film. Naturally with a cast like this, the performances were all good. The main challenge we had, was to find ways to integrate Spector’s songs into the story. How to use the music to open up scenes in the film and add montages. This meant all of the songs had to be cleared. We were largely successful, except with John Lennon’s Imagine, where Yoko Ono had the final say. Although she was open to our using the song, ultimately she and David couldn’t agree to how it would be integrated creatively into the film.”

Phil Spector was cut digitally on an Avid Media Composer. Like many feature editors, Barbara Tulliver started her career cutting film. She said, “I’m one of the last editors to embrace digital editing. I went into it kicking and screaming, but so did the directors I was working with at the time. When I finally moved over to Avid, they were pretty well established as the dominant nonlinear edit system for films. I do miss some things about editing on film, though. There’s a tactile sense of the film that’s almost romantic. Because it takes longer to make changes, film editing is more reflective. You talk about it more and often in the course of these discussions, you discover better solutions than if you simply tried a lot of variations. In the film days, you talked about the dramatic and emotional impact of these options. This is still the case, but one has to be more vigilant about making that happen – as opposed to just re-cutting a scene twenty different ways, because it is easy and fast – and then not know what you are looking at anymore.”

df_philspector_1“Today, I cut the same way I did when I was cutting film. I like to lay out my cut as a road map. I’ll build it rough to get a sense of the whole scene, rather than finesse each single cut as I go. After I’ve built the scene that way, I’ll go back and tweak and trim to fine-tune the cut. Digital editing for me is not all about the bells-and-whistles. I don’t use some of the Avid features, like multi-camera editing or Script Sync. While these are great features, some are labor-intensive to prepare. When you have a minimal crew without a lot of assistants, I prefer to work in a more straightforward fashion.”

Tulliver concluded with this thought, “Although I may be nostalgic about the days of film editing, it would be a complete nightmare to go back to that. In fact, several years ago one director was interested in trying it, so I investigated what it would take. It’s hard to find the gear anymore and when you do, it hasn’t been properly maintained, because no one has been using it. Not to mention finding mag stripe and other materials that you would need. The list of people and labs that actually know how to handle a complete film project is getting smaller each year, so going back would just about be impossible. While film might not be dead as a production medium, it has passed that point in post.”

Originally written for Digital Video magazine.

©2013 Oliver Peters

DaVinci Resolve Workflows

df_resolve_main

Blackmagic Design’s purchase of DaVinci Systems put a world class color grading solution into the hands of every video professional. With Resolve 9, DaVinci sports a better user interface that makes it easy to run, regardless of whether you are an editor, colorist or DIT working on set.  DaVinci Resolve 9 comes in two basic Mac or Windows software versions, the $995 paid and the free Lite version. The new Blackmagic Cinema Camera software bundle also includes the full (paid) version, plus a copy of Ultrascope. For facilities seeking to add comprehensive color grading services, there’s also a version with Blackmagic’s dedicated control surface, as well as Linux systems configurations.

Both paid and free versions of Resolve (currently at version 9.1) work the same way, except that the paid version offers larger-than-HD output, noise reduction and the ability to tap into more than one extra GPU card for hardware acceleration. Resolve runs fine with a single display card (I’ve done testing with the Nvidia GT120, the Nvidia Quadro 4000 and the ATI 5870), but requires a Blackmagic video output card if you want to see the image on a broadcast monitor.

Work in Resolve 9 generally flows left-to-right, through the tabbed pages, which you select at the bottom of the interface screen. These are broken into Media (where you access the media files that you’ll be working with), Conform (importing/exporting EDL, XML and AAF files), Color (where you do color correction), Gallery (the place to store and recall preset looks) and Deliver (rendering and/or output to tape).

Many casual users employ Resolve in these two ways: a) correcting camera files to send on to editorial, and b) color correction roundtrips with NLE software. This tutorial is intended to highlight some of the basic workflow steps associated with these tasks. Resolve is deep and powerful, so spend time with the excellent manual to learn its color correction tools, which would be impossible to cover here.

Creating edit-ready dailies – BMCC (CinemaDNG media)

The Blackmagic Cinema Camera can record images as camera raw, CinemaDNG image sequences. Resolve 9 can be used to turn these into QuickTime or MXF media for editing. Files may be graded for the desired final look at this point, or the operator can choose to apply the BMD Film preset. This log preset generates files with a flat look comparable to ARRI Log-C. You may prefer this if you intend to use a Log-to-Rec709 LUT (look up table) in another grading application or a filter like the Pomfort Log-to-Video effect, which is available for Final Cut Pro 7/X.df_resolve_1_sm

Step 1 – Media: Drag clip folders into the Media Pool section.

Step 2 – Conform: Skip this tab, since the clips are already on a single timeline.

df_resolve_3_smStep 3 – Color: Make sure the camera setting (camera icon) for the clips on the timeline are set to Project. Open the project settings (gear icon). Change and apply these values: 1) Camera raw – CinemaDNG; 2) White Balance – as shot; 3) Color Space and Gamma – BMD Film.

Step 4 – Deliver: Set it to render each clip individually, assign the target destination and frame rate and the naming options. Then choose Add Job and Start Render.

The free version of Resolve will downscale the BMCC’s 2.5K-wide images to 1920×1080. The paid version of Resolve will permit output at the larger, native size. Rendered ProRes files may now be directly imported into FCP 7, FCP X or Premiere Pro. Correct the images to a proper video appearance by using the available color correction tools or filters within the NLE that you are using.

Creating edit-ready dailies – ARRI Alexa / BMCC (ProRes, DNxHD media)

df_resolve_2_smBoth the ARRI Alexa and the Blackmagic Cinema Camera can record Apple ProRes and Avid DNxHD media files to onboard storage. Each offers a similar log gamma profile that may be applied during recording in order to preserve dynamic range. Log-C for the Alexa and BMD Film for Blackmagic. These profiles facilitate high-quality grading later. Resolve may be used to properly grade these images to the final look as dailies are generated, or it may simply be used to apply a viewing LUT for a more pleasing appearance during the edit.

Step 1 – Media: Drag clip folders into the Media Pool section.

Step 2 – Conform: Skip this tab, since the clips are already on a single timeline.

Step 3 – Color: Make sure the camera setting for the clips on the timeline are set to Project. Open the project settings and set these values: 3D Input LUT – ARRI Alexa Log-C or BMD Film to Rec 709.

df_resolve_4_smStep 4 – Deliver: Set it to render each clip individually, assign the target destination and frame rate and the naming options. Check whether or not to render with audio. Then choose Add Job and Start Render.

The result will be new, color corrected media files, ready for editing. To render Avid-compatible MXF media for Avid Media Composer, select the Avid AAF Roundtrip from the Easy Setup presets. After rendering, return to the Conform page to export an AAF file.

Roundtrips – using Resolve together with editing applications

DaVinci Resolve supports roundtrips from and back to NLEs based on EDL, XML and AAF lists. You can use Resolve for roundtrips with Apple Final Cut Pro 7/X, Adobe Premiere Pro and Avid Media Composer/Symphony. You may also use it to go between systems. For example, you could edit in FCP X, color correct in Resolve and then finish in Premiere Pro or Autodesk Smoke 2013. Media should have valid timecode and reel IDs to enable the process to work properly.

df_resolve_5_smIn addition to accessing the camera files and generating new media with baked-in corrections, these roundtrips require an interchange of edit lists. Resolve imports an XML and/or AAF file to link to the original camera media and places those clips on a timeline that matches the edited sequence. When the corrected (and trimmed) media is rendered, Resolve must generate new XML and/or AAF files, which the NLE uses to link to these new media files. AAF files are used with Avid systems and MXF media, while standard XML files and QuickTime media is used with Final Cut Pro 7 and Premiere Pro. FCP X uses a new XML format that is incompatible with FCP 7 or Premiere Pro without translation by Resolve or another utility.

Step 1 – Avid/Premiere Pro/Final Cut Pro: Export a list file that is linked to the camera media (AAF, XML or FCPXML).

Step 2- Conform (skip Media tab): Import the XML or AAF file. Make sure you have set the options to automatically add these clips to the Media Pool.

Step 3 – Color: Grade your shots as desired.df_resolve_6_sm

Step 4 – Deliver: Easy Setup preset – select Final Cut Pro XML or Avid AAF roundtrip. Verify QuickTime or MXF rendering, depending on the target application. Change handle lengths if desired. Check whether or not to render with audio. Then choose Add Job and Start Render.

df_resolve_9_smStep 5 – Conform: Export a new XML (FCP7, Premiere Pro), FCPXML (FCP X) or AAF (Avid) list.

The roundtrip back

The reason you want to go back into your NLE is for the final finishing process, such as adding titles and effects or mixing sound. If you rendered QuickTime media and generated one of the XML formats, you’ll be able to import these new lists into FCP7/X or Premiere Pro and those applications will reconnect to the files in their current location. FCP X offers the option to import/copy the media into its own managed Events folders.

df_resolve_7_smIf you export MXF media and a corresponding AAF list with the intent of returning to Avid Media Composer/Symphony, then follow these additional steps.

Step 1 – Copy or move the folder of rendered MXF media files into an Avid MediaFiles/MXF subfolder. Rename this copied folder of rendered Resolve files with a number.

Step 2 – Launch Media Composer or Symphony and return to your project or create a new project.df_resolve_8_sm

Step 3 – Open a new, blank bin and import the AAF file that was exported from Resolve. This list will populate the bin with master clips and a sequence, which will be linked to the new MXF media rendered in Resolve and copied into the Avid MediaFiles/MXF subfolder.

Originally written for DV magazine / Creative Planet Network

©2013 Oliver Peters

Zero Dark Thirty

df_zdt_1Few films have the potential to be as politically charged as Zero Dark Thirty. Director Kathryn Bigelow (The Hurt Locker, K-19: The Widowmaker) and producer/writer Mark Boal (The Hurt Locker, In the Valley of Elah) have evaded those minefields by focusing on the relentless CIA detective work that led to the finding and killing of Osama bin Laden by US Navy SEALs. Shot and edited in a cinema verite style, Zero Dark Thirty is more of a suspenseful thriller, than an action-adventure movie. It seeks to tell a raw, powerful story that’s faithful to the facts without politicizing the events.

The original concept started before the raid on bin Laden’s compound occurred. It was to be about the hunt, but not finding him, after a decade of searching. The SEAL raid changed the direction of the film; but, Bigelow and Boal still felt that the story to be told was in the work done on the ground by intelligence operatives that led to the raid. Zero Dark Thirty is based on the perspective of CIA operative Maya (Jessica Chastain), whose job it is to find terrorists. The Maya character is based on a real person.

Zero Dark Thirty was filmed digitally, using ARRI Alexa cameras. This aided Kathryn Bigelow’s style of shooting by eliminating the limitation of the length of film mags. Most scenes were shot with four cameras and some as many as six or seven at once. The equivalent of 1.8 million feet of film (about 320 hours) was recorded. The production ramped up in India with veteran film editor Dylan Tichenor (Lawless, There Will Be Blood) on board from the beginning.

According to Tichenor, “I was originally going to be on location for a short time with Kathryn and Mark and then return to the States to cut. We were getting about seven hours of footage a day and I like to watch everything. When they asked me to stay on for the entire India shoot, we set up a cutting room in Chandigarh, added assistants and Avids to stay up to camera while I was there. Then I rejoined my team in the States when the production moved to Jordan. A parallel cutting room had been set up in Los Angeles, where the same footage was loaded. There, the assistants could also help pull selects from my notes, to make going through the footage and preparing to cut more manageable.”df_zdt_3

William Goldenberg (Argo, Transformers: Dark of the Moon) joined the team as the second editor in June, after wrapping up Argo. Goldenberg continued, “This film had a short post schedule and there was a lot of footage, so they asked me to help out. I started right after they filmed the Osama bin Laden raid scene, which was one of the last locations to be shot and the first part of the film that I edited. The assembled film without the raid was about three hours long. There was forty hours of material just for the raid and this took about three weeks to a month to cut. After I finished that, Dylan and I divided up the workload to refine and hone scenes, with each making adjustments on the other’s cuts. It’s very helpful to have a second pair of eyes in this situation, bouncing ideas back and forth.”

As an Alexa-based production, the team in India, Jordan and London included a three-man digital lab. Tichenor explained, “This film was recorded using ARRIRAW. With digital features in the past, my editorial team has been tasked to handle the digital dailies workload, too. This means the editors are also responsible for dealing with the color space workflow issues and that would have been too much to deal with on this film. So, the production set up a three-person team with a Codex Digilab and Colorfront software in another hotel room to process the ARRIRAW files. These were turned into color-corrected Avid DNxHD media for us and a duplicate set of files for the assistants in LA.” Director of photography Greig Fraser (Snow White and the Huntsman, Killing Them Softly) was able to check in on the digilab team and tweak the one-light color correction, as well as get Tichenor’s input for additional shots and coverage he might need to help tell the story.

df_zdt_4Tichenor continued, “Kathryn likes to set up scenes and then capture the action with numerous cameras – almost like it’s a documentary. Then she’ll repeat that process several times for each scene. Four to seven camera keep rolling all day, so there’s a lot of footage. Plus the camera operators are very good about picking up extra shots and b-roll, even though they aren’t an official second unit team. There are a lot of ways to tell the story and Kathryn gave us – the editors – a lot of freedom to build these scenes. The objective is to have a feeling of ‘you are there’ and I think that comes across in this film. Kathryn picks people she trusts and then lets them do their job. That’s great for an editor, but you really feel the responsibility, because it’s your decisions that will end up on the screen.”

Music for the film was also handled in an unusual manner. According to Goldenberg, “On most films a composer is contracted, you turn the locked picture over to him and he scores to that cut. Zero Dark Thirty didn’t start with a decision on a composer. Like most films, Dylan and I tried different pieces of temp music under some of the scenes that needed music. Of all the music we tried, the work of Alexandre Desplat (Argo, Moonrise Kingdom) fit the best. Kathryn and Mark showed Alexandre a cut to see if he might be interested. He loved it and found time in his schedule to score the film. Right away he wrote seven pieces that he felt were right. We cut those in to fit the scene lengths, which he then used as a template for his final score. It was a very collaborative process.”

Company 3 handled the digital intermediate mastering. Goldenberg explained, “The nighttime raid scene has a very unique look. It was very dark, as shot. In fact, we had to turn off all the lights in the cutting room to even see an image on the Avid monitors. Company 3 got involved early on by color timing about ten minutes of that footage, because we were eager and excited to see what the sequence could look like when it was color timed. When it came to the final DI, the film really took on another layer of richness. We’d been looking at the one-light images so long that it actually took a few screenings to enjoy the image that we’d been missing until then.”

df_zdt_2Both Tichenor and Goldenberg have been cutting on Avid Media Composers for years, but this film didn’t tax the capabilities of the system. Tichenor said, “This isn’t an effects-heavy film. Some parts of the stealth helicopters are CG, but in the Avid, we mainly used effects for some monitor inserts, stabilization and split screens.” Goldenberg added, “One thing we both do is build our audio tracks as LCR [left, center, right channel] instead of the usual stereo. It takes a bit more work to build a dedicated center channel, but screenings sound much better.”

Avid has very good multicamera routines, so I questioned whether these were of value with the number of cameras being used. Tichenor replied, “We grouped clips, of course, but not actual multicam. You can switch cameras easily with a grouped clip. I actually did try for one second on a scene to see if I could use the multicam split screen camera display for watching dailies, but no, there was too much going on.” Goldenberg added, “There are some scenes that – although they were using multiple cameras – the operators would be shooting completely different things. For instance, actors in a car with one camera and other cameras grabbing local flavor and street life. So multicam or group clips were less useful in those cases.”

The film’s post schedule took about four months from the first full assembly until the final mix. Goldenberg said, “I don’t think you can say the cut was ever completely locked until the final mix, since we made minor adjustments even up to the end; but, there was a point at one of the internal screenings where we all knew the structure was in place. That was a big milestone, because from there, it was just a matter of tightening and honing. The story felt right.” Tichenor explained, “This movie actually came together surprisingly well in the time frame we had. Given the amount of footage, it’s the sort of film that could easily have been in post for two years. Fortunately with this script and team, it all came together. The scenes balanced out nicely and it has a good structure.”

For addition stories:

DV’s coverage of Zero Dark Thirty’s cinematography

An interview with William Goldenberg about Argo

FXGuide talks about the visual effects created for the film.

New York Times articles (here and here) about Zero Dark Thirty

Originally written for DV magazine / Creative Planet Network

©2012, 2013 Oliver Peters

Offline to online with 4K

df_4k_wkflw_01

The 4K buzz  seems to be steam-rolling the industry just like stereo3D before it. It’s too early to tell whether it will be an immediate issue for editors or not, since 4K delivery requirements are few and far between. Nevertheless, camera and TV-set manufacturers  are building important parts of the pipeline. RED Digital Cinema is leading the way with a post workflow that’s both proven and relatively accessible on any budget. A number of NLEs support editing and effects in 4K, including Avid DS, Autodesk Smoke, Adobe Premiere Pro, Apple Final Cut Pro X, Grass Valley EDIUS and Sony Vegas Pro.

Although many of these support native cutting with RED 4K media, I’m still a strong believer in the traditional offline-to-online editing workflow. In this post I will briefly outline how to use Avid Media Composer and Apple FCP X for a cost-effective 4K post pipeline. One can certainly start and finish a RED-originated project in FCP X or Premiere Pro for that matter, but Media Composer is still the preferred creative  tool for many editing pros. Likewise, FCP X is a viable finishing tool. I realize that statement will raise a few eyebrows, but hear me out. Video passing through Final Cut is very pristine, it supports the various flavors of 2K and 4K formats and there’s a huge and developing ecosystem of highly-inventive effects and transitions. This combination is a great opportunity to think outside of the box.

Offline editing with Avid Media Composer

df_4k_wkflw_04_smAvid has supported native RED files for several versions, but Media Composer is not resolution independent. This means RED’s 4K (or 5K) images are downsampled to 1080p and reformatted (cropped or letterboxed) to fit into the 16:9 frame. When you shoot with a RED camera, you should ideally record in one of their 4K 16:9 sizes. The native .r3d files can be brought into Media Composer using the “Link to AMA File(s)” function. Although you can edit directly with AMA-linked files, the preferred method is to use this as a “first step”. That means, you should use AMA to cull your footage down to the selected takes and then transcode the remainder when you start to fine tune your cut.

Avid’s media creation settings are the place to adjust the RED debayer parameters. Media Composer supports the RED Rocket card for accelerated rendering, but without it, Media Composer can still provide reasonable speed in software-only transcoding. Set the debayer quality to 1/4 or 1/8, and transcoding 4K clips to Avid DNxHD36 for offline editing will be closer to real-time on a fast machine, like an 8-core Mac Pro. This resolution is adequate for making your creative decisions.df_4k_wkflw_02_sm

df_4k_wkflw_08_smWhen the cut is locked, export an AAF file for the edited sequence. Media should be linked (not embedded) and the AAF Edit Protocol setting should be enabled. In this workflow, I will assume that audio post is being handled by an audio editor/mixer running a DAW, such as Pro Tools, so I’ll skip any discussion of audio. That would be exported using standard AAF or OMF workflows for audio post. Note that all effects should be removed from your sequence before generating the AAF file, since they won’t be translated in the next steps. This includes any nested clips, collapsed tracks and speed ramps, which are notorious culprits in any timeline translation.

Color grading with DaVinci Resolve

df_4k_wkflw_03_smBlackmagic Design’s DaVinci Resolve 9 is our next step. You’ll need the full, paid version (software-only) for bigger-than-HD output. After launching Resolve, import the Avid AAF file from Resolve’s conform tab. Make sure you check “link to camera files” so that Resolve connects to the original .r3d media and not the Avid DNxHD transcodes. Resolve will import the sequence, connect to the media and generate a new timeline that matches the sequence exported from Media Composer. Make sure the project is set for the desired 4K format.

df_4k_wkflw_09_smNext, open the Resolve project settings and adjust the camera raw values to the proper RED settings. Then make sure the individual clips are set to “project” in their camera settings tab. You can either use the original camera metadata or adjust all clips to a new value in the project settings pane. Once this is done, you are ready to grade the timeline as with any other production. Resolve uses a very good scaling algorithm, so if the RED files were framed with the intent of resizing and repositioning (for example, 5K files that are to be cropped for the ideal framing within a 4K timeline), then it’s best to make that adjustment within the Resolve timeline.df_4k_wkflw_05_sm

Once you’ve completed the grade, set up the render. Choose the FCP XML easy set-up and alter the output frame size to the 4K format you are using. Start the render job. Resolve 9 renders quite quickly, so even without a RED Rocket card, I found that 4K ProRes HQ or 4444 rendering, using full-resolution debayering, was completed in about a 6:1 ratio to running time on my Mac Pro. When the renders are done, export the FCP XML (for FCP X) from the conform tab. I found I had to use an older version of this new XML format, even though I was running FCP X 10.0.7. It was unable to read the newest version that Resolve had exported.

Online with Apple Final Cut Pro X

df_4k_wkflw_11_smThe last step is finishing. Import the Resolve-generated XML file, which will in turn create the necessary FCP Event (media linked to the 4K ProRes files rendered from Resolve) and a timeline for the edited sequence. Make sure the sequence (Project) settings match your desired 4K format. Import and sync the stereo or surround audio mix (generated by the audio editor/mixer) and rebuild any effects, titles, transitions and fast/slo-mo speed effects. Once everything is completed, use FCP X’s share menu to export your deliverables.

©2013 Oliver Peters