Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro Legacy Am I misunderstanding nesting?

  • Am I misunderstanding nesting?

    Posted by Dylan Reeve on May 9, 2008 at 12:45 am

    Let’s imagine I have a sequence called “Ep 1 – Part 1”, then I create a new sequence called “Ep 1 – Compile Master”. I open the Part 1 sequence in the Viewer and drag/edit into the Compile to nest it in that sequence.

    I would then expect that if I make a change to the “Ep 1 – Part 1” sequence in my project that it would be reflect in the Compile, but this isn’t the case. Instead I seem to have two copies of the sequence now, one that’s available from the Browser, and one that I can only reach by double-clicking on the nested sequence in my Compile sequence.

    Is this right? It certainly was my impression that a nested sequence was more like a link to another sequence, but now it appears to be more like a copy of a sequence (which seems much less useful).

    I haven’t got the manual handy at the moment (I’m at home now) but the stuff I’ve read online seems a little ambiguous on exactly how this relationship works.

    Dave Gardner replied 17 years, 9 months ago 13 Members · 30 Replies
  • 30 Replies
  • Russell Lasson

    May 9, 2008 at 1:09 am

    That seems consistent with how nesting works here. Whether or not you like it is a different story. I might suggest using the feedback option if you feel strongly about it.

    -Russ

    Russell Lasson
    Kaleidoscope Pictures
    Provo, UT

  • Dylan Reeve

    May 9, 2008 at 1:45 am

    It just seems to defeat the advantage of it. In Avid I can edit a sequence into another one, even ‘nest’ it into a single layer if I want, but it only exists there as a copy of the source sequence, I’d thought that FCP saw it as a reference to the source sequence, which would actually seem to be a benefit, rather than the way it is at the moment, which just confuses matters because there are then sequences which only exist within other sequences, and can only be accessed through the sequence in which it exists.

    I’m now curious, if I nest Sequence A in Sequence B, and then duplicate Sequence B as Sequence C, then will changes made to the nested Sequence A in Sequence B also be reflected in C? (Well, I’m confused).

  • Tom Wolsky

    May 9, 2008 at 1:52 am

    From what you describe I don’t understand why this is happening. Your work procedure should make the sequence recursive. What you do in Part 1 should be reflected in Compile. Unless you did a copy and paste this should work. The only time this may not happen is you have I/O marked in Part 1. That I/O will be honored as a clip when the sequence is edited into another sequence.

    All the best,

    Tom

    Class on Demand DVDs “Complete Training for FCP6,” “Basic Training for FCS2” and “Final Cut Express Made Easy”
    Author: “Final Cut Pro 5 Editing Essentials” and “Final Cut Express 3.5 HD Editing Workshop”

  • Russell Lasson

    May 9, 2008 at 2:13 am

    Maybe I’m wrong then. I’m just recently starting to get over my phobia of nesting in FCP. I’ll play with it sometime and see what’s happening.

    -Russ

    Russell Lasson
    Kaleidoscope Pictures
    Provo, UT

  • Dylan Reeve

    May 9, 2008 at 2:56 am

    Nope, definitely not copy-pasting.

    I take a sequence from the browser, drop it in the Viewer, then edit it into the timeline (with F9 or whatever).

    If I then go back and make a change in that source sequence, the change is not reflected in the timeline I nested it in. If I double click on the nested sequence it opens up another one in the Timeline (so I have two tabs called ‘Part 1’ for example) which doesn’t reflect any changes made to the one I access from the Browser.

  • Nick Toth

    May 9, 2008 at 3:13 am

    Try dragging the sequence directly from the browser to the timeline bypassing the viewer step.

    NT

  • Jeremy Garchow

    May 9, 2008 at 3:18 am

    Also, when you nest part 1, make sure you close it in the timeline window, then open it from the compile nest. Once you open it from the compile nest, any changes you make should update.

    Jeremy

  • Tom Wolsky

    May 9, 2008 at 3:40 am

    I followed your direction step by step and cannot reproduce the behavior you’re seeing. If I make a new sequence. Take an existing sequence and drag it into the Viewer (bypassing this step makes no difference) and edit it into the new sequence. Opening the Part 1 sequence from inside the Browser or inside the compile sequence will make no difference and produce the same result.

    If the part 1 sequence is open in the timeline window and you drag the sequence from the browser to the viewer, the part 1 sequence in the timeline automatically closes.

    As long as there are no I/O points marked in the part 1 sequence when it’s in the browser it works correctly.

    All the best,

    Tom

    Class on Demand DVDs “Complete Training for FCP6,” “Basic Training for FCS2” and “Final Cut Express Made Easy”
    Author: “Final Cut Pro 5 Editing Essentials” and “Final Cut Express 3.5 HD Editing Workshop”

  • Bret Williams

    May 9, 2008 at 4:24 am

    He’s yet to say whether he’s marking IO in the viewer. I have to assume he is, otherwise why the heck waste the time of dragging it into the viewer? He said he’s pressing F9 (and not dragging it from the viewer) so sounds like a IO F9 kinda guy. Dylan?

  • Rafael Amador

    May 9, 2008 at 4:36 am

    I think all the mess is because Dylan is with FC 5.1.x
    In FC 6 this have been fixed.

    Mac OX 10.5.2-FC 6.02-QT 7.4.1
    G5 2x2Gh 4GbRAM-BlackMagic Extreme
    PMBP 17″Core2Duo 4GbRAM-AJA ioHD
    JVC DTV-17″
    SONY EX-1 . SONY PD170
    ..and always a big mess on top of the table.

Page 1 of 3

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy