The Vive Lighthouse tracking technology suffers from jitter by default. It was never intended to be used for professional camera tracking and it uses cheap consumer parts. EZTeack can filter the tracking data to hide some of the jitter, but it will be a bit like putting lipstick on a pig. You definitely shouldn’t use the dejittering in Aximmetry on top of the EZTrack filtering since it will likely only cause more issues. 

That being said, looking at the test footage there seems to be some issue beyond tracking jittering. Is your camera and EZTrack system properly genlocked to the same clock source? Is your Aximmetry rendering settings and Decklink output settings (you are capturing the video from a Decklink, right?) running at the same frame rate? Your main Decklink output should have the Sync checkbox enabled. 

"The Vive Lighthouse tracking technology suffers from jitter by default. It was never intended to be used for professional camera tracking and it uses cheap consumer parts. EZTeack can filter the tracking data to hide some of the jitter, but it will be a bit like putting lipstick on a pig. You definitely shouldn’t use the dejittering in Aximmetry on top of the EZTrack filtering since it will likely only cause more issues. "

That's why we bought EZTrack´s own SWAN trackers instead of HTC Vives. Antilatency was not readily available when the system was commissioned and Optitrack or Mo-Sys were outside the budget. Does anybody here have practical experience with the EZTrack SWAN units btw.? EZTrack claims that they perform significantly better than Vives, but at the same time say that a lens with a focal length of 70mm will already suffer from visible jitter again? I´m getting a bit wary about their claims here..

"That being said, looking at the test footage there seems to be some issue beyond tracking jittering. Is your camera and EZTrack system properly genlocked to the same clock source? Is your Aximmetry rendering settings and Decklink output settings (you are capturing the video from a Decklink, right?) running at the same frame rate? Your main Decklink output should have the Sync checkbox enabled. "

That's what I suspect as well. Although all the basic things seem to be  correct - everything is set to 30p and genlocked, the sync checkbox on the PGM output of the Decklink is enabled. Any other ideas what could be wrong here?

Hi,

I think there might not be anything wrong other than tracking inaccuracies due to the long focal lengths.
Also, enabling any clamping filter and dejitter features can introduce additional delay, which you should account for in the Tracking Delay of the camera compound.
In the case of Aximmetry's Dejitter, you shouldn't change the Tracking Delay. With Aximmetry's Dejitter there will be a slightly increased delay only when moving in and out from the stationary position (Thresh).

In this video: https://www.dropbox.com/scl/fi/lt5qaz67oj09u9d71tc6f/Trackingtest_EZTrack766.mp4?rlkey=n2878fg8on6icn5ecctn775v1&e=1&st=qjn556q5&dl=0
it seems like there might also be jitter from the camera's stand, but I am not entirely sure.

Warmest regards,

So what do you consider too long of a focal length for accurate optical tracking then? This is at 40mm:

https://www.dropbox.com/scl/fi/qkyb3yxob4u67luerbepy/CAM3_SWAN_40mm_unclamped.mp4?rlkey=u8z7wsxul5ceh66qaimes6lhh&st=45ubfrri&dl=0

Hi,

I believe this tracking is accurate for a 40mm lens using Lighthouse Base Stations. If the shifting is indeed caused by the fluid head and the jump in tracking is not related to the tracking system. I have written more about these issues here: https://my.aximmetry.com/post/4014-camera-calibratorbasic-camera-calibrator  

Warmest regards,