Note: The information below is outdated and relates to a discontinued app.
Shotgun’s Import Scans app brings relevant editorial information about your scans into Shotgun, which can then be used to request pulls as part of the turnover process to vendors. After compiling the footage to be pulled in the edit, export out an EDL (or tab-delimited text file) and drag this into the app to create Versions in Shotgun that represent these plate and element scans.
Note: The information that follows assumes you are using an Avid editing system. Much of it will be the same for other systems, but contact Shotgun support if you have any questions.
Preparing and exporting editing data
The Import Scans app provides two options for bringing in data from an editing system: either via EDL with locators, or via a tab-delimited text file.
Note: Which option you use will likely be due to personal preference. The tab-delimited text file route allows for importing more editorial information into Shotgun, but if you’re going to be using locators anyway then generating EDLs will be a much quicker approach.
Option 1 — Export EDL with locators
With this approach, you create a Sequence with everything you want to scan for a particular pull request, using locators to indicate which shots they relate to. Then you can export an EDL, along with a set of thumbnails, to be used with the Import Scans app.
First, create (or copy) a new Sequence. The Import Scans app will use the Sequence name to generate a Playlist name (for subsequent use with the Request Scan app), so be sure to give the Sequence the same name you intend to use for the request.
In the Sequence itself, include just the footage you intend to scan, so that each clip corresponds to a single pull and that the start and end of each clip corresponds to the total amount of footage needing to be pulled (inclusive of any handles).
Note: By default, the Import Scans app assumes 0-frame handles. Handle frame lengths can be specified in Shotgun after the import.
Ensure that each clip contains a single locator (the locator color does not matter), which has the desired name of the scan (this will be used as the “Version Name” in Shotgun). When you’re ready, export the Sequence as an EDL to a folder of your choice.
Next, export the Sequence locators as JPEGs to the same folder, and in the settings, ensure that “Sequential Files” and “Markers Only” are checked.
Option 2 — Export tab-delimited text file
With this approach, you create a bin with individual clips for everything you want to scan for a particular pull request, including columns for additional metadata. Then you can export a tab-delimited file, along with a set of thumbnails, to be used with the Import Scans app.
First, create a new bin. The Import Scans app will use the bin’s name to generate a Playlist name (for subsequent use with the Request Scan app), so be sure to give the bin the same name as you intend to use for the request. Make sure the bin displays columns for all the information you wish to export.
The following columns are required by this process and must be included in the bin:
- “Name” (or “Version Name”)
- “Clip” (or “Source Clip”)
- “Start” (as a timecode)
- “End” (as a timecode)
Here, “Name” represents what the scan should be called (which will be shown as the “Version Name” in Shotgun), and “Clip” should be the editorial name of the clip.
The following columns are not required but will be used if provided:
- “Head” (or “Head Duration”)
- “Tail” (or “Tail Duration”)
- “First Frame”
- “Comments” (or “VFX Comments”)
Note: The app can be configured to use default values for many of the optional columns.
Any other columns will be ignored. To avoid potential conflicts it’s best to not include any unnecessary columns.
Tip: The Import Scans app can be configured to either assume handles are included within the start and end timecodes, or that they will be added based on the head and tail values provided.
Add all the clips (or subclips) you want to include in the bin, and verify that the information listed for each is correct. Then when you’re ready, export the bin to a tab-delimited text file to a folder of your choice.
Next you’ll want to save the thumbnails for each of the clips in the bin, making sure that each is named the same as the corresponding clip name. Put all of these in the folder along with the tab file.
Import to Shotgun
Once you have created a folder with the exported data, you’re ready to use the Import Scans app to create Versions in Shotgun to track and manage these scans.
To launch the app, either:
- Open the Shotgun Desktop app, browse to your project, and click the Import Scans icon, or
- In your browser, from any Shotgun page in your project, choose Project Actions > Import Scans.
Note: You must have the Shotgun Desktop app installed. For more information about the Shotgun Desktop app, Getting started with Shotgun Desktop.
The Import Scans window will be shown.
To import the data, drag the folder with the exported data onto the app.
Note: Make sure you drag the folder itself, and not just the EDL or tab-delimited text file, or else the import will complete without including the thumbnails.
Once complete, you can click “Jump to Shotgun” to be taken to the newly created Playlist with the clips needing to be pulled. From here you can edit any information, or proceed to issue the request, via the “Request Scan” app.
Controlling Import Scans’ behavior
The Import Scans app has a number of different aspects that can be configured to accommodate different workflows. To change any of the following behaviors, contact Shotgun support.
The app will automatically try to fill in the Link field for each scan based on the Version Name. For example, if the scan is named “042_CE_0490_bg01_v01”, it would be linked to an existing Shot called “042_CE_0490”. Depending on your naming conventions, this link may be left blank when you use the app.
Note: By default, the app expects shots to be named in the form 001_AA_0010 and scans to be 001_AA_0010_el01_v01.
Automatic Shot creation
The app will automatically create a new Shot if it can’t find an existing one to fill in the Link field, unless the scan doesn’t match the expected naming conventions (such as when importing lens grids).