NLE Tips – Week 2

df_nle2_1_sm

Adobe Premiere Pro – Stacked Sequences

If you are used to editing in Adobe Premiere Pro or Apple Final Cut Pro “legacy”, then you are familiar with the concept of tabbed sequences. That is, you can have several open sequences, which each appear as a tab in the timeline window. This lets editor work between them, using copy and paste functions or compare one version of an edit to another. (Click images for an expanded view.)

Adobe’s interface design is based on dockable windows. In Premiere Pro, this means you can arrange the window layout in various custom workspace configurations that are conducive to your personal style or task needs. Sequences can be torn off into separate window elements. They may then be docked as a tab or embedded into any of four sides of the window as a separate pane within that window. Therefore, you can easily dock two sequences on top of each other within the same timeline window. When you do this, the focus of the sequence viewer and the effects control panel will follow whichever clip is selected by the editor in either sequence.

df_nle2_2_smLet’s say that you like to work from a “selected takes” sequence to a second sequence that is a “cutdown” of these selects. Stack one sequence above the other and then simply drag a clip from sequence 1 to sequence 2. Or highlight a clip in sequence 1, copy it and paste it to sequence 2. This also makes it easy to re-arrange the order of clips from one sequence to the other, when building stories based on soundbite and voice-over elements.

In another example, you might have two versions of an edit, such as a long-form cut for the web and a :30 cut for commercial TV. Each will have the same effects applied to shots that are common to both versions. Stack the sequences and open the effects controls. As you click on a clip, the effects that have been applied are revealed in the control panel. Or you can apply new effects to that clip by adding them to this open window.

df_nle2_3_smOnce you’ve applied and adjusted effects in the long-form cut, select the effects in that window and copy them. Then click on the same shot in the second sequence. The effect control window has been “refocused” on the other clip and is therefore empty. Paste the matching effect(s) to the empty effects control panel. Now the shot in the short-form cut will match the appearance of that same shot from the long-form cut. All done by simply moving back and forth between the two stacked sequences in the timeline window.

©2014 Oliver Peters

NLE Tips – Week 1

df_nle1_1_sm

Avid Media Composer Pointers

Getting better results out of your editing experience means learning a few useful tricks. For the next few posts, I’ll offer some suggestions intended to improve your efficiency on several popular editing applications. This first post covers three quick tips with Avid Media Composer. (Click images for an expanded view.)

Film strips

df_nle1_3_smOne of the features of Apple’s FCP X that I really like is the way the selected clip is displayed when the “event” browser (bin) is set to the list view. The selected clip is shown at the top of the browser window as a film strip covering the length of that clip. This makes it very easy to look at the strip and identify at a glance that the shot starts as a wide and zooms to a close-up. The Avid frame view won’t give you such information without scrubbing. But did you know there’s a similar film strip solution in Media Composer?

Most editors are used to double-clicking a clip in a bin to load it into the source viewer. For many, it’s a habit that ignores another approach. When selecting a clip in a bin, simply hit the enter key to load it into the viewer. No need to click or double-click. That’s the first step in this tip.

df_nle1_2_smThe Avid timeline window always loads two timelines – the edited sequence and the source. You can toggle between source and edit timelines with a keystroke. The timeline window can also be set to display a “film” video track. When doing so, you get a film strip view of the entire timeline. When you view the source side of the timeline window, the result is a film strip display of the entire source clip. By leaving the timeline window toggled to the source view with the film track enabled, you can quickly go through your bin selections using the enter key and checking out the clip in this film strip display. This will give you a fast way to review your footage with minimal scrubbing and clicking.

The Find menu

df_nle1_4_smWhen you call up the Media Composer Find menu (cmd-F on a Mac), you get several search options, including Phrase Find, if you’ve purchased that option and have indexed the audio files. Find works with more than Phrase Find, though. It can search for clips across all bins, but it also allows you to search for any text in locators (markers). If you’ve placed locators in your sequence and labelled these with text info, simply type the text into the Find menu search field, click the Find button and your play head will jump to that locator in the timeline.

Master bus

df_nle1_5_smWith Media Composer 7, Avid has added a master bus to the audio mixer panel. Aside from controlling overall levels, this bus will also accept real-time audio plug-ins from Media Composer’s standard set (RTAS) or from compatible third-party audio filters. I often will add a basic compressor/limiter to my mixes and with the new master bus, Avid has given me an ideal place for it.

