Hi there,
Timecode and Genlock Issues
Comments
Hi,
Note that the G sign is only used if you want to genlock the output of your capture card. It has nothing to do with incoming signals that are genlocked or not. Sadly, there is no way to determine if the signal (tracking or video) is genlocked or not.
More on genlock and G sign here: https://aximmetry.com/learn/tutorials/for-studio-operators/syncing-and-genlock/#genlock-aximmetry-video-output
Warmest regards,
I have the same problem, when the time code sync is enabled, the camera tracking FreeD always shown 'cant keep current latency.' I turned on SDI on screen but no timecode appeared nor the Gsign. I could sync genlock and timecode in UE5 but unable to do so in aximmetry. Please help, thank you.
Hi,
Genlock and Timecode are two different things.
For the TimecodeSync to work, both your tracking and video input must contain a matching timecode.
In the case of Genlock input, the input synchronization will happen because all the signals arriving at the capture card are already synchronized from the different hardware outputs that are connected to the Genlock System. The capture card and Aximmetry won't be able to tell if these inputs' hardware are synchronized by the Genlock System or not, as there are no matching timecodes or any other type of data being outputted just because a hardware is genlocked. You can only confirm Genlock on your hardware, for example in the case of Black Magic cameras the "ref" word shows up next to the timecode on the camera control monitor when the camera is genlocked.
The G letter here in Aximmetry means the output of the capture card is genlocked:
This means that your capture card is receiving a synchronization signal from the Genlock System and outputting the video according to that. But this will not affect the video inputs and won't make any incoming signal genlocked.
Warmest regards,
The FX6 can’t be genlocked, which is the central point when working with camera tracking that requires genlock. Without that there’s not much point in genlocking anything else in the camera tracking context. Aximmetry will genlock to the camera input signal and the Decklink Ref input only genlocks the the output of the Decklink.
So, right now the Vive Mars really isn’t suitable for cameras without genlocking capability. I’ve been advocating a system where the tracking data is genlocked in Aximmetry instead, so let’s hope Vive Mars implements something like this.