flex 1007

7/31/2019 Flex 1007

1/58

7/31/2019 Flex 1007

2/58

FLEx EDL Exchange Protocol Version 1007 Page 2

7/31/2019 Flex 1007

3/58


Table of Contents

About FLEx ................................................................................................................................................4INTRODUCTION AND DISCUSSION........................................................................................................ 5RECORD ID CODE SUMMARY................................................................................................................. 9Code 000 - FLEx FILE ORIGINATOR DESCRIPTION DATA RECORD ...............................................12

Code 010 - PROJECT/FLEx FILE TITLE LINE DATA RECORD ........................................................... 15Code 011 - CLIENT AND TRANSFER FACILITY DATA RECORD.......................................................16Code 012 - DATE AND PERSONNEL DATA RECORD......................................................................... 17Code 013 - HEADING NOTES DATA RECORD..................................................................................... 19Code 100 - EDIT TYPE DATA RECORD ................................................................................................ 20Code 101 - EDIT TRACK OVERRIDE DATA RECORD .........................................................................24Code 110 - SLATE DATA RECORD ....................................................................................................... 26Code 111 - LAB ROLL and INK NUMBER DATA RECORD New.........................................................28Code 120 - SCRIPT DATA RECORD...................................................................................................... 30Code 121 - USER DATA RECORD (New) .............................................................................................31Code 200 - TELECINE EDIT DATA RECORD ........................................................................................ 32Code 201 - TELECINE EDIT DATA RECORD ........................................................................................ 35Code 300 - VTR EDIT DATA RECORD................................................................................................... 38

Code 301 - VTR STANDARD EDIT DATA RECORD New.....................................................................40Code 400 - ATR EDIT DATA RECORD .................................................................................................. 42Code 401 - ATR STANDARD EDIT DATA RECORD New .................................................................... 44Code 402 - ATR SOUND FILE NAME RECORD New............................................................................ 46Code 403 - ATR SOUND FILE CHANNEL NUMBER RECORD New.................................................... 48Code 500 - VIDEO SWITCHER TRANSITION EFFECTS DATA RECORD...........................................50Code 600 - AUDIO MIXER TRANSITION EFFECTS DATA RECORD .................................................. 52APPENDIX A ............................................................................................................................................ 54APPENDIX B ............................................................................................................................................ 56APPENDIX C REVISION HISTORY AND DETAIL................................................................................. 57

7/31/2019 Flex 1007

4/58


About FLEx

FLEx (Film Log EDL Exchange) Protocol is intended to permit the automated

communication of information between the telecine bay and off- and on-line editing systems.

This information consists of a database relating all original film reel, positional, and KeyKode

(TM) data of transferred "elements" (scenes and takes) to the corresponding destinationvideotape reel and time code. In some cases an additional time code representing sound

"sync" and sound reel are carried in the database to assist the process of conforming sound to

picture. The record tapes created in telecine become playback tapes during the video off-line

process, during which a conventional EDL (edit decision list) is created that represents (via

videotape reel designations and time codes) the finished show. "Trace" software can then

examine each edit decision in the EDL, find the corresponding film material in the FLEx

database, and produce a film conform list ("negative cutters list") as output.

FLEx also supports list-driven field-accurate and varispeed automated editing in the telecine

bay and can be used to facilitate conforming film material for release in multiple video

standards or to generate multiple tape masters in various formats simultaneously.

da Vinci is working with a variety of edit system and time code equipment manufacturers,

and post production users, to incorporate FLEx support into current and existing products. We

are incorporating FLEx support into our popular TLC Telecine Editing System, and other

products. Production and Post Production centers that have available the services of a

computer database-literate individual can immediately benefit from adopting FLEx in their

facility.

FLEx is an evolving standard. Your suggestions are encouraged.

Audience and Scope of this Document

This document is intended for those individuals familiar with general knowledge of computer

concepts, such as the ASCII code, disk files, and similar notions, who wish to implement FLEx

compatible systems. Also assumed is a general knowledge of video and film editing. It is not

intended to be a tutorial on computer science, nor a precisely "formal" specification in the sense

of a SMPTE standard. It is intended to provide sufficiently unambiguous information and

guidance to a television engineer or television-literate programmer to successfully

implement FLEx input, interpretation, and output processing on modest computers.

If questions arise, the title page of this document shows the current contact for more

information.

For those of you interested in FLEx for dailies-logging applications of the TLC Telecine

Editing System, please read this document thoroughly then refer to Appendix A for some

helpful hints about where TLC places dailies data within FLEx data records.

7/31/2019 Flex 1007

5/58


INTRODUCTION AND DISCUSSION

ASCII FLEx

ASCII FLEx is intended to be stored on disk and transmitted between users in "non-real-time"applications, typically on floppy disks.

ASCII FLEx files consist of a series of ASCII FLEx records each terminated by one or more

carriage-return line-feed pairs. The first three characters of each record should be interpreted as a

record ID code ranging from 000 to 999. The record ID code defines the type of record, i.e.,

the number, type, and position of data fields that data record type contains. Processing

software should first examine each record's ID code then take appropriate action on the

