Agisoft PhotoScan 1.0.0 pre-release

[Peter]

i have pro version

[chadfx]

Hi Peter, perhaps this helpful post created by Lee will be of use, then?

http://ir-ltd.net/delivering-aligned-and-scaled-photoscan-outputs/

Cheers, -C

[Matt]

Hi Alexey,

I am having issues with the classify point cloud functionality.  Runs very quickly in 1736 but no luck with build 1760. In 1736 it just initialized for a few seconds and then away it went now it just stalls after the second initialize. I should add that I have been giving up after fifteen minutes based on previous experience and reverting to build 1736.

Also has the softness/blur issue in the ortho export been resolved in the 1760 build as I have had to revert to 9.1 for production ortho export my forested areas or areas of very complex geometry.

Thanks again to the team for the awesome product.

[piste]

Hi Everybody...
Some new features to implement in this new version:

• Add 6 usefull view buttons (Upper view, bottom, front, back, left and right)
• Add some usefull combo for navigation mode (for example ctrl + left click to rotate pointcloud or model around z-axis, shift + left click to rotate pointcloud/3D model around x-axis...)
• Add a mesh edit mode (create polylines to bound mesh on street or clean surface, delete manually spikes or wrong vertex...)
• Add automatic identification of planes in meshed model for geotechnical purposes...

These are only suggestions.. 

Thanks agisoft team!

[andyroo]

Matt,

In 1760 I am getting clean orthos (0.15 m ortho and 0.5m dem from canon d12 at 500-750 meters elevation) where the detail looks as good as I saw in 0.8.5 and better than 0.9.1 I think. Settings are high alignment, ultra high density point cloud, and custom 50 000 000 face mesh. I think it's slower than 0.9.1 though, and the water noise might actually be worse - I tried it on moderate, which is supposedly the default values from 0.8.5?

I miss having more control over noise reduction.

Also I have had a crash while batch-building mesh (I think during a save) that corrupted a project file, so beware.

And when I try to view the mesh I get a timeout error on my video card (but I am running a mixed AMD/Invidia setup). Dense point cloud viewing/editing works fine. I wish there was a way to remove disconnected clusters of points from the main pointcloud because those are mostly blunders.

[Alexey Pasumansky]

Hello Peter,

In the version 1.0.0 there's "Rotate object" tool on the toolbar that can be used to reorient model relatively to the coordinate system axis prior to the export or model upload.

Hello Matt,

Have you performed the classification on the same project with the same number of points in the dense cloud?

[Alexey Pasumansky]

Hello piste,

1. Add 6 usefull view buttons (Upper view, bottom, front, back, left and right)
2. Add some usefull combo for navigation mode (for example ctrl + left click to rotate pointcloud or model around z-axis, shift + left click to rotate pointcloud/3D model around x-axis...)

1. This is already implemented in 1.0.0 - you can use NumPad hotkeys or corresponding view options in the view menu.
2. For such rotation purposes you can use red, green and blue circles located on the trackball, thus rotation will be performed only around the corresponding axis and other rotations will be locked.

[Matt]

Hi Andyroo,

Thanks for the input. The main area I am having trouble with in the orthos is in dense bush where I get this 'fog' below the canopy. I can work around this by classifying the dense cloud and filtering out everything but  the ground (build 1736) then exporting the project back to 9.1 and exporting the mosaic from there (its not ideal).

I think we are doing much the same thing in the way of time series work so it may be worth having a chat sometime. Although I suspect I am on the opposite side of the earth to you on the land down under.  I have been sucessfully running the AMD/Nvidia combo for over a year now with no real issues.  I have stopped upgrading the nvidia drivers at 311.06 as I am running a GTX 590 and run the most up to date catalyst drivers.  No Stalling when I am viewing meshes although I never really bother with anything over 40 mill on my processing machine. I suspect the Titan 6 GB would solve your issues with large mesh display but it would still be pretty bad in the openCL processing side.

HI Alexey,

Yep tried it with numerous dense clouds at everything from low through to ultra high, they all work in 1736 not at all in 1760. Given up using 1760 at this stage as I am under the pump with projects. I will try and have another look at it tonight while I am processing.

Thanks

[RHenriques]

Version 1.0 1760 has issues and is very unstable under MacOS 10.9 Mavericks.
Main issues are:

- Some camera position polygons are black instead of blue.
- Box limits are strange pixelated black lines, instead of smooth gray ones.
- If the "Rotate Region tool" is selected, the box becomes black. It's impossible to see anything inside it (see image).
- While select Batch and try to change parameters in any process, PS crashes immediately.   


There are some annoyances in the interface, mainly related with displacement of feature access. Menus have disappeared (for instance "view matches") and now have a more awkward way to get it (second click in the photos pane). The use of an image scale is now less obvious than in previous versions. As I already said in a previous reply, about options for photo filtering, any software should always provide, at least, 2 ways to get to a feature among a menu command, a button or a right mouse click pop up menu. PS, lately, tends to abuse of the latest option without provide any other. Functions are there indeed but are less obvious for most users.
Keep on the good work.

[Matt]

HI Alexey,

Still cannot get the classify point cloud to work on build 1760. Basically freezes the software and needs to be shut down via task manager.

[bisenberger]

Version 1.0.0 build 1760.
Build Dense Cloud with 166 cameras, settings Ultra high/Mild, running for almost 2.5 hours showing 0% done, CPU at 15%, and memory at 9%. Tried to cancel process, but wouldn't, so had to end process with task manager.

It also seems like photo matching takes longer than in version 0.9.1.

[Alexey Pasumansky]

Hello Matt,

We'll check that.


Hello RHenriques,

We also see some visualization issues on Mavericks, while on the previous MacOS PhotoScan works fine. However, Batch Process crashes under Mavericks will be fixed in the next PhotoScan update.
As for the GUI suggestions we are trying to make the interface easier, for example, View Matches in 1.0.0 allows to click on exact photo in the Photos pane and see its matches with the rest of images, whereas in previous versions one had to search for the photo label in the long list. But still we are considering different options and if you have any additional suggestions we will appreciate them.

Hello bisenberger,

What are the computer specifications and memory commit in Task Manager?

[bisenberger]

Intel Core i7-3770K CPU @ 3.50GHz
32.0 GB RAM
GTX 660 3 GB
GTX 460 1 GB

Memory 2.6/31.9 GB (8%) it was at 9% when running Build Dense Cloud mentioned in previous post.

[bisenberger]

When using Gradual Selection - Reprojection error on sparce point cloud it selects a number of points. If I delete the points and run Gradual Selection - Reprojection error again, it keeps selecting about the same number of points.

[Alexey Pasumansky]

Hello bisenberger,

Have you got the log file from that processing? I've just finished Ultra reconstruction for 150 image project and got memory consumption peak about 26 GB. And the processing time was about 17 hours for depth maps reconstruction (double-Xeon workstatation with single GTX580) and 1.5 hours for dense point cloud generation.