The structure of the CineLink file comprises a set of elements which define the rules the given file will be processed by.

The mandatory and optional elements are described in detail in the tables and samples below.

Important
Cinegy Convert v11 CineLink files are not compatible with Cinegy Convert legacy ones. The corresponding error message will appear.
Note
The CineLink file elements not recognized by processing modules will be ignored.

Mandatory Elements

ElementDescription

<source>

Defines the source media to be used to generate media streams.

<metadata>

Defines the additional metadata fields that describe the source.

Note
In case several CineLink files define the same metadata value, the last one in the list will provide the final metadata value. For example, task contains several sources, all of them are CinegyLink files with some metadata. The final metadata set for the Source will be combination of all distinct metadata with values being overridden in case defined several times.

MCRitem as a Source

The CineLink <source> section allows to define timeline XML specification as a source for media streams by <timeline> element. The following XML shows possible structure of the section:

<source>
  <media>
     <timeline>
             --- XML ---
     </timeline>
</media>
Note
Only single <timeline> element may be present inside the <source> section.
Important
The timeline XML syntax should follow the Cinegy Cinegy MCR item timeline XML specification.

Specifying Separate Files as a Source

The CineLink <source> section allows separate files specification as a source for media streams. The following XML shows the possible structure of the section:

 <source>
     <tracks>
        <video location='\\server\path\file.mxf'/>
        <audio location='\\server\path\file2.mxf' order='1'/>
        <audio location='\\server\path\file2.mxf' track='2' order='0'/>
        <data location='\\server\path\file3.mxf' track='0'/>
     </tracks>
</source>
Note
The three supported types of tracks are: video, audio and data.

Only single <tracks> element may be present inside the <source> element. Reordering of tracks can be achieved by the order element in the table below.

Specifying Muxed Files a Source

The CineLink <source> section allows muxed file specification as a source for media streams. The following XML sample shows the possible structure of the section:

<source>
     <file location='\\server\path\file.mxf' />
</source>

In this case all tracks from the specified file share intended to generate one media stream.

Initial Timecode Support

The CineLink <source> section supports defining the initial timecode. When the "Import to Archive" task is set, this value is checked and if detected, is applied to Original Tape In of the Master Clip. The sample below shows the possible XML schema:

<timefield name="startTime">
   <timecode frameRate="29.97">11;12;13;29</timecode>
  </timefield>

Traffic Program ID Processing

The XML sample below shows the possible structure of a CineLink file with "traffic_program_id" field defined:

  <metadata>
   <field name="traffic_programm_id" value="123"/>
	 <field name="clip_description" value="Some description"/>
  </metadata>
</cinelink>

Having defined the "traffic_program_id" field, the Cinegy Archive database is being searched for nodes with the corresponding Traffic ID. In case the node is a master clip and parent is a Placeholder Roll, the import operation is executed to this Placeholder Roll. As a result, new master clip is created inside a Placeholder Roll.

Important
The TV format defined for the Placeholder should correspond to the processed items format. In case the formats do not match, an warning message will appear in the log and the import process will be resumed as "traffic_program_id" field is not defined.

When the "traffic_program_id" field is not defined, the import to Cinegy Archive database proceeds according to the configured in the related profile settings.

Optional Elements

ElementDescription

<name>

Defines the source name to be used for {src.name} macro, empty value by default.

<ext>

Defines the source extension to be used for {src.ext} macro, empty value by default.

<location>

Defines the source location to be used for {src.location} macro, empty value by default.

<media>

Defines the way the video will be processed.

<startTime>

Defines the starting point for the clip.

<framerate>

Defines the actual framerate of the clip.

<duration>

Defines the file duration considering the default timecode value.

<offset>

Defines read start (SOM) from the beginning of media (00:00:00:00).

<tracks>

Defines audio, video or data tracks to be processed. It is possible to specify the order for tracks processing.

<order>

Defines the order for tracks processing.

Note
The tracks with order attribute are expected to be processed initially, considering minor value first. The tracks having no defined order attribute, will be processed in the second turn randomly; their order is not guaranteed.
Important
Refer to the Source Macros article to get detailed information on the supported macros.

Duration and Offset Support

The CineLink file supports definition of start and duration.

The sample XML structure with defined media start is provided in the examples below:

<media>
 <offset>
  <timecode frameRate="29.97">00:04:10.29</timecode>
 </offset>

The sample specifies duration in the format HH:MM:SSpFF where "p" can be either a ":" ";" "," or "." to indicate drop frame or non-drop frame.

Note
Short forms of timecodes are not supported.

The sample XML with specified duration is provided below:

<media>
 <duration>
    <time>45:13,123</time>
</duration>

The duration is specified in the format HH:MM:SSpMS, where "p" can be either a "," or "." to indicate ms part. Here, the short forms are supported. An example of time format explanation is given in the table below:

TimeDescription

0.125

125 ms

34.125

34 sec 125 ms

56

56 sec

12:56

12 mins 56 sec