Precision in a Click: PFTrack Camera Sensor Database
- Adam Hawkes
- 3 days ago
- 5 min read
In high-stakes matchmoving, the conflict between speed and sub-pixel accuracy is constant. Manually inputting camera data is a notorious drain on production time, it requires searching disparate sources for specs, cross-referencing active sensor areas and shooting modes, and then hoping the information found online is reliable.
The PFTrack Camera Sensor Database fundamentally changes this workflow. It translates repetitive, error-prone technical setups into a professional standard in just a few clicks, enabling you to dedicate your focus to achieving the highest-quality camera solve, not tedious data entry. This article details why the Database is indispensable for your pipeline, how to leverage its functionality, and the methods for extending it to accommodate proprietary or custom camera assets.
Why Accuracy Matters: The Foundation of Your Solve
Field of View (FOV) is governed by two core parameters: the camera's sensor size and its focal length. For example, a 50 mm lens on a full-frame (36×24 mm) sensor gives about a 39.6° horizontal FOV; change the sensor to APS-C (24×16 mm), and the same lens yields a narrower FOV of only ≈27° (the “crop factor” effect). These values determine how 2D image data is projected into 3D space, directly influencing perceived scale, perspective, and depth.
While PFTrack is highly capable of estimating FOV, and even lens distortion, when explicit sensor or focal length data is unknown, PFTrack performs best when supplied with accurate physical measurements. Providing real-world camera metrics ensures the strongest foundation for precise, repeatable results.
This level of accuracy becomes especially critical in multi-shot sequences, where consistent focal length interpretation across shots is essential. Without defined physical parameters, slight variations in estimated FOV can lead to inconsistencies in scene scale, misaligned assets, or solve drift across edits.
Even small discrepancies in sensor dimensions, on the order of tenths of a millimeter, can introduce meaningful errors in FOV calculations, which in turn degrade 3D track quality and overall solve fidelity. The bottom line is that supplying accurate, real-world camera metrics removes ambiguity: the solver has one less unknown to estimate, which yields more stable and precise production-grade tracking.
While manually entering sensor details can be error prone, especially when relying on ambiguous manufacturer specifications, PFTrack provides the perfect solution: the Camera Sensor Database.
The Workflow Advantage: Why Presets Matter
When you need to enter the camera sensor size manually switching to the camera sensor database provides four immediate benefits:
Eliminating Ambiguity: Manufacturer specifications can be vague, often listing "total" vs. "effective" pixels or using very generalised terminology to approximate size such as ‘Super 35’.
Preventing Calculation Errors: Calculating the physical size of a sensor based on pixel pitch or unverified online info is prone to error. A single millimetre of discrepancy can degrade the quality of a 3D solve.
Managing Shoot Modes: Modern cameras frequently use specific shoot modes (cropping or windowing the sensor). Manually calculating these deviations is complex; the database provides accurate presets from major manufacturers for these modes in seconds.
Team-Wide Consistency: On large features with multiple artists, the database ensures every user is working with identical, verified camera parameters, preventing drift between different shots.
For a deeper look on sensor modes and terminology we have a camera sensor size guide available here.
How to Use the Sensor Database
The sensor database is integrated into the areas where camera data is defined. You can access it in two primary locations, the Clip Input node and the Camera Lens Distortion Presets panel.
It’s designed to be a seamless part of your workflow and can be launched using the following button . It is broken down into three sections:
Database selection and information.
Camera make and model selection.
Sensor information and shoot mode selection.
Camera Sensor Database in action
Quickly select verified sensor presets and ensure physically accurate FOV across your shots in PFTrack.
Find Your Camera: Type in your manufacturer or camera model in or browse the list (e.g. "RED Komodo" or "Sony Venice").
Select the ‘Shoot Mode’: Pick the sensor shoot mode used in the clip. Modes that don’t match resolution will be greyed out.
Click ‘Use Sensor’ to automatically fill in the sensor measurements in both Clip Input Node & camera lens distortion presets.
You can filter the list further by checking for proxies 2x & 4x as well as matching resolution and aspect ratio.
Pro Tip: Need more flexibility
The database allows users to switch between The Pixel Farm’s internal database and the Matchmove Machines database. This provides unparalleled flexibility, if a specific or niche camera body isn't found in one, a quick toggle often finds it in the other.
Expanding the Database: Custom XML Data
For proprietary camera rigs, prototypes, or bespoke setups, PFTrack allows you to expand the database with your own metrics. By creating a custom sensor xml file, you can define custom sensor sizes for your projects that can be selected directly within the camera sensor database.
File structure:
To simplify the process, PFTrack ships with an example-sensors.xml file. This file serves as a template for defining your own <camera>, <sensor>, and <modes>. You can find the template in the installation folder on your system /media/example-sensors.xml. The custom .xml file you create can be named whatever you want.
Where to put your custom file?
Once you have created your custom xml file you will need to place it in the directory listed below, once in place relaunch PFTrack and you will have access to the updated file via the camera sensor database dropdown.
MacOS: /Users/USERNAME/Documents/The Pixel Farm/PFTrack/presets/sensors
Windows: C:\Users\USERNAME\Documents\The Pixel Farm\PFTrack\presets\sensors
Linux: /home/USERNAME/Documents/The Pixel Farm/PFTrack/presets/sensors
For a deep dive into the XML schema and specific formatting rules, please refer to our User Defined File Formats Documentation.
Pro Tip: Centralised Management - for Multi-User Pipelines
For studios managing multiple PFTrack seats, maintaining a "single source of truth" for camera data is essential for pipeline integrity. Rather than managing local files on every machine, you can centralise your custom presets:
Place your custom.xml file in a centralised network location accessible by all workstations.
In the PFTrack software settings, navigate to ‘Additional file locations’ and point the ‘Sensor presets’ path to your network directory.
Once configured, any update made to the central XML file is propagated across the entire facility and available in PFTrack on relaunch.
This centralised approach allows Pipeline TDs to deploy updated camera information for a specific feature or production once, ensuring every artist, regardless of their workstation, is working with identical, verified technical specifications. You can use multiple xml files as well with each defining the cameras used for a specific production, this can be further customised with a project or company logo.
Conclusion
The Camera Sensor Database isn't just a convenience; it is a precision tool. By moving away from manual entry and unverified data, you safeguard your solves and streamline your pipeline.
Ready to upgrade your tracking? Ensure you are running the latest version of PFTrack to access the most recent camera sensor database updates.
Want to add a camera model to our database, or discuss a camera system you're using for tracking with other professional matchmovers? Join our support community here.
