Shifting Cues

Shifting cues involves updating their positions within the timeline while preserving their durations. This typically means that the music itself hasn't changed; rather, the points at which the cues are placed have shifted.

This operation moves the IN, OUT, and Sequencer Start (when provided) timecodes by an identical time increment.

To shift cues in CueDB, you can proceed in two ways:

Individual Cue Shift

For shifting a single cue, click on any timecode field (IN, OUT, or Sequencer Start) and input a new timecode or use a + or - followed by a timestamp to add or subtract time respectively (see last picture below for examples of values to use). Then press enter while holding the Shift key to apply the change; this action tells CueDB to adjust the remaining timecode fields by the same amount. For instance, modifying the IN field will automatically shift OUT and Sequencer Start correspondingly.

Bulk Cue Shift

Select the cues you want to shift by using the checkboxes on the left side of the cue list. Navigate to Tools > Shift Cues or use the shortcut Ctrl + L and decide whether to shift based on the IN timecode, Sequencer Start, or an offset value.

Note: This feature is only available when at least one cue is selected.

This will shift all selected cues 1 minute later, based on changing the IN time of 1m01.
This will shift all selected cues 5 seconds later, based on changing the Sequencer Start timecode of 1m01. Note: a current Sequencer Start timecode must be set for this action to work
This will shift all selected cues 1 minute later.

For offset values, use + (or no symbol) to add time and - to subtract time. Separate HH:MM:SS:FF with dots (.) or colons (:), and leading zeros are optional. To shift by frames, enter digits only. For seconds, only seconds and frames are required, and for minutes, hours can be omitted. Full timecode is also supported.

Only current timecodes are shifted; version timecodes remain unchanged.

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.