Detect Tracking Delay

Hi,

I have question about tracking delay.

In the input tab there is a key with a function called"detect tracking delay". This function, it works properly on a machine with local rendering machine , but not on remote machines. I would like instructions how to use this tool correctly on remote machines.

On remote machines, the color is correctly detected, but when panning the camera, the procedure does not end. I could pan with this camera all day long and aximmery is not able to calculate the tracking delay.

I will add that the PANASONIC UE 150 camera is set to 1080p50 and the output SDI is set to 1080i50.

Thanks fo

martin86

Eifert@Aximmetry

Hi,

The issue you're experiencing may stem from a slow panning speed and not the multi-machine setup. When panning, the system calculates the degree to which the camera has rotated over the past 3 seconds. To ensure a successful measurement, this value needs to at least match the camera's Field of View (FOV). Simply put, for the measurement to be deemed successful, the camera should rotate from one edge of the frame to the other within a 3-second window.

To resolve this issue, consider increasing the panning speed of your PTZ camera, or zoom into the target and attempt the Tracking Delay measurement like that.

Warmest regards,

martin86

Hi, Thank you for your reply.

Hi, Thank you for your reply. Today I checked by connecting 2 Panasonic UE 150 cameras to one rendering machine. Surprisingly, everything works properly. So I split the cameras back into individual renderers and the delay detection doesn't work. Please explain what I am doing wrong, what I am setting incorrectly in multimachine mode.

If necessary, I will send the aximmerty settings.

I will also add that today I tried to set origin for two PTZ cameras using ArUco markers and, as in the case of Detect tracking delay, it works on the local machine with one camera and with two cameras, but it does not work in mutimachine mode.

By the way, today install the latest version of Aximmetry Broadcast and when selecting the key in the Key tab, changing the monitor mode to Matte Aximmetry stops working and creates a crash file.

martin86

Hi,

Today I did another test. It turned out that on the second, remote machine, the tracking delay is detected correctly, but the procedure does not end, the message flashes for a moment and then the procedure starts from the beginning. I am posting a link to the slow motion video.

https://we.tl/t-DKBWCWMr1u

Eifert@Aximmetry

Hi,

Thank you for the video. Actually, as of now, both tracking delay and origin detection are not supported on the remote machines in a green camera multi-machine setup. We apologize for any confusion this may have caused and for the goose chase. These features are on our task list for future development.

Regarding origin detection, you have the option to use the [Common_Studio]:Compounds\Tools\NDI_Channel_Out.xcomp compound to transmit the video from the remote machine to your control machine via NDI video (you will have to change the Engine pin of the compound). On the control machine, this NDI video can be added as an input and utilized for origin detection. However, please note that this workaround is not feasible for tracking delay correction, as the NDI connection introduces an additional delay that cannot be accounted for in this context.

Warmest regards,

Eifert@Aximmetry

Hi Martin,

The new Aximmetry version 2024.2.0 BETA has been released. https://aximmetry.com/learn/software-version-history/#%E2%96%BA-Latest:%202024.2.0

This version fixes that both Detect Origin and Delay Detect were not working in the multi-machine setup on remote machines. It also addresses other similar camera compound functionalities that may not have been working correctly in a multi-machine environment.

Warmest regards,

martin86

Hi,

Thanks, for a quick troubleshooting. I'm downloading the latest version and testing.

Regards

Detect Tracking Delay

Cookie consent