remaining characters in the record.

A few record types are mandatory, most are optional and their inclusion is a function of

product capability, specific project requirements or facility policy. FLEx is specificallydesigned to avoid imposing bureaucratic overhead and costs on the user and FLEx product

developer, while maintaining a standardized growth path and permitting virtually unlimited edit-

bay automation once the need arises.

Also, an expansion and customization feature is built into the FLEx specification so that anyone

can expand upon the basic FLEx structure without formal approvals and delays, when adding

features for proprietary, short-term, or special needs. Such customization does not affect

transfer of other, standard contents of the FLEx file to and from third party computer systems.

Only the data records actually required by the user application need be present in the FLEx file.

The detailed definition of each record appears in the pages that follow. Each definitionincludes a discussion of intended usage, the generic record format, and an example. FLEx

implementers submitting new record types for inclusion in the proposed standard are

encouraged to document and submit them in a similar style. da Vinci has established a dial-up

BBS (electronic bulletin board system) to facilitate this application process, at 818-902-0937

(14,400 baud,N,8,1). Call the BBS to set up your initial account up, then fax the user name to

us so that we can grant your account FLEx file area access rights.

Within each data record, individual data fields are delineated by their column position, rather

than by "space" or "comma" delimiting (two other common methods). Fixed column delimiting

was selected because it is easy to view and edit manually, and to permit user-entered data to

include commas and spaces (such as in show titles and similar textual entries). To clarify thecolumn positions of data fields in each data record definition in this document, a "column

ruler" is shown directly above each such definition. The ruler looks like this:

0 1 2 3 4 5 6 701234567890123456789012345678901234567890123456789012345678901234567890123456789||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||

Of course, this ruler is not present in actual FLEx files.

7/31/2019 Flex 1007

6/58


Note that columns are counted beginning with column 0, not 1, and therefore represent

indices into conventional character string arrays (at least for programming languages that

begin counting array elements with index 0).

Records need not be of fixed length if the last data field of the record is variable. Forexample, a short facility name (see record 011 format) may terminate with a carriage-return

line-feed pair early (or be padded to length with spaces), however a short client name (in the

same example) must be padded with ASCII space characters to preserve the column position of

subsequent data fields.

Processing software reading ASCII FLEx files record-by-record can safely assume no single

record shall exceed 255 characters in length, including the carriage-return line-feed pair (i.e., a

maximum of 253 data characters). Software generating ASCII FLEx file output shall conform

to this length limit; it is suggested that 80 columns or less be used whenever practical. All

record definitions in this document conform to the 80 column limit. Unused numeric fields

should be assumed to contain zero if they are found to contain a space or carriage return(perhaps as a result of manual text editing on a word processor), however, FLEx software

implementers should insure at least a single ASCII '0' (48 decimal, 30 hex) be present in

unused numeric fields in computer generated output.

Software generating FLEx data records must not insert control codes (ASCII codes less than 32

decimal, 20 hex), except for carriage-return and line-feed codes. Bear this in mind when

designing custom (900 series) data records. If binary data must be stored in a FLEx record

(from an EMEM dump, for example), conversion to "hex-ASCII" format (i.e., 2 printable hex

characters per original byte) is suggested. In short, do not create records which can not be

directly printed, viewed and edited on off-the-shelf word processors.

As a general rule, software implementers are cautioned to design their software in a robust

manner, expecting the possibility that human edited FLEx contents may not be perfectly

formatted, and that "reasonable" assumptions may be necessary. These are noted from time-to-

time throughout this document.

In the generic definitions,

a means any printable alphanumeric upper or lower-case text or ASCII space in some cases

FLEx expects to see particular string text, as specified.

# means an ASCII numeric digit of the range [0-9] inclusive; means a fixed positiondecimal point separating whole part from fraction;

Boldface text represents string literal constant text appearing in the data record purely to

enhance human readability of the FLEx file contents when viewed, edited and printed.

In the examples,Italic textshows variable (i.e., user generated) sample data.

7/31/2019 Flex 1007

7/58


A final explanatory note. Unless specifically indicated, in this document the words "record",

"field", and "code" shall refer to their conventional meanings in the data processing industry,

rather than their usage in the television industry. Specifically, if time code is being discussed,

"time code" will appear, not "code".

FLEx Time code Numeric Format

FLEx uses a video-field-accurate time code format derived from the TLC Editor. A video field

ID is appended to the basic time code value, and drop/non-drop status is encoded by the

punctuation characters used to separate digit groups:

hh:mm:ss:ff.0Means a non-drop frame number, video field 1

hh:mm:ss:ff.1Means a non-drop frame number, video field 2

hh;mm;ss;ff,0Means a drop frame number, video field 1

hh;mm;ss;ff,1Means a drop frame number, video field 2

Of course, each of these is a 13 character ASCII string--not a BCD or other value.

EBU time code values use the non-drop punctuation.

24 Frame time code will also carry the non-drop punctuation.

Field-accurate time codes are required in order to permit seamless insert edit replacement of

3:2 pull down imagery, and to identify the 3:2 ("SMPTE") framing relationship of each edit.

