Importing ADR Cues from Ordered File Formats
ADR Cue Numbering Scheme
The chosen ADR Cue numbering scheme for imported cues should first be set in the PROJECT tab in the top left of the ADR Master window.
Click the + on the right of the Cue Numbering Scheme field. There are 4 fields to chose from:
- Char Name
- Char pfx
- Pic Version
Once the desired fields are added, they appear as boxes in the field box to the left. Their order can be shuffled by clicking a box and moving it to the desired point in the cue name. Additionally, you can click between, before or after them to add fixed text that will be used as part of the cue number.
To choose whether cues are named Globally or By Character, use the Mode selector.
Use the text box to the right of Zero Padding to select the number of digits in the cue number. This is done by adding zeroes to the start of the cue number so that all cue numbers are the same length, e.g. 0001, 0164, 1265, etc. With a zero padding of 3 ADR will add leading zeros to all numbers so they are all 3 digits long (e.g. 001).
To import ADR cues stored in one of the supported ordered formats, select File > Import Events from File and choose a file from the browser window & click Open.
The ‘Select Tracks to Import’ window
When importing Pro Tools® Session Info text files, a separate, Select Tracks to Import window will first appear, allowing for selection of which character tracks to import.
This window does not appear for other Ordered file formats.
There are a few useful buttons to help select more tracks quickly. These include:
Select All Cue Tracks - Activates only the tracks with recognised ADR cues.
Select All Tracks - Activates all tracks
Deselect All Tracks - Deactivates all tracks
Once the desired tracks have been chosen, click the Continue button at the bottom.
The ‘Import Visual Events from File’ window
The ‘Import Visual Events from File’ window will appear next.
If the file being imported is not a Pro Tools Session Text file, this window will be the first to appear.
The window is separated into two sections: the top section shows the column mapping of the ADR cues in a table-like manner; and the bottom shows the import settings.
ADR Cue Column mapping table
In the most ideal case, both the “Start TC” and “End TC” columns are mapped & the ADR Cues will retain their correct logged duration.
If the end timecode is missing, the default cue length set in the Preferences will be used.
If the end timecode is the only value available, it will be ignored, as there is no accurate start point in that case.
In case the imported file does not contain timecode information, you can still import the file and define the events’ timing after importing.
Text, comment, actor… are only additional information per cue which are desirable but not necessary to import the cues in the first place.
ADR Cue Import Settings section
Skip First Line - Check this box if importing a CSV or DBF file which contains a header line as the first line. ADR Master will use the first line to guess the column mapping and will ignore it for the actual content.
Applies Only to CSV and DBF Files. Please make sure before importing whether the file contains a header by inspecting it in a Text editor.
If no Event Type Column is Present, Import Events as: - As explained above, you can map the content of supported files to several properties of the events to be created when importing. One of the mappings is for the event type. When mapped, the column values will be used to set the visual event type. If not mapped, a default type will be used, which can be selected in the dropdown menu.
Text Encoding - Every text file has an internal text encoding. The encoding determines how the file content should be interpreted. A text file basically is nothing more than a sequence of bytes and ADR Master needs to know which character set to use to decode the bytes into human readable characters. That is why it is important to match the same export & import Text Encoding types. It is unfortunately not easily possible to detect the character set programmatically (it usually works for UTF-16 and for UTF-8). If you're uncertain about the text encoding used in the text file, try different text encodings until the best results are achieved. Problems will usually be visible with special characters like German Umlauts for example.
Offset Imported Cues by - add or subtract a defined timecode offset to all cues when importing them. For example, if the timeline start timecode is set to 01:00:00:00, but the imported cue sheet references a 10 hour start, you could simply enter 09:00:00:00 in the text box here to offset all imported cues by 9 hours.
Negative values are also permitted.
To bulk import the cues into the timeline, click the Import Events To Timeline button. The events will appear in the Timeline & in the Event list.
Or to import the cues as a script and enter a manual logging mode, click Import Events as Script.