Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro Legacy Comments not retained when importing EDL (into FCP or Avid)!

  • Comments not retained when importing EDL (into FCP or Avid)!

    Posted by Mike Barber on May 28, 2009 at 3:31 am

    Two editors using the same EDL (exported by FCP 6.whatever-the-latest-is) on different systems—Avid on Windows, FCP on Mac (same that gen’d the EDL)—are both experiencing the same issue: when importing the EDL, the comments don’t make it.

    In the EDL, each has a comment that was from the Comment A field of the FCP browser. I export the EDL and then import it into a new project, everything goes according to plan except for the missing comments!

    The editor in a different facility has the exact same headache when importing it into Avid!

    Is this actually expected behaviour, or is something amiss?

    Doug Beal replied 16 years, 11 months ago 5 Members · 8 Replies
  • 8 Replies
  • John Pale

    May 28, 2009 at 3:44 am

    Yes. EDL’s have no idea what a browser or a bin or clip is.
    They are designed for linear tape based edit controllers from the 1970’s.

    What are you using an EDL for? There may be a more modern solution than that, depending on the application.

  • Mike Barber

    May 28, 2009 at 4:01 am

    Basically, the client (who uses Avid) sent me a bunch of QT dailies in order to pull selects. After going through a few dozen clips with the VFX supervisor, I assembled the sections of the clips we wanted onto a timeline in FCP and then exported the EDL (as well as a QT) with a brief yet unique description for each clip as a comment.

    I send this EDL and QT to the client who then has the DPX sequences generated and delivered to us. I’m not sure if there is a better way to do it, but I am always open to new/better ideas.

    So, I take it that we shouldn’t expect the comment fields to be retained?

  • Doug Beal

    May 28, 2009 at 11:54 am

    Not at my machine right now but is there not a check box as to include comments and which field of comments to retain?
    I remember four comment fields. don’t remember which one sticks with the edl or if all can

    Doug Beal
    Editor / Engineer
    Rock Creative Images
    Nashville TN

  • Mike Barber

    May 28, 2009 at 12:54 pm

    Yes, but that’s in the export, not in the import.

  • Mike Barber

    May 28, 2009 at 4:28 pm

    FYI, here is an excerpt from the EDL:


    001 001 V C 11:02:08:14 11:02:20:00 01:00:00:00 01:00:11:11
    * FROM CLIP NAME: VX348-1.MOV
    * COMMENT: LENS_DEFOCUS_DIRTY

    002 001 V C 11:40:53:24 11:41:00:16 01:00:11:11 01:00:18:03
    * FROM CLIP NAME: VX348-1 PT2.MOV
    * COMMENT: DIRTY_DEBRIS_01

  • Kevin Monahan

    May 28, 2009 at 11:21 pm

    In the past, only Comment Column 4 would be carried over in any EDL. See if this still works.

    Kevin Monahan
    http://www.fcpworld.com
    Author – Motion Graphics and Effects in Final Cut Pro

  • Ernesto Crvalo

    May 29, 2009 at 1:06 am

    EDLs are terrible. You do have another much better option for getting to avid from FCP which is Automatic Duck’s Pro Export FCP 4.0. But it’s not as free as EDL.

  • Doug Beal

    May 29, 2009 at 10:49 am

    I guess I didn’t get what you are trying to accomplish. Are you expecting the comments to show up in the reconnect? in some window or column? I don’t recall that as a capability on import. it’s just the edit number, reel number, edit type, tracks, duration & TC I/O master I/O that translates on import.

    I come from the linear days so if we are working with EDLs we do a printout and verify the hard copy against the import. comments are printed as you show in your example.
    we still deal with EDLs in a red workflow using Assimilate Scratch and FCP or Avid. We still print them out to verify, in addition to visually matching against a ref QT w BITC.

    To move between FCP and Avid MC or DS automatic duck gets it done but the only way I trust comments to translate is a printout. Auto duck generates an HTML that looks similar to an EDL.
    Because of the different code used for DVE, text gen, speed ramps etc between edit softwares a lot of this won’t translate so comments are quite useful, but must be printed out from a text program or database like filemaker.
    with Scratch, notes can be attached to the footage or placeholders in the slots on the construct so shots destined for VFX can be kept up with prior to final conform. helps us old guys to remember what’s happening and allows someone to follow the breadcrumbs.

    Doug Beal
    Editor / Engineer
    Rock Creative Images
    Nashville TN

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