Agisoft Metashape 1.7.0 pre-release

[Alexey Pasumansky]

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.

[Alexey Pasumansky]

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.

[Paulo]

Yes, Alexey,

the crash report appeared only the first time this issue occurred then I just get exit from Mertashape without crash report...

[mcstieg]

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! 

[Paulo]

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:

Code: [Select]

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...

[nik_ska]

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

[Alexey Pasumansky]

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.

[Alexey Pasumansky]

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.

[Alexey Pasumansky]

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?

[Diego]

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

[Alexey Pasumansky]

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).

[Paulo]

Hello Alexey,

yes thank you for the fixes!

Eager to see the final release,

Best wishes for 2021!

[Paulo]

Hello,

in latest release, there is a new option in Align Photos to Exclude stationary tie points.

What does this option do?

[Alexey Pasumansky]

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.

[Shadow]

"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 !