After I have processed a project on the cloud. And try to open it on Pix4D desktop I get “Error: failed to read cameras!”
I have looked everywhere online just haven’t found any explanation to this error. This has happened with 2 different projects I have processed on the cloud and then tried to open on the desktop. This error seems to be related to why I can’t view point cloud on the desktop. I contacted Pix4D support about the issue and they told me to try the following:
Close the Pix4D project.
Move all images downloaded from the cloud into one folder.
In the result folders, navigate to …\project_name\3_dsm_ortho\project_data.
Delete the folder meditor.
Open the .p4d file with Pix4D desktop.
Select the new image path when prompted.
I tried this but I was still unable to view the point cloud on the desktop. Here is a screen shot of what I’m seeing for the first project:
Here is a screen shot of the second project. It is showing an error with the point cloud “Increase density of 3D points”
I’ve been in touch with Pix4D support and it sounds like it is a problem on their end. I recieved the following response from support this morning:
“We have managed to reproduce the issue from our side in multiple machines. Additionally, there are more projects with the same issue and other users experience the same error. That means that it is something related to our processes, rather than your machine. I believe if you try to process the project locally you will not face any issue.
Our investigation up to this point indicates that there is an problem with downloading the results of step 2. However, our developers need some more time to better understand the issue in order to fix it.
Since I cannot provide any time estimation of the fix, I would recommend running all steps of processing locally in order to get the results faster”
Thanks Maria - I keep all my images on an external hard drive and knew it was seeing them ok because the map view worked. but not the raycloud. And this happened after processing locally…and after a software update to 4.2.15 I will try processing
again locally. Evan
I had the same exact problem as described above and I was able to resolve it fairly easily.
Step 1. With your project closed, move the original input images to a different folder. (These are the images that you input when setting up your project, before you upload to the cloud for processing.)
Step 2. Open your cloud processed project.
Step 3. Pix4D should now prompt you to navigate to the folder where original input images now reside. Select the folder and click okay.
After doing this the issue with “Error: failed to read cameras!” did not occur and I am able to utilize the rayCloud view. I do not know exactly what is going on here, but this did fix the problem. My guess it that is has something to do with having input imagery in multiple folders before cloud processing. I recommend having all input imagery in the same folder.
As Logan mentioned, in case you face this error you should always check that all the images are in a single folder. If not, please add all of them in one folder. Additionally, try to copy the .p4d file outside of the results folder, so that you have a folder with all the images, the results folder and the .p4d file.
However, there are cases that even creating this files structure might fail. This is an issue that we are currently investigating in order to make the Pix4D Cloud experience more stable.
We are still having this problem months after the initial bug report. Are the developers still working on a fix? Changing the file structure didn’t help.
Please follow the instruction to overcome the problem.
Ensure that you have all the images stored in one single folder and the copy of those images doesn’t exist on your computer (the folder is not redundant).
Ensure that .p4d file is outside of the Result Folder so that you have a folder with all the images, the results folder and the .p4d file.
Open project.
Pix4Dmapper should prompt you to navigate to the folder where images are located, select the proper folder and click OK.
However, you can still meet yourself with a similar view to this one, where the processing results are still missing.
Open the Result Folder.
Ensure that all the processing files are stored there.
After it, you will be able to see the rayCloud of your project.
Save the project to remain the image path.
Allison in your case, can you check step 5 and let me know if it works for you?
Thanks Beata! It turns out I was wrong, we hadn’t yet moved the images into a single folder when we had this problem, and doing so fixed it, sorry about that!
I can see that there are 7429 images that you’re processing. Am I right saying that you’re processing them in one bath? It’s not a merged project, right?
Investigating the error I can say that it appeared after the Keypoints Extraction Process. The keypoints were extracted, however, the information can’t be written into .p4d file. Therefore the errors:
no blocks computed,
no calibrated cameras
error e0046: Processing failed. No calibrated cameras
appeared subsequently.
My questions:
Have you ever experienced a similar problem with any other project?
Where did you save the project, on some external drive? Is there enough space? Do you have there
edit/write permissions?
Additionally:
Your NVIDIA driver is outdated. You can download the one for you from NVIDIA website.
I suppose that you processed each step (Step 1,2,3) in each subproject that you had and now you want to merge DTMs. However, it is not the proper workflow of how you should merge subprojects. Please have a look at our articlehow to merge projects and the video included to learn more about this process. If you have some questions related to this method, you can reach us here.
Hi we are having an issue with a project of ours,
after we run the initial processing with full image scale we get this error:
" [Error]: Failed to read cameras! "
initially the project was in the same folder as the images, later we removed the project and recreated it with the images in a separate folder but the issue remained.
These cookies are necessary for the website to function and cannot be switched off in our systems.
They are usually only set in response to actions made by you which amount to a request for services, such as setting your privacy preferences,
logging in, or filling in forms. These cookies do not store any personally identifiable information.
These cookies allow us to count visits and traffic sources so we can measure and improve the performance of our site.
They help us to know which pages are the most and least popular and see how visitors move around the site.
All information these cookies collect is aggregated and therefore anonymous.
If you do not allow these cookies we will not know when you have visited our site, and will not be able to monitor its performance.
These cookies may be set through our site by our advertising partner (Google).
They may be used by Google to build a profile of your interests and show you relevant adverts on other sites.
They do not directly store personal information but are based on uniquely identifying your browser and internet device.
If you do not allow these cookies, you will experience less targeted advertising.