Agisoft Metashape
Agisoft Metashape => General => Topic started by: Dmitry Semyonov on October 12, 2020, 11:50:23 AM
-
Pre-release version of Agisoft Metashape 1.7.0 is available for download.
This pre-release is considered as unstable and is not recommended for production use.
Please use the links below for download:
Agisoft Metashape Standard edition
Windows 64 bit (https://s3-eu-west-1.amazonaws.com/download.agisoft.com/metashape_1_7_0_x64.msi)
Mac OS X (https://s3-eu-west-1.amazonaws.com/download.agisoft.com/metashape_1_7_0.dmg)
Linux 64 bit (https://s3-eu-west-1.amazonaws.com/download.agisoft.com/metashape_1_7_0_amd64.tar.gz)
Agisoft Metashape Professional edition
Windows 64 bit (https://s3-eu-west-1.amazonaws.com/download.agisoft.com/metashape-pro_1_7_0_x64.msi)
Mac OS X (https://s3-eu-west-1.amazonaws.com/download.agisoft.com/metashape-pro_1_7_0.dmg)
Linux 64 bit (https://s3-eu-west-1.amazonaws.com/download.agisoft.com/metashape-pro_1_7_0_amd64.tar.gz)
Agisoft Metashape Python 3 Module (requires Professional edition license)
Windows 64 bit (https://s3-eu-west-1.amazonaws.com/download.agisoft.com/Metashape-1.7.0-cp35.cp36.cp37.cp38-none-win_amd64.whl)
Mac OS X (https://s3-eu-west-1.amazonaws.com/download.agisoft.com/Metashape-1.7.0-cp35.cp36.cp37.cp38-abi3-macosx_10_13_x86_64.whl)
Linux 64 bit (https://s3-eu-west-1.amazonaws.com/download.agisoft.com/Metashape-1.7.0-cp35.cp36.cp37.cp38-abi3-linux_x86_64.whl)
Agisoft Metashape Java Library (requires Professional edition license)
Download (https://s3-eu-west-1.amazonaws.com/download.agisoft.com/metashape-java-api-1.7.0.zip)
Metashape 1.7.0 Change Log (https://www.agisoft.com/pdf/metashape_changelog.pdf)
Metashape 1.7.0 Python API Reference (https://www.agisoft.com/pdf/metashape_python_api_1_7_0.pdf)
Please let us know if you have any problems using this version.
Please post problems and/or questions concerning other Metashape version in separate topics.
This topic will be removed when the final 1.7.0 version is released.
Note
Project files created with 1.7.0 version can't be opened with earlier versions.
EDIT:
Metashape 1.7.0 build 11736 was finally released. Thank you for useful feedback.
Please use the links on the main Metashape page for download:
Download Installers (http://www.agisoft.com/downloads/installer/)
-
Hi Dmitry, could give us an explanation of the connected components feature ? Is it a pixel connectivity method ?
-
Hi Dmitry, could give us an explanation of the connected components feature ? Is it a pixel connectivity method ?
I was about to ask the same question!
-
First observations compared to 1.6:
- Camera alignement is currently (a lot) slower in 1.7 & uses more CPU process during the matching points stage.
- Depth maps génération is also way slower (and uses more CPU process) but also compute depths maps for the whole images no longer being constrained by the bounding box (which is a good thing IMO but not sure if this is the sole reason for the performance decrease)
(https://i.postimg.cc/7Z8VGgQG/Screenshot-2020-10-12-141442.jpg)
- Depth maps filtering is way too aggressive (?) now
1.6.5
(https://i.postimg.cc/WbRWgLd1/Screenshot-2020-10-12-150427.jpg)
(https://i.postimg.cc/nrTG65G6/Screenshot-2020-10-12-151734.jpg)
(https://i.postimg.cc/wTfk2CvN/Screenshot-2020-10-12-151527.jpg)
1.7
(https://i.postimg.cc/6ptMbrLs/Screenshot-2020-10-12-150330.jpg)
(https://i.postimg.cc/XNgLGG6Q/Screenshot-2020-10-12-151653.jpg)
(https://i.postimg.cc/MKKDy6Wx/Screenshot-2020-10-12-151608.jpg)
Win10
Intel i7 6700K
32GB
Radeon VII
Mak
-
This seems to have the same memory scaling issues that the Refine Mesh option has.
Following errors on a project with 180 photos (61mpix)
EDIT: That being said, when it worked on a smaller project i did notice reduction of noise in the output model. Eager to test more :)
-
Can you explain:
• Added out-of-core processing support for dense cloud import, colorization and merging.
What does this mean?
-
Can you explain:
• Added out-of-core processing support for dense cloud import, colorization and merging.
What does this mean?
That means you are not RAM-bound in processing.
-
Here are two comparisions between 1.6.5 and 1.7.0
https://ibb.co/TMwNjfd
https://ibb.co/2nJ1Dv0
In one example it does a better job and in the other a worse job. It seems that dubious parts are handled better now.
I think some of the settings/parameters should be exposed so we can fine tune things.
-
Hi Dmitry, could give us an explanation of the connected components feature ? Is it a pixel connectivity method ?
The connected components for image alignment seems to be kind of an auto grouping of pictures, more or less geographicaly homogeneous among each other. It might also only be the tip of the iceberg of this new process. AM spread each picture in three groups, no matter how large is the data set.
-
Hello,
Whats is the workflow for laser scan import? Agisoft treats indiidual scans as cameras and tries to align them? Result can be seen in attatched image.
-
Cuda is not active in MacOS. Nvidia GPU's appear as OpenGL. In my case I have two and ony one appears available in the GPU list.
-
Cuda is not active in MacOS. Nvidia GPU's appear as OpenGL. In my case I have two and ony one appears available in the GPU list.
The latest OSX version that supports CUDA is High Sierra 10.13.
Mak
-
Cuda is not active in MacOS. Nvidia GPU's appear as OpenGL. In my case I have two and ony one appears available in the GPU list.
The latest OSX version that supports CUDA is High Sierra 10.13.
Mak
That's the OS version that I'm using, precisely because of CUDA, with Two Nvidia 1080 Ti, without any major problem in 1.6.5 (despite a few Cuda crashes once in a while).
-
Hello,
Whats is the workflow for laser scan import? Agisoft treats indiidual scans as cameras and tries to align them? Result can be seen in attatched image.
Hello geodesy,
Current approach is the following:
- prepare scans from terrestrial laser scanner in E57 format;
- open Metashape and use File Menu -> Import -> Import Laser Scans option and select all E57 files, specify the output folder where the converted files will be saved (which can be used later in other project without repeating the conversion operation);
- add common digital camera images (if any) for the same scene;
- run Align Photos operation as usual.
For the laser scanning data Metashape is using spherical panoramas for the image matching, which are captured by the scanner or the intensity map, if the scanner is not capable of saving spherical panoramas. Then during the dense cloud or mesh generation operation the photogrammetric depth maps are merged with the depth information coming from the laser scanner.
-
Cuda is not active in MacOS. Nvidia GPU's appear as OpenGL. In my case I have two and only one appears available in the GPU list.
Hello Renato,
Do you have cuda-enable tweak set up via Advanced preferences tab?
Please also provide the output of the following command executed via the Console pane and specify the CUDA driver version installed:
Metashape.app.enumGPUDevices()
-
I have seen that the depth maps generation has a complete new algorithm in new version. However I have tested on a set of 280 UAV images and it seems that process is much longer than 1.6.5...
It reached 7% progress and estimated time to finish was at 13 hours and going up so I cancelled and reinstalled v.1.6.5 to complete depth maps in :
Depth Maps
Count 280
Depth maps generation parameters
Quality High
Filtering mode Aggressive
Processing time 4 hours 29 minutes
Memory usage 1.70 GB
Software version 1.6.5.11249
File size 1.37 GB
so new approach may be interesting but if it takes such more time than it is not feasible...
My system is:
Software name Agisoft Metashape Professional
Software version 1.6.5 build 11249
OS Windows 64 bit
RAM 15.95 GB
CPU Intel(R) Core(TM) i7-3630QM CPU @ 2.40GHz
GPU(s) GeForce GTX 670MX
-
Paul, thanks for sharing. Efficient processing is a huge factor as image sets get larger and larger. Simactive's Correlator3D is making good progress on reducing reconstruction processing time of large images sets, so it is possible. Perhaps Agisoft has some optimization coming as well.
-
[For laser scans] Current approach is the following:
...
- run Align Photos operation as usual.
Does that mean that the poses of the laser scans will be adjusted in addition to the internal and external parameters calculated for the standard cameras?
As a user who commonly combines laser scan data with photogrammetry that is not at all what I would want to happen. The laser scan data will almost always be coming from other software where we have much more control over the alignment process. Therefore the laser scan data should be treated as fixed (no pose adjustments) and photos aligned to it.
I haven't had a chance to test the implementation in Metashape 1.7.0 extensively yet. However, my past experience with the general method of treating scans as spherical panoramas for alignment purposes suggests that the results will likely be very unstable. The resulting panoramas are typically low resolution and, if they are intensity only scans, relatively low contrast; so few tie points are likely to be detected by Metashape's feature detector. From the few small tests I've tried on 1.7.0 that is indeed what seems to be happening.
From a process efficiency perspective, what I want to do as a user is use intensity only scans to capture geometry and photogrammetry to capture color.
-
I am comparing 1.7 with 1.6.5. 1.7 is much slower (54 minutes vs 40, in my case of creating a 3D model (OBJ).
It uses also much more memory
Depth map creation 3.5 GB and 20 minutes vs 1 GB and 10 minutes
Orthomosaic Reconstruction 9 minutes and 6.8 GB vs 3 minutes 30 seconds and 2.7 GB
GTX 1051 TI, 32GB
-
Hello ,
I ve try to install pre-release on RYZEN 3900x Windows 10 but installer finish without install metashape.
What can i do ?
Thank you
-
I can't seem to use GPU for depth map generation. I get the following error:
Warning: Device GeForce GTX 1070 Ti ignored because it has 5958/8192 MB available, but 6870 MB required
Log up to that point is attached. I have two identical GPUs and haven't had any issues like this in the past.
-
hi,
occlusion map generation takes for ever
2020-10-27 13:37:53 postprocessing atlas... done in 5.486 sec
2020-10-27 13:38:02 Finished processing in 200.162 sec (exit code 1)
2020-10-27 13:38:51 BuildTexture: mapping mode = Keep uv, page count = 1, texture size = 8192, texture type = Normal map, source data = Model, transfer_texture = 0
2020-10-27 13:38:51 Generating textures...
2020-10-27 13:38:51 Initializing...
2020-10-27 13:40:10 Baking textures...
2020-10-27 13:40:10 Computing tangent vectors...
2020-10-27 13:40:11 Computing normals for baking...
2020-10-27 13:40:11 Transferring attributes...
2020-10-27 13:40:23 Applying textures...
2020-10-27 13:40:32 Finished processing in 101.502 sec (exit code 1)
2020-10-27 13:45:29 BuildTexture: mapping mode = Keep uv, page count = 1, texture size = 8192, texture type = Occlusion map, source data = Model, transfer_texture = 0
2020-10-27 13:45:29 Generating textures...
2020-10-27 13:45:29 Initializing...
2020-10-27 13:46:36 Calculating ambient occlusion...
2020-10-27 15:04:31 Finished processing in 4742.23 sec (exit code 0)
2020-10-27 15:04:31 Error: Aborted by user
-
Cuda is not active in MacOS. Nvidia GPU's appear as OpenGL. In my case I have two and only one appears available in the GPU list.
Hello Renato,
Do you have cuda-enable tweak set up via Advanced preferences tab?
Please also provide the output of the following command executed via the Console pane and specify the CUDA driver version installed:
Metashape.app.enumGPUDevices()
Hi Alexey
Yes, I have the tweak activated for Cuda. I've included the outputs from "Metashape.app.enumGPUDevices()" from 1.7 and 1.6.5 for comparition.
There's clearly a difference between the two versions in number of GPU's detection.
Best Regards
Renato
-
:'( Hi Dmitry
I've run into the problem with the Metashape 1.7.0. Build 11340 - WIN/PRO version. On some projects it makes the Tiled model while on some it exits immediately with the message :
Assertion 23910910010 failed at line 54
It seems that it appeared after changing the Region properties like resizing, moving etc.
What is the solution?
Best, Darko
Should I mention that the Tiled Model was started right after the Alignment process with the Depth Maps option set to Ultra High and Faces to Low while the pixel size was left as it was.
-
I have seen that the depth maps generation has a complete new algorithm in new version. However I have tested on a set of 280 UAV images and it seems that process is much longer than 1.6.5...
Hello Paul,
It would be helpful to see the processing log related to the depth maps generation in the version 1.7 pre-release.
-
[For laser scans] Current approach is the following:
...
- run Align Photos operation as usual.
Does that mean that the poses of the laser scans will be adjusted in addition to the internal and external parameters calculated for the standard cameras?
As a user who commonly combines laser scan data with photogrammetry that is not at all what I would want to happen. The laser scan data will almost always be coming from other software where we have much more control over the alignment process. Therefore the laser scan data should be treated as fixed (no pose adjustments) and photos aligned to it.
I haven't had a chance to test the implementation in Metashape 1.7.0 extensively yet. However, my past experience with the general method of treating scans as spherical panoramas for alignment purposes suggests that the results will likely be very unstable. The resulting panoramas are typically low resolution and, if they are intensity only scans, relatively low contrast; so few tie points are likely to be detected by Metashape's feature detector. From the few small tests I've tried on 1.7.0 that is indeed what seems to be happening.
From a process efficiency perspective, what I want to do as a user is use intensity only scans to capture geometry and photogrammetry to capture color.
Hello Jed,
Yes, it can be said that the laser scans are aligned together with the common images.
If you need to rely on the accurate scanner locations, you can input corresponding coordinates to the Reference pane for the related camera instances and adjust the accuracy value for them in order to increase the weight for them.
And you are right that the intensity maps would provide lower number of tie points compared to spherical panoramas, however, manually placed markers (on the scanner data and on the digital camera images) could assist the alignment process, if there automatically detected tie points are not sufficient.
-
I am comparing 1.7 with 1.6.5. 1.7 is much slower (54 minutes vs 40, in my case of creating a 3D model (OBJ).
It uses also much more memory
Depth map creation 3.5 GB and 20 minutes vs 1 GB and 10 minutes
Orthomosaic Reconstruction 9 minutes and 6.8 GB vs 3 minutes 30 seconds and 2.7 GB
GTX 1051 TI, 32GB
Hello iidancom,
New depth maps generation process will be optimized for the final 1.7.0 release and actually considerable performance improvement is expected in the next pre-release update.
As for the orthomosaic generation time difference, I assume that it is mainly related to the ghosting filter option used in 1.7, which was not available in the version 1.6. Have you compared the timing with the disabled ghosting filter?
-
I ve try to install pre-release on RYZEN 3900x Windows 10 but installer finish without install metashape.
What can i do ?
Hello Laurent,
Are you observing any errors during the installation? If there are any, please provide the related screenshots or specify exact error message observed.
-
I can't seem to use GPU for depth map generation. I get the following error:
Warning: Device GeForce GTX 1070 Ti ignored because it has 5958/8192 MB available, but 6870 MB required
Log up to that point is attached. I have two identical GPUs and haven't had any issues like this in the past.
Hello dcobra,
Please check, if it helps to set up the following teak to 40 value, via Advanced Preferences tab -> Tweaks dialog:
main/depth_pm_max_neighbors
-
occlusion map generation takes for ever
2020-10-27 13:45:29 BuildTexture: mapping mode = Keep uv, page count = 1, texture size = 8192, texture type = Occlusion map, source data = Model, transfer_texture = 0
2020-10-27 13:45:29 Generating textures...
2020-10-27 13:45:29 Initializing...
2020-10-27 13:46:36 Calculating ambient occlusion...
2020-10-27 15:04:31 Finished processing in 4742.23 sec (exit code 0)
2020-10-27 15:04:31 Error: Aborted by user
Hello ferengi,
How many polygons are there in the source and target models used for the occlusion map generation? Also please specify the parameters used for the mesh reconstruction for both models (if they are different) - source option, method used and interpolation.
-
I've run into the problem with the Metashape 1.7.0. Build 11340 - WIN/PRO version. On some projects it makes the Tiled model while on some it exits immediately with the message :
Assertion 23910910010 failed at line 54
Hello Darko,
Please specify, if you have "fine level task subdivision" option enabled in the Advanced Preferences tab? Additionally please provide the processing log related to the failed operation.
-
I can't seem to use GPU for depth map generation. I get the following error:
Warning: Device GeForce GTX 1070 Ti ignored because it has 5958/8192 MB available, but 6870 MB required
Log up to that point is attached. I have two identical GPUs and haven't had any issues like this in the past.
Hello dcobra,
Please check, if it helps to set up the following teak to 40 value, via Advanced Preferences tab -> Tweaks dialog:
main/depth_pm_max_neighbors
Alexey,
Thank you for the suggestion. It worked.
Best,
Cody
-
[For laser scans] Current approach is the following:
...
- run Align Photos operation as usual.
Does that mean that the poses of the laser scans will be adjusted in addition to the internal and external parameters calculated for the standard cameras?
As a user who commonly combines laser scan data with photogrammetry that is not at all what I would want to happen. The laser scan data will almost always be coming from other software where we have much more control over the alignment process. Therefore the laser scan data should be treated as fixed (no pose adjustments) and photos aligned to it.
...
Yes, it can be said that the laser scans are aligned together with the common images.
If you need to rely on the accurate scanner locations, you can input corresponding coordinates to the Reference pane for the related camera instances and adjust the accuracy value for them in order to increase the weight for them.
...
I would also like to see an option to just check a box or similar to force laser scan alignment to be preserved exactly, if it had been registered already in a 3rd party package, otherwise the function would not be useful. It seems a lot of manual work to input the coordinates of each laser setup (and presumably orientation?) to ensure they stay fixed. I take great care over my registration and wouldn't trust any algorithm to do a better job! We treat our laser data as sacred and once it is registered everything else (so many things...) is derived from it, but can not be allowed to affect it!
I haven't actually tried 1.7 yet so I might not know what I'm talking about, but it seemed like a potential issue!
-
It seems a lot of manual work to input the coordinates of each laser setup (and presumably orientation?) to ensure they stay fixed. I take great care over my registration and wouldn't trust any algorithm to do a better job! We treat our laser data as sacred and once it is registered everything else (so many things...) is derived from it, but can not be allowed to affect it!
Agreed 100%. Treating laser scans as fixed should be the default behavior. Perhaps other users have a use-case where they should be freely adjusted but I strongly suspect that is a minority position, in which case, it should require additional settings to achieve.
If setting scan locations and rotations is the way to prevent scans from moving that should happen automatically during import and their accuracy weights set high enough that they do not move at all during future alignments.
-
I ve try to install pre-release on RYZEN 3900x Windows 10 but installer finish without install metashape.
What can i do ?
Hello Laurent,
Are you observing any errors during the installation? If there are any, please provide the related screenshots or specify exact error message observed.
hello Alexey
i don't have a special error only this message...
thanks
-
Pre-release version of Agisoft Metashape 1.7.0 is available for download.
It is possible that for this new version will be incorporated into the generation of images without distortion the possibility of eliminating the effect of Rolling Shutter, or there is some way to do it with the current version, thank you very much
*GUI option (File Menu -> Export -> Undistort Photos) = does not correct Rolling shutter effect
Thanks for your support
-
I can't seem to use GPU for depth map generation. I get the following error:
Warning: Device GeForce GTX 1070 Ti ignored because it has 5958/8192 MB available, but 6870 MB required
Log up to that point is attached. I have two identical GPUs and haven't had any issues like this in the past.
Hello dcobra,
Please check, if it helps to set up the following teak to 40 value, via Advanced Preferences tab -> Tweaks dialog:
main/depth_pm_max_neighbors
Alexey,
Thank you for the suggestion. It worked.
Best,
Cody
I just finished processing a dense point cloud and the result is amazing. Much less noise than previous versions. Great work!
-
Sorry, I've forgotten to Quote it. It is all about Tiled model failure.
Hi Alexey,
Thank's for your answer.
1. Yes "Fine level task subdivision" was checked
2. The log file is attached to this message.
I've noticed that sometimes it works and sometimes not. Cannot figure out what is the trigger.
Best, Darko
I've just tried to do the Dense Cloud and Mesh.. Nothing works with the same message in that project.
-
Pre-release version of Agisoft Metashape 1.7.0 is available for download.
It is possible that for this new version will be incorporated into the generation of images without distortion the possibility of eliminating the effect of Rolling Shutter, or there is some way to do it with the current version, thank you very much
*GUI option (File Menu -> Export -> Undistort Photos) = does not correct Rolling shutter effect
Thanks for your support
Dmitry or Alexey,
Some possibility, by many means I have made this query and I do not get any response. Thanks for your reply.
-
Sorry, I've forgotten to Quote it. It is all about Tiled model failure.
Hi Alexey,
Thank's for your answer.
1. Yes "Fine level task subdivision" was checked
2. The log file is attached to this message.
I've noticed that sometimes it works and sometimes not. Cannot figure out what is the trigger.
Best, Darko
I've just tried to do the Dense Cloud and Mesh.. Nothing works with the same message in that project.
Hello Darko,
Please check if the same issue is observed in 1.7.0 pre-release update, build 11429.
-
I am coming back to depth maps generation time of 1.7 vs 1.6.
I have a set of 280 16 MPix images taken from a Drone.
In version 1.6 I got following results:
Depth Maps
Count 280
Depth maps generation parameters
Quality High
Filtering mode Aggressive
Processing time 4 hours 29 minutes oe 269 min
Memory usage 1.70 GB
Software version 1.6.5.11249
File size 1.37 GB
so average generation time per image is 269 / 280 = 0.96 min
In version 1.7, I got these results on 268 images as some were disabled:
Depth Maps
Count 268
Depth maps generation parameters
Quality High
Filtering mode Mild
Processing time 6 hours 11 minutes or 371 min
Memory usage 5.46 GB
Software version 1.7.0.11429
File size 1.44 GB
so average generation time per image is 371/ 268 = 1.38 min
So average generation time per image is 44% greater in version 1.7 compared to 1.65....
I think Agisoft should really try to optimize time performance so that 1.7 becomes feasible...
-
Hi Alexey
The 1.7.0 build 11429 still has troubles to detect all the available CUDA GPU's (1.6.5 is working just fine), as I told in my last post.
Cheers
-
Sorry, I've forgotten to Quote it. It is all about Tiled model failure.
Hi Alexey,
Thank's for your answer.
1. Yes "Fine level task subdivision" was checked
2. The log file is attached to this message.
I've noticed that sometimes it works and sometimes not. Cannot figure out what is the trigger.
Best, Darko
I've just tried to do the Dense Cloud and Mesh.. Nothing works with the same message in that project.
Hello Darko,
Please check if the same issue is observed in 1.7.0 pre-release update, build 11429.
Hello Aleksey,
Unfortunately the problem remains even in the latest version, build 11429. With the other sample I have tried to make locally first and it bailed out with the same message and later I have tried to delegate the job to the cloud and after 15 minutes it reached 51% and stopped there for couple of hours. It ended with the message "Connection Closed (RemoteHostClosedError).
So I just exited it and tried the sample I did before and started the Log. But the result was the same. The Log file is attached to this message.
Best, Darko
-
I get following error when blending textures in Build Tiled Model from Depth Maps:
Error: Cannot find suitable device
I think it is related to missing VK_EXT_shader_viewport_index_layer.
Using GPU GeForce GTX 670MX.
Same error appears when using Build Texture....
See attached log...
Update:
it seems version 1.6 has same missing extension issue for GPU GeForce GTX 670MX but it deals with it by continuing Texture Blending using CPU. See:
2020-11-06 01:47:46 Agisoft Metashape Professional Version: 1.6.5 build 11249 (64 bit)
2020-11-06 01:47:46 Platform: Windows
2020-11-06 01:47:46 CPU: Intel(R) Core(TM) i7-3630QM CPU @ 2.40GHz (laptop)
2020-11-06 01:47:46 CPU family: 6 model: 58 signature: 306A9h
2020-11-06 01:47:46 RAM: 16.0 GB
2020-11-06 01:47:48 OpenGL Vendor: NVIDIA Corporation
2020-11-06 01:47:48 OpenGL Renderer: GeForce GTX 670MX/PCIe/SSE2
2020-11-06 01:47:48 OpenGL Version: 4.6.0 NVIDIA 425.31
....
2020-11-06 01:49:32 Blending textures...
2020-11-06 01:49:34 Found 1 GPUs in 0.433 sec (CUDA: 0.396 sec, OpenCL: 0.037 sec)
2020-11-06 01:49:36 Using device: GeForce GTX 670MX, 5 compute units, free memory: 2490/3072 MB, compute capability 3.0
2020-11-06 01:49:36 driver/runtime CUDA: 10010/8000
2020-11-06 01:49:36 max work group size 1024
2020-11-06 01:49:36 max work item sizes [1024, 1024, 64]
2020-11-06 01:49:36 got device properties in 0.001 sec, free memory in 2.467 sec
2020-11-06 01:49:36 Initializing context...
2020-11-06 01:49:37 Extension VK_EXT_shader_viewport_index_layer is missing on device
2020-11-06 01:49:37 Cannot use GPU. Reason: Cannot find suitable device
2020-11-06 01:49:37 Performing blending on CPU...
....
so maybe same approach can be taken to deal with this problem in v.1.7
-
I ve try to install pre-release on RYZEN 3900x Windows 10 but installer finish without install metashape.
What can i do ?
Hello Laurent,
Are you observing any errors during the installation? If there are any, please provide the related screenshots or specify exact error message observed.
hello Alexey
i don't have a special error only this message...
thanks
hello Alexey,
i have test the new release and i have the same error
thanks for you answer
-
Alexey > could you please give us more info about connected components and their meaning ? It is difficult to try out on a feature which has no clear use case
-
[For laser scans] Current approach is the following:
...
- run Align Photos operation as usual.
Does that mean that the poses of the laser scans will be adjusted in addition to the internal and external parameters calculated for the standard cameras?
As a user who commonly combines laser scan data with photogrammetry that is not at all what I would want to happen. The laser scan data will almost always be coming from other software where we have much more control over the alignment process. Therefore the laser scan data should be treated as fixed (no pose adjustments) and photos aligned to it.
...
Yes, it can be said that the laser scans are aligned together with the common images.
If you need to rely on the accurate scanner locations, you can input corresponding coordinates to the Reference pane for the related camera instances and adjust the accuracy value for them in order to increase the weight for them.
...
I would also like to see an option to just check a box or similar to force laser scan alignment to be preserved exactly, if it had been registered already in a 3rd party package, otherwise the function would not be useful. It seems a lot of manual work to input the coordinates of each laser setup (and presumably orientation?) to ensure they stay fixed. I take great care over my registration and wouldn't trust any algorithm to do a better job! We treat our laser data as sacred and once it is registered everything else (so many things...) is derived from it, but can not be allowed to affect it!
I haven't actually tried 1.7 yet so I might not know what I'm talking about, but it seemed like a potential issue!
I would also like for the laser scan data to remain registered. I am trying it now for the past few days and making some progress.
I had to use 40 markers to align 4 laser scans and 4 360 degree panorama photos due to the spacing between the laser scans and also no transition from camera positions. However, the laser scan data came directly from FARO Scene ready to go.
The imported laser data does have reference metadata such as position, yaw, pitch, roll but when I try to use that information and align by reference, the program crashes and sends an error report. I imagine that eventually, the scan data can be positioned using the reference metadata and forced to stay in that position by placing markers and assigning xyz values but it sure would be nice to have that done by default.
Thank you for a great start!
-
I got following error generating Dense cloud:
2020-11-07 00:06:53 BuildDenseCloud: quality = High, depth filtering = Mild, PM version, point colors = 1
2020-11-07 00:06:53 Generating depth maps...
2020-11-07 00:06:53 Preparing 48 cameras info...
2020-11-07 00:06:53 Finished processing in 0.026 sec (exit code 0)
2020-11-07 00:06:53 Error: Assertion 23910910010 failed at line 54!
The data set consists of 48 Phantom3 images with rolling shutter compensation on. Optimization was done with Fit Additional parameters on...
-
I ve try to install pre-release on RYZEN 3900x Windows 10 but installer finish without install metashape.
What can i do ?
Hello Laurent,
Are you observing any errors during the installation? If there are any, please provide the related screenshots or specify exact error message observed.
hello Alexey
i don't have a special error only this message...
thanks
hi alexey,
i 've sucessefully install , i've stop real time virus protection of win 10
thanks
-
I got following error generating Dense cloud:
2020-11-07 00:06:53 BuildDenseCloud: quality = High, depth filtering = Mild, PM version, point colors = 1
2020-11-07 00:06:53 Generating depth maps...
2020-11-07 00:06:53 Preparing 48 cameras info...
2020-11-07 00:06:53 Finished processing in 0.026 sec (exit code 0)
2020-11-07 00:06:53 Error: Assertion 23910910010 failed at line 54!
The data set consists of 48 Phantom3 images with rolling shutter compensation on. Optimization was done with Fit Additional parameters on...
I Reported this as a bug some days ago: once you switch the compensation off, some tears of pain are shed due to high pixel matching errors, but still you get your point cloud. At this stage I'm wondering if this compensation is of any use as there is the option for Image-Variant Parameters. With the new pre-release version I can't even align images, but at least can see that the same rolling shutter compensation issue hasn't been completely addressed yet on projects aligned using the previous pre-release. Still, the software has included some nice settings, and is creating better models than previous official releases, I find.
Os
-
Rolling shutter compensation on. At this stage I'm wondering if this compensation is of any use as there is the option for Image-Variant Parameters.
Rolling shutter compensation; Of course it works and is of great help, and has nothing to do with Image-Variant Parameters, this version is not final yet, if you want to use rolling shutter use version 1.6.5 in the meantime.
-
I experience many Metashape crashes when aligning 527 images from DJI Phantom 4 Pro. It exits from Metashape with crash report window appearing. It seems to happen during Selecting pairs ... just after KeyPoint detection..... See attached log. Also attached is image of GPU performance monitor just after crash (indicated by red vertical line).....
I also experienced same crash trying to align a set of Mavic 2 Pro images.....
Update: got same crash with a set of 101 images from SODA camera EbeeX
-
[For laser scans] Current approach is the following:
...
- run Align Photos operation as usual.
Does that mean that the poses of the laser scans will be adjusted in addition to the internal and external parameters calculated for the standard cameras?
As a user who commonly combines laser scan data with photogrammetry that is not at all what I would want to happen. The laser scan data will almost always be coming from other software where we have much more control over the alignment process. Therefore the laser scan data should be treated as fixed (no pose adjustments) and photos aligned to it.
...
Yes, it can be said that the laser scans are aligned together with the common images.
If you need to rely on the accurate scanner locations, you can input corresponding coordinates to the Reference pane for the related camera instances and adjust the accuracy value for them in order to increase the weight for them.
...
I would also like to see an option to just check a box or similar to force laser scan alignment to be preserved exactly, if it had been registered already in a 3rd party package, otherwise the function would not be useful. It seems a lot of manual work to input the coordinates of each laser setup (and presumably orientation?) to ensure they stay fixed. I take great care over my registration and wouldn't trust any algorithm to do a better job! We treat our laser data as sacred and once it is registered everything else (so many things...) is derived from it, but can not be allowed to affect it!
I haven't actually tried 1.7 yet so I might not know what I'm talking about, but it seemed like a potential issue!
I would also like for the laser scan data to remain registered. I am trying it now for the past few days and making some progress.
I had to use 40 markers to align 4 laser scans and 4 360 degree panorama photos due to the spacing between the laser scans and also no transition from camera positions. However, the laser scan data came directly from FARO Scene ready to go.
The imported laser data does have reference metadata such as position, yaw, pitch, roll but when I try to use that information and align by reference, the program crashes and sends an error report. I imagine that eventually, the scan data can be positioned using the reference metadata and forced to stay in that position by placing markers and assigning xyz values but it sure would be nice to have that done by default.
Thank you for a great start!
Hello, I also would recommend lidar being considered registered on import as well. I’ve been currently trying to setup FARO Scene data being sent into Metashape in the past (I do not have the ability to demo 1.7 at this time with work). Often I need to generate textures/missing areas on already registered and locked lidar data so having this option would be helpful.
I am curious as to how points/normal generate is handled - is there by chance documentation outlining how these work together? I’m currently assuming the lidar is converted into a six pack camera station image of the lidar with tie points to it’s own lidar cloud data, but if there are any videos/documentation outlining this more, it would help in providing some feedback.
Also, is it possible to transfer point normals to another lidar cloud import (i.e. I have a basic setup of the lidar registered and I have a cleaned evenly dense cloud that I want to transfer/interpolate point normals from one to the other so as to mesh that cloud instead). If this doesn’t exist with the 1.7 demo, I’ll see about putting in a feature request.
Thanks!
-
Hey,
Can we also have a Total Points argument in the python implementation of SamplePoints? (if we want exact amount of points).
Edit: on some testing I also got a following faulty result (see image)
-
I experience many Metashape crashes when aligning 527 images from DJI Phantom 4 Pro. It exits from Metashape with crash report window appearing. It seems to happen during Selecting pairs ... just after KeyPoint detection..... See attached log. Also attached is image of GPU performance monitor just after crash (indicated by red vertical line).....
I also experienced same crash trying to align a set of Mavic 2 Pro images.....
Update: got same crash with a set of 101 images from SODA camera EbeeX
Hello Paul,
There was a bug related to the image matching stage, when the incremental image alignment feature is used (keep points stored in the project and new images are added), it should be fixed in the next pre-release update. But can you please specify, whether you are observing the similar issues even for newly created project with the initial image matching operation?
-
Hello Alexey,
I started from scratch, loading 101 images from SODA camera and started image alignment and got same crash after image key point detection and starting Selecting pairs .... The crash report was sent....At moment of crash both Compute_0 and 3D processes of GPU spike to 100%.
Here is log collected til crash:
2020-11-21 11:15:36 Loading photos...
2020-11-21 11:15:38 Finished processing in 2.586 sec (exit code 1)
2020-11-21 11:16:46 AlignPhotos: accuracy = High, preselection = generic, reference, keypoint limit = 50000, tiepoint limit = 10000, apply masks = 0, filter tie points = 0, adaptive fitting = 1
2020-11-21 11:16:46 Matching photos...
2020-11-21 11:16:46 Detecting points...
2020-11-21 11:16:46 Found 1 GPUs in 0.002 sec (CUDA: 0.002 sec, OpenCL: 0 sec)
2020-11-21 11:16:49 Using device: GeForce GTX 670MX, 5 compute units, free memory: 2494/3072 MB, compute capability 3.0
2020-11-21 11:16:49 driver/runtime CUDA: 10010/8000
2020-11-21 11:16:49 max work group size 1024
2020-11-21 11:16:49 max work item sizes [1024, 1024, 64]
2020-11-21 11:16:49 got device properties in 0.001 sec, free memory in 2.893 sec
2020-11-21 11:16:50 [GPU] photo 1: 50000 points
2020-11-21 11:16:52 [GPU] photo 2: 50000 points
2020-11-21 11:16:52 [CPU] photo 0: 50000 points
2020-11-21 11:16:53 [GPU] photo 3: 50000 points
2020-11-21 11:16:55 [GPU] photo 5: 50000 points
2020-11-21 11:16:56 [GPU] photo 6: 50000 points
2020-11-21 11:16:56 [CPU] photo 4: 50000 points
2020-11-21 11:16:57 [GPU] photo 7: 50000 points
2020-11-21 11:16:59 [GPU] photo 9: 50000 points
2020-11-21 11:17:00 [CPU] photo 8: 50000 points
2020-11-21 11:17:00 [GPU] photo 10: 50000 points
2020-11-21 11:17:01 [GPU] photo 12: 50000 points
2020-11-21 11:17:03 [GPU] photo 13: 50000 points
2020-11-21 11:17:04 [CPU] photo 11: 50000 points
2020-11-21 11:17:04 [GPU] photo 14: 50000 points
2020-11-21 11:17:05 [GPU] photo 16: 50000 points
2020-11-21 11:17:07 [GPU] photo 17: 50000 points
2020-11-21 11:17:07 [CPU] photo 15: 50000 points
2020-11-21 11:17:08 [GPU] photo 18: 50000 points
2020-11-21 11:17:09 [GPU] photo 20: 50000 points
2020-11-21 11:17:11 [GPU] photo 21: 50000 points
2020-11-21 11:17:11 [CPU] photo 19: 50000 points
2020-11-21 11:17:12 [GPU] photo 22: 50000 points
2020-11-21 11:17:13 [GPU] photo 24: 50000 points
2020-11-21 11:17:15 [CPU] photo 23: 50000 points
2020-11-21 11:17:15 [GPU] photo 25: 50000 points
2020-11-21 11:17:16 [GPU] photo 27: 50000 points
2020-11-21 11:17:17 [GPU] photo 28: 50000 points
2020-11-21 11:17:18 [CPU] photo 26: 50000 points
2020-11-21 11:17:19 [GPU] photo 29: 50000 points
2020-11-21 11:17:20 [GPU] photo 31: 50000 points
2020-11-21 11:17:21 [GPU] photo 32: 50000 points
2020-11-21 11:17:22 [CPU] photo 30: 50000 points
2020-11-21 11:17:23 [GPU] photo 33: 50000 points
2020-11-21 11:17:24 [GPU] photo 35: 50000 points
2020-11-21 11:17:25 [GPU] photo 36: 50000 points
2020-11-21 11:17:26 [CPU] photo 34: 50000 points
2020-11-21 11:17:27 [GPU] photo 37: 50000 points
2020-11-21 11:17:28 [GPU] photo 39: 50000 points
2020-11-21 11:17:29 [CPU] photo 38: 50000 points
2020-11-21 11:17:29 [GPU] photo 40: 50000 points
2020-11-21 11:17:31 [GPU] photo 42: 50000 points
2020-11-21 11:17:32 [GPU] photo 43: 50000 points
2020-11-21 11:17:33 [CPU] photo 41: 50000 points
2020-11-21 11:17:33 [GPU] photo 44: 50000 points
2020-11-21 11:17:35 [GPU] photo 46: 50000 points
2020-11-21 11:17:36 [GPU] photo 47: 50000 points
2020-11-21 11:17:37 [CPU] photo 45: 50000 points
2020-11-21 11:17:37 [GPU] photo 48: 50000 points
2020-11-21 11:17:39 [GPU] photo 50: 50000 points
2020-11-21 11:17:40 [GPU] photo 51: 50000 points
2020-11-21 11:17:41 [CPU] photo 49: 50000 points
2020-11-21 11:17:41 [GPU] photo 52: 50000 points
2020-11-21 11:17:43 [GPU] photo 54: 50000 points
2020-11-21 11:17:44 [GPU] photo 55: 50000 points
2020-11-21 11:17:45 [CPU] photo 53: 50000 points
2020-11-21 11:17:45 [GPU] photo 56: 50000 points
2020-11-21 11:17:47 [GPU] photo 58: 50000 points
2020-11-21 11:17:48 [CPU] photo 57: 50000 points
2020-11-21 11:17:48 [GPU] photo 59: 50000 points
2020-11-21 11:17:50 [GPU] photo 61: 50000 points
2020-11-21 11:17:51 [GPU] photo 62: 50000 points
2020-11-21 11:17:52 [GPU] photo 63: 50000 points
2020-11-21 11:17:53 [CPU] photo 60: 50000 points
2020-11-21 11:17:54 [GPU] photo 64: 50000 points
2020-11-21 11:17:55 [GPU] photo 66: 50000 points
2020-11-21 11:17:57 [GPU] photo 67: 50000 points
2020-11-21 11:17:57 [CPU] photo 65: 50000 points
2020-11-21 11:17:58 [GPU] photo 68: 50000 points
2020-11-21 11:17:59 [GPU] photo 70: 50000 points
2020-11-21 11:18:01 [CPU] photo 69: 50000 points
2020-11-21 11:18:01 [GPU] photo 71: 50000 points
2020-11-21 11:18:02 [GPU] photo 73: 50000 points
2020-11-21 11:18:03 [GPU] photo 74: 50000 points
2020-11-21 11:18:04 [CPU] photo 72: 50000 points
2020-11-21 11:18:05 [GPU] photo 75: 50000 points
2020-11-21 11:18:06 [GPU] photo 77: 50000 points
2020-11-21 11:18:08 [GPU] photo 78: 50000 points
2020-11-21 11:18:08 [CPU] photo 76: 50000 points
2020-11-21 11:18:09 [GPU] photo 79: 50000 points
2020-11-21 11:18:10 [GPU] photo 81: 50000 points
2020-11-21 11:18:12 [GPU] photo 82: 50000 points
2020-11-21 11:18:12 [CPU] photo 80: 50000 points
2020-11-21 11:18:13 [GPU] photo 83: 50000 points
2020-11-21 11:18:14 [GPU] photo 85: 50000 points
2020-11-21 11:18:16 [CPU] photo 84: 50000 points
2020-11-21 11:18:16 [GPU] photo 86: 50000 points
2020-11-21 11:18:17 [GPU] photo 88: 50000 points
2020-11-21 11:18:18 [GPU] photo 89: 50000 points
2020-11-21 11:18:19 [CPU] photo 87: 50000 points
2020-11-21 11:18:20 [GPU] photo 90: 50000 points
2020-11-21 11:18:21 [GPU] photo 92: 50000 points
2020-11-21 11:18:23 [GPU] photo 93: 50000 points
2020-11-21 11:18:23 [CPU] photo 91: 50000 points
2020-11-21 11:18:24 [GPU] photo 94: 50000 points
2020-11-21 11:18:25 [GPU] photo 96: 50000 points
2020-11-21 11:18:27 [GPU] photo 97: 50000 points
2020-11-21 11:18:27 [CPU] photo 95: 50000 points
2020-11-21 11:18:28 [GPU] photo 98: 50000 points
2020-11-21 11:18:30 [GPU] photo 100: 50000 points
2020-11-21 11:18:31 [CPU] photo 99: 50000 points
2020-11-21 11:18:31 points detected in 105.068 sec
2020-11-21 11:18:31 Selecting pairs...
2020-11-21 11:18:31 Found 1 GPUs in 0.001 sec (CUDA: 0.001 sec, OpenCL: 0 sec)
2020-11-21 11:18:31 Using device: GeForce GTX 670MX, 5 compute units, free memory: 2503/3072 MB, compute capability 3.0
2020-11-21 11:18:31 driver/runtime CUDA: 10010/8000
2020-11-21 11:18:31 max work group size 1024
2020-11-21 11:18:31 max work item sizes [1024, 1024, 64]
Note hat Keep keypoints option was not checked.....
-
Hello Paul,
Thank you for additional information.
I think you should be able to avoid these crashed in the current pre-release by disabling CPU utilization in the GPU Preferences tab. But the proper fix will be implemented in the next 1.7.0 update.
-
Thanks Alexey,
I was able to do alignment on this 101 image data set disabling the Use CPU in the GPU preferences. However Alignment Time is much greater compared to 1.6.5. See attached file.
Note that Image matching increases dramatically from 16 min to 55 min while Image alignment time reduces a little bit from 5 min to under 4 min.
I do hope image matching time will be better optimized in future release!
-
Hello Paul,
I have used the banchmarking dataset in the versions 1.6.5 and 1.7.0 and got comparable timing for image matching:
https://www.dropbox.com/s/hh5yg0fmpr4bpn3/benchmarking_1.3.zip?dl=0
The same processing settings have been used (similar to your test) and also fine level task subdivison has been disabled (the processing performed in Untitled - unsaved project).
Do you see in the logs that GPU is used in both runs properly, without any fallbacks?
-
Hi Alexey,
I think that the difference is due that for lower mid level cards as Geforce GTX 670MX using CPU in GPU processes does affect greatly performance. In previous test for 1.6.5. the Use CPU was checked in GPU options. I redid test without checking Use CPU and get following results:
Alignment parameters
Accuracy High
Generic preselection Yes
Reference preselection Source
Key point limit 50,000
Tie point limit 10,000
Guided image matching No
Adaptive camera model fitting Yes
Matching time 58 minutes 37 seconds
Matching memory usage 185.48 MB
Alignment time 3 minutes 53 seconds
Alignment memory usage 66.07 MB
Software version 1.6.5.11249
The 58 min of matching time is comparable to the 55 min obtained in version 1.7.
So it is hoped that with next release, Using CPU in GPU processes will also considerably reduce Matching time.....
-
I have used the banchmarking dataset in the versions 1.6.5 and 1.7.0 and got comparable timing for image matching
Is it possible to install 1.6.5 and 1.7.0 preview on the same machine for testing/benchmarking? I haven't tried since before licensing methods changed, and it involved copying the install dir to a new location before installing the next/test version...
Andy
-
Hello Andy,
Yes, you can have both versions installed on the same machine. On Windows OS you should install version 1.6.5 first, then copy/move installation directory to some custom location, where it will be run from, and then install version 1.7.0 by the default path.
If version 1.6.5 has been activated, then with the installation directory you will also copy the .lic file and would not require to perform any additional actions - both versions will work under the same license.
-
Hello Alexey!
Have been able to download the photos from dropbox (had a ticket 6.11. 147228) to verify a depth maps problem with 1.7 I didn't have with 1.6x? (Medium quality if fine, both higher ones lead to holes in the model).
Thank you! :D
-
Have been able to download the photos from dropbox (had a ticket 6.11. 147228) to verify a depth maps problem with 1.7 I didn't have with 1.6x? (Medium quality if fine, both higher ones lead to holes in the model).
Hello mcstieg,
Pre-release has been just updated, hopefully you will no longer observe those holes in the mesh. At least I haven't observed any problems when re-processing your project in the recent pre-release version.
-
What's changed in the latest pre-release build 11539? The change log does not look to have been updated.
Also, What are "connected components"?
There is a new "Components" level on the Workspace tree structure but there are no right click commands or other functions that seem to relate to "component" objects. What is that all about?
-
In latest release, I still get error in Blending Textures part of Build Textures....
2020-12-01 13:55:15 Blending textures...
2020-12-01 13:55:15 Found 1 GPUs in 0.002 sec (CUDA: 0.001 sec, OpenCL: 0.001 sec)
2020-12-01 13:55:15 Using device: GeForce GTX 670MX, 5 compute units, free memory: 2474/3072 MB, compute capability 3.0
2020-12-01 13:55:15 driver/runtime CUDA: 10010/8000
2020-12-01 13:55:15 max work group size 1024
2020-12-01 13:55:15 max work item sizes [1024, 1024, 64]
2020-12-01 13:55:15 All cameras are fine
2020-12-01 13:55:15 Initializing context...
2020-12-01 13:55:16 Extension VK_EXT_shader_viewport_index_layer is missing on device
2020-12-01 13:55:16 Finished processing in 2318.81 sec (exit code 0)
2020-12-01 13:55:16 Error: Cannot find suitable device
Note that in version 1.6, this problem with older GPUs is avoided by continuing processing with CPU...
-
I no longer experience crashes when aligning 20 MP images... Good work!
Attached file compares version 1.6.5 and 1.7 alignment of a set of 188 Phantom4pro images on following system
OS Windows 64 bit
RAM 15.95 GB
CPU Intel(R) Core(TM) i7-3630QM CPU @ 2.40GHz
GPU(s) GeForce GTX 670MX
with Use CPU when performing GPU accelerated processing checked in GPU preferences in both cases.
Alignment time for v1.7 is 34 min 12 sec while for v1.6 it is 35 min 46 sec....
-
Cuda enabled GPU's are not recognized yet in the MacOS version, under MacOS High Sierra (1 december beta). Version 1.6.5 recognize them without any problem. Seems to be a regression from version 1.6.5 here.
Best Regards
-
Cuda enabled GPU's are not recognized yet in the MacOS version, under MacOS High Sierra (1 december beta). Version 1.6.5 recognize them without any problem. Seems to be a regression from version 1.6.5 here.
Hello Renato,
We are working on the issue with NVIDIA cards recognition on older macOS version.
-
Have been able to download the photos from dropbox (had a ticket 6.11. 147228) to verify a depth maps problem with 1.7 I didn't have with 1.6x? (Medium quality if fine, both higher ones lead to holes in the model).
Hello mcstieg,
Pre-release has been just updated, hopefully you will no longer observe those holes in the mesh. At least I haven't observed any problems when re-processing your project in the recent pre-release version.
Hello Alexey,
just sent you an E-Mail this morning. Unfortunately, the holes are still there with the new release - with and without gradual selection and optimization. Medium works. High and ultra look terrible.
Thank you for your work! Hopefully this can be found and fixed. :)
-
Hello mcstieg,
Thank you for the project and the images, we will re-process it on different hardware configurations, as the issue could be related to particular hardware or driver issue.
-
Driver update did the job! It works. :D
-
FYI your 1.7 Python API doc still says "Python 3.5" on page 3 even though the 1.7 changelog states: "• Updated Python to version 3.8." (thank goodness ;-).
-
1.7.0 11539
I built a mesh on a project with 371 photos and only had 10 depth maps produced. I then tried a smaller project with only 10 photos and ended up with only 1 depth map.
I reran the 10 photo project using 1.6.5 just to be sure, and have 10 good depth maps. I tried 1.7.0 on medium and on high with the same result - 1 depth map.
My computer
macOS 11.0.1
iMac (Retina 5K, 27-inch, 2017)
4.2 GHz Quad-Core Intel Core i7
64 GB 2400 MHz DDR4
Radeon Pro 580 8 GB
Tom
-
version 1.7.0 build 11539.
got some inaccurate results in depthmaps generation. not sure if results from to less image overlap or something else.
Input: 57x 16bit tif files from 61mp raws. 24mm g-master lens.
-
1.7.0 11539
I built a mesh on a project with 371 photos and only had 10 depth maps produced. I then tried a smaller project with only 10 photos and ended up with only 1 depth map.
I reran the 10 photo project using 1.6.5 just to be sure, and have 10 good depth maps. I tried 1.7.0 on medium and on high with the same result - 1 depth map.
Hello Tom,
Can you please send one of these projects (371 or 10 photos) with the alignment only (in PSZ format) to support@agisoft.com?
-
version 1.7.0 build 11539.
got some inaccurate results in depthmaps generation. not sure if results from to less image overlap or something else.
Input: 57x 16bit tif files from 61mp raws. 24mm g-master lens.
Hello Exorbitart,
Is it possible to share the complete image set and related project with alignment results to support@agisoft.com?
Also have you checked if 1.6.5 results are better? Probably the surface itself has some reflections which affect the reconstruction results.
-
I am creating a Footprint Polygon for selected cameras using following script https://github.com/agisoft-llc/metashape-scripts/blob/master/src/footprints_to_shapes.py
The polygon shows correctly in Model view but it is not closed in Ortho view (missing last segment) see attached screen view
Update: after saving project and reopening, same footprint now appears with just 3 segments. See attached 2nd screen. It seems the script should add an extra corner to footprint vector list equal to first so as to work correctly with latest release...
New update: doing following changes to above mentioned script fixes the problem:
def process_camera(chunk, camera):
if camera.type != Metashape.Camera.Type.Regular or not camera.transform or not camera.selected:
return # skipping NA cameras and non selected
sensor = camera.sensor
corners = list()
for (x, y) in [[0, 0], [sensor.width - 1, 0], [sensor.width - 1, sensor.height - 1], [0, sensor.height - 1]]:
ray_origin = camera.unproject(Metashape.Vector([x, y, 0]))
ray_target = camera.unproject(Metashape.Vector([x, y, 1]))
corners.append(surface.pickPoint(ray_origin, ray_target))
if not corners[-1]:
corners[-1] = chunk.point_cloud.pickPoint(ray_origin, ray_target)
if not corners[-1]:
break
corners[-1] = chunk.crs.project(T.mulp(corners[-1]))
corners.append(corners[0]) # add 5th corner equal to first
if not all(corners):
print("Skipping camera " + camera.label)
return
if len(corners) == 5: # changed 4 to 5
shape = chunk.shapes.addShape()
shape.label = camera.label
shape.attributes["Photo"] = camera.label
shape.type = Metashape.Shape.Type.Polygon
shape.group = footprints
shape.vertices = corners
shape.has_z = True
with concurrent.futures.ThreadPoolExecutor(multiprocessing.cpu_count()) as executor:
executor.map(lambda camera: process_camera(chunk, camera), chunk.cameras)
see 3rd attachment
-
Hello Paul,
This seems to be due to the latest changes in internal shape representation in build 11539. Thank you for pushing the script update.
-
Any projected release date for version 1.7?
-
Hello danderson4,
I think it will be very end of December (or maybe early January). Usually major release updates are published on December 31st.
-
Hello Alexey,
Support of the new depth maps generation for the cameras with the rolling shutter compensation not available yet (build 11539), I hope it is ready before the final version, and support to correct rolling shutter in images without distortion.
Best regards,
Diego
-
version 1.7.0 build 11539.
got some inaccurate results in depthmaps generation. not sure if results from to less image overlap or something else.
Input: 57x 16bit tif files from 61mp raws. 24mm g-master lens.
Hello Exorbitart,
Is it possible to share the complete image set and related project with alignment results to support@agisoft.com?
Also have you checked if 1.6.5 results are better? Probably the surface itself has some reflections which affect the reconstruction results.
Hello Alexey,
I send you some example phtos, the report and the resulting maps that represent the output model. The full project is to big to send (66GB).
Hope you can see anything that help to clarify the issues.
thanks,Benjamin
-
Hello Diego,
New depth maps should work with the rolling-shutter cameras in the latest 1.7.0 pre-release (11539), which errors are you observing?
-
In latest release. I get crashes when using Detect Powerlines. Data set: 140 eBee 16Mpix images.
First crash on aligned set with 1.4.3 version and min_altitude 5 m;
Second crash after doing new alignment with 1.7 and min_altitude 5 m;
Third crash with min altitude set to 1m.
In each case report was sent to support...
In previous pre release I did successfully use Detect Power lines see attached ....
Update: new trial using new generated DEM as basis for altitude. It seems the original DEM had some issue causing crashes.
Now Detect Powerlines terminates without error using min_altitude of 5 m. see 2nd attachment...
Sorry for any inconvenience caused....
-
Hello Alexey,
Well, it doesn't work at all well, my proof is as follows:
A very small delimited zone with version 1.6.5 in just 15 seconds processes the dense cloud in lowest quality, what is expected for a small zone and low resolution.
2020-12-08 11:31:15 checking for missing images... done in 0.009 sec
2020-12-08 11:31:15 Finished processing in 0.009 sec (exit code 1)
2020-12-08 11:31:15 BuildDenseCloud: quality = Lowest, depth filtering = Mild, point colors = 1
2020-12-08 11:31:15 Generating depth maps...
...........
...........
2020-12-08 11:31:30 422779 points extracted in 0.837 sec
2020-12-08 11:31:30 saved dense cloud in 0.053 sec
2020-12-08 11:31:30 loaded dense cloud data in 0 sec
2020-12-08 11:31:30 dense clouds joined in 0.025 sec
2020-12-08 11:31:30 loaded camera partition in 0.001 sec
2020-12-08 11:31:30 Finished processing in 15.475 sec (exit code 1) (Only 15.475 sec)
But in the version 1.7 build 11539 is broken, after 35 minutes says that still needs more than 3 hours to finish and does not advance, something that in the previous version took only 15 seconds, clearly does not work, the new version, has interesting changes but things that already worked well in previous versions were broken in this new version.
I hope all this can be fixed before releasing a new version
Best regards,
Diego
-
Hello Diego,
Do you use GPU for the processing, which model and which driver version? And can you provide the log from 1.7.0 related to the beginning of the processing operation which includes the actual depth maps generation (if it ever starts).
-
Thanks Alexi!
Cannot wait for the new release
Dave
-
Hello Paul,
Was the DEM generated in Metashape or imported from external source?
-
Hello Alexey,
the original DEM was generated in Metashape but it had some issue with CRS (compound CS WGS84/UTM 14 with Vert_datum CGVD 2013) as in Ortho display I could see the DEM but the corresponding underlying satellite imagery would not display. So I regenerated new DEM using ITRF08/UTM14 + ggm2010 height and now everything is OK for Detecting powerlines and display in Ortho View....
-
Do you use GPU for the processing, which model and which driver version? And can you provide the log from 1.7.0 related to the beginning of the processing operation which includes the actual depth maps generation (if it ever starts).
Hello Alexey,
Driver GPU Nvidia 417.22, version 1.7 finished in more than 3 hours versus 15 seconds of version 1.6.5
2020-12-08 11:35:47 checking for missing images... done in 0.009 sec
2020-12-08 11:35:47 Finished processing in 0.009 sec (exit code 1)
2020-12-08 11:35:47 BuildDenseCloud: quality = Lowest, depth filtering = Mild, PM version, point colors = 1
2020-12-08 11:35:48 Generating depth maps...
......
......
2020-12-08 14:47:12 452130 points extracted in 0.763 sec
2020-12-08 14:47:12 saved dense cloud in 0.054 sec
2020-12-08 14:47:12 loaded regions in 0 sec
2020-12-08 14:47:12 loaded dense cloud data in 0 sec
2020-12-08 14:47:12 joining 1 dense point clouds
2020-12-08 14:47:12 dense clouds joined in 0.04 sec
2020-12-08 14:47:12 loaded camera partition in 0.001 sec
2020-12-08 14:47:12 loaded regions in 0 sec
2020-12-08 14:47:12 Finished processing in 11484.6 sec (exit code 1)
Attached log file full,
Best regards,
Diego
-
Hello Diego,
Thank you for sharing the log. It seems that the depth maps pre-processing step related to internal correcting of the images is taking long time on your system.
In the next pre-release update this stage will be ported to GPU (providing that at least one GPU device is selected) and it should work significantly faster.
-
Hello Alexey,
Something that also seems to happen is that in reality v1.7 does not take the region into account when selecting the cameras, in version 1.6.5 it selects 15 cameras from the region but in version 1.7 it selects 579 cameras, that is to say all , although in the end the dense point cloud is only from the region, it is that going from 15 seconds to 3 hours is crazy, even so without using the GPU, although the GPU is activated
Best regards,
Diego
-
Diego,
As I noted in my first post in this thread it looks like the bounding box volume no longer affects the depth maps generation. for example the full frame is always used to generated the depth map even if only a small part of the image is present/needed in the bounding box & all cameras are used. This will obviously drastically affect compute time depending on the project but on the flip side the depth maps quality should be more precise & detailed. At least that's what I noticed.
Mak
-
Mak,
I understand that using the entire depth image, but using 579 cameras where the maximum region needs 15 is ridiculous, that's why I say that going from 15 seconds in version 1.6.5 to more than 3 hours in version 1.7 has no justification, something is already wrong in the code.
Best regards,
Diego
-
Hello
I got this error, latest build, JPG images only (no openxr):
2020-12-11 17:39:59 BuildModel: quality = Ultra high, depth filtering = Mild, PM version, reuse depth maps, source data = Depth maps, surface type = Arbitrary, face count = 90000000, volumetric masking = 0, OOC version, interpolation = Enabled, vertex colors = 1
2020-12-11 17:39:59 Generating mesh...
2020-12-11 17:39:59 Compression level: 1
2020-12-11 17:39:59 Preparing depth maps...
2020-12-11 17:39:59 3678 depth maps
...
2020-12-13 01:04:19 Devices performance:
2020-12-13 01:04:19 - 56% done by [GPU 1] with timings: 1801 s = 0% load hists + 47% load cams + 3% calcs
2020-12-13 01:04:19 - 42% done by [GPU 2] with timings: 1801 s = 0% load hists + 48% load cams + 2% calcs
2020-12-13 01:04:19 - 2% done by [GPU 3] with timings: 1801 s = 0% load hists + 60% load cams + 0% calcs
2020-12-13 01:04:26 finished group #19/189: 2946 cameras, 1826.85 s working (0% files opening + 59% IO + 41% unpacking + 0% queueing)
2020-12-13 01:04:27 Initing hists in leaves group #20/189: [512; 549)...
2020-12-13 01:04:38 total cubes: 108923782 cubes, 1662.05 MB, 144.828 MB/s
2020-12-13 01:04:38 Data: 2493.07 MB hists, 640.062 MB pyramid
2020-12-13 01:04:38 Found 3 GPUs in 0.001 sec (CUDA: 0 sec, OpenCL: 0.001 sec)
2020-12-13 01:04:39 [GPU 1] Using device: GeForce RTX 2060 SUPER, 34 compute units, free memory: 7174/8192 MB, compute capability 7.5
2020-12-13 01:04:39 driver/runtime CUDA: 11010/8000
2020-12-13 01:04:39 max work group size 1024
2020-12-13 01:04:39 max work item sizes [1024, 1024, 64]
2020-12-13 01:04:39 [GPU 2] Using device: GeForce RTX 2060 SUPER, 34 compute units, free memory: 7108/8192 MB, compute capability 7.5
2020-12-13 01:04:39 driver/runtime CUDA: 11010/8000
2020-12-13 01:04:39 max work group size 1024
2020-12-13 01:04:39 max work item sizes [1024, 1024, 64]
2020-12-13 01:04:39 [GPU 3] Using device: GeForce RTX 2080 SUPER, 48 compute units, free memory: 6852/8192 MB, compute capability 7.5
2020-12-13 01:04:39 driver/runtime CUDA: 11010/8000
2020-12-13 01:04:39 max work group size 1024
2020-12-13 01:04:39 max work item sizes [1024, 1024, 64]
2020-12-13 01:08:01 openexr error: Error reading pixel data from image file "openexr". Data decompression (zlib) failed.
2020-12-13 01:08:14 [GPU 1] Exception
2020-12-13 01:08:14 [GPU 3] Exception
2020-12-13 01:08:14 [GPU 2] Exception
2020-12-13 01:08:14 Peak memory used: 70.67 GB at 2020-12-11 18:49:49
2020-12-13 01:08:14 deleting all temporary files...
2020-12-13 01:09:03 done in 49.356 s
2020-12-13 01:09:03 Finished processing in 113343 sec (exit code 0)
2020-12-13 01:09:03 Error: Can't decompress depth
-
Hello eltama,
Which 1.7.0 build number you are using, the OS version and what is the NVIDIA driver installed?
-
Hello Alexey
Metashape version: 11539, Os Win 10 Pro: build 19042.685, version 20H2, Nvidia driver: Game studio 457.51.
Now I build mesh again with the same confiration but with Nvidia driver: studio driver 457.30
-
Alexey
The quality of dense point cloud that is generated in v1.7 and the filter by confidence tool is a major step forward for the underwater models that I work on. Top marks.
I have run into a bit of a dead end with a variation of the workflow I am using. I initially generated the DPC with no colour but calculating point confidence. I then filtered by confidence to get rid of the noise. Finally, I coloured the PDC.
All is good except that I wanted to display the dense point cloud confidence with a view to getting rid of more noise but the point confidence appears to have been removed by colouring the dense point cloud. I have not been able to find a menu option to re-calculate point confidence.
Build 1.7.11539 standard edition on windows 10.
-
Hi,
I wanted to test that new laser scans meshing function, but it does not work for me. I've sucesfully imported and aligned the scans, but when I try to make a mesh from them, I just get error "Not enough cameras". The scene is 54 laser scans made with Leica RTC360, scans were registered in Cyclone Register 360 and exported as E57. There are no photos, just the scans (which is probably the main problem). Am I doing something wrong, or is in current version not possible to mesh laser scans alone, without any photos?
Thanks.
-
I wanted to test that new laser scans meshing function, but it does not work for me. I've sucesfully imported and aligned the scans, but when I try to make a mesh from them, I just get error "Not enough cameras". The scene is 54 laser scans made with Leica RTC360, scans were registered in Cyclone Register 360 and exported as E57. There are no photos, just the scans (which is probably the main problem). Am I doing something wrong, or is in current version not possible to mesh laser scans alone, without any photos?
Hello LipcaCZ,
The possibility of using only laser scans for the surface (dense cloud, mesh) generation will be included in the next pre-release update.
-
The quality of dense point cloud that is generated in v1.7 and the filter by confidence tool is a major step forward for the underwater models that I work on. Top marks.
I have run into a bit of a dead end with a variation of the workflow I am using. I initially generated the DPC with no colour but calculating point confidence. I then filtered by confidence to get rid of the noise. Finally, I coloured the PDC.
All is good except that I wanted to display the dense point cloud confidence with a view to getting rid of more noise but the point confidence appears to have been removed by colouring the dense point cloud. I have not been able to find a menu option to re-calculate point confidence.
Build 1.7.11539 standard edition on windows 10.
Hello BjFaeTorphins,
Thank you for reporting, we will try to fix it in the next pre-release update as well.
Upd: Unfortunately, the fix has not been included to 11637 build, but is ready for the next update.
-
Metashape version: 11539, Os Win 10 Pro: build 19042.685, version 20H2, Nvidia driver: Game studio 457.51.
Now I build mesh again with the same confiration but with Nvidia driver: studio driver 457.30
Hello eltama,
The corruption of the depth map in the project could be related to the memory issues. I can remember only a few somewhat similar reports (with "Null Image" error message), that may indicate on the system stability issues rather than on the program bugs.
If the problem is reproducible, I can suggest to run multi-threaded Memtest86 for some long time.
-
Hello Alexey
Thank you for the tip, (I try Memtest86 with this clock frequencies and with a lower one) but now I can fix the problem with studio driver 457.30, I had to stop my simulation with BuildModel: quality = Ultra high, it will take more than 30 days probably due 61MB x 3678 cameras, but with a BuildModel: quality = high is fine and done with only 3 days, congratualtion, much better detail then 1.65, still some "onion" layers over surfaces, in my simulation, I accidentally mix 25mm set with 24mm images, some of them are made with focus stacking tecnique, I do same simulation with 1.65 and post comparison.
Thanks
-
Hello Diego,
Thank you for sharing the log. It seems that the depth maps pre-processing step related to internal correcting of the images is taking long time on your system.
In the next pre-release update this stage will be ported to GPU (providing that at least one GPU device is selected) and it should work significantly faster.
Hello Alexey,
Thank you very much, excellent work, now it works very well in the latest build 11637. For when the possibility apply the rolling shutter corrections for undistorted images export?
Best regards,
Diego
-
With latest pre release, I tried regenerating depth maps for 8 spherical 50 Mpixel images with High quality and Mild filtering....on following system
OS Windows 64 bit
RAM 15.95 GB
CPU Intel(R) Core(TM) i7-3630QM CPU @ 2.40GHz
GPU(s) GeForce GTX 670MX
The processing time is a huge 1 hour 27 min compared to less than 10 min for version 1.6.2
Depth Maps Generation on 8 spherical images (50 Mpix) using CPU in GPU processing
1.6.2.10247 1.7.0.11637
Depth Maps Parameters
Quality High High
Filtering mode Mild Mild
Processing time 9 minutes 56 seconds 1 hour 27 minutes
Memory usage 1.76 GB 2.72 GB
File size 85.01 MB 109.86 MB
Attached is processing log....
clearly such long processing times are not feasible on such system..
Update: I regenerated the depth maps but this time unchecking Use CPU in GPU processing and it finished in 31 min 55 sec but still considerably higher than 1.6.2... Funny because in previous versions, I found that all GPU processing runs faster with use CPU checked for this relatively low performance GPU type (GTX 670MX).
-
1.7.0 11539
I built a mesh on a project with 371 photos and only had 10 depth maps produced. I then tried a smaller project with only 10 photos and ended up with only 1 depth map.
I reran the 10 photo project using 1.6.5 just to be sure, and have 10 good depth maps. I tried 1.7.0 on medium and on high with the same result - 1 depth map.
My computer
macOS 11.0.1
iMac (Retina 5K, 27-inch, 2017)
4.2 GHz Quad-Core Intel Core i7
64 GB 2400 MHz DDR4
Radeon Pro 580 8 GB
Hello Tom,
Please check build 11637 (published yesterday), hopefully it will fix the reported problem.
-
Cuda enabled GPU's are not recognized yet in the MacOS version, under MacOS High Sierra (1 december beta). Version 1.6.5 recognize them without any problem. Seems to be a regression from version 1.6.5 here.
Hello Renato,
We are working on the issue with NVIDIA cards recognition on older macOS version.
Hi Alexey
All the GPU's are now perfectly recognized again (latest beta from 17th December). Nice work!
Best Regards
-
Hello Renato,
These are very good news! Thank you for posting.
-
Hello Alexey,
I ran a couple of tests on smaller projects and the results are very good with build 11637. The resulting mesh is superior to any I have seen in previous versions.
It is interesting that the depth maps look very different than previous versions but when I choose Export depth, the exported images look basically identical. Not sure what that means, just curious.
I am running a much more complex project now will report any issues, but I am not expecting any.
Excellent progress!
Tom
-
I notice that now in latest pre release, all shapes appear with same color ( HTML #c0c0c0 which seems to be color of 1st shape group) regardless of their original color. Also dashed black line symbol for outer boundary no longer appears...
Please see attached...
-
Hello Renato,
These are very good news! Thank you for posting.
Hey Alexey, can you explain what Generate Defocus Masks is?
-
Dear Agisoft team,
I tried o run some laserscanning data saved as E57 format but every time i import the data the sw keep says "Error: Empty file list", dose any have an idea about that error?
Thanks
-
Hello all.
Ive noticed that in latest pre release, Model View now has 3 more buttons : DEM, OrthoMosaic and Show BaseMap. So that in model view you can now display a Base Map (Satellite or Open Street Map) as a backdrop to your mdel.
See attached screen copy..
However if you try to use first 2 buttons (DEM or OrthoMosaic) then application crashes...
-
Ive noticed that in latest pre release, Model View now has 3 more buttons : DEM, OrthoMosaic and Show BaseMap. So that in model view you can now display a Base Map (Satellite or Open Street Map) as a backdrop to your mdel.
See attached screen copy..
However if you try to use first 2 buttons (DEM or OrthoMosaic) then application crashes...
Hello Paul,
Does it happen for any project? In which coordinate system DEM and orthomosaic are referenced in the crashed projects?
-
I tried o run some laserscanning data saved as E57 format but every time i import the data the sw keep says "Error: Empty file list", dose any have an idea about that error?
Hello Mohammed,
It seems that you are trying to load point cloud instead of individual laser scans (with depth data) via Import Laser Scans command.
-
I tried o run some laserscanning data saved as E57 format but every time i import the data the sw keep says "Error: Empty file list", dose any have an idea about that error?
Hello Mohammed,
It seems that you are trying to load point cloud instead of individual laser scans (with depth data) via Import Laser Scans command.
Dear Alexey,
I used the commend File---Import---Import LaserScanner and the sw keep gives me the error!
Do you want me to send you the E57 file?
Best
Mohamed
-
Hello Mohamed,
Import Laser Scans command assumes that you are loading individual scans - per scanner location, which contain the depth data, intensity and, optionally, spherical panorama.
You can send the E57 to support@agisoft.com, but according to the message it seems that the input data is not in the required format and is merged point cloud instead.
-
Hello Mohamed,
Import Laser Scans command assumes that you are loading individual scans - per scanner location, which contain the depth data, intensity and, optionally, spherical panorama.
You can send the E57 to support@agisoft.com, but according to the message it seems that the input data is not in the required format and is merged point cloud instead.
Thanks Alexey i already send it.
-
Hi Alexey,
the crash (which actually is the sw just exiting without any Crash message) seems to happen just with projects referenced in following CRS: WGS 84 / UTM zone 14N + GGM2010 height. or any Compound CRS using GGM2010 geoid...
I tried using DEM or OrthoMosaic button in Model view in other projects with different CRS`s without any problem.
Update: got same crash or impeteous exit from sw using following CRS : COMPD_CS["NZGD2000 / New Zealand Transverse Mercator 2000 + NZVD2016 height"....
-
Hello Mohamed,
Import Laser Scans command assumes that you are loading individual scans - per scanner location, which contain the depth data, intensity and, optionally, spherical panorama.
You can send the E57 to support@agisoft.com, but according to the message it seems that the input data is not in the required format and is merged point cloud instead.
Thanks Alexey i already send it.
Hello Mohammed,
Import Laser Scans feature supports only structured point clouds (currently in PTX and E57 formats). In the provided files this information has been discarded (probably, during the conversion from the raw scans to E57) and the point clouds became "not structured".
Probably, you should adjust the scans pre-processing pipeline in order to keep the structured scan information.
-
the crash (which actually is the sw just exiting without any Crash message) seems to happen just with projects referenced in following CRS: WGS 84 / UTM zone 14N + GGM2010 height. or any Compound CRS using GGM2010 geoid...
I tried using DEM or OrthoMosaic button in Model view in other projects with different CRS`s without any problem.
Update: got same crash or impeteous exit from sw using following CRS : COMPD_CS["NZGD2000 / New Zealand Transverse Mercator 2000 + NZVD2016 height"....
Hello Paul,
If you can also send the crash report after similar 1.7.0 crash, it would be helpful.
Upd. I think I have found one report from you, related to this problem.
-
Yes, Alexey,
the crash report appeared only the first time this issue occurred then I just get exit from Mertashape without crash report...
-
Hello Alexey!
Is it possible to add the dropbox API zu metashape so we are able to read/write files to dropbox?
Thank you and best wishes for 2021! ;D
-
Dear support,
with latest release, I get following error when trying to generate depth maps on small subset of 21 aligned images:
Error: Assertion 239120391022012 failed at line 2012!
Here is log of operation:
2020-12-28 18:42:57 Agisoft Metashape Professional Version: 1.7.0 build 11701 (64 bit)
2020-12-28 18:42:57 Platform: Windows
2020-12-28 18:42:57 CPU: Intel(R) Core(TM) i7-3630QM CPU @ 2.40GHz (laptop)
2020-12-28 18:42:57 CPU family: 6 model: 58 signature: 306A9h
2020-12-28 18:42:57 RAM: 16.0 GB
2020-12-28 18:42:59 OpenGL Vendor: NVIDIA Corporation
2020-12-28 18:42:59 OpenGL Renderer: GeForce GTX 670MX/PCIe/SSE2
2020-12-28 18:42:59 OpenGL Version: 4.6.0 NVIDIA 425.31
2020-12-28 18:42:59 Maximum Texture Size: 16384
2020-12-28 18:42:59 Quad Buffered Stereo: not enabled
2020-12-28 18:42:59 ARB_vertex_buffer_object: supported
2020-12-28 18:42:59 ARB_texture_non_power_of_two: supported
2020-12-28 18:43:02 LoadProject: path = C:/Users/paul.pelletier/Documents/Cienaga_180926/cienega21FOTOS.psx
2020-12-28 18:43:03 Loading project...
2020-12-28 18:43:03 loaded project in 0.075 sec
2020-12-28 18:43:03 Finished processing in 0.076 sec (exit code 1)
2020-12-28 18:43:31 BuildDenseCloud: quality = High, depth filtering = Mild, PM version, point colors = 1
2020-12-28 18:43:31 Generating depth maps...
2020-12-28 18:43:31 Preparing 21 cameras info...
2020-12-28 18:43:31 cameras data loaded in 0.045 s
2020-12-28 18:43:31 cameras graph built in 0.001 s
2020-12-28 18:43:31 filtering neighbors with too low common points, threshold=50...
2020-12-28 18:43:31 Camera 654 has no neighbors
2020-12-28 18:43:31 Camera 723 has no neighbors
2020-12-28 18:43:31 Camera 651 has no neighbors
2020-12-28 18:43:31 avg neighbors before filtering: 14.7619 (49% filtered out)
2020-12-28 18:43:31 limiting neighbors to 40 best...
2020-12-28 18:43:31 avg neighbors before limiting: 7.47619 (0% limited out)
2020-12-28 18:43:31 neighbors number min/1%/10%/median/90%/99%/max: 0, 0, 0, median=9, 11, 12, 12
2020-12-28 18:43:31 cameras info prepared in 0.048 s
2020-12-28 18:43:31 saved cameras info in 0.018
2020-12-28 18:43:31 Partitioning 21 cameras...
2020-12-28 18:43:31 number of mini clusters: 2
2020-12-28 18:43:31 1 groups: avg_ref=21 avg_neighb=0 total_io=100%
2020-12-28 18:43:31 max_ref=21 max_neighb=0 max_total=21
2020-12-28 18:43:31 cameras partitioned in 0 s
2020-12-28 18:43:31 saved depth map partition in 0.017 sec
2020-12-28 18:43:31 loaded cameras info in 0.004
2020-12-28 18:43:31 loaded depth map partition in 0 sec
2020-12-28 18:43:31 already partitioned (21<=50 ref cameras, 0<=200 neighb cameras)
2020-12-28 18:43:31 group 1/1: preparing 21 cameras images...
2020-12-28 18:43:31 point cloud loaded in 0.001 s
2020-12-28 18:43:31 Found 1 GPUs in 0.499 sec (CUDA: 0.46 sec, OpenCL: 0.039 sec)
2020-12-28 18:43:32 Using device: GeForce GTX 670MX, 5 compute units, free memory: 2493/3072 MB, compute capability 3.0
2020-12-28 18:43:32 driver/runtime CUDA: 10010/8000
2020-12-28 18:43:32 max work group size 1024
2020-12-28 18:43:32 max work item sizes [1024, 1024, 64]
2020-12-28 18:43:53 group 1/1: cameras images prepared in 21.876 s
2020-12-28 18:43:53 Finished processing in 22.365 sec (exit code 0)
2020-12-28 18:43:53 Error: Assertion 239120391022012 failed at line 2012!
I previously was able to generate a tiled model on same subset without any problem...
-
I have a couple of issues with 1.7:
1. I can't build a Diffuse texture. AO and Normal maps work fine.
2. When dragging and dropping a folder with pictures to the Workspace, Metashape now creates a "Chunk N" while 1.6.x created a Chunk named by the folder name
-
For when the possibility apply the rolling shutter corrections for undistorted images export?
Hello Diego,
The rolling shutter corrections should be now treated properly for the undistorted cameras export via Convert Images dialog in build 11701.
-
with latest release, I get following error when trying to generate depth maps on small subset of 21 aligned images:
Error: Assertion 239120391022012 failed at line 2012!
I previously was able to generate a tiled model on same subset without any problem...
Hello Paul,
It seems to be a new bug of the latest pre-release (will be fixed in the next update) related to the lack of the tie points between the overlapping cameras.
-
I have a couple of issues with 1.7:
1. I can't build a Diffuse texture. AO and Normal maps work fine.
2. When dragging and dropping a folder with pictures to the Workspace, Metashape now creates a "Chunk N" while 1.6.x created a Chunk named by the folder name
Hello nik_ska,
The issue with the GPU-based texture blending should be fixed in the latest 1.7.0 pre-release update (build 11701).
As for the automatic chunk renaming according to the drag-and-dropped folder, do you recall, in which Metashape version the desired behavior has been observed?
-
For when the possibility apply the rolling shutter corrections for undistorted images export?
Hello Diego,
The rolling shutter corrections should be now treated properly for the undistorted cameras export via Convert Images dialog in build 11701.
Hello Alexey,
Thank you very much to you and your team, excellent support.
Best regards and happy New Year.
Diego
-
the crash (which actually is the sw just exiting without any Crash message) seems to happen just with projects referenced in following CRS: WGS 84 / UTM zone 14N + GGM2010 height. or any Compound CRS using GGM2010 geoid...
I tried using DEM or OrthoMosaic button in Model view in other projects with different CRS`s without any problem.
Update: got same crash or impeteous exit from sw using following CRS : COMPD_CS["NZGD2000 / New Zealand Transverse Mercator 2000 + NZVD2016 height"....
Hello Paul,
The crash related to the Base Map display in the Model view in combination with DEM/Ortho display should be fixed in the published 11701 update.
Also there are some fixes related to the shapes (like proper display of the boundary shapes in the Ortho view mode).
-
Hello Alexey,
yes thank you for the fixes!
Eager to see the final release,
Best wishes for 2021!
-
Hello,
in latest release, there is a new option in Align Photos to Exclude stationary tie points.
What does this option do?
-
Hello Paul,
"Exclude stationary tie points" feature allows to suppress the tie points which appear in the exactly same locations of the image frame on multiple images.
It should allow to avoid false matches for the turntable scenario, when the camera is fixed; and to suppress the tie points related to the lens artifacts or stationary elements in the image frame, such as parts of the drone construction, for example.
-
"Exclude stationary tie points" feature allows to suppress the tie points which appear in the exactly same locations of the image frame on multiple images.
Sweet ! This will be quite useful indeed.
Thanks for all the work, can't wait to use the final release !
-
Hello Shadow,
Version 1.7.0 has been published on Downloads page:
https://www.agisoft.com/downloads/installer/
Feel free to share your feedback on the latest version.
-
Hi, happy new year ! When can we expect a upgrade of the pdf manual for 1.7 ?
-
Happy new Metashape version!
Exclude stationary points... sounds like a great help for rotary table scans, doesn't it?
-
Hi, happy new year ! When can we expect a upgrade of the pdf manual for 1.7 ?
Hello flyzk,
The PDF manual will be published later in January. Meanwhile the manual prototype is available as built-in application help.
-
:( Continuous shutdown of the application during building the mesh with depth maps - during calculating depth maps.
new nvidia drivers uploaded
final build 1,7
-
Hello lunar,
Please enable Write Log to File option in the General Preferences tab, re-start Metashape and if the issue persists, send the saved log to support@agisoft.com.
-
Hello Alexy
Same error here, metashape quit without error in the log fle, mesh set in highest and high quality:
2021-01-03 03:24:41 Agisoft Metashape Standard Version: 1.7.0 build 11736 (64 bit)
2021-01-03 03:24:41 Platform: Windows
2021-01-03 03:24:41 CPU: AMD Ryzen Threadripper 1950X 16-Core Processor (desktop)
2021-01-03 03:24:41 CPU family: 23 model: 1 signature: 800F11h
2021-01-03 03:24:41 RAM: 127.9 GB
2021-01-03 03:24:42 OpenGL Vendor: NVIDIA Corporation
2021-01-03 03:24:42 OpenGL Renderer: GeForce RTX 2080 SUPER/PCIe/SSE2
2021-01-03 03:24:42 OpenGL Version: 4.6.0 NVIDIA 460.89
2021-01-03 03:24:42 Maximum Texture Size: 32768
2021-01-03 03:24:42 Quad Buffered Stereo: not enabled
2021-01-03 03:24:42 ARB_vertex_buffer_object: supported
2021-01-03 03:24:42 ARB_texture_non_power_of_two: supported
2021-01-03 03:24:46 Loading project...
2021-01-03 03:24:49 loaded project in 3.165 sec
2021-01-03 03:24:49 Finished processing in 3.198 sec (exit code 1)
2021-01-03 03:25:06 checking for missing images...Checking for missing images...
2021-01-03 03:25:12 done in 5.853 sec
2021-01-03 03:25:12 Finished processing in 5.853 sec (exit code 1)
2021-01-03 03:25:12 BuildModel: quality = High, depth filtering = Mild, PM version, source data = Depth maps, surface type = Arbitrary, face count = High, volumetric masking = 0, OOC version, interpolation = Enabled, vertex colors = 1
2021-01-03 03:25:12 Generating depth maps...
2021-01-03 03:25:12 Preparing 9964 cameras info...
2021-01-03 03:25:26 cameras data loaded in 13.268 s
2021-01-03 03:26:12 cameras graph built in 46.628 s
2021-01-03 03:26:12 filtering neighbors with too low common points, threshold=50...
2021-01-03 03:26:12 Camera 3878 has no neighbors
2021-01-03 03:26:12 Camera 3888 has no neighbors
2021-01-03 03:26:12 Camera 4026 has no neighbors
2021-01-03 03:26:12 Camera 4571 has no neighbors
...
2021-01-03 03:26:12 avg neighbors before filtering: 634.779 (90% filtered out)
2021-01-03 03:26:12 limiting neighbors to 40 best...
2021-01-03 03:27:32 avg neighbors before limiting: 61.1616 (55% limited out)
2021-01-03 03:27:32 neighbors number min/1%/10%/median/90%/99%/max: 0, 0, 6, median=37, 40, 40, 40
2021-01-03 03:27:32 cameras info prepared in 139.811 s
2021-01-03 03:27:35 saved cameras info in 3.159
2021-01-03 03:27:35 Partitioning 9964 cameras...
2021-01-03 03:27:35 number of mini clusters: 767
2021-01-03 03:27:35 256 groups: avg_ref=38.9219 avg_neighb=187.617 total_io=582%
2021-01-03 03:27:35 max_ref=39 max_neighb=381 max_total=420
2021-01-03 03:27:35 cameras partitioned in 0.071 s
2021-01-03 03:27:35 saved depth map partition in 0.011 sec
2021-01-03 03:27:39 loaded cameras info in 3.503
2021-01-03 03:27:39 loaded depth map partition in 0.01 sec
2021-01-03 03:27:39 already partitioned (38<=50 ref cameras, 184<=200 neighb cameras)
2021-01-03 03:27:39 group 1/1: preparing 222 cameras images...
2021-01-03 03:27:39 point cloud loaded in 0.086 s
2021-01-03 03:27:40 Found 2 GPUs in 0.174 sec (CUDA: 0.063 sec, OpenCL: 0.111 sec)
2021-01-03 03:27:40 Using device: GeForce RTX 2080 SUPER, 48 compute units, free memory: 6646/8192 MB, compute capability 7.5
2021-01-03 03:27:40 driver/runtime CUDA: 11020/8000
2021-01-03 03:27:40 max work group size 1024
2021-01-03 03:27:40 max work item sizes [1024, 1024, 64]
2021-01-03 03:27:40 Using device: GeForce RTX 2080 SUPER, 48 compute units, free memory: 6693/8192 MB, compute capability 7.5
2021-01-03 03:27:40 driver/runtime CUDA: 11020/8000
2021-01-03 03:27:40 max work group size 1024
2021-01-03 03:27:40 max work item sizes [1024, 1024, 64]
2021-01-03 03:29:10 group 1/1: cameras images prepared in 90.406 s
2021-01-03 03:29:10 group 1/1: expected peak VRAM usage: 4970 MB (775 MB max alloc, 9630x14397 mipmap texture, 40 max neighbors)
2021-01-03 03:29:10 group 1/1: 222 x frame
2021-01-03 03:29:10 group 1/1: 222 x uint8
2021-01-03 03:29:10 Found 2 GPUs in 0 sec (CUDA: 0 sec, OpenCL: 0 sec)
2021-01-03 03:29:10 Using device: GeForce RTX 2080 SUPER, 48 compute units, free memory: 6639/8192 MB, compute capability 7.5
2021-01-03 03:29:10 driver/runtime CUDA: 11020/8000
2021-01-03 03:29:10 max work group size 1024
2021-01-03 03:29:10 max work item sizes [1024, 1024, 64]
2021-01-03 03:29:10 Using device: GeForce RTX 2080 SUPER, 48 compute units, free memory: 6693/8192 MB, compute capability 7.5
2021-01-03 03:29:10 driver/runtime CUDA: 11020/8000
2021-01-03 03:29:10 max work group size 1024
2021-01-03 03:29:10 max work item sizes [1024, 1024, 64]
2021-01-03 03:29:10 [GPU 1] group 1/1: estimating depth map for 1/38 camera 225 (9 neighbs)...
2021-01-03 03:29:10 [GPU 2] group 1/1: estimating depth map for 2/38 camera 513 (40 neighbs)...
2021-01-03 03:30:14 Agisoft Metashape Standard Version: 1.7.0 build 11736 (64 bit)
2021-01-03 03:30:14 Platform: Windows
2021-01-03 03:30:14 CPU: AMD Ryzen Threadripper 1950X 16-Core Processor (desktop)
2021-01-03 03:30:14 CPU family: 23 model: 1 signature: 800F11h
2021-01-03 03:30:14 RAM: 127.9 GB
2021-01-03 03:30:14 OpenGL Vendor: NVIDIA Corporation
2021-01-03 03:30:14 OpenGL Renderer: GeForce RTX 2080 SUPER/PCIe/SSE2
2021-01-03 03:30:14 OpenGL Version: 4.6.0 NVIDIA 460.89
2021-01-03 03:30:14 Maximum Texture Size: 32768
2021-01-03 03:30:14 Quad Buffered Stereo: not enabled
2021-01-03 03:30:14 ARB_vertex_buffer_object: supported
2021-01-03 03:30:14 ARB_texture_non_power_of_two: supported
Happy New Year!
-
Just to say that I've run the new version on a project with 2500 photos and it had no problems creating the depth maps or the mesh at Ultra-High.
Well done to everyone at Agisoft.
-
Hello Shadow,
Version 1.7.0 has been published on Downloads page:
https://www.agisoft.com/downloads/installer/
Feel free to share your feedback on the latest version.
Thanks !
1.7.0 downloaded and installed, so far I haven't had any issue. Thanks for all your work !
-
I'm noticing higher reprojection error in this release. Have there been changes in image alignment to cause this? On a model processed in 1.6.5 I'm getting ~0.3 pix RMS and in 1.7.0 I'm getting ~ 0.4 pix RMS.
-
Hello Alexy
Same error here, metashape quit without error in the log fle, mesh set in highest and high quality:
2021-01-03 03:24:41 Agisoft Metashape Standard Version: 1.7.0 build 11736 (64 bit)
2021-01-03 03:24:41 Platform: Windows
2021-01-03 03:24:41 CPU: AMD Ryzen Threadripper 1950X 16-Core Processor (desktop)
2021-01-03 03:24:41 CPU family: 23 model: 1 signature: 800F11h
2021-01-03 03:24:41 RAM: 127.9 GB
2021-01-03 03:24:42 OpenGL Vendor: NVIDIA Corporation
2021-01-03 03:24:42 OpenGL Renderer: GeForce RTX 2080 SUPER/PCIe/SSE2
2021-01-03 03:24:42 OpenGL Version: 4.6.0 NVIDIA 460.89
2021-01-03 03:24:42 Maximum Texture Size: 32768
2021-01-03 03:24:42 Quad Buffered Stereo: not enabled
Hello eltama,
Is the problem reproducible with only one of GPUs enabled or whether it happens with any single card enabled?
If there are any error-marked lines in Windows Event Viewer -> Windows Logs -> Application section related to metashape.exe, please export such lines to .evtx file and send it to support@agisoft.com.
-
i found this - ucrtbase.dll
- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>100</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2021-01-02T19:05:57.7816226Z" />
<EventRecordID>19031</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>Application</Channel>
<Computer>#########</Computer>
<Security />
</System>
- <EventData>
<Data>metashape.exe</Data>
<Data>1.0.0.1</Data>
<Data>5fedd4ec</Data>
<Data>ucrtbase.dll</Data>
<Data>10.0.19041.546</Data>
<Data>43cbc11d</Data>
<Data>c0000409</Data>
<Data>000000000007287e</Data>
<Data>4744</Data>
<Data>01d6e1320b61cad9</Data>
<Data>C:\Program Files\Agisoft\Metashape\metashape.exe</Data>
<Data>C:\WINDOWS\System32\ucrtbase.dll</Data>
<Data>87f99bf8-df48-4cb3-b2ea-c3faa645f7c7</Data>
<Data />
<Data />
</EventData>
</Event>
-
download and install 1,7 again, switch off task subdivision and have successful solution
-
Hey Alexey, can you explain what Generate Defocus Masks is?
Also very interested to know what this does and how it works.
Thanks,
JRP
-
Hey Alexey, can you explain what Generate Defocus Masks is?
Also very interested to know what this does and how it works.
Thanks,
JRP
Hi jrp,
I did some tests with this feature and it creates a mask in out-of-focus areas of the image. It seems to be similiar to Photoshops "Focus Area" tool, where based on local contrast etc. blurred parts are masked but it seems to be more sophisticated since you require a scaled model for the mask to work.
The results are great and this is super useful for creating textures without having to deal with out-of-focus areas being mapped to the texture.
This could also be useful when working with small objects where depth of field is always a problem: Create a rough, scaled model with all images, run the filter, realign with created masks (excluding feature detection on masked areas) and then running the high-res reconstruction. But I'm sure Alexey will clarify the use cases.
Thanks Agisoft team! Great update <3
-
It's a shame that this feature isn't present in the Standard version as I've been hoping for something like this for years. :'(
Mak
-
Hello Mak,
Currently defocus masking option requires the chunk to be scaled to the real world dimensions, which is not possible in Standard edition. However, we'll see, if there could be any approach to implement the feature in Standard edition.
-
Alexey,
Thanks for the info. Hopefully this is something that can be figured out.
Cheers
Mak
-
I tried out your latest Metashape release, and it's still broken!
This is what I get from opening a previous project and trying to process a Depth Map.
(https://www.agisoft.com/forum/index.php?action=dlattach;topic=12653.0;attach=15284;image)
Really disappointed by this :(
-
Hello 3D_Scan_Fan,
Which graphic cards do you have enabled in the GPU Preferences tab of Metashape? And which driver versions are installed for these GPUs?
-
Like before, I have two RX 580 graphic cards, both of which enabled.
Again, like before, I am using driver version 18.6.1.
All your recent versions up til 1.7.0. (maybe 1.6.5.) work with this older driver.
-
Like before, I have two RX 580 graphic cards, both of which enabled.
Again, like before, I am using driver version 18.6.1.
All your recent versions up til 1.7.0. (maybe 1.6.5.) work with this older driver.
Please send the complete processing log related to the failed operation to support@agisoft.com.
Some algorithms, including the depth maps generation, have been revised in the version 1.7.0.
-
Please find the log here:
2021-01-06 18:29:23 Agisoft Metashape Professional Version: 1.7.0 build 11736 (64 bit)
2021-01-06 18:29:23 Platform: Windows
2021-01-06 18:29:23 CPU: Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz (desktop)
2021-01-06 18:29:23 CPU family: 6 model: 60 signature: 306C3h
2021-01-06 18:29:23 RAM: 31.9 GB
2021-01-06 18:29:23 OpenGL Vendor: ATI Technologies Inc.
2021-01-06 18:29:23 OpenGL Renderer: Radeon RX 580 Series
2021-01-06 18:29:23 OpenGL Version: 4.5.13521 Compatibility Profile Context 24.20.11021.1000
2021-01-06 18:29:23 Maximum Texture Size: 16384
2021-01-06 18:29:23 Quad Buffered Stereo: not enabled
2021-01-06 18:29:23 ARB_vertex_buffer_object: supported
2021-01-06 18:29:23 ARB_texture_non_power_of_two: supported
2021-01-06 18:29:23 Using simple console. Rich console can be enabled in Preferences dialog.
2021-01-06 18:29:29 LoadProject: path = D:/My Projects/Photogrammetry projects/Ten24 FACS project/Test/Test.psx
2021-01-06 18:29:29 Loading project...
2021-01-06 18:29:30 loaded project in 0.339 sec
2021-01-06 18:29:30 Finished processing in 0.342 sec (exit code 1)
2021-01-06 18:29:36 BuildDenseCloud: quality = Ultra high, depth filtering = Mild, PM version, point colors = 1
2021-01-06 18:29:36 Generating depth maps...
2021-01-06 18:29:36 Preparing 120 cameras info...
2021-01-06 18:29:37 cameras data loaded in 0.275 s
2021-01-06 18:29:37 cameras graph built in 0.05 s
2021-01-06 18:29:37 filtering neighbors with too low common points, threshold=50...
2021-01-06 18:29:37 Camera 41 has no neighbors
2021-01-06 18:29:37 avg neighbors before filtering: 61.9167 (73% filtered out)
2021-01-06 18:29:37 limiting neighbors to 40 best...
2021-01-06 18:29:37 avg neighbors before limiting: 16.4833 (0% limited out)
2021-01-06 18:29:37 neighbors number min/1%/10%/median/90%/99%/max: 0, 4, 7, median=14, 31, 40, 40
2021-01-06 18:29:37 cameras info prepared in 0.507 s
2021-01-06 18:29:37 saved cameras info in 0.012
2021-01-06 18:29:37 Partitioning 120 cameras...
2021-01-06 18:29:37 number of mini clusters: 10
2021-01-06 18:29:37 3 groups: avg_ref=40 avg_neighb=32 total_io=180%
2021-01-06 18:29:37 max_ref=48 max_neighb=41 max_total=89
2021-01-06 18:29:37 cameras partitioned in 0.001 s
2021-01-06 18:29:37 saved depth map partition in 0.004 sec
2021-01-06 18:29:37 loaded cameras info in 0.016
2021-01-06 18:29:37 loaded depth map partition in 0 sec
2021-01-06 18:29:37 already partitioned (48<=50 ref cameras, 26<=200 neighb cameras)
2021-01-06 18:29:37 group 1/1: preparing 74 cameras images...
2021-01-06 18:29:37 point cloud loaded in 0.005 s
2021-01-06 18:29:37 Found 2 GPUs in 0.203 sec (CUDA: 0 sec, OpenCL: 0.203 sec)
2021-01-06 18:29:37 Using device: Radeon RX 580 Series (Ellesmere), 36 compute units, free memory: 8141/8192 MB, OpenCL 2.0
2021-01-06 18:29:37 driver version: 2580.6, platform version: OpenCL 2.1 AMD-APP (2580.6)
2021-01-06 18:29:37 max work group size 256
2021-01-06 18:29:37 max work item sizes [1024, 1024, 1024]
2021-01-06 18:29:37 max mem alloc size 4048 MB
2021-01-06 18:29:37 wavefront width 64
2021-01-06 18:29:37 Using device: Radeon RX 580 Series (Ellesmere), 36 compute units, free memory: 8141/8192 MB, OpenCL 2.0
2021-01-06 18:29:37 driver version: 2580.6, platform version: OpenCL 2.1 AMD-APP (2580.6)
2021-01-06 18:29:37 max work group size 256
2021-01-06 18:29:37 max work item sizes [1024, 1024, 1024]
2021-01-06 18:29:37 max mem alloc size 4048 MB
2021-01-06 18:29:37 wavefront width 64
2021-01-06 18:29:37 Using device: CPU Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz (using 2/8)
2021-01-06 18:29:38 Building kernels for Radeon RX 580 Series (Ellesmere)...
2021-01-06 18:29:39 Device 1
2021-01-06 18:29:39 Program build log:
2021-01-06 18:29:39 Error: Undeclared function index 1028
2021-01-06 18:29:39
2021-01-06 18:29:39
2021-01-06 18:29:39 Failed to compile binary dumped to C:/Users/*/AppData/Local/Agisoft/Metashape Pro/cache/kernel_cache/pm_undistort_templated4098Radeon RX 580 Series (Ellesmere)_FAILED
2021-01-06 18:29:39 Building kernels for Radeon RX 580 Series (Ellesmere)...
2021-01-06 18:29:41 Device 1
2021-01-06 18:29:41 Program build log:
2021-01-06 18:29:41 Error: Undeclared function index 1028
2021-01-06 18:29:41
2021-01-06 18:29:41
2021-01-06 18:29:41 Failed to compile binary dumped to C:/Users/*/AppData/Local/Agisoft/Metashape Pro/cache/kernel_cache/pm_undistort_templated4098Radeon RX 580 Series (Ellesmere)_FAILED
2021-01-06 18:29:41 Finished processing in 4.427 sec (exit code 0)
2021-01-06 18:29:41 Error: ciErrNum: CL_BUILD_PROGRAM_FAILURE (-11) at line 1087
>>>
-
The Radeon Software Adrenalin Edition 18.6.1 drivers are nearly 3 years old (!!).
Mak
-
And?
They still work.
Also, any version after that is not compatible with Photoscan 1.3.5. because of the removal of Spir-1.2.
Funny enough, the last time I saw this similar problem was with newer version of the driver.
-
It's a shame that this feature isn't present in the Standard version as I've been hoping for something like this for years. :'(
Mak
Same, I even went ahead and just built it as an extension myself. It works a bit differently but the results are pretty much the same except all masks are done in parallel.
The 170 version is more precise, though. Kudos :)
edit: hmm, i actually still have some advantages when I compared it head to head. yay wojtek!
-
It's a shame that this feature isn't present in the Standard version as I've been hoping for something like this for years. :'(
Mak
Same, I even went ahead and just built it as an extension myself. It works a bit differently but the results are pretty much the same except all masks are done in parallel.
The 170 version is more precise, though. Kudos :)
:'( $3499 (Professional version) is way above what I can spend though (just for one feature in my case) .
-
It's a shame that this feature isn't present in the Standard version as I've been hoping for something like this for years. :'(
Mak
Seconded. a defocus mask feature is highly desirable.
-
Also, any version after that is not compatible with Photoscan 1.3.5. because of the removal of Spir-1.2.
Funny enough, the last time I saw this similar problem was with newer version of the driver.
Hello 3D_Scan_Fan,
Metashape 1.7 uses hardware-accelerated textured from OpenCL API, which seems to be improperly supported in the drivers that you are using.
Is there any reason, why you need to use PhotoScan 1.3?
-
Hello all,
i understand that new depth maps generation method produces better detailed models than previously.
However for drone aerial mapping, the depth maps generation time is dramatically higher than v1.6 in case of lower end GPU Geforce GTX 670MX as previously reported. Also dense cloud quality is lower as shown in attached screen copy showing 2 clouds (1.6 and 1.7) side by side with a lot of noise in 1.7.
Comparing the accuracy of both clouds shows that they are quite consistent except for the noise. In 2nd attachment, the 1.7 cloud is colored by elevation...
As things stand I would continue using v1.6 for dense cloud and subsequent product generation. I hope this issue can be addressed.
-
Hello Paul,
I've made a small comparison for the depth maps generation time on the single machine (i7-4960X, GeForce RTX 3080, Windows 7) for 650 DJI nadir photos in High quality with Mild filtering.
1.7.0.11736
Depth maps: 47 min
Memory peak: 7.4 GB
1.6.6.11715
Depth maps: 65 min
Memory peak: 2.7 GB
-
Hi Alexey,
obviously with more recent GPUs processing times for recent version are better. But I am stuck with an older GeForce GTX 670MX and for this GPU times for depth mas generation are much longer!
Have you been able to investigate why I get much more noise in dense cloud for latest version?
-
Hello Paul,
The noise filtering will be improved with the next update.
As for the performance drop on the old cards, not sure, if we can improve it considerably.
-
Also, any version after that is not compatible with Photoscan 1.3.5. because of the removal of Spir-1.2.
Funny enough, the last time I saw this similar problem was with newer version of the driver.
Hello 3D_Scan_Fan,
Metashape 1.7 uses hardware-accelerated textured from OpenCL API, which seems to be improperly supported in the drivers that you are using.
Is there any reason, why you need to use PhotoScan 1.3?
Every version from 1.6.5. and downwards work fine with the drivers I'm using.
As for Photoscan 1.3.5., I've probably explained to you in another post and in emails that there are aspects in that version (particularly the Alignment process) tends to be better.
I don't understand why now with 1.7 it gets broken.
-
Hello Paul,
The noise filtering will be improved with the next update.
As for the performance drop on the old cards, not sure, if we can improve it considerably.
Thanks, Alexey for the update. I am now redoing the dense cloud using following tweak main/depth_pm_enable false and get results similar to 1.6 version see attached screen grab....
For now,I will be using this tweak on my laptop.
-
I'm still getting the Error: ciErrNum: CL_BUILD_PROGRAM_FAILURE (-11) at line 1087 when trying to process Depth Maps :(
Might this be fixed by any chance?? :'(
-
Hi all,
I have a model constructed from 188 aerial drone images referenced to Coordinate system WGS 84 + EGM96 height.
When I try to export to KMZ format I get Error: Vertical datum out of range
Why is this so?
NB. the export to KMZ works in version 1.6.6
-
I have a NVIDIA GeForce GTX 1660 Ti (6GB ram) and a NVIDIA RTX 2080 Super (8GB ram) in my system - both activated in Metashape. In version 1.65 they always shared the GPU workload but in version 1.7 I alawys get the following message in the log:
2021-01-11 11:39:52 Warning: Device GeForce GTX 1660 Ti ignored because it has 4572/6144 MB available, but 6134 MB required
The RTX 2080 Super is used. Does this mean, different GPUs with different amounts of RAM cannot be used together anymore in the new depth map generation process of version 1.7?
thanks
-
Hello Andreas
Try to connet RTX 2080 S to your monitor, so the GTX 1660 VRAM is completly free, close all other apps and lower monitor resolution.
Hope u fix it.
Regards
Elmar
-
Hello Elmar,
thank you for your reply - unfortunately this did not solve the problem. I also tried the "limiting neighbors" - tweak as Alexey recommended in an earlier post. At first none of the GPUs was used in the process. Limiting the neighbors to 40 with the tweak at least the RTX 2080 Super is used - but the 1660 Ti is constantly ignored. Is it maybe possible, that the algorithm is fully utilizing the capacity of the more powerful GPU, thus not being able to use the 1660 Ti anymore?
best regards,
Andreas
-
Alexey,
1.7 really does haves serious issues with floating geometry inside & outside meshes and other anomalies on the edges.
From the Banana project:
(https://i.postimg.cc/C517CqCD/Screenshot-2021-01-10-170903.jpg)
One more try with another project:
(https://i.postimg.cc/MHFD9ptL/Screenshot-2021-01-12-013759.jpg)
Just came across those from an other user on Facebook ( the blue one is from metashpae 1.7):
(https://i.postimg.cc/136HKPFW/138450173-10160515112444167-3364350198661215392-o.jpg)
(https://i.postimg.cc/JhLQ6gcR/138457723-10160515112704167-4476407775544932859-oz.jpg)
(https://i.postimg.cc/HsFz5jrc/138873203-10160515112834167-3367448478301996365-oza.jpg)
Mak
-
I have a model constructed from 188 aerial drone images referenced to Coordinate system WGS 84 + EGM96 height.
When I try to export to KMZ format I get Error: Vertical datum out of range
Why is this so?
NB. the export to KMZ works in version 1.6.6
Hello Paul,
We'll fix this problem in the next 1.7 update.
-
I have a NVIDIA GeForce GTX 1660 Ti (6GB ram) and a NVIDIA RTX 2080 Super (8GB ram) in my system - both activated in Metashape. In version 1.65 they always shared the GPU workload but in version 1.7 I alawys get the following message in the log:
2021-01-11 11:39:52 Warning: Device GeForce GTX 1660 Ti ignored because it has 4572/6144 MB available, but 6134 MB required
The RTX 2080 Super is used. Does this mean, different GPUs with different amounts of RAM cannot be used together anymore in the new depth map generation process of version 1.7?
Hello Andreas,
Can you please share the complete log related to the depth maps calculation stage? Also please specify, which type of the images you are working with (resolution, file type and bit depth).
-
Hello Alexey,
thank you for your reply. Attached you find a log file with the mentioned problem.
I usually work with .dng files, converted from Nikon D850 .nef Raw files - so a resolution of 8256x5504 pixels and a bit depth of 14bit.
thanks for your help,
Andreas
-
Had you try to use a more precise panorama camera? we have tried the new 1.7.0 with photos captured by Civetta and the result is pretty good. the new upgrade of Agisoft is really a thing.
In case you are also interested in Civetta: https://weiss-ag.com/civetta360camera/
[For laser scans] Current approach is the following:
...
- run Align Photos operation as usual.
Does that mean that the poses of the laser scans will be adjusted in addition to the internal and external parameters calculated for the standard cameras?
As a user who commonly combines laser scan data with photogrammetry that is not at all what I would want to happen. The laser scan data will almost always be coming from other software where we have much more control over the alignment process. Therefore the laser scan data should be treated as fixed (no pose adjustments) and photos aligned to it.
I haven't had a chance to test the implementation in Metashape 1.7.0 extensively yet. However, my past experience with the general method of treating scans as spherical panoramas for alignment purposes suggests that the results will likely be very unstable. The resulting panoramas are typically low resolution and, if they are intensity only scans, relatively low contrast; so few tie points are likely to be detected by Metashape's feature detector. From the few small tests I've tried on 1.7.0 that is indeed what seems to be happening.
From a process efficiency perspective, what I want to do as a user is use intensity only scans to capture geometry and photogrammetry to capture color.
-
Does anyone know how to apply the new/updated normal mapping function in 1.7.0?
Thanks!
-
Hello!
Anyone know where is the normal mapping feature option in metashape 1.7?
Thanks!
-
Hello zzha367,
Normal map generation is possible, if you have at least two polygonal models in the same chunk. Please see the related tutorial:
https://agisoft.freshdesk.com/support/solutions/articles/31000153952-texture-maps-normal-map-generation
-
thank you for your reply. Attached you find a log file with the mentioned problem.
I usually work with .dng files, converted from Nikon D850 .nef Raw files - so a resolution of 8256x5504 pixels and a bit depth of 14bit.
Hello Andreas,
In the 1.7.1 update there will be a tweak allowing to downscale images to 8-bit for the depth maps generation, which will considerably reduce the memory consumption. I think it wouldn't affect the resulting quality in general case.
-
Thanks for this information Alexey. I just tested with a set of 55 Nikon D850 raw images and had the same problem with the updated 1.71 version. The GTX 1660 Ti with 6GB of VRAM ist ignored. Could you please provide the mentioned tweak to reduce the images to 8 bit for DM creation?
thanks again,
Andreas
-
Hello Andreas,
Please create the following tweak via Advanced Preferences tab:
BuildDepthMaps/pm_convert_16u_to_8u and set its value to True.
-
Alexey,
The 1.7 user manual incorrectly states that Interpolation is only available when reconstructing from a Dense Cloud:
Interpolation (for point cloud source options only)
Btw https://www.agisoft.com/forum/index.php?topic=12653.msg57463#msg57463 (https://www.agisoft.com/forum/index.php?topic=12653.msg57463#msg57463) is still present i, 1.7.1
Mak
-
Hello Andreas,
Please create the following tweak via Advanced Preferences tab:
BuildDepthMaps/pm_convert_16u_to_8u and set its value to True.
Thanks Alexey, this seems to work - both my GPU's are now used again.
best whishes, Andreas
-
1.7 really does haves serious issues with floating geometry inside & outside meshes and other anomalies on the edges.
Hello Mak,
Do you see the improvement of the result, if Moderate or Aggressive depth filtering option is used for depth maps based mesh generation? (filtering can be selected now in Build Mesh dialog).
-
Alexey,
Not much difference unfortunately. You should try it with your Banana project to easily reproduce it.
Cheers
Mak
-
Alexey,
Not much difference unfortunately. You should try it with your Banana project to easily reproduce it.
Cheers
Mak
(https://i.postimg.cc/fWC5TbxH/Screenshot-2021-01-25-142642.jpg)
Now check out the tip of the Banana which is always incorrectly reconstructed in 1.7.x:
Disabled:
(https://i.postimg.cc/cCxmBqNM/disabled.jpg)
Mild:
(https://i.postimg.cc/rFpjdLjq/mild.jpg)
Moderate:
(https://i.postimg.cc/rFYJxYZx/modarate.jpg)
Agressive:
(https://i.postimg.cc/4yW188fC/Agressive.jpg)
Mak
-
i understand that new depth maps generation method produces better detailed models than previously.
However for drone aerial mapping, the depth maps generation time is dramatically higher than v1.6 in case of lower end GPU Geforce GTX 670MX as previously reported. Also dense cloud quality is lower as shown in attached screen copy showing 2 clouds (1.6 and 1.7) side by side with a lot of noise in 1.7.
Comparing the accuracy of both clouds shows that they are quite consistent except for the noise. In 2nd attachment, the 1.7 cloud is colored by elevation...
As things stand I would continue using v1.6 for dense cloud and subsequent product generation. I hope this issue can be addressed.
Hello Paul,
Have you tried Aggressive filtering in the 1.7.1 release version?
-
Hello Alexey,
yes the latest version 1.7.1 with agresive filtering produces much better dense clouds but of course with longer depth maps processing time compared to 1.6 (using Nvdia Geforce GTX 670MX) as was previously stated. Good work on filtering! See attached screen comparing 2 versions...
-
The 1.7 user manual incorrectly states that Interpolation is only available when reconstructing from a Dense Cloud:
Interpolation (for point cloud source options only)
Btw https://www.agisoft.com/forum/index.php?topic=12653.msg57463#msg57463 (https://www.agisoft.com/forum/index.php?topic=12653.msg57463#msg57463) is still present i, 1.7.1
Hello Mak,
The information regarding interpolation and depth filtering should be corrected now in the latest PDF version of Manual.
As for the banana example, in Aggressive mode I am not observing flying mesh components around the main model, although some areas which are poorly covered have small holes.
-
The 1.7 user manual incorrectly states that Interpolation is only available when reconstructing from a Dense Cloud:
Interpolation (for point cloud source options only)
Btw https://www.agisoft.com/forum/index.php?topic=12653.msg57463#msg57463 (https://www.agisoft.com/forum/index.php?topic=12653.msg57463#msg57463) is still present i, 1.7.1
Hello Mak,
The information regarding interpolation and depth filtering should be corrected now in the latest PDF version of Manual.
As for the banana example, in Aggressive mode I am not observing flying mesh components around the main model, although some areas which are poorly covered have small holes.
Alexey,
Strange. all I did was open the project orignal project and generate the mesh (only changing the filtering modes). We should be getting exactly the same result (unless there's different between OpenCL/CUDA path ?). Beside the flying mesh component are you seeing the same badly reconstructed tip of the banana?
Mak
-
In the changelog I found this a few build back: "Added Save camera track option for Sketchfab uploads." But for some reason I do not see this option under Metashape Standard 1.7.1.
Anyway, I always save a 3d file manually and upload it to Sketchfab. How can I then save and .fbx file with animation, so sketchfab can use the camera track as animation?
-
[For laser scans] Current approach is the following:
...
- run Align Photos operation as usual.
Does that mean that the poses of the laser scans will be adjusted in addition to the internal and external parameters calculated for the standard cameras?
As a user who commonly combines laser scan data with photogrammetry that is not at all what I would want to happen. The laser scan data will almost always be coming from other software where we have much more control over the alignment process. Therefore the laser scan data should be treated as fixed (no pose adjustments) and photos aligned to it.
...
Yes, it can be said that the laser scans are aligned together with the common images.
If you need to rely on the accurate scanner locations, you can input corresponding coordinates to the Reference pane for the related camera instances and adjust the accuracy value for them in order to increase the weight for them.
...
I would also like to see an option to just check a box or similar to force laser scan alignment to be preserved exactly, if it had been registered already in a 3rd party package, otherwise the function would not be useful. It seems a lot of manual work to input the coordinates of each laser setup (and presumably orientation?) to ensure they stay fixed. I take great care over my registration and wouldn't trust any algorithm to do a better job! We treat our laser data as sacred and once it is registered everything else (so many things...) is derived from it, but can not be allowed to affect it!
I haven't actually tried 1.7 yet so I might not know what I'm talking about, but it seemed like a potential issue!
Hi guys,
congratulations on the discussion.I have a question when importing TLS scans. I noticed that in the "Rerefences" panel, TLS scans (from Faro X-series) are read as panoramas, with all the related parameters (X, Y, Z, Pich, Roll, ect). My question is this: are TLS point clouds used in Tie point matching also to scale the cloud in true size or not? Or better is there a method to take TLS clouds into account to optimize the photogrammetric cloud?