Associating events in an EDL to Shots in Flow Production Tracking is a critical connection that the Import Cut app must make in order to fulfill its duties. Depending on the output and available information coming from editorial, this can be a challenge. With this in mind, Import Cut strives to do everything it can to link up the right Shots and supports multiple options for accomplishing this.

Shot Association Logic

The Shot-linking logic follows a priority order, based both on elements in the EDL and information in Flow Production Tracking. Here is the full rundown:

1. From Clip Name/Version Matching

` TITLE: HSM_video FCM: NON-DROP FRAME

001 JRUN_V09 V C 00:00:00:00 00:00:02:06 01:03:14:10 01:03:16:16

• FROM CLIP NAME: JRUN_0010_Anim_v09 `

]

The first and most natural way to associate EDL events to Shots is to simply use media from a Version in Flow Production Tracking. The “FROM CLIP NAME: “ Note the EDL corresponds to the name of the file in the editorial timeline, and Import Cut will cross-match that text with a Version in Flow Production Tracking for the Project. If it finds one and if that Version is linked to a Shot, it will associate the EDL event with that Shot—JRUN_0010.

2. Locator

TITLE: HSM_video 
FCM: NON-DROP FRAME 

001 JRUN_V09 V C 00:00:00:00 00:00:02:06 01:03:14:10 01:03:16:16 
* FROM CLIP NAME: JRUN_0010_Anim_v09 
* LOC: 00:00:01:00 YELLOW JRUN_0010 

The next thing Import Cut checks for is a Locator Note, as shown above. Locators are commonly used in Avid workflows, and are a convenient way to mark locations on the timeline with information—like, say, the name of a Shot. When Import Cut finds a Locator, it will cross-match that text with a Shot in Flow Production Tracking for the Project. If it finds one, it will associate the EDL event with that Shot—JRUN_0010 in our example.

3. Comment

TITLE: HSM_video 
FCM: NON-DROP FRAME 

001 JRUN_V09 V C 00:00:00:00 00:00:02:06 01:03:14:10 01:03:16:16 
* FROM CLIP NAME: JRUN_0010_Anim_v09 
* COMMENT: JRUN_0010 

If no Locator is found in the EDL, Import Cut will next check for a Comment. Comments are also Notes in the EDL, but are prefixed by the string “COMMENT: “ (note the colon and the space after). When Import Cut finds a Comment, it will cross-match the text after the prefix with a Shot in Flow Production Tracking for the Project. If it finds one, it will associate the EDL event with that Shot—JRUN_0010 in our example.

4. Note Without Label

TITLE: HSM_video 
FCM: NON-DROP FRAME 

001 JRUN_V09 V C 00:00:00:00 00:00:02:06 01:03:14:10 01:03:16:16 
* FROM CLIP NAME: JRUN_0010_Anim_v09 
* JRUN_0010 

Fourth in the priority list is a Note on the EDL event that is neither a Locator nor a Comment. In essence, this is a Note without any sort of prefix or label. When Import Cut finds any other Note, it will cross-match that text (whatever it is) with a Shot in Flow Production Tracking for the Project. If it finds one, it will associate the EDL event with that Shot—once again JRUN_0010 in our example.

If an EDL event has more than one Note, Import Cut will use the first one in the file and ignore any that come after it.

5. Just Type It

If options 1 through 4 aren’t able to match up the EDL event to a Shot, you can also just type in the desired Shot directly into Import Cut. Typing in your own value will be treated the same way the app handles the options where the Shot came through as part of the EDL. You can also modify the Shot in Import Cut after processing the EDL if needed.

The exception to this is when the EDL Event matches a Version. It is not possible to modify the Shot in Import Cut if it was found based on a Version linkage since Flow Production Tracking information is treated as canonical.

6. Blank is OK

Last but not least, you don’t have to associate each and every event in the EDL with a Shot. A blank value is ok! When an EDL event doesn’t match a Shot, Flow Production Tracking will still track it as a CutItem, store the in and out points, and use the base layer for playback during that section.

Using EDLs to Create New Shots

Thanks to its ability to create Shots in Flow Production Tracking, Import Cut also provides a fast and easy way to populate the system with Shots based on an EDL, saving the step of having to enter them in manually. By relying on conventions in the EDL itself, the app enables editorial to drive the push of information out to production with minimal (if any) extra effort. The goal is to ensure a seamless handoff and consistency across the board.

When creating Shots, Import Cut will set the status to the default status for Shots in Flow Production Tracking, as specified in the field configuration. It will also link the Shot to the the same entity that the Cut being imported is linked to, meaning if the Cut is being linked to the ‘JRUN’ Sequence, the app will set that in the Sequence field of the Shot JRUN_0015 when it creates it.