Hello Aximmetry Support Team,
We are evaluating Aximmetry in a broadcast studio environment and have two questions about lens and tracking calibration.
Aximmetry: 2026.3.1 (Build 39093)
Edition: Broadcast & Film Edition, using Aximmetry's native rendering engine (no Unreal Engine)
OS: Windows 11 Home 25H2
CPU / GPU / RAM: Intel Core Ultra 7 265K / NVIDIA GeForce RTX 5080 / 32 GB
Video I/O: DeckLink 8K Pro (Desktop Video 16.2)
Video format: 1920×1080 / 1080i59.94 (59.94 fields/s)
Genlock: Black Burst (BB)
Camera: Sony HDC-2000
Lens: Fujinon HA27x6.5
Tracking: Shotoku SPI-Touch / SPI-BOX, Free-D at 59.94 Hz via RS422-to-USB serial connection (38400 baud)
The camera, video equipment, and tracking system are synchronized to the same BB reference.
We performed lens calibration in Camera Calibrator by following the on-screen instructions and created a Calibration Profile.
We also used Basic Calibrator to manually fine-tune some zoom ranges.
When we started the system on the recording day and loaded the previously created Calibration Profile in Composer, the CG did not follow the real camera image correctly.
Specifically:
During pan and tilt movements, the CG appeared to move less than the real camera image, causing visible CG sliding.
Zoom tracking appeared to work approximately correctly.
During troubleshooting, we executed "Detect Origin" using an ArUco marker multiple times.
Starting with one particular execution of Detect Origin, an additional perspective mismatch appeared between the real camera image and the CG.
The CG sliding persisted for more than 30 minutes.
We then opened the calibration file in VS Code only to inspect its contents. We did not modify or save any changes to the file, and we did not change any settings in Aximmetry.
Aximmetry was left running during this time.
When we looked at the screen again, both the CG sliding and perspective mismatch had disappeared.
We have not identified what caused the issue or why it resolved without any changes.
Immediately after the CG sliding and perspective mismatch described in Issue 1 had disappeared, we tested dolly movement and encountered another problem.
On the previous day, we had performed Tracking Calibration using Camera Calibrator and confirmed that the CG correctly followed the camera during dolly movements.
However, when we tested dolly movement again after the symptoms in Issue 1 had disappeared, the same camera showed a significant mismatch in tracking direction.
The camera and tracking hardware had not been physically detached or disassembled and reassembled between the two days.
However, the camera and tracking equipment had been moved between studios without changing their relative physical arrangement.
The CG movement direction appeared to differ from the actual camera movement by approximately 150 degrees (visual estimate).
Restarting the PC did not resolve the issue.
However, after performing Tracking Calibration again using Camera Calibrator, the CG followed the real camera movement correctly.
This Tracking Calibration procedure was separate from the ArUco-based Detect Origin operation described in Issue 1.
What could cause CG sliding and perspective mismatch after loading a previously created Calibration Profile, followed by spontaneous recovery without changing any settings or file contents?
What parameters or diagnostic information should we check if this issue occurs again?
After moving the camera and tracking equipment between studios without changing their relative physical arrangement, is it necessary to repeat Tracking Calibration in Camera Calibrator, or would it be sufficient to use Detect Origin to align the virtual environment's origin with an ArUco marker by adjusting Delta Cam Transf?
Under what circumstances would a previously saved Tracking Calibration become invalid? What checks would you recommend to distinguish a Tracking Calibration issue from an incorrect alignment between the tracking coordinate system and the virtual environment (for example, an incorrect Delta Cam Transf setting)?
We would appreciate your advice on the possible causes and recommended calibration workflow.
Best regards.
Hello,
1, This is a new issue to us. Based on your description I assume that the file was cached locally from a network drive and failed to update properly. Loading the file in VS Code caused it to refresh from the network location.
2, If the issue is indeed connected to using a network drive, it can be fixed by either disabling "offline files" in Windows, or changing the configuration of the file server to avoid stale copies.
3, Certain tracking systems can change their orientation after restating / moving them to a different location. In this case, a new calibration is necessary.
note: You do not need to make a new lens calibration, only tracking calibration.
4, A new tracking calibration is necessary if the tracking sensor mounted on the camera moves even slightly or you attach a different lens to the camera body.
If the orientation of the tracked object (e.g. the sensor mounted on the camera) changes, a new calibration is also necessary.
in your case - if we are right - there is no separate tracking sensor, but the physical camera's orientation in the tracking system changes whenever you move studio, forcing you to recalibrate.
Best Regards,
Patrik