> For the complete documentation index, see [llms.txt](https://stage-precision.gitbook.io/grid/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://stage-precision.gitbook.io/grid/camera-calibration/project-setup/camera-tracking-sources/camera-tracking-protocols-overview.md). # Camera Tracking Protocols Overview ## Camera Tracking Protocols Overview Camera calibration workflows may require different types of source data depending on the selected tool. Some workflows only need camera position and rotation. Other workflows require lens encoder values such as zoom and focus. Axis-based workflows may require rail, pole, pan/tilt, crane, robotics, or other movement values. This page helps you understand: * which data each calibration tool requires * which tracking sources or protocols can provide that data * when multiple sources need to be combined * which Map options should be enabled in the Calibration Object {% hint style="info" %} Many camera tracking systems can output more than one protocol. For example, a product may have its own native protocol and also support **FreeD**. In this table, the product name and the protocol are listed separately so users can find their device and understand which Grid Studio source to use. {% endhint %} *** ## Source Data Types For calibration workflows, source data can be grouped into a few main categories. ### Position Position describes the camera or object location in 3D space. In the Calibration Object Map List, this data is enabled with **Use Pos**. ### Rotation Rotation describes the camera or object orientation. In the Calibration Object Map List, this data is enabled with **Use Rot**. ### Lens Encoder / Custom Data Lens encoder data usually means **Zoom** and **Focus**. In the Calibration Object Map List, this data is enabled with **Use Custom Data**. {% hint style="info" %} Iris values may exist in some protocols, but iris is not required for the camera calibration workflows described here. The relevant lens encoder values are usually **Zoom** and **Focus**. {% endhint %} ### Axis / Movement Data Axis or movement data can describe rails, dollies, lifts, cranes, poles, pan/tilt heads, robotic heads, cable cameras, or other mechanical systems. Depending on the integration, this data may be mapped as position/rotation, custom data, or through an axis-specific setup. *** ## Required Source Data by Calibration Tool Use this table to understand which kind of source data each calibration tool needs. ### Reading the Tool Requirements Table

Symbol	Meaning
✅	Required or normally used
❌	Not required
◐	Depends on the setup or selected options
⚠️	Required with important setup requirements

{% hint style="info" %} This table describes source data requirements only. It does not list all other requirements such as Live Camera Image Input, Calibration Screens, Measurement Points, Lens Profiles, or Alignment Profiles. {% endhint %} ### Tool Requirements Matrix

Calibration Tool	Position	Rotation	Lens Encoder	Axis / Movement Data
Lens Calibration	❌	❌	✅	❌
Lens & Tracking Calibration	✅	✅	✅	❌
Lens & Tracking Calibration (Rotation Only)	❌	✅	✅	❌
Tracking Alignment	✅	✅	❌	❌
Alignment with Markers	✅	✅	❌	❌
Axis-Pole Calibration	❌	❌	◐	✅
Simple Static Calibration	❌	❌	❌	❌
Simple Static Calibration with Marker	❌	❌	❌	❌
Focusing on Points	❌	❌	❌	❌
Reposition from Marker	❌	❌	❌	❌
Reposition from Screen	❌	❌	❌	❌
Screen Reposition Without Profile	❌	❌	❌	❌
Screens Alignment	✅	✅	❌	❌

*** ## Tracking Source Capabilities Use this table to understand what kind of data a source or protocol can provide. ### Reading the Source Capability Table

Symbol	Meaning
✅	Supported / expected to provide this data
❌	Not supported / not expected to provide this data
◐	Partially supported or setup-dependent
⚠️	Supported, but requires careful setup
❓	Candidate / unclear / needs internal confirmation

{% hint style="warning" %} This table intentionally includes candidate systems and uncertain entries. Verify the final support status, protocol name, and available data before publishing. {% endhint %} ### Source Capability Matrix

Product / System	Protocol	Position	Rotation	Lens Encoder	Axis / Movement Data
AirPixel / Racelogic	freeD	✅	✅	✅	❌
Antilatency	Antilatency	✅	✅	❌	❌
ARRI LDS / LDE / UMC ecosystem	ARRI UMC4	❌	❌	✅	❌
BlackTrax	BlackTrax / RTTrP	✅	✅	❌	❌
Canon CV	Canon CV	❌	❌	✅	❌
cmotion	cmotion	❌	❌	✅	❌
DCS / DCS LDT-V2	DCS	❌	❌	✅	❌
Factory Optic SYNCRO-LINK MARK ZERO	Factory Optic	❌	❌	✅	❌
FoMa Antares	FreeD	❌	✅	✅	❌
FreeD	FreeD	✅	✅	✅	◐
FreeD	FreeD Serial	✅	✅	✅	◐
G3DVU	G3DVU	✅	✅	⚠️	❌
HTC VIVE Mars CamTrack	FreeD	✅	✅	◐	❌
HTC VIVE Tracker / SteamVR	OpenVR / SteamVR	✅	✅	❌	❌
LOLED Virtual	LONET 2	❌	❌	✅	❌
LOLED Virtual	LONET OSC	❌	❌	✅	❌
MJ Robotic	FreeD	◐	✅	✅	❌
Mo-Sys	Mo-Sys F4	✅	✅	⚠️	◐
Mo-Sys	Mo-Sys F4 serial	✅	✅	⚠️	◐
Mo-Sys	FreeD	✅	✅	✅	❌
MRMC / Nikon	FreeD	✅	✅	✅	❌
multiCAM	FreeD	✅	✅	✅	✅
Ncam / Zeiss	Ncam	✅	✅	⚠️	❌
Ncam / Zeiss	FreeD	✅	✅	✅	❌
OptiTrack	OptiTrack NatNet	✅	✅	❌	❌
OpenTrackIO	OpenTrackIO	✅	✅	✅	❌
Pixotope Camera Tracking	TrackMen	✅	✅	⚠️	❌
Pixotope Fly	TrackMen	✅	✅	⚠️	❌
PSN	PSN	✅	✅	❌	❌
Qualisys	Qualisys	✅	✅	❌	❌
Shotoku	FreeD	✅	✅	✅	❌
Shotover	Shotover	❌	✅	✅	❌
SMT	SMT	✅	✅	⚠️	❌
Sony OCELLUS	FreeD	✅	✅	✅	❌
Spidercam Frame B	Spidercam Frame B	✅	✅	✅	❌
StypeKit	Stype HF	✅	✅	⚠️	❌
StypeKit	FreeD	✅	✅	✅	❌
Stype RedSpy	Stype HF	✅	✅	⚠️	❌
Stype RedSpy	FreeD	✅	✅	✅	❌
TechnoCrane	TechnoCrane Serial	✅	✅	✅	❌
Technocrane	Technocrane	✅	✅	✅	❌
TrackMen	TrackMen	✅	✅	⚠️	❌
Vicon	Vicon	✅	✅	❌	❌
Vinten Heads	freeD	❌	✅	✅	❌
XD motion	FreeD	✅	✅	✅	❌
Zeiss CinCraft Scenario	Ncam	✅	✅	⚠️	❌
Zeiss CinCraft Scenario	FreeD	✅	✅	✅	❌

*** ## Combining Sources To combine sources, compare both tables. First, check which data the selected calibration tool requires. Then select one or more sources that provide the required data. In the Calibration Object, add each required map to the **Map List** and enable only the data that should be used from that map. ### Map Options

Required Data	Calibration Object Map Option
Position	Use Pos
Rotation	Use Rot
Zoom / Focus / Lens Encoder	Use Custom Data
Axis / Rail / Movement Values	Use Custom Data or axis-specific map setup

### Example: Transform Source + Lens Encoder Source

Source Role	Use Pos	Use Rot	Use Custom Data
Camera tracking source	on	on	off
Lens encoder source	off	off	on

{% hint style="info" %} Lens encoder values such as **Zoom** and **Focus** are handled as **Custom Data**. {% endhint %} ### Avoiding Duplicate Data When multiple maps are used, make sure the same data type is not enabled twice. For example, do not enable **Use Pos** on two different maps unless the workflow explicitly requires it. {% hint style="warning" %} Duplicate or conflicting position, rotation, or encoder values can lead to incorrect calibration results. Enable only the data that should be used from each map. {% endhint %} *** ## Raw Tracking and Encoder Values For calibration, Grid Studio should receive raw tracking and encoder values whenever possible. This is important because Grid Studio calculates and applies its own **Lens Profile** and **Alignment Profile**. ### Why Raw Values Are Important Some camera tracking systems can output proprietary protocol data that already includes: * lens distortion information * nodal shift data * zoom-dependent offsets * focus-dependent offsets * processed positional offsets These values must not influence the camera transform during Grid Studio calibration. If zoom- or focus-dependent shifts are already included in the incoming transform, the calibration result can become incorrect because the camera position is being changed before Grid Studio calculates its own alignment. {% hint style="warning" %} Avoid tracking data where lens distortion, nodal shifts, or zoom/focus-dependent positional offsets are already applied to the camera transform. Grid Studio needs raw tracking and encoder values so it can calculate and apply the correct Lens Profile and Alignment Profile itself. {% endhint %} ### Preferred Raw Protocols When available, **FreeD** is often preferred for calibration because many tracking systems can output raw position, rotation, zoom, and focus values through FreeD. Many manufacturers also provide their own proprietary protocols. These can be useful, but they may include additional lens or offset information that is not desired during Grid Studio calibration. If a system can output FreeD, this is often the cleanest starting point for calibration. ### Proprietary Protocols Manufacturer-specific protocols can provide useful tracking and lens data, but they may also include processed values. Before using a proprietary protocol for calibration, check whether it includes: * distortion correction * nodal offsets * lens-profile-dependent offsets * zoom/focus-dependent transform changes * non-raw lens values If these values are present, disable them in the Map Input if possible. *** ## Notes for Specific Source Types Some source types require additional care. ### Lens Metadata Sources Lens metadata sources may provide more than zoom and focus. They can also include: * iris * distortion information * shading or vignetting data * entrance pupil / nodal data * lens profile metadata * other manufacturer-specific data For Grid Studio calibration, only use the values that are required by the selected workflow. {% hint style="warning" %} Do not use manufacturer distortion, shading, nodal, or profile-dependent values as calibration source data unless the workflow explicitly requires them. {% endhint %} ### PTZ Cameras Many PTZ cameras can output FreeD. In these cases, the user may look for the camera model in this table, but the Grid Studio source is usually **FreeD**. PTZ FreeD data can often include: * pan * tilt * zoom * focus For rotation-only or pan/tilt workflows, check that the required values are available and mapped correctly.

Product / System	Protocol	Position	Rotation	Lens Encoder	Axis / Movement Data
Bolin R9-420N	FreeD	❌	✅	✅	❌
Bolin R9 Series	FreeD	❌	✅	✅	❌
Canon CR-N300	FreeD	❌	✅	✅	❌
Canon CR-N350	FreeD	❌	✅	✅	❌
Canon CR-N400	FreeD	❌	✅	✅	❌
Canon CR-N500	FreeD	❌	✅	✅	❌
Canon CR-N700	FreeD	❌	✅	✅	❌
Canon CR-X300	FreeD	❌	✅	✅	❌
Lumens VC-A71P	FreeD	❌	✅	✅	❌
Lumens VC-A71SN	FreeD	❌	✅	✅	❌
Panasonic AW-UE100	FreeD	❌	✅	✅	❌
Panasonic AW-UE150	FreeD	❌	✅	✅	❌
Panasonic AW-UE160	FreeD	❌	✅	✅	❌
Panasonic AW-UE80	FreeD	❌	✅	✅	❌
PTZOptics MOVE 4K	FreeD	❌	✅	✅	❌
Sony FR7	FreeD	❌	✅	✅	❌
Sony FR7	OpenTrackIO	❌	✅	✅	❌
Sony BRC-X1000	FreeD	❌	✅	✅	❌
Sony BRC-H800	FreeD	❌	✅	✅	❌
Telycam Explore SE	FreeD	❌	✅	✅	❌
Telycam PTZ Series	FreeD	❌	✅	✅	❌

### Robotics, Rails, Cranes, and Cable Cameras Robotic systems, camera rails, cranes, and cable cameras may provide movement data in different ways. Some systems output a complete camera transform. Other systems output separate axis values that need to be interpreted by a dedicated axis, rail, pole, or camera rig object. For these systems, check whether the data should be used as: * position and rotation * custom data * axis-specific movement data * a combined FreeD transform * a vendor-specific protocol *** ## Before Continuing Checklist Before selecting a tracking source for calibration, check the following: * The product or system is listed in the source capability matrix, or a compatible protocol is known. * The protocol provides the data required by the selected calibration workflow. * Position and rotation are available if the workflow requires camera tracking. * Zoom and focus encoder values are available if the workflow requires Lens Calibration. * Axis or movement values are available if the workflow requires axis-based calibration. * Encoder values are available as raw values whenever possible. * Proprietary lens correction, distortion, nodal shift, or zoom/focus-dependent offsets are not applied to the camera transform. * The required data is mapped correctly to the Camera Object. * The Calibration Object references the correct maps in **Maps → Map List → Input Map**. * **Use Pos**, **Use Rot**, and **Use Custom Data** are enabled only where needed.