Agisoft PhotoScan 1.3.0 pre-release

[Alexey Pasumansky]

Hello bisenberger,

Project files are not backward compatible, you need to use Save As -> PhotoScan 1.2.0 format when saving the PSZ project from the newest version.

[maddin]

Is there a way to turn off the auto-placement of markers (blue flag)? In my test, it is doing more harm than good.

[Alexey Pasumansky]

Hello maddin,

You can use Place marker option to put a projection of existing marker on photo.

In the version 1.3 there would be a possibility to choose New Marker option from the Place Marker menu, thus you do not need to create new marker instance first.

[maddin]

You can use Place marker option to put a projection of existing marker on photo.

In the version 1.3 there would be a possibility to choose New Marker option from the Place Marker menu, thus you do not need to create new marker instance first.

Not sure I explained well what my issue is:
In 1.3, I place a marker on one photo. Automatically, PS creates (blue flagged) markers in all the other photos. Unfortunately, these blue markers are often in wrong locations. In version 1.26, placing one marker in a photo would create epipolar lines in the other photos; then, upon placement of the next marker, all other photos would get a grey marker suggestion, which is fine. Now in 1.3, that grey suggestion stage seems to be replaced. Since the blue markers are in wrong locations, I get very bad refinement. Is there a way to prevent those blue markers?

[Alexey Pasumansky]

Hello maddin,

If you do not wish marker projections to be created automatically (blue flags) using available surface (point cloud, mesh, etc.) you need to you Place marker option in Photo view instead of Create Marker.

[andrey.d]

Dear Aleksey,

Could I manage mem,  virtual mem and cpu cores by script.
I see examples for cpu cores setting,  but it don't work in last build of 1.3.

Thanks.

[Alexey Pasumansky]

Hello andrey.d,

There's no setting to manage the memory or CPU usage in PhotoScan 1.3.

The CPU cores option that was available in the version 1.2 was related to the depth maps calculation procedure only when at least one GPU device was turned on. The setting defined how many CPU cores would be used for the depth maps calculation, other cores could be used for the GPU tasks management.

[RHenriques]

Hi Alexey, about my previous message:

"However I noticed that my two GPU's are not appearing into the OpenCL TAB. Version 1.2.6 are using them without any problem.  My Machine is a MacPro Octacore with two AMD Radeon HD FirePro 500 GPU's."

Aren't you supporting these GPU's anymore or still a work in progress?
Cheers

[Alexey Pasumansky]

Hello RHenriques,

I think we'll provide special installer for Mac users that have AMD cards. Currently there are some issues with OpenCL drivers on Mac OS X.

[RHenriques]

Great Alexey. Some others, like me, invested a lot in these machines to use with PhotoScan. I'm very satisfied with it and it's not that old. That would be awesome. Without the drivers this version feels a lot slower than version 1.2.6, mainly when using mesh or texture view.
Cheers

[Alexey Pasumansky]

Hello RHenriques,

Sure, we understand the issue and we'll be finding a proper solution for it. For some reason AMD drivers for Mac OS X do not include SPIR support.

[Diego]

Hello Alexey,

Exactly how it works multichannel support for point cloud colors, format export?

Thanks.

[bisenberger]

I see a new build was released yesterday. 

Updated to version 1.3.0 build 3745.
« Last Edit: January 31, 2017, 01:30:29 PM by Dmitry Semyonov »


Will start checking it out tomorrow.

[mwittnebel]

thats nice i will also start to test the new version.

@Alexey Pasumansky

did you have a new target release date for a stable 1.3.0 version ?

[Alexey Pasumansky]

@Alexey Pasumansky

did you have a new target release date for a stable 1.3.0 version ?

I think the end of this week or beginning of the next one.