Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro auditioning within a compound clip workflow

  • Craig Alan

    July 8, 2013 at 11:36 pm

    How about saving this single modified clip as a compound clip as Jeff suggested? And do you agree with his warning that FC doesn’t like too many compounds? And yes I would save it as a new parent.

    Mac Pro, macbook pro, Imacs (i7); Camcorders: Panasonic AG-HPX170/AG-HPX250P, Canon HV30/40, Sony Z7U, VX2000, PD170; FCP 6 certified; write professionally for a variety of media; teach video production in L.A.

  • Jeremy Garchow

    July 8, 2013 at 11:47 pm

    [Craig Alan] “How about saving this single modified clip as a compound clip as Jeff suggested? And do you agree with his warning that FC doesn’t like too many compounds? And yes I would save it as a new parent.”

    It’s a way to do it, yes.

    Yes, I do agree that many compounds can trip up FCPX.

  • Jeff Kirkland

    July 9, 2013 at 12:33 am

    [Craig Alan] “But doesn’t it seem like a silly work around to create a compound clip just to get it saved in the browser? “

    FCPX is still in it’s early stages of evolution and silly or not, sometime it’s just the way the app works. I hear that Apple do look at customer feedback so feel free to send ’em a feature request…

    I tend to use compound clips as snapshots – it could be of an entire project timeline as a backup before I make changes or an individual clip to preserve whatever I’ve done to that. [alt]+g–>give it a name isn’t really much more effort than dragging a clip back into the event library and has the advantage that I can group as large a section of the timeline as I want.

    As to how many is too many… depends what’s in ’em and how powerful your computer is. Can’t say there’s a hard and fast rule other than use them sparingly. And when you do hit that tipping point you’ll get slow projects, corrupt projects that hang and don’t open, or take hours to open, mysterious crashes – generally lots of unpredictable behaviour that comes from FCPX running out of resources.

    For all of that, it doesn’t happen often these days but when I get a call from editor friends asking why FCPX is behaving badly, my first question is always “how many compound clips do you have on the timeline”. It’s usually nesting compound clips inside other compound clips that does the damage.

    Jeff Kirkland | Video Producer | Southern Creative Media | Melbourne Australia
    http://www.southerncreative.com.au | G+: https://gplus.to/jeffkirkland | Twitter: @jeffkirkland

  • Mark Morache

    July 9, 2013 at 2:17 am

    I’ll sometimes create a scrap timeline. Once you’ve opened it and opened your primary timeline you can easily select a portion and use the arrows above the left side of the timeline window to switch between timelines, cutting or copying portions and moving them into your scrap timeline.
    You can create the scrap timeline as a project or create a compound clip that will live in the event browser. It should work either way.

    And as far as having too many compound clips, I believe the new way fcpx handles compound clips fixed most of that.

    ———
    Don’t live your life in a secondary storyline.

    Mark Morache
    FCPX/FCP7/Xpri/Avid
    Evening Magazine,Seattle, WA
    https://fcpx.wordpress.com

  • Jeremy Garchow

    July 9, 2013 at 2:19 am

    [Mark Morache] “And as far as having too many compound clips, I believe the new way fcpx handles compound clips fixed most of that.”

    *most but not all.

    Lots of compounds and lots of synced clips seems to cause weird things in FCPX. It is certainly better than how it used to be, though.

  • Craig Alan

    July 9, 2013 at 5:06 am

    Got it, thanks. I guess the compound clip was FCPX’s answer to having more than one sequence per project (even though you could have a different project with the same media). And again although I don’t need to save modified clips frequently, I certainly feel the need a couple of times per project. In FCP 7 it was often a subclip in the browser (FCP X favorite but in 7 you could have more than one per master clip) or dragging a clip back from the timeline.

    Surprises me they would have a powerful feature like saving compound clips as either parent or dependent and yet have no way to same a modified clip. But I get it and can live with it.

    Mac Pro, macbook pro, Imacs (i7); Camcorders: Panasonic AG-HPX170/AG-HPX250P, Canon HV30/40, Sony Z7U, VX2000, PD170; FCP 6 certified; write professionally for a variety of media; teach video production in L.A.

  • Jeremy Garchow

    July 9, 2013 at 5:12 am

    [Craig Alan] “Surprises me they would have a powerful feature like saving compound clips as either parent or dependent and yet have no way to same a modified clip.”

    The way compounds work now is not how they always worked. The compound in Event method is relatively new.

  • David Steiner

    November 19, 2018 at 1:12 pm

    hey,
    So, any news on the “FCP X gets slow when using many compound clips” ?

    I break up projects into “scenes” (20 seconds to 3 minutes each, average ~1m30), then use “reference new parent” to try out different edits of a scene.

    Problem is, gets slow. tried deleting .flexolibrary file, resetting preferences (command-option while starting fcp x), doesn’t make a difference. My “currentversion.fcpevent” in the event folder (not in the project folder) is 2 gigs… guess it contains all the compound clips

    any solution to this? this “reference new parent” workflow is one big reason why FCP X is better than premiere pro/davinci resolve etc. so getting rid of this workflow is a non-starter ☺

    anyone found some solutions? moving some projects to another event? offloading old compoundclips somewhere, but how? does using “duplicate project as snapshot” make a difference?

  • Jeremy Garchow

    November 19, 2018 at 1:48 pm

    Where is your library located (what drive)? Where is the cache located? Where is your media located?

  • David Steiner

    November 19, 2018 at 2:38 pm

    Library is on 1Tb MacBook Pro 2018 SSD, cache and media are on external usb3 2Tb SSD. Media is Alexa logic ProRes4444 (ie not very high datarate)

Page 3 of 4

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