Some additional Media Composer tips here and here.

If you are serious about your Media Composer chops, here are three great books that will help you up your game.

Avid Uncut: Workflows, Tips, and Techniques from Hollywood Pros (Steve Hullfish)

Avid Agility: Working Faster and More Intuitively with Avid Media Composer, Third Edition (Steven Cohen)

Avid Media Composer 6.x Cookbook  (Ben Hershleder)

df_nle1_6

©2014 Oliver Peters

FCP X Screen Layouts

df_fcpxscrns_1_sm

One of the things I really liked about Final Cut Pro “legacy” was the ability to create and customize numerous screen layouts. By rearranging its collection of tabbed and floating windows, it was easy to design and save numerous, task-specific, personalized screen layouts of the user interface. When I edit, I prefer to work on dual-display workstations, so I can lay out my tools with plenty of screen real estate. This usually means source bins and clips in one screen and the viewers and timeline in the other.

This level of interface customization is one of the features that I miss in Final Cut Pro X. Apple’s basic design for FCP X is intended to optimize it for single-display use, especially iMacs and MacBook Pros. The user interface for FCP X is more static than FCP “legacy” – using fly-out panels instead of moveable, floating, tabbed or docking windows. Nevertheless, if you have a dual-screen set-up, there are actually quite a few variations that the interface enables. A nice feature is that some of the show/hide toggles can be mapped to the keyboard. For now, you can’t save configurations, but it is reasonably quick to open, close and swap interface elements. (Click any of the images for an expanded view.)

df_fcpxscrns_2_sm

One interesting concept is that you can access various open FCP X Libraries using Mission Control. It’s not always fool-proof and I haven’t found it all that useful, but it is possible.

df_fcpxscrns_3_sm

In a typical two-display workstation with the main menu on the right display, you can open the viewers or event browser on the secondary display. That’s left in this example, with the events set to display on the secondary monitor. The event browser includes a panel that displays the libraries, events, keyword collections and smart collections. A button in the lower left corner of the interface lets you hide this panel. Doing so sets the browser focus only on the clips for the selected location and thus reduces clutter.

df_fcpxscrns_4_sm

The event browser can be set to display clips as skimmable, filmstrip thumbnails or as a list of clips. In the list view, the selected clip is displayed as a single filmstrip across the top of the event browser. The viewer can be set to be a single, unified viewer that toggles between clips and the timeline. Alternatively, a second event viewer can be opened for a traditional 2-up source/record display.

df_fcpxscrns_5_sm

You may also choose to display the viewers on the secondary display, which leaves the timeline and events on the main display. Video scopes are tied to the viewers and can be displayed in a horizontal (next to the image) or vertical (under the image) position.

df_fcpxscrns_6_sm

Some plug-ins use on-screen controls. One such filter is Hawaiki Color – a color grading tool. Its OSC may be displayed around the image or fullscreen as an image overlay. With the viewer on the secondary screen and scopes enabled, the editor maintains focus only on one screen while color correcting shots.

df_fcpxscrns_7_sm

The timeline display offers several clip height options. The smallest is the “chiclet” view. The timeline clips can be expanded with other views that emphasize more of the picture information or more of the audio waveforms. In addition, video animation can be revealed for a clip. This will display keyframes for in-timeline adjustments.

df_fcpxscrns_8_sm

I recently discovered that the order of which monitor is considered the primary and secondary display can be swapped. Simply drag the main window by the top header bar to the other monitor. As you do, the window on the secondary display automatically shifts to the opposite monitor. Then, click the green plus symbol at the top corner of the window to have it properly fill the screen. This example demonstrates that the fullscreen viewer window can be shifted onto either screen.

df_fcpxscrns_9_sm

In this final example, the viewer/timeline and event browser (on the secondary display) are shifted from one screen to the next.

©2014 Oliver Peters

Comparing Final Cut Pro X, Media Composer and Premiere Pro CC

df_nle_1_sm

The editing world includes a number of software options, such as Autodesk Smoke, Grass Valley EDIUS, Lightworks, Media 100, Sony Vegas and Quantel. The lion’s share of editing is done on three platforms: Apple Final Cut Pro, Avid Media Composer or Adobe Premiere Pro. For the last two years many users have been holding onto legacy systems, wondering when the dust would settle and which editing tool would become dominant again. By the end of 2013, these three companies released significant updates that give users a good idea of their future direction and has many zeroing in on a selection.

df_nle_11_sm

Differing business models

Adobe, Apple and Avid have three distinctly different approaches. Adobe and Avid offer cross-platform solutions, while Final Cut Pro X only works on Apple hardware. Adobe offers most of its content creation software only through a Creative Cloud subscription. Individual users have access to all creative applications for $49.99 a month (not including promotional deals), but when they quit subscribing, the applications cease to function after a grace period. Users may install the software on as many computers as they like (Mac or PC), but only two can be activated at any time.

Apple’s software sells through the Mac App Store. Final Cut Pro X is $299.99 with another $49.99 each for Motion and Compressor. Individual users may install and use these applications on any Mac computers they own, but enterprise users are supposed to purchase volume licenses to cover one installation per computer. With the release of FCP X 10.1, it appears that Apple is offering updates at no charge, meaning that once you buy Final Cut, you never pay for updates. Whether that continues as the official Apple policy from here on is unknown. FCP X uses a special version of XML for timeline interchange with other applications, so if you need to send material via EDL, OMF or AAF – or even interchange with previous versions of Final Cut Pro – you will need to augment FCP X with a variety of third-party utilities.

Avid Media Composer remains the only one of the three that follows a traditional software ownership model. You purchase, download and install the software and activate the license. You may install it on numerous Macs and PCs, but only one at a time can be activated. The software bundle runs $999 and includes Media Composer, several Avid utilities, Sorenson Squeeze, Avid FX from BorisFX and AvidDVD by Sonic. You can expand your system with three extra software options: Symphony (advanced color correction), ScriptSync (automated audio-to-script alignment) and PhraseFind (a dialogue search tool). The Symphony option also includes the Boris Continuum Complete filters.

Thanks to Avid’s installation and activation process, Media Composer is the most transportable of the three. Simply carry Mac and Windows installers on a USB key along with your activation codes. It’s as simple as installing the software and activating the license, as long as any other installations have been de-activated prior to that. While technically the FCP X application could be moved between machines, it requires that the new machine be authorized as part of a valid Apple ID account. This is often frowned upon in corporate environments. Similarly, you can activate a new machine as one of yours on a Creative Cloud account (as long as you’ve signed out on the other machines), but the software must be downloaded again to this local machine. No USB key installers here.

df_nle_5_sm

Dealing with formats

All three applications are good at handling a variety of source media codecs, frame rates and sizes. In some cases, like RED camera files, plug-ins need to be installed and kept current. Both Apple and Avid will directly handle some camera formats without conversion, but each uses a preferred codec – ProRes for Final Cut Pro X and DNxHD for Media Composer. If you want the most fluid editing experience, then transcode to an optimized codec within the application.

Adobe hasn’t developed its own mezzanine codec. In fact, Premiere Pro CC has no built-in transcoding tools, leaving that instead to Adobe Prelude or Adobe Media Encoder. By design, the editor imports files in their native format without transcoding or rewrapping and works with those directly in the sequence. A mix of various formats, frame rates, codecs and sizes doesn’t always play as smoothly on a single timeline as would optimized media, like DNxHD or ProRes; but, my experience is that of these three, Premiere Pro CC handles such a mix the best.

Most of us work with HD (or even SD) deliverables, but higher resolutions (2K, UHD, 4K) are around the corner. All three NLEs handle bigger-than-HD formats as source media without much difficulty. I’ve tested the latest RED EPIC Dragon 6K camera files in all three applications and they handle the format well. Both Adobe and Apple can output bigger sequence sizes, too, such as 2K and 4K. For now, Avid Media Composer is still limited to HD (1920 x 1080 maximum) sequences and output sizes. Here are some key features of the most recent updates.

df_nle_3_sm

Adobe Premiere Pro CC (version 7.2.1)

