Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro Legacy Time Sensitive EDL Question…please help

  • Time Sensitive EDL Question…please help

    Posted by Eli Mavros on June 23, 2008 at 2:51 pm

    I am exporting EDLs for a color correct session using the C-Mode work around I found here on the cow. I don’t really see the difference, order-wise, from just exporting the EDL as “source”…I do see a difference though between the Media Start and Media End timecodes. The problem is, that neither of them make any sense, because the in and outs in the edl don’t even fall within the timecodes listed in the media Start and End. The media Start and End seem to be all off. I have been working with subclips, could this be the problem? Do I need to treat this like I used to with avid and use the media manager to make a new project with new master clips based on my subclips first and then make EDLs from that project? Does it even matter as long as my clip in and outs are right?

    Thanks,
    Eli
    p.s.
    I have given EDLs for color corrects without experiencing this before (or at least I never noticed it.

    Michael replied 17 years, 10 months ago 2 Members · 3 Replies
  • 3 Replies
  • Eli Mavros

    June 23, 2008 at 2:56 pm

    Wow…Monday morning brain fart. Those timecodes are not the media start and end, but the clips’ placement in the timeline. Yikes…I feel like a dope. Thanks anyways.

    Best,
    Eli

    Eli Mavros

  • Eli Mavros

    June 23, 2008 at 3:07 pm

    Why is there a work around, when choosing to export an EDL using “Source” timecode seems to give you a perfectly good CMODE EDL? Did this feature not used to work and thus the work around? I am comparing the two EDLS from both methods, and the clips seem to be in the exact same ascending order.

    Best,
    Eli

    Eli Mavros

  • Michael

    June 23, 2008 at 4:02 pm

    It never worked properly for me and many others, hence the workarounds. If it works for you, great. Maybe it’s been fixed in 6.03?

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