Software applications not requiring field-accuracy may simply strip the last two characters

from each ASCII time code string during processing.

FLEx Film Counter and KeyKode (TM) Numeric Formats

Film edit points are specified in one of two formats, encoded by punctuation:

ffffff+ff Means six digits of feet, plus (film) frames, example:002000+08

hfhfhf&ff Means six digits of half-feet, plus (film) frames, example:004000&08

Leading zeroes may generally be omitted, software developers should not assume them, nor

assume left- or right-hand justification when reading data records.

Of course, most 35mm projects will use feet+frames, and 16mm will use half_feet+frames.

This will be the case for any Kodak KeyKode (TM) numbered stock. However, FLEx allows

either format to be used with either film gauge.

7/31/2019 Flex 1007

8/58

7/31/2019 Flex 1007

9/58


RECORD ID CODE SUMMARY

Here is a brief summary of record codes, group ranges and intended usage, the detailed

definition of each data type is presented in the pages that follow. Data record numbers below

900 not shown here are not yet defined, and are reserved for future specification:

Code Name and Usage

000-009 FILE IMPLEMENTATION DATA RECORDS, as follows:

000 FLEx File Originator Description Record

Identifies details of the device that created the FLEx file,

to facilitate processing of the file contents by the recipient.

010-099 SESSION HEADING DATA RECORDS, as follows:

010 Project/FLEx File Title Line Data Record

Project title.

011 Client and Transfer Facility Data Record

Client name and post/transfer facility names.

012 Date and Personnel Data Record

Production and transfer dates, personnel and telecine bay.

013 Heading Notes Data Record

User defined notes for other information not appearing above.

100-199 TRANSFER EDIT DATA RECORDS, as follows:

100 Edit Type Data Record

Defines 3:2 pull down, video standard, and edit tracks.

101 Edit Track Override Data Record

Permits revised track selection on a per-recorder basis.

110 Slate Data Record

Carries scene, take, camera roll, and "production" time code.

111 Lab Roll and Ink Number data fields

120 Script Data RecordAttaches misc. script notes to an edit.

200-299 TELECINE TRANSPORT DATA RECORDS

200 Telecine Edit Data Record 4 perf 35mm or 16 mm modes

Defines reels, edit points, and edge code for telecine transport(s)

7/31/2019 Flex 1007

10/58


201 New Telecine Edit Data Record 3 perf implementation

Defines reels, edit points, and edge code for telecine transport(s)

Code Name and Usage, continued

300-399 VTR TRANSPORT DATA RECORDS, as follows:

300 VTR Edit Data Record

Defines reels, edit points and mode for VTR(s)

301 VTR Video Standard Data Record

400-499 ATR TRANSPORT DATA RECORDS, as follows:

400 ATR Edit Data Record

Defines reels and edit points and mode for ATR(s)

401 ATR Video Standard Data Record

402 ATR Audio File Data Record

403 ATR Audio File Track Data Record

500-599 VIDEO SWITCHER EFFECTS DATA RECORDS, as follows:

500 Video Switcher Transition Effects Data Record

Defines types and timing of switcher edit transition(s)

600-699 AUDIO MIXER EFFECTS DATA RECORDS, as follows:

600 Audio Mixer Transition Effects Data Record

Defines types and timing of mixer edit transition(s)

700-899 AUXILIARY DEVICE CONTROL DATA RECORDS, (undefined, reserved)

900-999 USER SPECIFIC CUSTOM FORMAT DATA RECORDS

(user defined, unspecified)

7/31/2019 Flex 1007

11/58


7/31/2019 Flex 1007

12/58


Code 000 - FLEx FILE ORIGINATOR DESCRIPTION DATA RECORD

ID Code 000 Usage: Mandatory.

Record code 000 is reserved for specifying details of the device that created the FLEx file, sothat if known implementation differences exist from one product to the next or between

product software releases, the receiving software can take appropriate action. Although all

FLEx files should adhere to the prevailing FLEx protocol standard record codes and formatting

for record codes 000-899, it is anticipated that certain manufacturers may elect to introduce

new record types to meet specific needs prior to formal incorporation into the protocol

standard document. To do so, the manufacture should contact the FLEx Protocol Manager to

coordinate allocation and format assignment of new record codes below 900.

Codes 900-999 are user defined and require no formal authorization; they are intended for

product specific setup/configuration data storage and retrieval and for proprietary feature

related data records. Receiving software should simply retain in place (not process or relocatewithin the file) 900-999 series records unless specifically designed to interpret them according

to the manufacturer code present in record 000. Manufacturers are encouraged to format their

data records to fit within 80 columns whenever possible, for ease of viewing and printing on

low cost computer equipment. If a manufacturer needs more than 100 data records for

proprietary needs, a single 900 series code can be used, having a sub-code field contained

within it followed by sub-code data fields. This permits virtually unlimited expansion of record

types while maintaining compatibility with the basic FLEx standard.

A record 000 should appear as the first record of the file. If more than one instance of a

record 000 is present in the file (as might occur after joining multiple files), the data

