Your camera is not supported at this time - PIX4Dreact
This article explains why a user might see a warning that a camera isn't supported and what steps to take to resolve the issue.
IN THIS ARTICLE
What to do if the camera is not supported?
Which cameras are supported in PIX4Dreact?
Error in camera parameters file
PIX4Dreact 1.6 and newer is compatible with imagery from all drone models. Using the latest version is recommended before attempting image processing.
For PIX4Dreact 1.5 and previous versions, PIX4Dreact will display the message "Your camera is not supported at this time" when a camera is not in the database. This can occur for recently released cameras, less popular cameras, or if the resolution of a camera was changed in the camera's settings. In this case, a custom camera parameters file (.xml) will be required to process the unsupported imagery. This .xml file acts as an amendment to the camera database and will allow PIX4Dreact to begin processing.
This is an example of what PIX4Dreact displays when a camera is not supported:
"We are sorry. Your camera is not supported at this time."
What to do if the camera is not supported?
A user might see a warning or error message because the camera model being used is not yet in our database. This often happens with recently released or less common cameras.
The behavior depends on the version of PIX4Dreact
-
PIX4Dreact 1.6 and newer: The software is often able to process images from unsupported cameras as long as they contain the required technical data (e.g., focal length, image resolution). However, an error can occur if this metadata is missing.
-
PIX4Dreact 1.5 and older: The software is more restrictive and requires a camera to be explicitly listed in its database. If a camera is not in the database, an error message will appear, "We are sorry. Your camera is not supported at this time" and the images cannot be processed without a custom file.
The best first step is to ensure the most current version of PIX4Dreact is being used, as new versions include new camera models.
- Update PIX4Dreact: The latest version is more flexible and can often process images from unsupported cameras automatically. Download latest PIX4Dreact version (If using a Perpetual license, ensure the S&U license is active.)
- Download a Custom Camera Parameter File: Please click on the download link and follow the steps below to import the file.
🚦 Click here to download a Camera Parameter File for PIX4Dreact
To use the file, perform the following steps:
- On the dashboard, click on the PIX4Dreact SETTINGS and select Camera parameters file.
- Click Select file and select the .xml file in the file dialog.
- Exit the settings and create a project to process the dataset. The camera parameters file is used automatically.
The file can be un-linked by clicking Remove in the Camera parameters file page of the settings. The parameters will then not be used anymore. If a camera parameter file is provided for a specific camera, its values override any corresponding values in the image Exif data or the internal database.
Important: Thermal images can be processed using the provided file to generate a colorized visualization of relative temperature variations within the scene. This enables the identification of relatively warmer and cooler areas. However, absolute pixel temperature values cannot be retrieved, as radiometric data is not supported. This limitation applies to currently unsupported thermal image sources, such as the M30T.
Same error after importing the XML
If the downloaded file does not enable processing or if the resulting orthomosaic is of poor quality, and a valid Support and Upgrades license is available, contact Pix4D support with the complete dataset. An updated .xml file can then be provided to ensure compatibility with the imagery.
Which cameras are supported in PIX4Dreact?
Check our supported cameras and resolutions here: Supported cameras - PIX4Dreact.
Error in camera parameters file
If PIX4Dreact displays a message that the XML contains errors, please:
- Ensure the provided XML has the correct format:
- Ensure there are no empty tags:
- Ensure there are no incomplete tags like <rigs/> at the beginning or <mappings/> at the end.