Importing Visual Events from Ordered File Formats
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 ‘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 visual events in a table-like manner; and the bottom shows the import settings.
Visual Event Column mapping table
In the most ideal case, both the “Start TC” and “End TC” columns are mapped & the visual events 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 is additional information per cue which is desirable but not necessary to import the cues in the first place.
Visual Events Import Settings section
Skip First Line - Check this box if importing a CSV which contains a header line as the first line. Video Sync will use the first line to guess the column mapping and will ignore it for the actual content.
Applies Only to CSV. 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 Video Sync 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 10:00:00:00, but the imported cue sheet references a 1 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 button. The events will appear in the Timeline & in the Event list.