following each record 000 shall be interpreted according to the contents of the most recentrecord 000. In the event a file does not begin with a record 000, the prevailing SMPTE FLEx

standard protocol should be assumed by the processing software, and all 900-999 series records

ignored.

Format:

0 1 2 3 4 5 6 701234567890123456789012345678901234567890123456789012345678901234567890123456789||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||000 Manufacturer aaaaaaaaaa No. ### Equip aaaaaaaaaa Version ######## FLEx ####

Example:000 Manufacturer da Vinci No. 022 Equip TLC Version 400 FLEx 1006

Interpretation:

This file was created on a da Vinci TLC. da Vinci is manufacturer 022; the TLC was running

software version 400, and writing a FLEx file compatible with FLEx protocol document

version 1006.

7/31/2019 Flex 1007

13/58

7/31/2019 Flex 1007

14/58

7/31/2019 Flex 1007

15/58


Code 010 - PROJECT/FLEx FILE TITLE LINE DATA RECORD

ID Code 010 Usage: Optional.

The title line record holds the text of the project title or FLEx file title. If more than oneinstance of a record 010 is present in the file (as might occur after joining multiple files), the

data records following each record 010 shall be interpreted as being associated with the most

recent record 010 title.

Format:

0 1 2 3 4 5 6 701234567890123456789012345678901234567890123456789012345678901234567890123456789||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||010 Title aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa

Example:

010 Title TLC Madness, Show #888, Air Date: 05-01-2001

Field Definitions:

Index Length Description

00-02 3 Record ID Code 010

04-08 5 "Title" A string literal constant.

10-79 70 Alphanumeric Title text, assigned by user.

Notes:

This example demonstrates why comma or space delimited data fields were rejected in

designing the ASCII FLEx format; i.e., most people expect to use spaces and commas in the

text data they enter.

In general, record ID codes 010-099 are intended for "heading" information; i.e., information

that applies "globally" to all following records in the FLEx file. One or more groups of

heading records may appear in a single file (perhaps as a result of file joining or to indicate thestart of records corresponding to a new act, shoot date, etc.). If more than one instance of a

heading record or group is present in the file, the data following each shall be interpreted

as associated with the most recent heading record(s).

7/31/2019 Flex 1007

16/58

7/31/2019 Flex 1007

17/58


Code 012 - DATE AND PERSONNEL DATA RECORD


This record identifies the shoot and transfer dates, the telecine bay used, and the colorist andassistant's initials.

Format:

0 1 2 3 4 5 6 701234567890123456789012345678901234567890123456789012345678901234567890123456789||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||012 Shoot Date xx-yy-zz Transfer Date xx-yy-zz Opr aaa Asst aaa Bay aaaaaaaa

Example:

012 Shoot Date 02-01-01 Transfer Date 02-02-01 Opr RGB Asst YUV Bay TC-1012 Shoot 2002-02-29 Xfer Date 2002-10-31 Opr RGB Asst YUV Bay TC-1

Field Definitions:



04-13 10 "Shoot Date" A string literal constant. Optionally Shoot could be used to

allow different date formats.

15/13-22 8 Alphanumeric date string, assigned by user. Optionally, the date format could beexpanded to allow the YYYY-MM-DD which is widely used. See Notes.

25-37 13 "Transfer Date" A string literal constant. Optionally Xfer Date could be used

to allow different date formats.

39/37-46 8 Alphanumeric date string, assigned by user. Optionally, the date format could be

expanded to allow the YYYY-MM-DD which is widely used. See Notes.

49-51 3 "Opr" A string literal constant.

53-55 3 Alphanumeric colorist's initials, assigned by user.

58-61 4 "Asst" A string literal constant.

63-65 3 Alphanumeric assistant's initials, assigned by user.

68-70 3 "Bay" A string literal constant.

7/31/2019 Flex 1007

18/58


72-79 8 Alphanumeric bay ID string, assigned by user.

Notes:

The original FLEx format provided a date format as mm-dd-yy commonly used in North

America. This string was meant to be flexible and could be expanded to allow the yyyy-mm-ddformat provided the label text is shortened. Since this is a departure of the original FLEx

protocol, users should be aware of the minor incompatibilities. As long as the facility provider

and the end user are aware of the format, there should be few problems. Since it is a text string,

any punctuation may be used to separate the dates.

7/31/2019 Flex 1007

19/58


Code 013 - HEADING NOTES DATA RECORD


Allows inclusion of additional user supplied "heading" text as needed throughoutFLEx file.

Format:

0 1 2 3 4 5 6 701234567890123456789012345678901234567890123456789012345678901234567890123456789||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||013 Notes aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa

Example:

013 Notes Reels 213A and 213B are KeyKoded; reel 99 is stock shot footage.

Field Definitions:



04-08 5 "Notes" A string literal constant.

10-79 70 Alphanumeric note string, user supplied.

Note: This field only appears once in the Heading area for each FLEx file. For event by eventnote data, see data field 120, Script below.

7/31/2019 Flex 1007

20/58

7/31/2019 Flex 1007

21/58

7/31/2019 Flex 1007

22/58

7/31/2019 Flex 1007

23/58


