Hello Aximmetry Support Team,

We are experiencing periodic "Cannot keep latency" warnings in both Basic Calibrator and Camera Calibrator, while Composer does not show the same warning.

We would also like to confirm how In-to-Out Latency settings are shared between Aximmetry applications.

• 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)

• Tracking: Shotoku SPI-Touch / SPI-BOX, Free-D at 59.94 Hz, synchronized to BB

• Composer In-to-Out Latency: 7 frames

• Input Extra Delay: 2 frames

Issue 1: Periodic Latency Warning

While using Basic Calibrator or Camera Calibrator, a warning indicating "Cannot keep latency" appears at approximately 135-second intervals.

When the warning occurs, the entire camera image preview area inside the Calibrator is covered by a magenta warning display with the message "Cannot keep latency."

This happens in both Calibrators.

However, Composer does not show the same warning in our environment.

During a previous Camera Calibrator test, we also tried increasing Composer's In-to-Out Latency setting to 10 frames, but the warning continued to appear.

Changing the video input setting between AUTO and 1080i59.94 did not resolve the issue either.

We have a reference image showing a similar warning display, although it was not captured directly from Basic Calibrator or Camera Calibrator.

We also tested Aximmetry in another environment using the same PC, but with different external equipment and hardware.

In that environment, neither Basic Calibrator nor Camera Calibrator displayed the periodic "Cannot keep latency" warning.

Therefore, the issue has only been observed in the particular equipment configuration described above.

We have not yet identified which equipment, setting, or condition is responsible for this difference.

We found the following official forum discussion:

https://my.aximmetry.com/post/4830-can-not-keep-latency-aximmetry-calibrato

According to this discussion, we understand that In-to-Out Latency settings are shared between Aximmetry applications, including Composer and the Calibrators.

However, we could not find any place in Basic Calibrator or Camera Calibrator where the currently applied In-to-Out Latency value is displayed.

Also, visually, the camera preview in the Calibrators appears to have less delay than the camera preview in Composer.

This is only a visual observation and has not been confirmed by an actual latency measurement.

Therefore, we are unsure whether the Composer In-to-Out Latency setting is actually applied to the Calibrators in the same way.

1. What could cause the "Cannot keep latency" warning to appear approximately every 135 seconds in both Basic Calibrator and Camera Calibrator, while it does not occur in Composer?

2. Does Aximmetry 2026.3.1 still share the In-to-Out Latency setting between Composer, Basic Calibrator, and Camera Calibrator?

3. If the setting is shared, how can we confirm the actual In-to-Out Latency value being used by each Calibrator?

4. Are there any recommended diagnostic methods, additional settings, or logs available to investigate this issue? In particular, which settings or parameters should we compare between the affected and unaffected equipment configurations?