The current build of Premiere Pro CC was released towards the end of 2013. Adobe has been enhancing editing features with each new update, but two big selling points of this version are Adobe Anywhere integration and Direct Link between Premiere Pro CC and SpeedGrade CC. Anywhere requires a shared server for collaborative workflows and isn’t applicable to most users who don’t have an Anywhere infrastructure in place. Nevertheless, this adds the client-side application integration, so those who do, can connect, sign in and work.

df_nle_7_smOf more interest is Direct Link, which sends the complete Premiere Pro CC timeline into SpeedGrade CC for color correction. Since you are working directly with the Premiere Pro timeline, SpeedGrade functions with a subset of its usual controls. Operations, like conforming media to an EDL, are inactive. Direct Link facilitates the use of various compressed codecs that SpeedGrade wouldn’t normally handle by itself, since this is being taken care of by Premiere Pro’s media engine. When you’ve completed color correction, the saved timeline is sent back to Premiere Pro. Each clip has an applied Lumetri filter that contains grading information from SpeedGrade. The roundtrip is achieved without any intermediate rendering.

df_nle_6_smThis solution is a good first effort, but I find that the response of SpeedGrade’s controls via Direct Link are noticeably slower than working directly in a SpeedGrade project. That must be a result of Premiere Pro working in the background. Clips in Premiere Pro with applied Lumetri effects also require more resources to play well and rendering definitely helps. The color roundtrip results were good in my tests, with the exception of any clips that used a filter layer with a LUT. These displayed with bizarre colors back in Premiere Pro.

You can’t talk about Premiere Pro without addressing Creative Cloud. I still view this as a “work in progress”. For instance, you are supposed to be able to sync files between your local drive and the Cloud, much like DropBox. Even though everything is current on my Mac Pro, that tab in the Creative Cloud application still says “coming soon”. Others report that it’s working for them.

df_nle_2_sm

Apple Final Cut Pro X (version 10.1)

This update is the tipping point for many FCP 7 users. Enough updates have been released in over two years to address many of the concerns professional editors have expressed. 10.1 requires an operating system update to Mavericks (10.9 or later) and has three marquee items – a revised media structure, optimization for 4K and overall better performance. It is clear that Apple is not about to change the inherent design of FCP X. This means no tracks and no changes to the magnetic timeline. As with any update, there are plenty of small tweaks, including enhanced retiming, audio fades on individual channels, improved split edits and a new InertiaCam stabilization algorithm.

df_nle_9_smThe most obvious change is the move from separate Events and Projects folders to unified Libraries, similar to Aperture. Think of a Library as the equivalent to a Final Cut Pro 7 or Premiere Pro CC project file, containing all data for clips and sequences associated with a production. An FCP X Library as viewed in the Finder is a bundled file, which can be opened using the “show package contents” Finder command. This reveals internal folders and files for Events, Projects and aliases linked to external media files. Imported files that are optionally copied into a Library are also contained there, as are rendered and transcoded files. The Libraries no longer need to live at the root of a hard drive and can be created for individual productions. Editors may open and close any or all of the Libraries needed for an edit session.

df_nle_8_smFCP X’s performance was optimized for Mavericks, the new Mac Pro and dual GPU processing. By design, this means improved 4K throughput, including native 4K support for ProRes, Sony XAVC and REDCODE camera raw media files. This performance boost has also filtered down to older machines. 10.1 brought better performance with 1080p ProRes and even 5K RED files to my 2009 Mac Pro. Clearly Apple wants FCP X to be a showcase for the power of the new Mac Pro, but you’ll get benefits from this update, even if you aren’t ready to leap to new hardware.

Along with Final Cut Pro X 10.1, Apple also released updates to Motion and Compressor. The Motion update was necessary to integrate the new FxPlug3 architecture, which enables developers to add custom interface controls. Compressor was the biggest change, with a complete overhaul of the interface in line with the look of FCP X.

df_nle_4_sm

Avid Media Composer (version 7.0.3)

The biggest feature of Media Composer 7.0.3 is optimization for new operating systems. It is qualified for Windows 8.1 and Mac OS X 10.8.5, 10.9 and 10.9.1. There are a number of interface changes, including separate audio and video effects palette tabs and changing the appearance of background processing indicator icons. 24fps sound timecode is now supported, the responsiveness with the Avid Artist Color Controller has been improved and the ability to export a simplified AAF file has been  added.

df_nle_10_smTranscode choices gain a set of H.264 proxy file codecs. These had been used in other Avid news and broadcast tools, but are now extended into Media Composer. Support for RED was updated to handle the RED Dragon format. With the earlier introduction of 7.0, Avid added background transcoding services and FrameFlex – Avid’s solution for bigger-than-HD files. FrameFlex enables resizing and pan/scan/zoom control within that file’s native resolution. Media Composer also accepts mixed frame rates within a single timeline, by applying Motion Adapters to any clip that doesn’t match the frame rate of the project. 7.0.3 improves control over the frame blending method to give the editor a better choice between temporal or spatial smoothness.

There is no clear winner among these three. If you are on Windows, then the choice is between Adobe and Avid. If you need 4K output today, Apple or Adobe are your best option. All three handle a wide range of popular camera formats well – especially RED. If you like tracks – go Avid or Adobe. If you want the best application for the new Mac Pro, that will clearly be Apple Final cut Pro X. These are all great tools, capable of any level of post production – be it commercial, corporate, web, broadcast entertainment or feature films. If you’ve been on the fence for two years, now is the time to switch, because there are no bad tools – only preferences.

Originally written for Digital Video magazine / CreativePlanetNetwork.

©2014 Oliver Peters

Lone Survivor

df_ls_01

The Iraq and Afghanistan wars have already spawned a number of outstanding films, but one that is bound to set the bar higher is the recently-released Lone Survivor, starring Mark Wahlberg as US Navy SEAL Marcus Luttrell. In early screenings, a number of critics have already compared the film favorably with Saving Private Ryan and Black Hawk Down.

df_ls_06Skip ahead a paragraph if you are concerned about spoilers. The story is based on Luttrell’s best-selling memoir by the same name. It focuses on the failed 2005 Operation Red Wings in which a four-man SEAL team that included Luttrell was sent to retrieve an Al Queda-aligned Taliban leader. Their position was discovered by local shepherds and the SEALs had to decide whether to let them go or kill them. After a unit discussion, the locals were released, which presumably compromised the SEAL unit’s position. Finding themselves surrounded and outnumbered, a firefight ensued. A helicopter sent to extract the team was shot down resulting in the deaths of sixteen, including SEAL and Army special operations units. In the fight, Luttrell’s three teammates were also killed. The story continues with the unusual circumstances that led to his survival through the help of local tribesmen and subsequent rescue. The team leader, Lt. Michael P. Murphy, received a posthumous Congressional Medal of Honor for his actions on that day.

Making this film was entrusted to writer/director Peter Berg (Battleship, Hancock, The Kingdom, Friday Night Lights). For the edit, Berg tapped Colby Parker, Jr., who has cut seven films with Berg. Parker works on a mix of films, music videos and commercials. In fact, he first met Berg doing a Limp Bizkit music video. For commercials, Parker works out of LA’s Rock Paper Scissors editorial company, also home to Academy Award-winning editors, Angus Wall and Kirk Baxter (The Girl with the Dragon Tattoo, The Social Network).

df_ls_07I recently spoke with Parker about his experiences on Lone Survivor. Parker explained, “While we were working on Hancock, Peter brought in Marcus and introduced him. We were going to go full speed into Lone Survivor, but then Battleship came up first, so that had to be put on the back burner. After Battleship, it was back to Lone Survivor, but Peter had to find independent financing for it. He had to work really hard to make it happen. Peter has a great affection for three things – his son, football and the military. His father was a Navy historian, so this was a passion project for him.”

Marcus Luttrell was instrumental in the film staying technically accurate. Parker continues, “Marcus was involved in approving the locations, as well as the edit. In a typical war movie, you see a lot of yelling in a battle as commands are issued back and forth. That’s completely different from how the SEALs operate. They are very disciplined units and each member knows what each person’s role is and where there should be. Communication is often silent through signals and there’s a lot of flanking. The SEALs call it ‘water through trees’. The SEALs tend to shoot sparsely and then wait for a response, so the enemy will reveal their position. I had to recut some scenes, to minimize the yelling that wasn’t correctly portrayed.”