01;00;00;00,0 = 215,784 video fields of delay (drop frame at 59.94/sec, an exact hour)

For typical split delays of under a minute, the two formats yield equal delays.

7/31/2019 Flex 1007

24/58

7/31/2019 Flex 1007

25/58


Notes:

If no record 101 entries pertain to the current edit, the default tracks contained in record 100

apply to all recorders. One or more record 101 entries may be present in a single edit, asneeded to adjust track selections on individual transports.

7/31/2019 Flex 1007

26/58

7/31/2019 Flex 1007

27/58


take" on the spliced reel may come from unrelated camera rolls. In such cases, the telecine

transport data record will show a "lab" (intermediary) reel ID string.

The sound roll ID and time code, if present, will match that found in one of the ATR transport

data records for the current edit, if the edit system is synchronizing a 1/4" or DAT transport

via slate time code. Otherwise, these fields are blank or could be used to reference a mag track.

7/31/2019 Flex 1007

28/58

7/31/2019 Flex 1007

29/58


this record is present (optionally), the parsing software would have better knowledge of this

information.

7/31/2019 Flex 1007

30/58


Code 120 - SCRIPT DATA RECORD


Script or other misc. editing or telecine transfer notes for each edit can be maintained in oneor more script records. This record is intended to permit recalling an edit by its script notes,

for example.

Format:

0 1 2 3 4 5 6 701234567890123456789012345678901234567890123456789012345678901234567890123456789||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||120 Scrpt aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa

Example:

120 Scrpt POV launch tower; PA: "T-minus...6...5... Abort, retry, ignore?>"

Field Definitions:



04-08 5 "Scrpt" A string literal constant.

10-79 70 Alphanumeric script note string, user supplied.

7/31/2019 Flex 1007

31/58


Code 121 - USER DATA RECORD (New)


This new optional record provides for additional text data fields to be carried through thesession. Two fields, User 1 and User 2 have been added for this purpose. A possible use for

these fields would be remarks like MOS, Shot Names that dont fit in the Scene data area, or a

place to flag selects, leaving the Script notes for other purposes.

Format:

0 1 2 3 4 5 6 701234567890123456789012345678901234567890123456789012345678901234567890123456789||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||121 User1 aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa User2 aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa

Example:

121 User1 MOS User2 Shot Name 123

Field Definitions:



04-08 5 "User1" A string literal constant.


42-46 5 "User2" A string literal constant.


7/31/2019 Flex 1007

32/58

7/31/2019 Flex 1007

33/58


48-50 3 "Key" a string constant.

52-56 5 The film manufacturer, if known (can be derived from KeyKode).

EASTM Eastman Kodak CompanyFUJI Fuji Film Company

AGFA Agfa-Gevaert N.V.

[00,04-99] an unassigned manufacturer code

not known

58-65 8 KeyKode number prefix and emulsion; or edge code prefix if known.

Examples:

KJ123456 5296 Emulsion, KeyKode prefix 123456

96123456 same as above, refer to Eastman Kodak KeyKode handoutfor more information. For conventional key numbers, this field holds any

alphabetic prefix characters found ahead of the key number, or is blank.

67-75 9 KeyKode or conventional key number in-point, with frame offset to exact first

frame of imagery transferred in edit.

77 1 "p" A string constant; abbreviation for "perf"

78 1 Of the four perfs in each 35mm frame, the perf aligned with the "zero frame

reference mark" of KeyKode numbered film stock. Refer to Kodak KeyKode

handout. Blank for conventional key numbers.

35mm Gauge 16mm Gauge

'1' perf at top of image Always '1' for 16mm

'2' upper middle perf

'3' lower middle perf

'4' bottom perf of frame

'?' or if unknown

Notes:

The transport user name is optional. Best image consistency is often obtained when re-

transferring material on the same telecine as was used for the original transfer. "Length" rather

than "duration" terminology is specifically used to refer to the edit interval since the meaning of

the latter term is ambiguous when transferring at other than "standard" speed. The edit-in

position is the first frame of imagery transferred to tape; the edit length shows the total length

transferred to tape, regardless of the speed of the film.

7/31/2019 Flex 1007

34/58

7/31/2019 Flex 1007

35/58

7/31/2019 Flex 1007

36/58


38-46 9 The total edit length as an absolute count of film frames instead of key+frames as

in record 200 format. This simplifies conversion software with regard to long

and short feet phasing as in 3 perf.

48-50 3 "Key" a string constant.

52-56 5 The film manufacturer, if known (can be derived from KeyKode)

EASTM Eastman Kodak Company

FUJI Fuji Film Company

AGFA Agfa-Gevaert N.V.

[00,04-99] an unassigned manufacturer code

not known

58-65 8 KeyKode number prefix and emulsion; or edge code prefix if known.

Examples:

KJ123456 5296 Emulsion, KeyKode prefix 123456

96123456 same as above, refer to Eastman Kodak KeyKode handout

for more information. For conventional key numbers, this field holds any

alphabetic prefix characters found ahead of the key number, or is blank.

67-75 9 KeyKode or conventional key number in-point, with frame offset to exact first

frame of imagery transferred in edit.

