CameraTracking: Ncam: 172.27.90.107:38860: Cannot match timecode. The difference to the reference timecode is about -480672 frames. Try to use this value as Tracking Delay, then adjust it manually until you get a matching track.
glowgo
Comments
Eifert@Aximmetry
-
Hi,
Do you use timecode synchronization between your Ncam system and studio camera? If not, leave the Timecode Sync parameter turned off. Note that the timecode reported by your tracking system and camera input currently shows a difference of 480672 frames, which indicates that they are not in sync.
Aximmetry has the Timecode Sync parameter enabled by default because most tracking systems only report timecode when timecode sync is active. If there is no timecode from the tracking system, Aximmetry simply ignores this setting. However, your Ncam system might be an exception, and could be reporting a timecode even when it is not actually synchronized.
An error occurred while uploading, please try again.
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,
Do you use timecode synchronization between your Ncam system and studio camera? If not, leave the Timecode Sync parameter turned off. Note that the timecode reported by your tracking system and camera input currently shows a difference of 480672 frames, which indicates that they are not in sync.
Aximmetry has the Timecode Sync parameter enabled by default because most tracking systems only report timecode when timecode sync is active. If there is no timecode from the tracking system, Aximmetry simply ignores this setting. However, your Ncam system might be an exception, and could be reporting a timecode even when it is not actually synchronized.
Warmest regards,