I have two cameras at the entrance without tracking, one camera 50 frames, the second 20 frames, I constantly get the error "cannot keep latency"
anzaaximm
Comments
Adam@Aximmetry
-
Hi anzaaximm,
The "Cannot keep latency" message means
that the system can’t hold a constant delay between input and output.
This is related to the video inputs’ In-to-out latency
parameter, which specifies the constant delay should try to keep between the
incoming video and the final output.
This means the message has nothing to do with your video inputs having
different frame rates (50p and 20p). We would still recommend matching both
camera frame rates to the rendering frame rate if possible, to avoid
stuttering.
Check your current setting. If it is smaller than 7
frames, try increasing it and see whether the message disappears. If the
lowest value you can set without receiving the error message is higher than 7
frames, there may be other issues in your setup worth investigating.
One possible cause is the performance of the machine
Aximmetry is running on. If a frame takes longer to render than the frame
budget, the latency cannot be held. Try loading a simple scene, or temporarily
lowering the render frame size or frame rate — if the message stops, it is a
performance issue.
The capture device itself may also be the cause. USB
cameras, IP cameras and virtual sources deliver frames at varying intervals,
unlike the fixed hardware timing of an SDI capture card. Run each camera on its
own to see whether the message follows one of them.
An error occurred while uploading, please try again.
We are planning maintenance on MyAximmetry site from 2026-SEP-14 07:00 to 08:00 UTC. During this period, the site will not be available. Please refrain from initiating any ordering processes around this time to avoid potential issues.
Cookie consent
Our website uses cookies to give you the best online experience, also we use other technologies to improve
and analyze our website traffic, and to understand where our visitors are coming from.
Hi anzaaximm,
The "Cannot keep latency" message means that the system can’t hold a constant delay between input and output.
This is related to the video inputs’ In-to-out latency parameter, which specifies the constant delay should try to keep between the incoming video and the final output.
This means the message has nothing to do with your video inputs having different frame rates (50p and 20p). We would still recommend matching both camera frame rates to the rendering frame rate if possible, to avoid stuttering.
You can find In-to-out-latency under Edit > Preferences > Video Input:
The correct value is hardware-dependent and found by trial and error and should be the lowest value that runs clean.
You can learn more about In-to-out latency in our documentation:
https://aximmetry.com/learn/virtual-production-workflow/inner-workings-of-aximmetry/in-to-out-latency/
Check your current setting. If it is smaller than 7 frames, try increasing it and see whether the message disappears. If the lowest value you can set without receiving the error message is higher than 7 frames, there may be other issues in your setup worth investigating.
One possible cause is the performance of the machine Aximmetry is running on. If a frame takes longer to render than the frame budget, the latency cannot be held. Try loading a simple scene, or temporarily lowering the render frame size or frame rate — if the message stops, it is a performance issue.
If that turns out to be the case, check whether your setup matches the system requirements for Aximmetry in our documentation below:
https://aximmetry.com/learn/virtual-production-workflow/supported-hardware/pc/system-requirements-for-workstations/
Also make sure that no Windows power saving or performance limiting settings are enabled, and that no other resource-heavy application is running, as these can all limit GPU and CPU performance.
The capture device itself may also be the cause. USB cameras, IP cameras and virtual sources deliver frames at varying intervals, unlike the fixed hardware timing of an SDI capture card. Run each camera on its own to see whether the message follows one of them.
Warmest regards,
Adam