77 1 "p" A string constant; abbreviation for "perf"

78-79 2 Expanded perf range [1:nn] where nn is the highest perf pertaining to the film

gauge in use.

In 3 perf, p1 means the prior reference dot appears a the top (head) of the

reference frame. p2 means the prior reference dot appears at the middle of the

reference frame. p3 means the prior reference dot appears a the bottom (tail) of

the frame.

For any gauge, p , or p?, or p?? shall indicate the perf relationship is

unknown.

Notes:

This record has been added to support 3 perf and various other film types. Use this record in

replacement of code Record 200 for all new film types. Parsing software should look for either

record type. Record 201 could be made to replace record 200 in the future.

7/31/2019 Flex 1007

37/58

7/31/2019 Flex 1007

38/58

7/31/2019 Flex 1007

39/58


"##.## Fps" A playback; at speed shown in frames/sec

"##.## Rec" A disk recorder; " " " " "

A playback at standard speed

"Playback " A playback at standard speed

(In all the above, recall that FLEx is case insensitive)

20-27 8 The VTR's reel assignment.

29-30 2 "At" A string literal constant.

32-44 13 The edit in-point time code.

46-48 3 "For" A string literal constant.

50-62 13 The length of the edit, if known else blank.

64-68 5 "Using" A string literal constant.

70-78 9 The time code source; one of the following:

Unknown; unspecified.

"LTC " Longitudinal time code

"LTC USER " Longitudinal user bits

"VITC " Vertical interval time code

"VITC USER" Vertical interval user bits

"ASTC " DVR Vertical interval time code

"ASTC USER" DVR Vertical interval user bits

"TIMER x " Tape timer; x='1' or '2'

"VITC AUTO" VTR is auto-selecting LTC/VITC"LTC TIMER" Editor is jamming timer 1 to LTC

(In all the above, recall that FLEx is case insensitive)

Additional values pending--for example, the VITC's line number.

Notes:

The last mode implies the editing system is selectively reading the LTC track, and presetting the

transport's TIMER-1 prior to start of pre-roll so as to extrapolate from time code during long

pre-rolls for which insufficient time code was originally recorded. This is a frequent problem

with 1/4" audio reels.

Longitudinal and VITC tracks are being used with increasing sophistication, often carryingdissimilar data. For example, user bits may carry production "sound sync" time code or

another useful time code reference signal. FLEx specifies the source of edit time code for this

reason.

7/31/2019 Flex 1007

40/58

7/31/2019 Flex 1007

41/58


1080i/25

720P/59

720P/60

Allow user to define new modes as necessary.

25-32 8 "Edit Out" A string literal constant.

34-46 13 The Edit Out-point time code. This should agree with the duration defined.

48-54 7 "TC Type" A string literal constant.

56-58 3 The type of time code used as defined by the following strings:

30D 30 Drop Frame

30N 30 Non Drop Frame

25 25 Frame EBU24 24 Frame

Notes: This record is designed to provide specific video standard on a per deck basis. While

optional, systems running in a Dual Sync mode, such as the TLC should provide this record as

a means of defining specific standard data. The new Edit Out field is provided to simplify

calculating this information from the previous record. The Time Code Type field also simplifies

parsing the type from the video standard. Additionally, there may be sessions where the time

code type does not match the video standard.

7/31/2019 Flex 1007

42/58

7/31/2019 Flex 1007

43/58


32-44 13 The edit in-point time code.

46-48 3 "For" A string literal constant.

50-62 13 The length of the edit, if known else blank.

64-68 5 "Using" A string literal constant.

70-78 9 The time code source; one of the following:

Unknown; unspecified.

"LTC " Longitudinal time code

"LTC USER " Longitudinal user bits

"VITC " Vertical interval time code

"VITC USER" Vertical interval user bits

"TIMER x " Tape timer; x='1' or '2'

"VITC AUTO" ATR is auto-selecting LTC/VITC

"LTC TIMER" Editor is jamming timer 1 to LTC(In all the above, recall that FLEx is case insensitive)

Notes:

Use of VITC with a transport identified in the FLEx listing as an ATR may imply a VTR was

used purely as an audio transport (e.g. U-Matic PCM, etc.).

The last mode implies the editing system is selectively reading the LTC track, and presetting the

transport's TIMER-1 prior to start of pre-roll so as to extrapolate from time code during long

pre-rolls for which insufficient time code was originally recorded. This is a frequent problem

with 1/4" audio reels.

7/31/2019 Flex 1007

44/58


Code 401 - ATR STANDARD EDIT DATA RECORD New

ID Code 401 Usage: Optional. Provides similar data as VTR Record 301.

This optional data record provides for more detailed video standard definitions on a per deckbasis. The Edit Out time has been optionally provided for better usability. The Time Code Type

is defined since there could easily be multiple types in a session. A new Media Type field has

been defined.

Format:

0 1 2 3 4 5 6 701234567890123456789012345678901234567890123456789012345678901234567890123456789||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||401 Vid Std aaaaaaaaaa Edit Out hh.mm.ss.ff.f TC Type aaa

Examples:

