Skip to main content
Skip table of contents

Tracking Maintenance Procedure

The Tracking engines are designed to run the Pixotope tracking system unattended for long periods of time without having to actively maintain either the operating system or software. The following practices are meant to keep the systems in best working order.



  • Perform an operations check before going on air (see below)

  • The tracking software should be terminated when the studio is out of use. This serves both to reduce processor load and extend the lifespan of the infrared light, which will turn off when the software is not running.

  • Depending on the tracking engine hardware configuration, the tracking computer should be powered down when the studio is out of use. Small form factor machines, such as barebone PCs, laptops or similar, are not designed to run powered on for multiple days. To reduce crew workload when bringing a studio on air,  the tracking software can be set to autostart when the engine powers on.

  • System temperature check: Use the Psensor program to check that essential hardware components like CPU, GPU and Video I/O card have an acceptable temperature.

    • CPU: < 90°C

    • GPU: < 80°C

    • Video I/O: < 80°C

Operations Check

Simple tests can offer a quick analysis of the tracking before going on air:

  • Ensure graphics are in their usual position when launching the scene

  • Ensure graphics move in sync with the video when the camera is panned

  • Determine if the virtual graphics are zoomed in at the same ratio as the real video and zooms in synchronously with the video

  • Ensure there is no visible jitter in the graphics when the camera is still

Dos and Don’ts

Once your system has been commissioned, follow these practices to ensure proper maintenance and care, to keep the same quality as achieved during installation:

  • The sensor unit will have been mounted in place during installation. This unit must not change its relative position nor orientation to the tracked camera. Any changes to this positioning, even by millimeters or tenths of a degree, can potentially cause visible offsets. If the mounting has shifted or changed, a new offset calibration must be performed, which can include  fine tuning adjustments.

  • The system will also have been commissioned to a particular lens. The mounting of the lens on the camera body must not change. If the lens has to be removed and remounted, the center shift must be revised.

  • All studio staff should be aware of the above two points. Whenever lens or sensor unit mounting is changed or reconfigured, those in charge of tracking must be informed.

  • Whenever changes are made to the environment where an optical tracking sensor looks into, the current reconstruction should be extended by some keyframes taken of that area.

Tracking Engines


Without official notice, there will be no need to update either the operating system or software. Updates may be needed if: there is a required bugfix for the specific system or new features are desired.

Updates may go along with new dependencies such as driver- or kernel-updates. It is recommended to perform any updates only when sufficient time is available to react to further software modifications needed.


The use of Linux itself is a sufficient protection against viruses. The Linux operating system used for tracking has furthermore been streamlined to run only essential services needed for tracking and remote support. By reducing the software overhead, the need for anti-virus protection is also reduced.

In case there are requirements to run additional protection, in order to comply with regulations or laws, the following recommendations can be taken into consideration:

  • Keep the tracking engines air-gapped from the internet during use. Note, that update or remote support sessions may require internet connectivity

  • ClamAV anti-virus software was qualified in August 2023 to run on a tracking engine. At the time, ClamAV was found not to interfere with engine performance during on-air use. However, manual or scheduled scans should not be performed during on-air use

  • When using anti-virus software, schedule regular anti-virus scans or perform them manually during a time when the engine is not on air

  • When using anti-virus software, schedule regular anti-virus database updates or perform them manually during a time when the engine is not on air

Third-Party Software

Certified software comes pre-configured on the operating system. All third-party software has to be tested for interference in correlation with the on-air tracking software, before going on air, and can not be supported by Pixotope support or engineering.

We always recommend a system configuration remain as close to the installation state as possible. Third party software can interfere with system performance, this includes video conferencing and remote desktop software such as: Zoom, Google Hangouts, TeamViewer, Anydesk etc...

Similarly, running software such as Dropbox or Adobe Creative Cloud can interfere both with network and hard drive bandwidth.


Once a tracking system is commissioned, there is no reason tracking quality will degrade unless software or hardware changes have been made post-installation. Most malfunctions result from hardware connectivity or manipulation (see “Dos and Don’ts”) 

When troubleshooting, first determine whether all signals are properly connected to the tracking system. If anything is out of the ordinary, check all physical connectors and cables: new disconnects or timing issues are not attributable to software unless the original configuration has been manually altered post-commissioning. Use the following list to start troubleshooting your system:

  • In the Chief Video window, ensure a live video of the tracked camera is visible (does not apply to Pixotope Fly setups)

  • In the Chief, under the lens tab, check the “Dump Parameters” box and ensure the system log prints live lens data values (does not apply to fixed lens setups)

  • In the Chief, under the IMU tab, check the “dump IMU” box and ensure the system log prints live IMU data

  • In the Chief, under the WorkerCam tab, select the “Dump” option “final” to ensure the system log prints live position and orientation data.

  • In the Worker, ensure the sensor unit video is visible

Further checks are:

  • In the Worker video, dark blue tiles indicate areas that contain tracked feature points

  • In the Worker video, light blue tiles indicate areas where feature points are expected but currently not visible. If these tiles occupy a large portion of the video, even when nothing is obstructing that part of the view, try reloading the reconstruction

  • In the Chief window, in the WorkerCam tab, the final tracking data can be printed in the System Log window. The last column of this dump tells the timing of the tracking data packages. It should be constantly close to the duration of a frame or field

  • When zooming in with no camera movement, ensure the graphics do not shift their position in the image center (test for center shift, an indicator of the lens having been removed)

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.