“Nesting” in Final Cut Pro and Avid Xpress Pro

By S Simmons. Filed in Avid editing, Final Cut Pro  |  
TOP del.icio.us digg

NESTING.jpg

In this 6th installment of Avid vs. FCP we take a look at “nesting” in the applications and how the term differs.

First, give the nesting article a read at this link.

I think it’s obvious that if I could choose only one “nesting” feature then it would be what Final Cut Pro offers. I think the main thing to consider is that while Avid and Final Cut Pro are very similar (“same buttons, different places” is one phrase I like to use to describe the two apps) there are still aspects that are very different. Nesting and the handling of multiple effects would be one of the biggest differences. But similar results can be achieved. Though it does have limitations that can bite the editor if he/she is not careful, the Final Cut Pro nesting concept is something I wish that Avid would add in Xpress Pro.

3 comments to ““Nesting” in Final Cut Pro and Avid Xpress Pro”

  1. Comment by Chi-Ho Lee:

    I edit on both Final Cut and Avid. But I disagree with your overall take that FCP is more “computery” and hence more click and drag than Avid. The FCP keyboard has much more levels of keys that you can map so it can contain many more keyboard shortcuts if you take the time to map them. For example, your article says that CMD-Drag is the way to edit a sequence from the viewer without nesting. CMD-F9 and CMD-F10 will perform that function with Inserting and Overwriting as well. But a keyboard option does not seem possible from reading your article. I’m amazed that I have to click and drag across a clip to enter slip/slide mode in Avid, where in FCP, I can just hit S or SS and select the clip. What if that clip in Avid is very long? I either have to lasso for a long time or minimize the timeline first and then lasso that clip. Much more tedious than FCP. Hit S and then click the clip.

    Same with your article on trimming, you seem to imply that click and drag is the only way to trim in the timeline in FCP. With keyboard shortcuts being so important to every editor, I think you should start listing the FCP shortcuts in these articles so readers understand that clicking is not the only method, which many non FCP editors tend to think it is.

    I appreciate your articles. They are fair and very level handed.

  2. Comment by editblog:

    Chi-Ho,
    you are very correct in that you can actually map more things to keystrokes in FCP than Avid, but as you mention about the MCD-F9 and 10 shortcuts you can see there are many different ways to perform an operation on both apps. There are several other ways to enter slip/slide on an Avid that the lasso method as well so it still really does come down to personal preference. I’ll keep the keyboard shortcut suggestions in might when I write the second series of the Avid & (vs.?) FCP articles….. thanks for the comment!

  3. Comment by mike janowski:

    Hey Scott-

    Stumbled upon your site and blog while searching for information regarding the behavior of nested sequences in FCP. Found this quote (which I have to take issue with) in an article you wrote a while ago:

    “When you double click a nested sequence it opens the full edit in a new tab and any changes made in the original timeline are reflected in the nest.”

    That’s not entirely true. When you double-click a nest, it opens up a UNIQUE INSTANCE of the sequence, a copy if you will, of the original sequence you nested. This sequence, though identical (at first) to the sequence in your browser/bin, doesn’t really appear in the browser/bin. Changes made to this unique copy are reflected in the sequence containing the nests…but ARE NOT reflected in the original sequence (i.e., the one in your browser/bin).

    I make this distinction because I’m fighting this problem right now. I’m working on a 30 minute TV show for WGN (Chicago). We’re editing packages, and then I put the show together, editing the packages in the Show sequence as nests. The problem comes in when we make changes to the packages. Doing it directly in the Show sequence is quick and convenient. However, the EP wants to make sure that each segment package is current, as there may come a time when we re-run certain packages in future shows. This presents a problem with our current method; updating the segment in the Show sequence does not update it in the Segment project. I’ve resorted to lassoing the updated nested segment and dragging it into the segment project, which seems to work most of the time to provide me with a “real” copy of the edited segment as it appears in the Show timeline.

    Furthermore, double-clicking a nested sequence can cause other headaches. Double-clicking on the video track of a nest opens up what appears to be the entire nest…however, only changes made to the VIDEO tracks are reflected in the changed nest…in order to alter audio tracks, one needs to double-click on the AUDIO tracks of the nest.

    Thanks for the space to opine…always glad to hear if I’ve missed or mis-stated anything…mike