Cooke reports lens fingerprints, not camera position

The stage

Cooke Optics' /i Technology embeds lens metadata directly into cinema lenses, and Cooke's own Digital Lens System page, retrieved 16 September 2026, describes it as capturing per-frame key lens data at every shot. The stated fields are pinhole focal length for spherical and anamorphic lenses, a dynamic squeeze ratio for anamorphic lenses, and entrance pupil offsets and centre shifts. Cooke calls the result 'the Lens Fingerprint, Digitised,' and states the technology is built into more than 300 lens models across manufacturers, with major motion-picture cameras offering native compatibility that embeds the data directly into camera RAW files without extra hardware.

What the documents establish

The page is explicit that /i Technology reports lens state, not camera position: focus, iris, zoom and the geometric values above, delivered on-set into camera files and in post through Nuke nodes Cooke calls the Cooke Lens System. It is not a camera-tracking system and this entry does not describe it as one. A second Cooke document, its dated camera and lens definitions paper of 21 July 2023, explains why a field like pinhole focal length needs a precise, shared definition at all: the paper states that inconsistent meanings of ordinary terms such as 'focal length' are 'a major barrier to allowing hardware and software from different vendors to interoperate.' Read together, the two documents show /i Technology's specific fields exist to resolve exactly that ambiguity, not to add data for its own sake. Neither document names which specific camera models or which data-management systems carry the extended compatibility Cooke's page also claims.

The department view

The camera assistant sets the choices, focus, iris, zoom, that /i Technology records without extra manual logging, while the DIT and VFX-facing data wrangler are the ones who pull that metadata into the pipeline described on Cooke's virtual-production page. For an XR or LED-volume shoot specifically, Cooke states a data-management system delivers the metadata to the XR or VFX team, positioning /i Technology as an input to that team's frustum-matching process rather than the tracking layer itself, which a separate camera-tracking system still has to provide.

What to check before you build

This is an editorial checklist. Confirm the specific lens and camera model in use actually carry /i Technology, since Cooke states a count of supported lens models rather than naming every one. Verify which data-management or on-set asset system a production's pipeline actually uses, since Cooke's stated 'extended compatibility' does not name the systems. Do not treat /i Technology metadata as a substitute for camera-position tracking; confirm a separate tracking system is in place for frustum rendering.

• Does the lens and camera pairing on this stage actually carry /i Technology, and at what data rate?
• Which data-management system in this pipeline actually reads the entrance-pupil and squeeze-ratio fields Cooke describes?
• Is a separate camera-tracking system supplying position data, since /i Technology reports lens state only?

Cooke's own materials describe a defined, per-frame lens-metadata protocol built to remove terminology ambiguity between departments, distinct in kind from the camera-tracking systems it is commonly paired with on a virtual-production stage.