Timecode Drifts on Aximmetry Gateway

We are attempting to implement multi-camera virtual production operation using Aximmetry DE Composer 2025.1 running on multiple EC2 instances in AWS, with Aximmetry Gateway 2025.1.

A Timecode Master has been prepared, and timecode is embedded into both VITC and LTC fields of the SDI signal via Videotron MUX-70U.


Over several days, while monitoring the Timecode value in the Video In node, I noticed timecode drift occurring on multiple machines.

I reset the Timecode Master and changed the Timecode sent to the Gateway, but the timecode visible in the Composer's Video In remained unchanged.

The following are the troubleshooting steps attempted:

・Toggling the Gateway's TimecodeMaster check - did not fix it

・Unplugging and replugging the SDI cable - did not fix it

・Reselected the SDI input device: Fixed

・Stopped and restarted the Gateway service: Fixed

The Gateway application had been running continuously for about 4-5 days.

I want to confirm whether this phenomenon of timecode synchronization breaking is a known issue and what countermeasures exist.

   Satoshi Watanabe

コメント

Eifert@Aximmetry
  -  

Hi Satoshi,

Unfortunately, the Gateway's documentation was a bit misleading regarding what the Timecode Master does, which might have caused some confusion. We have now corrected the documentation to clarify this point. The Timecode Master does not perform any syncing.

  • If Timecode Master is checked, the timecode from the selected video input will be used as the timecode source for all video streams.
  • If Timecode Master is unchecked, Aximmetry’s base timecode will be used as the source for all video streams.

I'm not sure under what circumstances or where you experienced timecode drift. However, if you want to synchronize every video input to each other based on timecode, it would be very hard to do with a multi-machine setup running on multiple EC2 instances in AWS. Instead, you would need to perform the timecode synchronization on another computer or device that receives all the final outputs.
In that scenario, as long as your video sources are already connected to a timecode/genlock source, they should arrive at the capture card simultaneously. Therefore, there should not be any issue with Gateway overwriting their timecode.

Note that timecode synchronization between tracking data and video sources is a separate topic. You can manage this within Gateway using the tracking panel's TC sync option. Further information can be found here: https://aximmetry.com/learn/virtual-production-workflow/starting-with-aximmetry/aximmetry-gateway/using-aximmetry-gateway/#camera-tracking 

Changing the Timecode Master while a stream is running will not work for various reasons. To apply such changes or to reset the timecode, you will likely need to stop and then start the stream again:

Warmest regards,