Agisoft Metashape

Agisoft Metashape => General => Topic started by: stephan on January 11, 2019, 06:41:35 PM

Title: Metashape 1.5 build 7492 align issues
Post by: stephan on January 11, 2019, 06:41:35 PM
I just updated to the last version and it seems that it is broken... something went wrong between metashape preview build 7336 and current build 7492... I haven't changed any of my API codeand camera alibnments come out in a very inconsistent way: half of the time PhotoScan aligns only 20% of cameras and my project crashes. Does anyone else have issues ?
Title: Re: Metashape 1.5 build 7492 align issues
Post by: Alexey Pasumansky on January 11, 2019, 06:50:58 PM
Hello stephan,

Can you please share a sample image set that we can use for testing purposes to reproduce the difference in the alignment results?

Also do you observe such difference only if pre-selection is used, or it doesn't matter?
Title: Re: Metashape 1.5 build 7492 align issues
Post by: stephan on January 12, 2019, 12:16:13 AM
Hi Alexey,
I don't have access to a sample image set that I could share right now but I am testing the pre-selection thing. It looks like it occasionally fails when generic_preselection is TRUE, but I never use reference_preselection so need to test that still.

It seems there are some other differences in the API I have some individual functions that no longer work, I'm trying to debug this too.
Title: Re: Metashape 1.5 build 7492 align issues
Post by: stephan on January 12, 2019, 01:02:52 AM
I can no longer reproduce the issue it seems although I got it a few times before. I will try to get some data to you for a test.
Title: Re: Metashape 1.5 build 7492 align issues
Post by: stephan on January 12, 2019, 01:08:24 PM
With preselection set to False I cannot reproduce the error. I ran about 20 renders overnight to test and it never failed.
Title: Re: Metashape 1.5 build 7492 align issues
Post by: stephan on January 13, 2019, 05:45:59 PM
I ran some more tests and it has failed a couple of times again, even with preselection off. I will try to roll back to  previous version to compare.
Title: Re: Metashape 1.5 build 7492 align issues
Post by: Alexey Pasumansky on January 13, 2019, 06:06:37 PM
Hello stephan,

If there's any sample image set that can be used to reproduce the alignment difference of versions 1.4 and 1.5, it would be helpful, if you can provide it.
Title: Re: Metashape 1.5 build 7492 align issues
Post by: lauri on March 01, 2019, 08:44:02 AM
Hello,

Any update regarding this? We have the same problem, image sets that used to align with 90 %, now do only with 50 %. Update 1.5.0 -> 1.5.1 didn't solve the issue. I have to change back to Photoscan in the meanwhile.
Title: Re: Metashape 1.5 build 7492 align issues
Post by: Alexey Pasumansky on March 01, 2019, 02:51:48 PM
Hello lauri,

Can you share the source images and the project with the alignment results saved in the version 1.5.1 to support@agisoft.com, so that we could reproduce the problem?
Title: Re: Metashape 1.5 build 7492 align issues
Post by: Mak11 on March 01, 2019, 03:37:22 PM
Hello lauri,

Can you share the source images and the project with the alignment results saved in the version 1.5.1 to support@agisoft.com, so that we could reproduce the problem?

I can't share any files right now unfortunately but I can confirm that alignement (with Generic preselection on) has become less reliable since the Generic Preselection optimizations introduced in  Metashape 1.5 build 7125 pre-releases a few months ago (no problem in the pre-release versions before 1.5 7125).

Mak
Title: Re: Metashape 1.5 build 7492 align issues
Post by: GrinGEO on April 22, 2019, 12:03:40 AM
I see same problems... most projects less than half of the images, mostly in the mid of the entire photogrammetry, are not aligned any more... Bevore more than 90% where aligned...
Title: Re: Metashape 1.5 build 7492 align issues
Post by: Mak11 on April 22, 2019, 01:13:07 AM
I see same problems... most projects less than half of the images, mostly in the mid of the entire photogrammetry, are not aligned any more... Bevore more than 90% where aligned...

Yes, Metashape has introduced quite a few "optimizations" that make it less reliable than Photoscan right now (the alignment issues described here, also the new mesh generation being completely messed up in 1.5.2).

Let's hope that the team is working on improving things in 1.5.3 (or at least reverting back) .

Mak
Title: Re: Metashape 1.5 build 7492 align issues
Post by: Alexey Pasumansky on April 22, 2019, 02:00:26 PM
Hello GrinGEO,

Which version you are using 1.5.0, 1.5.1 or 1.5.2?
Title: Re: Metashape 1.5 build 7492 align issues
Post by: jm on June 18, 2019, 07:32:50 PM
i have a Linux machine and a Windows machine both using 1.5.0, build 7492. The Windows machine aligns cameras 100% as expected and the Linux machine only gets about 50% of the cameras aligned. This is using the same data set for both machines and the same settings for both machines as well as the same GPU.
Title: Re: Metashape 1.5 build 7492 align issues
Post by: Alexey Pasumansky on June 18, 2019, 08:37:00 PM
Hello jm,

Can you please check, if you are observing any alignment issues with the latest Metashape version 1.5.3 build 8432?
Title: Re: Metashape 1.5 build 7492 align issues
Post by: jm on June 19, 2019, 11:25:54 PM
yes, we have updated to 1.5.3 build 8432 and still experience the problem on Linux machine. Windows machine continues to align all cameras as expected.
Title: Re: Metashape 1.5 build 7492 align issues
Post by: Alexey Pasumansky on June 20, 2019, 11:55:34 AM
Hello jim,

Then it would be helpful, if you could provide the projects in PSZ format with the alignment performed on Linux and Windows machines to support@agisoft.com, so that we could try to reproduce the problems.
Title: Re: Metashape 1.5 build 7492 align issues
Post by: Matt on September 02, 2019, 04:00:48 AM
HI Alexey,

I am also having alignment issues.  I have had to use Photoscan 1.4.3 to get my 21 GB photo dataset to align.
I have used the same settings and am getting vastly different results. Metashape is very quick but it simply does not align.
See attached