Mo-Sys tracking

Back to Posts

Hello,I am using Mo-sys tracking with Aximmetry Broadcast DE. Mos-Sys already has Lens file (json) then I would like to know if I can use this data and do not need make calibrate procedure or not. I try with camera calibrator app but it seems doesn't work because we use lens 23x7.6 Lens and 14x4.5 lens so some possition it can not move camera to there ( I also use small board).I also send a capture of Mo-Sys lens file.Please help me to solve this problem.

ThachNN6

Eifert@Aximmetry

Hi,

To utilize the Mo-Sys's Lens JSON file within the camera compound, you must connect it to the Manual Lens Dist pins:
Mo-Sys tracking
However, this process will most likely require a more intricate conversion from the JSON to Vector data than above. Additional details on this are provided below.

This will applied within the camera compound once the Manual Lens option is activated in the INPUT section:

Note, that the Manual Zoom and Focus settings will be automatically replaced with the data from the Lens file if it is formatted correctly.

The JSON file will be opened as a collection in Aximmetry and you will need to convert this data into a vector format representing the lens data. The vector maintains a standardized layout; however, the interpretation of data elements may vary across different description types.
The lens data in vector format should contain eight floating-point values:
1. 1 - DescType - Description Type:
      0 - OpenCV (the default Aximmetry format, Camera Calibrator also uses this)
      1 - Stype
      2 - Mo-Sys (you will have to use this, so your Vector must start with the value 2)
      3 - TrackMen
      4 - Camix
  2 - FOVX - horizontal Field Of View in degrees
  3 - Aspect - image Aspect Ratio
  4 - CX - Center Shift X component
  5 - CY - Center Shift Y component
  6 - K1 - Radial Distortion coefficient 1
  7 - K2 - Radial Distortion coefficient 2
  8 - SensorWidth - the width of the used area of the camera sensor
3. For an elaborate example of converting a different Lens data format, please refer to the compound found at: [Common_Studio]:Compounds\Tools\Lens_Distort_Vanishing.xcomp
  This compound might offer useful insights on parsing your lens JSON file.

Regarding the Aximmetry Camera Calibrator app, could you please provide the names of the camera lenses and camera bodies you work with? Additionally, could you specify during which parts or images of the calibration process you are unable to move the camera? Sharing screenshots of the issue would greatly assist in diagnosing the problem encountered when using those lenses with the Camera Calibrator app.

Warmest regards,

ThachNN6

Hi,

We use Sony HDC-3500 with Fujinon UA14x4.5BERD-S10 and UA 23x7.6BERD lens

Regards,

Thach

Eifert@Aximmetry

Hi Thach,

The Sony HDC-3500 is not traditionally designed for virtual production applications. With your current setup, the camera and lenses begin at a very low focal length. When employing the Camera Calibrator you should aim for a starting focal length of 18mm or higher. This adjustment will fix the issues you've previously encountered. By turning on the lens extender(s) you might reach the desired 18mm or higher focal length.

Additionally, upon reflection, I realize I should have mentioned this earlier: Ideally, you should add the lens file directly to the Mo-Sys system. If done, Aximmetry can seamlessly receive it from your camera tracking (Mo-Sys system), eliminating the need to manually input it into Aximmetry.

Warmest regards,

Mo-Sys tracking

Cookie consent