df_ls_05Lone Survivor involved a 44-day shoot in New Mexico, where the mountains were a sufficient substitute for Afghanistan. Tobias Schliessler (The Fifth Estate, Hancock) was the director of photography, working with RED cameras. According to Parker, they watched a lot of other war films for the right frame of mind. He explained, “As a reference for how the environment should look, the guideline was the documentary Restrepo about the Afghanistan war. This was his basis for sky, lighting and terrain.”

Editing took about six months. Parker said, “Peter likes to shoot with three cameras all the time, so there’s a lot of coverage. I edit while they are shooting, but I wasn’t on location. I like to blast through the footage to keep up with the camera. This way I can let Peter know if any extra coverage is needed. Often I’ll get word to the 1st AD and he’ll sneak in extra shots if the schedule permits. Although I will have a first assembly when the production wraps, Peter will never sit though a complete viewing of that. He works in a very linear manner, so as we start to view a scene, if there’s something that bothers him, we’ll stop and address it. My first cut was about two-and-a-half hours and the final length came in at two hours.”

df_ls_03Parker continued, “There were a number of scenes that paced well when we intercut them, rather than let them play as written in a linear fashion. For instance, we wanted to let the mission briefing scene play normally. This is where the SEAL team is briefed on their target.  That scene was followed by a scene of the target beheading a local. However, we realized that an actual briefing is very technical and rote – so intercutting these scenes helped keep the audience engaged.” In a film that is intended to accurately portray the frenetic events and chaos of a battle, continuity becomes a challenge for the editor. Parker explained, “In some of the key scenes, the cameras would be on the stars for their takes and then would be turned around to cover the side of the scene showing the Taliban. It was always an issue of matching the energy.”

df_ls_04“I purposefully wanted to make the battlefield clear for the audience. I didn’t want it to be a messy confusing battle. I wanted the audience to experience exactly what the SEALs felt, which was the Taliban closing in on them. I slowed down the pacing so the audience could really track the scene. I’ve had people tell me after screenings that they appreciated the way the first battle is presented, because they’re never lost or confused. In the key scene, where the seal team is debating about what to do with the goat herders, there was a lot of improvisation and a lot of coverage. There was so much strong footage that it was overwhelming. I ended up transcribing every line of dialogue to index cards, then I would lay them on the floor and edit the scene together with these cards.”

Another struggle was how much violence to show. Parker continued, “During the battle, there are scenes with long falls and jumps down the mountainside as the SEALS are looking for cover. These were very brutal visually and I had to be conscious of whether I was getting desensitized to the brutality and needed to dial it back some. One scene that I fought hard to keep in the way I’d cut it, was when Marcus breaks his leg. There’s a bone sticking out through the skin and he has to push it back in. Some folks thought that showing this was just too much, because it was too gruesome. That’s obviously extremely painful, but it’s accurate to what happened and tells a lot about what sort of people become SEALs. I’m glad it stayed in.”

df_ls_02Visual effects played a large role in making Lone Survivor. Image Engine Design (Elysium, Zero Dark Thirty, District 9) in Vancouver handled the majority of effects. The Chinook helicopter crash sequence was completed by ILM. Parker said, “There were a lot of practical visual effects done on location, but these were augmented by Image Engine. The crew did trek up into the upper mountains in New Mexico into some difficult places, so that created a realistic starting point. Muzzle flashes were added or enhanced and mountains were added to some backgrounds. The sets of the villages were only one or two huts and then Image Engine built everything around those. Same for the SEAL base. There were only a few real buildings and from that, they built out a larger base.”

Sound was also a key part of the experience. Parker explained, “Wylie Stateman (Django Unchained, Inglourious Basterds) was the supervising sound editor and working with him was very inspiring. He uses a lot of foley, rather than canned effects, and was able to build up a whole sound design ‘language’ for the environment of each scene. It was very collaborative. Wylie and I would discuss our ideas and massage edits to make the sound design more effective.”

The editorial department was set up with four Avid Media Composer systems connected via Unity shared storage. Parker is a big proponent of Avid. He said, “I strictly cut on Avid, but I like some of the improvements they made, thanks for the pressure put on them by Final Cut Pro. This includes some of the timeline-based editing changes, like the ability to copy and paste within the timeline.” The final DI and color grading was handled by Company 3 in Los Angeles.

Originally written for DV magazine / CreativePlanetNetwork.

©2014 Oliver Peters