Agisoft PhotoScan 1.4.0 pre-release

[Dmitry Semyonov]

Pre-release version of Agisoft PhotoScan 1.4.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 PhotoScan Standard edition
Windows 64 bit
Windows 32 bit
Mac OS X
Linux 64 bit

Agisoft PhotoScan Professional edition
Windows 64 bit
Windows 32 bit
Mac OS X
Linux 64 bit

PhotoScan 1.4.0 Change Log
PhotoScan 1.4.0 Python API

Please let us know if you have any problems using this version.

Please post problems and/or questions concerning other PhotoScan version in separate topics.

This topic will be removed when the final 1.4.0 version is released.

Note
Project files created with 1.4.0 version can't be opened with earlier versions.

EDIT:
Updated to version 1.4.0 build 5585.

[JMR]

CONGRATULATIONS, AGI TEAM! SEEMS A FORMIDABLE STEP AHEAD! THANKS FOR LISTENING!
Best regards,
GEOBIT

[Mohammed]

Congrats Agisoft Team, Keep going, u r the Best. Hope next release contain a speed on the Process time.

Mohamed

[Mohammed]

In Ortho Menu what is the use of (Rectangular, Circle, Free form Selection) when i open Ortho mode it dosen't select anything?

Mohamed

[Alexey Pasumansky]

Hello Mohamed,

Currently selection instruments in the Ortho view mode allows to select markers and shapes (actually, it worked in the same way in 1.3).

[Mohammed]

Oky thanks.
Also for the delighting new tool looks very promising and the result is quit good still need some improvments with hard shadow i guess.
Best.
Mohamed

[Paulo]

Great work... very good new features...

However in survey Statistics window the size of ellipse error for points or photos is not correct. In attached image, it shows at 1 to 1 scale and comparing to  distance scale would mean point or photo center errors of many meters while they are actually a few cm! And if you change sliding scale, size of reference ellipse does not change....

[Vlad]

Why the **ck 1.4 pre even if i define other folder to install removed 1.3 version?

But Mesh Refinement is amazing. You finally made this! But because you take one known paper about this method, most of users will did not find any profit comparing to non refined workflow
Mesh refinement required some changes. And can be faster that usual.

[Vlad]

One biggest problem that Mesh Refinement as usual for Agisoft is not out of core. And 2Gb VRAM not enough for average 2017 years scans.

This is bad, because your users is not rich studios that moved years from Photoscan to more modern tools. But hobbyists that still can have 1Gb or 2Gb VRAM GPU.

>4Mln poly mesh required ~2,3Gb of RAM and do not allow make refinement.

[SAV]

Great job, Agisoft team.

I haven't tested version 1.4.0 yet, but the change log looks quite impressive, especially:

- Animation pane for fly through videos #bigthumbsup

- 3Dconnexion Space Mouse support #bigthumbsup

- Radiometric normalisation based on cam exp parameters and irradiance sensor #bigthumbsup

- Cesium 3D tiles format support for tiled model export #bigthumbsup

- Survey statistics

- Offset estimation for fixed camera rigs

... to just name a few.

Impressive work.

Regards,
SAV

[Alexey Pasumansky]

However in survey Statistics window the size of ellipse error for points or photos is not correct. In attached image, it shows at 1 to 1 scale and comparing to  distance scale would mean point or photo center errors of many meters while they are actually a few cm! And if you change sliding scale, size of reference ellipse does not change....

Hello Paul,

The scale multiplier X1 means that the size of the ellipse for each camera is in 1:1 compared to scalebar in the bottom of the Survey Statistics dialog.

There is however, the minimal radius for the camera location, that is required to demonstrate the elevation error (by color).

[Vlad]

That's funny. Did you just copy and paste code from OpenMVS RefineMesh module for your mesh refinement?

Even if user decimate mesh to a deep **it and will play with 50images, such heado-on solution will always have not enough memory. At least OpenMVS can use CPU and RAM. And 300+ images still possible to process on 64Gb RAM.