401 Vid Std 1080/24Psf Edit Out 01:23:34.04.0 TC Type 24

Interpretation:

This new optional record is defined to cover multiple video standards in a session. This defines

the time code type for the deck as it may not be obvious from the standard. The Edit Out time is

optionally provided, however, this could be calculated from the Length fields in record 400. It is

placed here for human readable user convenience.

Field Definitions:



04-10 7 "Vid Std" A string literal constant.

11-21 10 New Video Standard Field as defined by one of the following strings:

"525/60" NTSC Traditional.

"625/25" PAL Traditional

625/24 Slow PAL

1080P/23

1080P/241080Psf/23

1080Psf/24

1080Psf/25

1080Psf/29

1080Psf/30

1080i/29

1080i/30

7/31/2019 Flex 1007

45/58

7/31/2019 Flex 1007

46/58


Code 402 - ATR SOUND FILE NAME RECORD New

ID Code 402 Usage: Optional. Provides sound file name and optional project title.

This optional data record provides for logging the audio sound file name and optional path.Intended for use with DIVA and INDAW audio recorders and similar devices.

Format:

0 1 2 3 4 5 6 701234567890123456789012345678901234567890123456789012345678901234567890123456789||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||402 FileName aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa

Examples:

402 FileName D344180R.wav

402 FileName Helen of Troy_T076_06180R_2.bwf402 FileName Shadows_DV85_ZAX80R_1.bwf

Interpretation:

Each audio recording or take may be located throughout the disk drive. This record will help

trace back the source of the field audio during the dailies transfer.

Field Definitions:



04-11 8 "FileName" A string literal constant.

13-79 67 Audio File Name to include file name extension. May or may not be case

sensitive so as to support the source drive system parameters.

This field may contain extended project information prior to the audio file name.

This text information will be separated by the underscore _ character. Three

types of information separated by the underscore _ character include:

-Project Title and/or location sound mixer comments.

-Sound Roll ID

-Audio file name with file extension name separated by a period ..

Notes: This field may include extra information normally found elsewhere in the FLEx file.

This was done to make a visual identification of the media information on location. The above

examples contain the following information:

D344180R.wav Name of sound file and extension.

7/31/2019 Flex 1007

47/58

7/31/2019 Flex 1007

48/58

7/31/2019 Flex 1007

49/58

7/31/2019 Flex 1007

50/58


Code 500 - VIDEO SWITCHER TRANSITION EFFECTS DATA RECORD

ID Code 500 Usage: Mandatory if one or more switcher effects during edit.

Defines the behavior of one or more switchers during the edit. Each switcher has its own #500record; each may have multiple #500 records in a single edit, if multiple delayed switcher

transitions are desired. In telecine, multiple switchers are increasingly common when

multi-format transfers are made simultaneously. For instance, a component and composite

combination, or an analog and digital combination may be used simultaneously.

Format:

0 1 2 3 4 5 6 701234567890123456789012345678901234567890123456789012345678901234567890123456789||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||500 aaaaa ## aaaaaaaa to aaaaaaaa Fx #### Rate ### Delay hh:mm:ss:ff.f

Examples:

500 GV100 01 Wipe REEL023 to Reel023B Fx -023 Rate 030 Delay500 RGB 02 Dissolve BLACK to 026 Fx Rate 060 Delay 00:00:05:00.0500 TENXL 8 Cut to 121C Fx Rate Delay 00:01:00:00.0500 GV200 1 Register 123 to 001A Fx 2 Rate 15 Delay 00;00;56;12,1

Field Definitions:



04-08 5 The user's switcher name, if any.

10-11 2 Unique switcher ID number, range [00-99]; defines which switcher performs the

effect.

13-20 8 The type of effect to perform; one of:

"Dissolve" A fade transition, see Rate for rate

"Wipe " A wipe transition, see Fx for wipe code

"Cut " A cut

"Register" A switcher register recall, Fx holds the register number to

recall.

(other values pending)

22-29 8 The "from" source reel assignment, output before the effect. If the edit is

associated with a switcher cross point lacking a transport, the reel must still be

defined. Common assignments include "BLACK" "AUX" "BARS" "SLATE",

per example 2.

7/31/2019 Flex 1007

51/58


31-32 2 "to" A string literal constant.

34-41 8 The "to" source reel assignment, output after the effect. Non-transport cross

points must be defined per "from" above.

43-44 2 "Fx" A string literal constant.

46-49 4 Wipe code (see notes) or switcher effects register number.

51-54 4 "Rate" A string literal constant.

56-58 3 The transition rate expressed as a video frame count [000-999].

60-64 5 "Delay" A string literal constant.

66-78 13 The delay between the start of the edit and start of effect.

Notes:

Refer to SMPTE document RP 146-1987 for the suggested standard assignment of wipe patterns

to wipe codes. Negative wipe codes result in reversal of the normal effect transition direction.

A single FLEx edit may contain any number of #500 switcher data records. Edit systems that

intend to auto-conform from FLEx files should read and pre-process all effects records before

pre-roll begins. Do not assume #500 records are sorted by ascending transition delay times,

