Agisoft Metashape 1.6.0 pre-release

[jnb]

Hello,

I was wondering about the new options in the align photos stage : source - estimated - sequential.
I think sequential speaks for itself but what do the others ?

Thank you

[Mak11]

Team,

What's the ETA of the next 1.6 pre-release build?

Cheers

Mak

[Alexey Pasumansky]

Hello Mak,

Next pre-release update is expected by the end of this week, or maybe during the next week.

[Alexey Pasumansky]

I was wondering about the new options in the align photos stage : source - estimated - sequential.
I think sequential speaks for itself but what do the others ?

Sequential pre-selection is trying to match the images with a bunch of their neighbors according to the camera labels.

Estimated preselection is based on the estimated camera locations after initial alignment (for example, performed using rough accuracy settings).

One of the possible scenarios of use - when aligning the video sequence frames run Sequential preselection at first and then Estimated preselection, if there are intersecting parts of the image acquisition path.

[Mak11]

Hello Mak,

Next pre-release update is expected by the end of this week, or maybe during the next week.

Great. Patiently waiting.

Cheers

Mak

[Mak11]

I'm now encountering full system crashes/lock-ups with 1.6 Build 9217 during the "Estimating camera locations..." (which is 100% CPU bound) part of the alignement process on some data-sets (those who seems the more  intensive to process). Never had Photoscan/Metashape hard lock a PC like that before. First time it happened I got a BSOD. All other attempts resulted in a hard lock (only solution is to hard reset the system).

Only thing that pop-ed up in the Event Viewer is this (when the BSOD happened):

Log Name:      Application
Source:        Application Error
Date:          21-Oct-19 12:11:26 AM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      DESKTOP-4612L03
Description:
Faulting application name: metashape.exe, version: 1.0.0.1, time stamp: 0x5d90ea7f
Faulting module name: ntdll.dll, version: 10.0.18362.418, time stamp: 0x99ca0526
Exception code: 0xc0000005
Fault offset: 0x000000000009fab0
Faulting process id: 0x26f0
Faulting application start time: 0x01d58791bf92b983
Faulting application path: C:\Program Files\Agisoft\Metashape\metashape.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: 6f7e4ac4-b51e-48cc-8a9a-0dc3d14c95c9
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2019-10-20T22:11:26.605443100Z" />
    <EventRecordID>38721</EventRecordID>
    <Channel>Application</Channel>
    <Computer>DESKTOP-4612L03</Computer>
    <Security />
  </System>
  <EventData>
    <Data>metashape.exe</Data>
    <Data>1.0.0.1</Data>
    <Data>5d90ea7f</Data>
    <Data>ntdll.dll</Data>
    <Data>10.0.18362.418</Data>
    <Data>99ca0526</Data>
    <Data>c0000005</Data>
    <Data>000000000009fab0</Data>
    <Data>26f0</Data>
    <Data>01d58791bf92b983</Data>
    <Data>C:\Program Files\Agisoft\Metashape\metashape.exe</Data>
    <Data>C:\WINDOWS\SYSTEM32\ntdll.dll</Data>
    <Data>6f7e4ac4-b51e-48cc-8a9a-0dc3d14c95c9</Data>
    <Data>
    </Data>
    <Data>
    </Data>
  </EventData>
</Event>

Uninstalled 1.6 and re-installed 1.5.5 & everything seems to work fine.

EDIT: Happening on 1.5.5...🤔 Must be a hardware issue on my side...

Lowered my CPU clock & no more crashes since... Looks like it's on its last leg..

Cheers

MAK

[Mak11]

Dmitry, Alexey,

Added GPU-based texturing generation support for NVIDIA GPUs.

Any chance/hope that OpenCL support (AMD GPUs & Intel iGPUs soon to be released Intel dGPUs) will be added?

Cheers

Mak

[wojtek]

Thanks for the revised UV parameterization!

It seems that dense meshes no longer have really high overlap ratio although i do get much lower fill ratio in return. Are there any new settings we can use via python for buildUV?

[Mak11]

I'm guessing that this will come back.. but the Calculate Vertex Colors option is no longer available when generating meshes via the Depth Maps.

Mak

[Alexey Pasumansky]

Dmitry, Alexey,

Added GPU-based texturing generation support for NVIDIA GPUs.

Any chance/hope that OpenCL support (AMD GPUs & Intel iGPUs soon to be released Intel dGPUs) will be added?

Hello Mak,

GPU texturing relies on Vulkan API which is supported by all GPU vendors. But we encountered some problems in AMD driver implementation - when they will be resolved we will be able to confirm GPU texturing on AMD. Intel GPUs will be tested after that.

As for the vertex colors and volumetric masks - they are not gone forever and will be back for out-of-core mesh implementation in the next pre-release update.

[Mak11]

Alexey,

Glad to know that it's Vulkan based & not CUDA. What kind of issue did you encounter on AMD GPUs? Also, does the current CPU fallback provide the same end result (but slower) that the GPU path?

One more question: the out of core mesh generation seems to rely a lot less on GPU compute after the depth maps have been generated, right?
Haven't test a whole lot but I'm happy to see that the final mesh output is now better with less of the unwanted polys everywhere.

Edit:

Trimming seems to be a bit strange:

1.6 9217:



1.6 9397:



(also "main/mesh_trimming_radius: 30" doesn't seem to have any effect at all now)

BTW there's a typo in the console log it says Outlier instead of Outliner during texture generation.

Cheers

Mak

[Paulo]

I am curious to know what Fit additional corrections option do in Optimize Cameras dialog?....

What are these corrections and when should we use this option?

[Alexey Pasumansky]

Hello Mak,

Looks like the trimmed areas have poor coverage by the depth maps. Do you have any trimming tweaks enabled?

The GPU utilization for the depth maps method should be during the similar steps as in the version 1.5 - similar parts of the method are GPU-accelerated.

As for the possible difference between CPU and GPU implementation results for the texture generation - they would not be identical, however, should look very similar and it shouldn't be possible to distinguish the difference in general case.

[Mak11]

Alexey,

No trimming tweaks were applied. If you try the Doll sample you will see similar results (holes) where there's poor depth map coverage (under the skirt) and  mesh_trimming_radius 30 doesn't seem to have any effect when applied in this build. (obviously 1.5.0 handled does cases perfectly without any tweaks...but you already know that 😉). Visibility Consistent Mesh Generation, Metashape up to v 1.5.1 ( & to a lesser degree Metashape 1.5.3+ with mesh_trimming_radius set to "30") correctly remeshed those holes/gaps. So there must be a way to fix this.


Yeah I'm seeing some GPU utilization but what appears in the console has changed quite a bit so it was harder to figure out what was happening.

Out-of-core meshing is perfectly working though. So big congrats on this achievement! Never went over 14GB of Ram usage on data-sets (with 150+/200+ 24MP images) that would fail before.

Cheers

MAK

Cheers

[Alexey Pasumansky]

I am curious to know what Fit additional corrections option do in Optimize Cameras dialog?....

What are these corrections and when should we use this option?

Hello Paulo,

Fit additional corrections option enables additional calibration coefficients that allows a better fit of the lens distortion model. This is especially important for wide angle lens with large radial distortions, e.g. DJI Phantom 4 RTK camera.

This option is mainly intended to be used in cases when highly accurate reference data is available (RTK/PPK) and it can help to achieve higher accuracy when no GCPs are available.