2 Axibridge issues and questions : Bugs or features ?

 

Hi,

I'm doing experiments with tracking forwarding in our studio and I've stumbled upon a few issues.

- First (small inconvenience) : in the Tracked and mixed camera compounds, the target IP address is invisible. I had to open the compound and expose the pin to make it work. Am I missing something ? How is it supposed to know which computer to send it to without it available ?

- Second (bigger issue) : I've been testing the tracking forwarding with different systems (PTZ, VIVE MARS and Intel T265) and it appears that Free-D data received on a broadcast license cannot be forwarded to a studio license via Axibridge. Tracking data from the Intel T265 appears to work however.

It's strange because they both look like simple transformation matrices when plugging a peeker at the back of the Camera Tracking module. Is that a bug ? Intended behaviour ?

Thank you for your help,

Eric

   ericmarodon

 
Profile Image
Eifert@Aximmetry
  -  

Hi Eric,

- First:

You don't need to set the target IP (Fwd Aux Targets) in a multi-machine setup. The system automatically recognizes the remote computer IP addresses. You only need to configure the Fwd Aux Targets if you are targeting a computer that is not part of the multi-machine setup. This is why the parameter is only available in the module itself, not in the camera compound.

- Second:

Even if you forward the tracking, the same license limitations apply. Since Free-D is a professional tracking protocol, it requires a Broadcast license. You can find more information on this here: https://aximmetry.com/learn/virtual-production-workflow/supported-hardware/professional-camera-and-object-tracking-systems/tracking-systems/#professional-tracking-systems
Note that tracking forwarding transmits not just the transformation data but also everything else being received, such as lens data or timecode.

Warmest regards,


 
Profile Image
ericmarodon
  -  

Thanks a lot for the clarification, that makes sense.

As a follow-up question, regarding the information transmitted : does it include the data in the camera calibration file too or do you have to link it separately on the remote machine too ? (I guess the latter, but just to make sure to not double the distortion).

Speaking of Calibration files, I also noticed that :

A) as soon as you map even only ONE tracking device with a calibration file, ALL calibration fields are then greyed out in the compound, even if they're not mapped.

and

B) You cannot create multiple mapped presets with the same device like this :

Mapped 1 : Vive Mars 1 / 12mm calibration file

Mapped 2 : Vive Mars 1 / 25 mm calibration file

Mapped 3 : Vive Mars 1 / 50 mm calibration file

All the calibration files switch to the last selected file.

It's a bit of a bummer if you want to quickly switch between prime lenses on the same camera.

So in effect, because of A) and B) the only way I found so far is not to map any device, which I think defeats the whole purpose of the system.

 
Profile Image
Eifert@Aximmetry
  -  

Hi,

Yes, the calibration profile is not transmitted, you have to link it separately on the remote machine too.

The Device Mapper is designed for global mapping, which is not something you'd typically change during a show. Instead, you adjust the mapping when you acquire new hardware in your studio, and this mapping will apply across all projects, eliminating the need to alter each project individually. So if you need to change devices during production, the Device Mapper will not serve you.

Thus, you either change the calibration profile in the Device Mapper for the mapped device. Or you don't map the device in the Device Mapper and then you can change the calibration profile in the camera compound when you select that device.
The calibration fields are only grayed out in the compound when the device is mapped, even if you choose the unmapped option. This helps users to add calibration profiles to devices that they didn't map previously.

Warmest regards,


;