Vista 5 M3 Digital Mixing System
5-162 AutoTouchPlus
Document generated: 28.08.13
SW V4.9
Offsets up to 99 Frames When offsetting, the add/subtract editor window will allow frames to be
entered up to 99 if the hh, mm and ss fields are all 0. For example if you
wanted to offset the timecode 1.5 seconds at 30 fps you could either press +,
1, 1, 5, Enter for adding 1 second 15 frames, or press +, 4, 5, Enter for adding
45 frames.
Remainder When converting from FODs to timecode strings there is the possibility of a
remainder. There are roughly 100 FODs per frame. If an FOD is converted
to a string and the string converted back to an FOD, any FOD between
the start of the frame and the original FOD would be lost. For example,
frame 00:00:00.01 starts at FOD 103. If FOD 105 is converted to the string
00:00:00.01 and the string converted to an FOD the result would be 103,
loosing two FODs in the process. During various operations like bumping
or offsetting, the timecode conversion routine keeps track of the remainder
automatically. Basically, having a remainder means that the FOD does not
exactly equal the beginning of the frame represented by the timecode string.
The following table illustrates the rules, regarding when remainders are saved
and when they are lost.
Action Remainder
User Enters any Timecode Digits No, FOD exactly matches string entered
User Captures Current Time Yes
Offsets Yes
Bump/Scroll Yes
Drag/Drop Yes
‘Intellibump’ When scrolling or bumping drop frame code to an invalid timecode, the con-
trol automatically adjusts to the next valid timecode. For example, if bump-
ing seconds up two times to achieve a 2-second offset from 00:10:59.00 to
00:11:01.00, the first bump will result in 00:11:00.00. This is invalid during
drop frame counting, so the control automatically sets it to 00:11:01.00. The
second bump would normally bump 1 second from the previous value, which
would yield 00:11:02.00. This is not what was desired.
The control keeps track of artificial frame bumps required to keep true to
the drop frame counting sequence and automatically re-compensates when
possible. This re-compensation is attempted until the timecode is commit-
ted or some other action besides bumping or scrolling the particular field is
performed. In the example above, the second bump performed would actually
yield 00:11:01.00 since the control would re-compensate for the two-frame
bump required to keep the drop frame rules.
To Next Page
Loading...
