New in v 1.5: EDL Pulls - Traceback & Relink

[amy (Amy Hawthorne)]

CORTEX Dailies now gives you the ability to use EDLs to pull and transcode media.

- YouTube

Your system could be in one of many states when you import the EDL, so we’ll go through a few cases, starting with the easiest one.

Case 1: Media Is in The Same Project and Still Online

1. Start a new Job
2. Select Import > CMX 3600 EDL
3. Browse to the EDL file and click Open
4. You will see a clip list, click Create Clips
5. Select one or more clips (usually Select All), right-click and choose Traceback
6. Leave Database Type as Current Project
   
7. Click Trace
8. Review results and click OK

In this case, the media will automatically be relinked and you’re ready to go.

##Case 2: Media is in a Different Project and Still Online

1. Start a new Job
2. Select Import > CMX 3600 EDL
3. Browse to the EDL file and click Open
4. You will see a clip list, click Create Clips
5. Select one or more clips (usually Select All), right-click and choose Traceback
6. Change Database Type to Other Project
   
7. Click the Browse … button and select the project’s cortexdb file. (Note: the default starting point for this Browse function is C:\ProgramData\MTI. For non-share installations, your DB files will likely be in the default DB folder, under a directory named with the project code)
   

8 .Click Trace
9. Review results and click OK

Case 3: Media does not already exist in any CORTEX Project

1. Create a new Job within the project you plan to use for the EDL pull
2. Select Import > Media Folder and select the source files for the EDL pull
3. Close this job.
4. Now, create a new job and follow procedure outlined in Case 1

Case 4: Media is Offline or Has Been Moved

1. Create clips and Traceback as described above in Case 1 or 2
2. Select and clip, right-click and choose Relink
3. Browse to the new location of the underlying media file.
4. CORTEX will automatically Relink to all nearby related files.
5. Repeat Relink for additional folders as needed.

[dave (David McClure)]

@amy

5. Select one or more clips (usually Select All), right-click and choose Traceback

Amy reported a bug that could cause a crash at this step in build 4350 today. That should be fixed in build 4362

[dave (David McClure)]

Also, I know @amy is working on adding additional topics about these other ways to do EDL pulls, but briefly, if you haven’t done the dailies and need to do an EDL pull you can:

1. create 1 or more jobs first and import all the original media first. Then create a new job for the pull and follow the steps above.
2. instead of doing the traceback through the existing project, you can do it through another database, which could be
   • a folder of ALEs
   • a folder of Final Cut Pro XMLs
   • a folder of Cortex Reel or Job Manifest XMLs

Be on the lookout for more walk throughs, but also feel free to fire away with questions.

[dave (David McClure)]

@amy and @peter found and fixed several issues with the EDL import and traceback feature today in build 4375

[ToddL (Todd Litchfield)]

Everything is importing and linking but DPX renders are failing.
V.1.5.3-b4776

[dave (David McClure)]

Can you try the 1.5.2 release version?

[ToddL (Todd Litchfield)]

OK this sort of works.
It creates DPX, but:

1. it doesn’t render from the EDL in-out points, it renders the whole clip it’s linked to.
2. renders with the ‘file name’ not the ‘comment name’

[dave (David McClure)]

I think this post should answer most of those issues. In short:

1. when importing EDL, choose ‘Use EDL Comment as Clip Name’
2. make sure deliverable is set to use {clipname}
3. when doing the traceback, de-select ‘Slate’ and ‘Edit’ so the name and in/out points are not overwritten by the clip it traces back to.

[ToddL (Todd Litchfield)]

Thanks for your help.
This all worked in V1.5.2