although this is the suggested manner in which to produce FLEx output files when a single

switcher is used. For multiple switcher configurations, other sorting priorities may appear. Forexample, the records may be sorted by switcher, then delay.

Cross point number assignments are not specified by this data record. It is assumed that

the user has established cross point assignments to reels prior to starting auto-assembly, or

that the edit system has saved the cross point assignment array in the FLEx file by using a

custom 900 series data record.

7/31/2019 Flex 1007

52/58


Code 600 - AUDIO MIXER TRANSITION EFFECTS DATA RECORD

ID Code 600 Usage: Mandatory if one or more audio mixer effects during edit.

Defines the behavior of one or more mixers during the edit. Each mixer has its own #600record; each may have multiple #600 records in a single edit, if multiple delayed mixer

transitions are desired.

This record type is similar to record type 500.

Format:

0 1 2 3 4 5 6 701234567890123456789012345678901234567890123456789012345678901234567890123456789||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||600 aaaaa ## aaaaaaaa to aaaaaaaa Fx #### Rate ### Delay hh:mm:ss:ff.f

Examples:

600 AMX 01 Register REEL023 to Reel023B Fx 8 Rate 030 Delay

Field Definitions: (refer also to the definition of record type 500, above)



04-08 5 The user's mixer name, if any.

10-11 2 Unique mixer ID number, range [00-99]; defines which mixer performs the effect.

13-20 8 The type of effect to perform; one of:

"Dissolve" A fade transition, see Rate for rate

"Cut " A cut

"Register" A mixer register recall, Fx holds the register number to recall

(other values pending)

22-29 8 The "from" source reel assignment, output before the effect.

31-32 2 "to" A string literal constant.

34-41 8 The "to" source reel assignment, output after the effect.

43-44 2 "Fx" A string literal constant.

46-49 4 Mixer effects register number.

7/31/2019 Flex 1007

53/58


51-54 4 "Rate" A string literal constant.

56-58 3 The transition rate expressed as a video frame count [000-999].

60-64 5 "Delay" A string literal constant.

66-78 13 The delay between the start of the edit and start of effect.

Notes:

A single FLEx edit may contain any number of #600 mixer data records. Edit systems that

intend to auto-conform from FLEx files should read and pre-process all effects records before

pre-roll begins. Do not assume #600 records are sorted by ascending transition delay times,

although this is the suggested manner in which to produce FLEx output files when a single

mixer is used. For multiple mixer configurations, other sorting priorities may be easier to

interpret. For example, the records may be sorted by mixer, then delay.

Cross point number, mixes, and fader group assignments are not specified by this data record.

It is assumed that the user has established such assignments to reels prior to starting auto-

assembly, or that the edit system has saved the assignment array in the FLEx file by using a

900 series data record.

7/31/2019 Flex 1007

54/58

7/31/2019 Flex 1007

55/58


20-27 The tape reel assignment of the ATR.

32-44 The time code frame representing sound sync to telecine

50-62 The length of the edit, expressed as a time code duration.

Also, TLC names the audio transport "SOUND" in columns 04-08 during dailies transfers

involving sound sync and copies the in-point time code to the slate data record 110 (above).

Obviously, an enhanced logging process can support far more information, such as session

heading data, A/V track selection to individual recorders and switcher signal routing, slate

information, script notes, etc.

Note: To facilitate downstream data processing, in all numeric data fields, film and time code

entries, TLC includes leading zeroes so that the positions of all punctuation characters are

fixed for all records of the same type. Software implementers should expect drop or non-drop,

and feet or half-feet formats to be present. Punctuation should be examined for each film andtape number processed, and the appropriate conversion routine executed.

In the event TLC doesn't know what film or tape number to use, the data field is all .

For instance, if sound sync "production" time code was not defined during the transfer edits, that

field in record 110 remains blank; it will not hold "00:00:00:00.0".

For all field types, TLC left-justifies all data entries, so that they appear next to fixed text labels

that may be associated with them, making printouts easier to read.

TLC writes its ASCII FLEx output to. MS-DOS type media, to filename.FLX, where

"filename" is user-determined at session time.

Generally, TLC uses feet+frames format numbering on 35mm stock, and half-feet format on

16mm stock, so as to correspond to the conventions used by the Eastman KeyKode numbering

technology. It is a simple matter in (your) software to convert between these formats, if needed.

Some FLEx lists may be "dirty." That is, one edit's out-point will not generally coincide with

the next edit's in-point, unless the colorist has taken pains to "clean the list." Later versions of

TLC software provides assistance in maintaining this relationship. In the event the list has not

been cleaned, it is best to go by each edit's VTR in-point to know precisely where that material

can be found on tape. Since it is almost universally the case that colorists assemble-edit their

"select takes" to tape sequentially, the differences between in-points of a FLEx list sorted byVTR in-points yields the duration of each edit. Styles differ, but each edit is generally "slate-

to-slate" or "flash-to-flash," thus having plenty of "handle" around the critical material.

7/31/2019 Flex 1007

56/58

7/31/2019 Flex 1007

57/58

7/31/2019 Flex 1007

58/58

flex 1007

Documents