Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro Legacy Nesting causing ripple problem.

  • Nesting causing ripple problem.

    Posted by Brad Sherman on May 22, 2008 at 5:39 pm

    I am tagging hundreds of spots for a tv station. I am using existing projects and timelines.

    Co-worker came up with brilliant idea to nest the audio tags so that we could simply build one timeline, then change the nest to lay off the other versions, i.e. tonight at 10 or tomorrow at 10.

    One project this plan worked perfectly. Each audio clip just lengthened or shortened while starting at the same tc on each of the hundred of spots.

    On the other, the nest rippled the layer when clip length changed.

    Cannot find any differences that account for this.

    Any ideas?

    Brad Sherman replied 17 years, 12 months ago 3 Members · 3 Replies
  • 3 Replies
  • Dylan Reeve

    May 23, 2008 at 4:24 am

    My experiments with nesting still leave me confused, but it now seems to work like this…

    If I open a Sequence into the view and mark In/Out points then edit or drag into the sequence, it now is a copy of that sequence, nested within the target sequence (so changes made to the original within the Browser have no effect). Also changes in duration of the nested sequence (accessed by double-clicking in timeline) don’t ripple the ‘host’ timeline.

    However if I just drag from the Browser into the sequence, then it maintains a relationship with the original, and any change in duration seems to ripple the timeline.

  • Walter Biscardi

    May 23, 2008 at 10:36 am

    [Brad Sherman] “On the other, the nest rippled the layer when clip length changed.”

    When the clip lengths are shortened, the nest does not ripple everything else.

    When the clip lengths in the Nest are lengthened beyond the original Nest length, then the nest becomes longer in the timeline and ripples everything else down the line.

    Stupid yes, but apparently this is the way Apple figures it should work, just like speed changes.

    But I have noticed that FCP 6.0.2 or 6.0.3 might have addressed this issue. It seems I’ve done some clip lengthening in a Nest, but the nest did not ripple out the timeline. Not in front of a system right now, but that might be the case.

    Walter Biscardi, Jr.
    Biscardi Creative Media
    HD and SD Production for Broadcast and Independent Productions.

    STOP STARING AND START GRADING WITH APPLE COLOR Apple Color Training DVD available now!
    Read my Blog!
    View Walter Biscardi's profile on LinkedIn

  • Brad Sherman

    May 23, 2008 at 9:54 pm

    You may be onto something here.

    Both jobs were imported from older versions of FCP to 6.0.3.

    The difference in the timelines might be due to each originating in different versions of old FCP in the last three or four years.

    I have found a way around it by making sure my first nest is the longest of the versions and then just using the shorter VO and some slug to make the duration match the longest in other versions. No ripple can happen that way.

    A convoluted workaround but still saving a ton of time.

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