One calibrated camera, one file.

A camera that has been measured once carries that knowledge in a file. Export it from the install that did the work, import it on another install, and that head flies there without going through the measuring again.

For a rental and staging company this is the difference between a truck of cameras and a truck of jobs. Heads come back from a show, the file stays on the shelf, and the next job starts with camerawork instead of set-up.

For an organization with more than one room or more than one site, it means a head that moves between rooms takes its behavior with it, and every room treats it the same way. A camera borrowed for a night behaves like a camera that lives there.

The file carries what the camera is and how it behaves. What belongs to one install — which machine drives the head, which switcher input it lands on, where it sits on the stage plan — stays at home, so importing a camera never disturbs the room you import it into.

On import, a camera on VISCA over IP is asked which camera it is before the file is trusted; any other head comes in marked unverified until somebody confirms it. If it is a different camera, it says so rather than flying on somebody else's measurements.

For an integrator, the file is part of the handover. A camera measured on the bench arrives on site with its behavior already known, so the time in the room goes to composing shots rather than repeating setup.

A profile never outranks the camera in front of you. If a camera on VISCA over IP answers as a different camera than the file, the software says so and refuses the file. A head it cannot ask is marked unverified until somebody confirms it.