All the tasks performed on the ingested material in Cinegy Desktop are based on the timecodes captured during the ingest process.

There are various timecode inconsistencies on video tapes which may cause serious issues for an ingest operator.

Timecode Breaks

There are different problems with the timecodes on the tapes. It is important to know how the ingestor processes the breaks, in order to provide successful outgest and export.

Refer to the following table to understand the problems and learn how the ingestor handles them.

Timecode Break Cinegy Ingest Action

Garbage timecode over a few frames

If the timecodes recover in less than N frames (depends on ingestor settings), ingest will continue as if there was no interruption. If the timecodes do not recover within N seconds, then a new "Entire Roll" master clip will be created, and the garbage fragment will be attached to the previous master clip.

Timecode jump

The ingestor creates a new "Entire Roll" master clip. Even a single frame jump will cause this action, so as to maintain the frame-by-frame precision of the ingested material for further outgest.

Date of shooting changes (DV only)

The ingestor creates a new master clip.

You can recognize easily if the OTC in the two consequent master clips is continuous; in this case, Cinegy Desktop displays special yellow triangle marks between the clips:

StoryboardView01
Important
Refer to the Refining Ingest section to learn how to manipulate the timecodes and shot boundaries.

Timecode Analysis

The timecode analysis values can be set in the "Shot change detector settings" dialog.

TCanalysis

Enter a value for "Max. tolerated inconsistency of timecode" and "Min. length of consistent timecode restored". The default values are 5 and 3 frames respectively.

If inconsistency between timecodes is less than the "Max. tolerated inconsistency of timecode" value and the number of inconsistent timecodes is less then the specified "Min. length of consistent timecode restored" value, the TC break is ignored and the ingest session continues.

Here is an example where the TC can be restored: 1 2 3 4 5 6 7 x x x 11 12 13 14 15…​

In this example, the timecode inconsistency is less than 5 frames and the number of consistent timecodes equals 3. As a result, this timecode inconsistency is ignored and the ingest session continues with no TC break; the consistent timecodes are generated.

TC and Live Ingest

During live ingest you normally attach your timecode generator to the ingest PC serial port (or to the port of the capture board) to record the value you want to use. In the scenario of de-synchronization between the capture board and the timecode generator during the ingest session, Cinegy Ingest will ignore further incorrect values and will use the frame counter to generate the proper linear timecode.

If there is no generator attached, Cinegy Ingest will use the PC clock to generate the timecodes. In this case, it is guaranteed that the timecode will always be linear throughout the entire ingest session.

Important
Refer to the Working with Timecodes article within the Cinegy Desktop Manual to learn more about using the timecodes in Cinegy Desktop.