This page provides information about the Tracking tab in Chaos Arena.


Overview

Camera tracking is described by a protocol and additional parameters for the protocol. There are also tracking offsets that specify the center point of the tracking system, and the center point of the tracker itself.


The currently supported protocols are:


Apart from the 3D camera position and orientation, FOV tracking is also supported for stYpe and EZtrack. It can change the inner frustum size dynamically, according to the current focal length of the camera lens.

The tracking origin in the scene is the pivot point of the projection geometry by default. The actual center point on the stage specified in the tracking system could be different. This is defined by the Tracking Origin Offset parameters in the configuration. Orientation offsets relative to the projection geometry can also be specified if needed. The tracking origin node option can also be used to control the origin in the scene.

The tracking system should ideally provide the position of the camera's entrance pupil point (often referred as the lens nodal point). The entrance pupil is a virtual point that's usually somewhere inside the lens and corresponds with the correct position of the virtual pinhole camera model. However, some tracking systems provide the camera sensor's position instead, or some other point relative to the actual tracker on the camera. This can be corrected using the Camera Offset parameters in the configuration. Orientation offsets of the tracker relative to the camera can also be specified if needed. Note that for stYpe and EZtrack this offset should not be needed.


General

Camera ID - ID string of the tracker to be used for the camera tracking. The tracking systems can send data for multiple physical trackers at the same time and this ID can filter them. For stYpe, this should always be "0".

Protocol – The tracking system (protocol) to use.

Port – The UDP port on which to listen for tracking data. Required for stYpe, FreeD, EZtrack, not used for OptiTrack, Vicon and LONET 2.

FOV – Horizontal field of view override in degrees. Used to override the FOV value from the tracking system or the scene. By default it's 0.0 which means that the override is disabled and the value from the tracking system or the scene is used. When disabled, the FOV is taken from the tracking system if it supports FOV tracking and currently provides a valid positive value, or from the main camera exported in the scene.

Recording Directory – A directory for the recorded camera tracking Alembic files. By default it's the Windows %TEMP% directory.

Sync Recording to Animation – When enabled, tracking samples are recorded only during the first animation playback with the exact animation times as rendered. This ensures that the exported Alembic file matches the scene animation when imported to the same scene. When disabled, all received samples are recorded with uniform time sampling based on the average FPS of the received data.

Unit Scale – Scaling factor for the position data received from the tracking system. Can be used for correction of incorrectly calibrated tracking systems or scenes with a wrong scale. Normally it should not be needed.

1 button – Reset the scaling factor to 1.0.

Uniform Scaling – If enabled, the scaling is uniform on all dimensions, otherwise it can be specified for each dimension separately.

Horizon Shift


Tracking Origin Offset 

Position and rotation offset of the tracking system relative to the current tracking origin in the configuration (the projection geometry or the tracking origin node if specified).


Camera Offset

Position and rotation offset of the camera's entrance pupil and orientation from the tracker's center point and orientation.


Auto-Apply – If enabled, changes to the offsets, FOV, or the camera ID are applied immediately during rendering, without having to press the Apply Configuration button.


Coordinate system

The coordinate system used for all offsets is (+X right, +Y forward, +Z up). Distances are in centimeters. Rotations are described as (pan, tilt, roll) in degrees. Positive pan angle corresponds to a pan to the right. Positive tilt angle corresponds to an upwards tilt. Positive roll angle corresponds to a clockwise roll when viewed from behind.


OptiTrack

The OptiTrack integration is different from most of the others as it uses a third party library for connecting to a server - normally the OptiTrack Motive application. Most of the other protocols are just connectionless UDP listeners that open a network port and listen for data on it.

Also, OptiTrack is not specifically a camera tracking system, it's a full motion capture system. There are various types of objects tracked - skeletons, rigid bodies, force plates, markers and so on. Currently the objects implemented for camera tracking are rigid bodies. Each rigid body has a streaming ID set in the server. This streaming ID is used as a camera ID.

Coordinate System

There seems to be a convention in OptiTrack that the coordinate system's forward direction points away from the screen (backwards when standing in front of the LED wall for example), not into the screen as most of the other systems. This usually causes the tilt and roll to be inverted, i.e. an upward tilt is interpreted as a downward tilt. It can be easily corrected by setting Pan 180 degrees for both the Camera Offset and the Tracking Origin Offset. This effectively rotates the entire coordinate system 180 degrees. Note however that all other offsets are still relative to the native coordinate system, meaning that the forward direction is looking away from the screen.

Protocol Settings


Vicon

The Vicon integration is similar to OptiTrack - uses a third party library for connecting to a server - normally the Shogun application.

Vicon is also a full motion capture system. The subject names are used as camera IDs.

Protocol Settings


LONET 2 

LONET 2 contains many fields for camera and lens tracking. Currently the only data used by Arena is the Camera Transform Data - camera name, position, orientation, timecode.
The protocol is tested only with the Lightcraft Jetset app.


Tracking protocol JSON plugin IDs

The protocols are implemented as plugins and the JSON configuration files store the plugin ID of the selected protocol: