In a number of sections of this user guide, reference is made to the normalisation or rounding of timecode values. The refers to the way that results of frame rate conversions and calculations are handled. Often the result of a conversion or calculation is not an integer number of frames at the target frame rate. Normalisation of the result will round the frame number value to the nearest integer value of frames at the target frame rate. By default the calculator will normalise results most of the time. To illustrate, here is a simple example.

10 frames divided by 3 = 3 frames.

Multiply this result by 3. What is the result?

If the result of the first calculation is normalised the result will be 9.

If the results are not normalised the result will be 10.

Which is the correct result really depends on the interpretation and both could be deemed to be correct. The Round Calculations preference determines which occurs.

Another example, this time when changing frame rates:

One frame at 24 frames per second is 1/24th of a second = 0.0417 seconds (approximately).

Converted to NTSC frames the calculator will convert this to, again, one frame. However one frame of NTSC is actually 1/29.97th of a second = 0.0333 seconds (approximately).

If the Round FPS Changes preference option is selected, the underlying value stored in the calculator will be rounded (Normalised) to the nearest frame value, in this case 0.0333 seconds. If not selected the value will remain with the seconds value. Which option is chosen will affect further calculations.