Input Interpolation

None Interpolation

None Interpolation keeps the incoming raw data and will not modify these at all.

None interpolation should be used if the timing of the incoming data matched perfectly the project timing and representing the required data values.

By adding delay input frames, Stage Precision buffered the incoming data to add delay. This is needed, if the tracking data are “too early”.

Time Based Interpolation

needs at least one frame delay to work.

Time Based interpolation uses the time of an incoming data package to interpolate the data between two frames automatically.

If the incoming data packages reach Stage Precision at 5ms (Project rate 50fps/20ms), the interpolated data will be influenced 75% from frame 0 and 25% from frame 1.

Frame package 0 delivered value 0, frame package 1 delivered value 0,5. The timing of the incoming data is at 5ms means at 25% within one frame. The result for the first frame will be 0,125.

Fixed Interpolation

needs at least one frame delay to work.

Fixed interpolation used the defined offset in percentage to interpolate the data between frames. This makes it possible to define a specific moment between two frames to use this interpolated data.

Frame package 0 delivered value 0, frame package 1 delivered value 0,5. The timing is set to 0,25 means 25%. The result for the first frame will be 0,125.

Subframe Interpolation

needs at least two input frames delay to work.

Subframe interpolation can interpolate missing frames when the data input is running on less frames then the project frame rate.

The blue line is an indicator that the input is delivering only every second frame.

To interpolate the missing data for frame 1 we need at least the data from frame 0 and frame 2.

Thats how the time inspector looks like if the input rate is heigher then the project rate. We seeing here 100fps incoming data at 50fps project rate.

This is the worst case scenario of incoming data. The Data has the wrong timing and wrong speed…