2017-09-20 16:28:32 RefineMesh: quality = Ultra high, iterations = 20, smoothness = 1
2017-09-20 16:28:32 Using device: GeForce GTX 960, 8 compute units, 2048 MB global memory, compute capability 5.2
2017-09-20 16:28:32   max work group size 1024
2017-09-20 16:28:32   max work item sizes [1024, 1024, 64]
2017-09-20 16:28:32 Analyzing mesh detalization...
2017-09-20 16:29:05 Memory required: 1743 Mb + 6 Mb = 1749 Mb
2017-09-20 16:29:05 Stage #1 out of 4
2017-09-20 16:29:05 Subdividing mesh...
2017-09-20 16:29:07 Memory required: 27 Mb + 6 Mb = 33 Mb
2017-09-20 16:29:07 Loading photos...
2017-09-20 16:29:09 loaded photos in 2.642 seconds
2017-09-20 16:29:09 Refining model...
2017-09-20 16:29:12 Iteration #1 out of 20
2017-09-20 16:29:40 Iteration #2 out of 20
2017-09-20 16:29:59 Iteration #3 out of 20
2017-09-20 16:30:07 Iteration #4 out of 20
2017-09-20 16:30:16 Iteration #5 out of 20
2017-09-20 16:30:28 Iteration #6 out of 20
2017-09-20 16:30:49 Iteration #7 out of 20
2017-09-20 16:31:12 Iteration #8 out of 20
2017-09-20 16:31:34 Iteration #9 out of 20
2017-09-20 16:31:54 Iteration #10 out of 20
2017-09-20 16:32:16 Iteration #11 out of 20
2017-09-20 16:32:38 Iteration #12 out of 20
2017-09-20 16:32:56 Iteration #13 out of 20
2017-09-20 16:33:14 Iteration #14 out of 20
2017-09-20 16:33:38 Iteration #15 out of 20
2017-09-20 16:33:57 Iteration #16 out of 20
2017-09-20 16:34:20 Iteration #17 out of 20
2017-09-20 16:34:39 Iteration #18 out of 20
2017-09-20 16:35:00 Iteration #19 out of 20
2017-09-20 16:35:09 Iteration #20 out of 20
2017-09-20 16:35:17 Stage #2 out of 4
2017-09-20 16:35:17 Subdividing mesh...
2017-09-20 16:35:20 Memory required: 108 Mb + 19 Mb = 128 Mb
2017-09-20 16:35:20 Loading photos...
2017-09-20 16:35:23 loaded photos in 2.516 seconds
2017-09-20 16:35:23 Refining model...
2017-09-20 16:35:31 Iteration #1 out of 20
2017-09-20 16:35:58 Iteration #2 out of 20
2017-09-20 16:36:25 Iteration #3 out of 20
2017-09-20 16:37:01 Iteration #4 out of 20
2017-09-20 16:37:42 Iteration #5 out of 20
2017-09-20 16:38:09 Iteration #6 out of 20
2017-09-20 16:38:37 Iteration #7 out of 20
2017-09-20 16:39:05 Iteration #8 out of 20
2017-09-20 16:39:32 Iteration #9 out of 20
2017-09-20 16:39:59 Iteration #10 out of 20
2017-09-20 16:40:26 Iteration #11 out of 20
2017-09-20 16:41:02 Iteration #12 out of 20
2017-09-20 16:41:34 Iteration #13 out of 20
2017-09-20 16:42:08 Iteration #14 out of 20
2017-09-20 16:42:42 Iteration #15 out of 20
2017-09-20 16:43:15 Iteration #16 out of 20
2017-09-20 16:44:33 Iteration #17 out of 20
2017-09-20 16:46:20 Iteration #18 out of 20
2017-09-20 16:46:52 Iteration #19 out of 20
2017-09-20 16:47:25 Iteration #20 out of 20
2017-09-20 16:47:56 Stage #3 out of 4
2017-09-20 16:47:56 Subdividing mesh...
2017-09-20 16:48:07 Memory required: 435 Mb + 72 Mb = 508 Mb
2017-09-20 16:48:07 Loading photos...
2017-09-20 16:48:10 loaded photos in 2.516 seconds
2017-09-20 16:48:10 Refining model...
2017-09-20 16:48:42 Iteration #1 out of 20
2017-09-20 16:50:57 Iteration #2 out of 20
2017-09-20 16:52:44 Iteration #3 out of 20
2017-09-20 17:05:25 Iteration #4 out of 20
2017-09-20 17:07:18 Iteration #5 out of 20
2017-09-20 17:08:58 Iteration #6 out of 20
2017-09-20 17:10:39 Iteration #7 out of 20
2017-09-20 17:12:18 Iteration #8 out of 20
2017-09-20 17:13:58 Iteration #9 out of 20
2017-09-20 17:15:39 Iteration #10 out of 20
2017-09-20 17:17:19 Iteration #11 out of 20
2017-09-20 17:18:59 Iteration #12 out of 20
2017-09-20 17:20:38 Iteration #13 out of 20
2017-09-20 17:22:18 Iteration #14 out of 20
2017-09-20 17:23:57 Iteration #15 out of 20
2017-09-20 17:25:38 Iteration #16 out of 20
2017-09-20 17:27:17 Iteration #17 out of 20
2017-09-20 17:28:57 Iteration #18 out of 20
2017-09-20 17:30:38 Iteration #19 out of 20
2017-09-20 17:32:17 Iteration #20 out of 20
2017-09-20 17:33:57 Stage #4 out of 4
2017-09-20 17:33:57 Subdividing mesh...
2017-09-20 17:34:42 Memory required: 1743 Mb + 287 Mb = 2030 Mb
2017-09-20 17:34:42 Loading photos...
2017-09-20 17:34:45 loaded photos in 3.218 seconds
2017-09-20 17:34:45 Refining model...
2017-09-20 17:36:57 Iteration #1 out of 20
2017-09-20 17:36:58 Finished processing in 4106.3 sec (exit code 0)
2017-09-20 17:36:58 Error: out of memory (2) at line 179

[Kjellis85]

Great stuff, a lot to look into!

I did a quick test with video import but could not get it to work. I am trying to import a mp4 file from a GoPro Hero 4 Black but I am getting an error message that reads "A media resource couldn't be resolved". I am unable to find any help on this issue in the helpfile.

Any sugestions?

[Alexey Pasumansky]

Hello Kjellis85,

Which OS you are using and which codec is used by the video?

[Alexey Pasumansky]

Even if user decimate mesh to a deep **it and will play with 50images, such heado-on solution will always have not enough memory. At least OpenMVS can use CPU and RAM. And 300+ images still possible to process on 64Gb RAM.

Currently refine mesh functionality is experimental feature in PhotoScan and is available on GPU only (CUDA / OpenCL), but we are planning to implement CPU support for this feature in the next updates.

As for the video memory consumption, it depends not on the number of images, but the image resolution and quality option selected in Refine Mesh dialog. Also the mesh size is important, but it's impact is considerably lower than the one related to the images.