Agisoft PhotoScan 1.3.0 pre-release

[Kjellis85]

A small but annoying bug; PhotoScan icons are not appearing, just generic windows icon. I am running win 10 and PS 1.3.0 3520 (64bit)
Bug was in Win 10, not PS.

[Airgo]

No GPU is found anymore!
With PS 1.3.0 3520 the settings window for the GPUs is empty and console says that my graphic cards do not support SPIR.
I am on MacBookPro mid 2012 with a NVIDIA GeForce GT 650M 512 MB.

[Alexey Pasumansky]

Hello Airgo,

You might need to install CUDA drivers, as they are not packed with the standard graphic card drivers for Mac OS X:
http://www.nvidia.com/object/mac-driver-archive.html

[Airgo]

Hello Alexey,

thank you. And should I work with the NVIDIA Web Driver or with the Default OS X Graphics Driver?
Which one will deliver better (faster) results?

[Alexey Pasumansky]

Hello Airgo,

Actually not sure, if it does matter. If you are able to see the GPU device in PhotoScan preferences with OS X default driver, then it's fine.

[Mohammed]

Hello Alexey,

I don't understand clearly this window so shall i check on GPU drivers to accelerate the process.
Thank you,,

[Alexey Pasumansky]

Hello tornado2011,

In the GPU devices list you need to choose the devices that you wish to be used in the processing. The check box in the bottom defines whether the CPU should be used in parallel to GPU  (the check box is on) or the processing should be perforemed on GPU only. Note that even if you uncheck the CPU option, there still will be some activity on CPU, as it controls GPU jobs.

In the latest update GPU is used at two processing steps: building depth maps and matching photos.

[Airgo]

Hello Alexej,
I see the NVIDIA GPU in both settings, Max OS X oder NVIDIA Web driver, so it seems really not to make any difference (maybe I will drive some tests for speed).
But what is gone is the Intel HD Graphics 4000. Can it be reactivated as well?

[Alexey Pasumansky]

Hello Airgo,

For Intel HD you need to update drivers (OpenCL), if it's possible on Mac OS X.

[Mohammed]

Hi Alexey,

Thanks for your quick answer.
I also face an issue while i put some GCPs on one of my recent projects i made Optimization, after that i decided to put some additional markers but when i place the marker on the specific area it jumped  couple of pixels and i have to correct the position again manually.

Thank you,
Mohammed

[Pascal]

Hello,
thanks for this new beta release, it seems that the key finding and matching use GPU now, the gain in time is considerable, but I noticed some differences in the result quality comparing to the pure CPU method.
Point color seems to be not correct and it is very difficult (sometime impossible) to have all the images matched with GPU when there is no problem with CPU, so the new method seems to be more demanding about shooting quality.
If this issue is not solvable, you could consider to give the possibility to use GPU only in dense reconstruction in case of difficulty with GPU matching.
Thanks.
Pascal
   

[Paulo]

Hi all,

yes it seems that with latest release, the matching algorithm does not find same number of Tie points as  in previous release.

I have a data set of 69 photos on which I performed matching with two latest releases and number of matches varies quite a bit.

Here is result of previous release Matching:

Point Cloud
Puntos 87,459 de 121,950
RMS error de reproyección 0.135979 (0.75202 pix)
Error de reproyección máximo 1.25603 (7.50969 pix)
Tamaño promedio de puntos característicos 4.92251 pix
Superposición efectiva 3.02671
Parámetros de orientación
Precisión Alta
Pre-procesar emparejamiento de imágenes Referencia
Puntos claves por foto 40,000
Puntos de enlace por foto 0
Restricción de máscara activa No
Adaptativo ajuste del modelo de cámara No
Tiempo búsqueda de puntos homólogos 5 minutos 7 segundos
Tiempo de orientación 42 segundos
Parámetros de optimización
Parámetros f, b1, b2, cx, cy, k1-k3, p1, p2
Fit rolling shutter No
Tiempo de optimización 1 segundo

and here is matching result for latest release:

Point Cloud
Points 61,346 of 90,573
RMS reprojection error 0.109892 (0.660971 pix)
Max reprojection error 0.453098 (6.862 pix)
Mean key point size 5.06373 pix
Effective overlap 2.87035
Alignment parameters
Accuracy High
Generic preselection Yes
Reference preselection Yes
Key point limit 40,000
Tie point limit 0
Adaptive camera model fitting No
Matching time 2 minutes 26 seconds
Alignment time 22 seconds
Optimization parameters
Parameters f, b1, b2, cx, cy, k1-k3, p1, p2
Fit rolling shutter No
Optimization time 1 seconds

Matching time is much faster but with lower number of points...

The question is what is the impact of alignment precision?

[bisenberger]

I prefer the previous mouse cursor for marker placement. It came to a point at the actual pick location and did not obscure the pick location. The new cursor surrounds the pick location with a circle and tics marks making it difficult to see the actual pick location.

Maybe just get rid of the circle with hatches and leave the center tic.

[Alexey Pasumansky]

I did it from a folder into the Applications folder. I just tried to enter as root user and the same happened.
I'm going to try to ihnibit gatekeeper to see is there's a difference.
Cheers

PS:No luck, even with Gatekeeper turned off.

Hello RHenriques,

Do you get similar errors all the time, with those strange paths?

[RHenriques]

Hi Alexey

Yes, same thing. I tested everything. The same error occur all the time. Sierra duplicates Photoscan to that folder that appears in the path but the folder seems not be accessible for write privileges, even for the root user. I guess that the possible solution is to generate a .lic file outside the application. Maybe using an invisible writable folder in a shared folder or in the user's home folder.
Cheers