Agisoft PhotoScan

Agisoft PhotoScan => General => Topic started by: Dmitry Semyonov on September 21, 2014, 04:26:54 PM

Title: Agisoft PhotoScan 1.1.0 pre-release
Post by: Dmitry Semyonov on September 21, 2014, 04:26:54 PM
Pre-release version of Agisoft PhotoScan 1.1.0 is available for download.

This pre-release is considered as unstable and is not recommended for production use.

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.1.0 version is released.

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

EDIT:
PhotoScan 1.1.0 build 2004 was finally released. Thank you for useful feedback.

Please use the links on the main PhotoScan page for download:
Download Installers (http://www.agisoft.com/downloads/installer/)
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: bisenberger on September 21, 2014, 05:03:01 PM
Can this version be installed alongside version 1.0.4, or does it overwrite it?
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: Dmitry Semyonov on September 21, 2014, 06:13:26 PM
Hello bisenberger,

Unfortunately only one PhotoScan version can be installed at a time, PhotoScan 1.1.0 installer will overwrite 1.0.4 version.

You can revert to a previous version at any time later by uninstalling PhotoScan 1.1.0 from Control Panel and installing 1.0.4 version afterwards.
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: ThomasVD on September 21, 2014, 06:22:06 PM
Some cool new features!! I'm doing a lot of processing atm so won't install to the beta version just yet, but looking forward to the stable release!
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: wojtek on September 21, 2014, 06:37:26 PM
Great!

Is there any basic guide for the network processing?
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: Dmitry Semyonov on September 21, 2014, 07:07:34 PM
Hello wojtek,

Please see an updated post with a link to basic network processing instructions.
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: wojtek on September 21, 2014, 09:07:25 PM
Thanks!

Is meshing considered for network processing as well (for future)?
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: hengefjes on September 22, 2014, 12:34:53 AM
Wow! That changelog is impressive  :) Great work! Can't wait to check it out. Will it be possible to install the viewer on other network clients?
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: Peter on September 22, 2014, 01:11:55 AM
Woohoo!!!
A viewer and fisheye support, cant w8 to try it out
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: Paulie on September 22, 2014, 09:04:32 AM
The Network features look great!

Can you please comment on the license requirements for running Photoscan Pro on multiple computers utilizing the network features?  Do you require additional licenses for the extra clients or processing nodes?

Kind Regards,
Paul
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: JRM on September 22, 2014, 10:53:22 AM
Hi, could you send the updated *.ts file for translation ? thanks
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: Alexey Pasumansky on September 22, 2014, 01:19:13 PM
Hello Paul,

PhotoScan Pro licenses are node-locked. And since each processing node can be used also in common mode, it requires separate license key for activation.
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: bigben on September 22, 2014, 01:54:20 PM
Fisheye support rocks!  :o  8)   Huge improvement on GoPro image sets
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: Porly on September 22, 2014, 04:19:53 PM
Hello Dmitry,

great work!

Are there any new options, features or improvements for orthophoto generation? Is this changelog the final version until the official release or may some features be added in the new future?

To be honest I hoped there would be some new tools like seamline editing or something like that, to improve the workflow and quality for orthophotos.


 
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: jedfrechette on September 22, 2014, 08:41:56 PM
PhotoScan Pro licenses are node-locked. And since each processing node can be used also in common mode, it requires separate license key for activation.

So $3500 USD/compute node, ouch! I guess I'm more accustomed to distributed renderer pricing so that seems awfully high. Plus that means all of the interactive licenses are going to be tied up during the compute task so work on other projects will need to stop.

Are there any plans to develop a compute only version to run on headless nodes that could be licensed in packs of 5 or 10?
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: Alexey Pasumansky on September 22, 2014, 08:45:29 PM
Hello Jed,

We have discounts for multi-license packs starting from three licenses. You can check the prices in FastSpring online shop or contact our sales department for detailed information.

We'll consider the possibility of headless node licenses in future.
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: bigben on September 23, 2014, 03:59:36 AM
I'd be interested in any recommendations for optimising performance on VMs using network processing and what the optimum combination of CPU/GPU would be for individual nodes.

e.g. At the moment the machine that hosts my VM has 32/16 (CPU/GPU cores). Would it be better to have 8 x 4/2 or 4 x 8/4 (or even 16 x 2/1) 

It may be better for our uni to provide a central pool of processing nodes rather than providing individuals with beefy VMs (?)
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: James on September 23, 2014, 05:08:38 PM
Alexey, im get problem with selecting images -im have pressed the CTRL key and clicking on images that want disable, but afther not same period of time the selection is lost, and im must start from begining to select images. mostly can set upto 3-10 images then it lost selection. have tested to change Keyeboard, mouse, try on another 2 PCs but same problem. And its not just this version... Haveo thers same problem  too ??
Hello Wishgranter,
Do these problems appear in Photos pane? If yes, then it is connected to the mouse-click during the mouse movement. In this case PhotoScan starts multiple selection and resets the previously selected files.

I thought this ^ was subsequently fixed, but now seems to be an issue again with 1.1.0.

I'm giddy in love with the new fisheye lens support though!
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: Alexey Pasumansky on September 23, 2014, 05:13:31 PM
Hello James,

Do you think adding selection while holding Ctrl key should also support multiple selection?
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: hengefjes on September 23, 2014, 05:38:16 PM
I can't export tiles for use with the viewer. The viewer can't open exported .oc3 files either. Also the Export Panorama function is grey(disabled?). Are there any special conditions that have to be met to use these tools?
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: Alexey Pasumansky on September 23, 2014, 05:50:15 PM
Hello hengefjes,

OC3 export works only for dense point cloud. Tile export is also based on dense point cloud and would not work if it is missing in the active chunk.

And brief tutorial regarding panorama export is attached.
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: hengefjes on September 23, 2014, 06:15:21 PM
Hello hengefjes,

OC3 export works only for dense point cloud. Tile export is also based on dense point cloud and would not work if it is missing in the active chunk.
"Export tiles" lets me choose some options for the export. -> Enter name and location -> A box which says "Processing in progress" shows briefly - then it just says: "Can't export model". Dense point cloud in active chunk is there, - not missing. - Will check out that panorama tutorial :)
Thank you for the quick replies!
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: Alexey Pasumansky on September 23, 2014, 06:20:41 PM
Hello hengefjes,

And what is the output in the Console pane related to the tile export? In the export tiles dialog you need to specify export resolution, so the model should be properly referenced to fit these units.
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: James on September 23, 2014, 06:54:58 PM
Hello James,
Do you think adding selection while holding Ctrl key should also support multiple selection?

I did enjoy being able to hold CTRL while dragging a single selection over distinct groups of multiple photos. I haven't tried out the new grouping functions of 1.1.0 yet though, which may negate the need for it in most cases.
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: ThomasVD on September 23, 2014, 10:06:29 PM
What exactly does the "Tie-Point limit" feature do? What does the default value of 1000 mean? And if you enter 0 (= infinite?) does this act the same as the previous version of PhotoScan?
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: hengefjes on September 24, 2014, 10:39:19 AM
Hello hengefjes,

And what is the output in the Console pane related to the tile export? In the export tiles dialog you need to specify export resolution, so the model should be properly referenced to fit these units.
Here's the console output:
Finished processing in 0 sec (exit code 1)
grid: 9x7x3 (5 levels)
Preprocessing images...
preprocessing images... done in 0.697 sec
Finished processing in 0.698 sec (exit code 0)
>>>
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: Patribus on September 24, 2014, 11:39:27 AM
Hello,

I was quite excited to see, that PS offers a panorama output now, since I work professionaly with aerial panoramas. 

Here some examples:
http://glauchau.aerorama.net/ (http://glauchau.aerorama.net/)
http://lvps176-28-21-156.dedicated.hosteurope.de/demos/elsilencio-pano1/ (http://lvps176-28-21-156.dedicated.hosteurope.de/demos/elsilencio-pano1/)
http://lvps176-28-21-156.dedicated.hosteurope.de/fv_panoramas/OurPiece_JBP_lbpano1/ (http://lvps176-28-21-156.dedicated.hosteurope.de/fv_panoramas/OurPiece_JBP_lbpano1/)

I always thought that the high quality of the image matching in PS could compete with other panorama software.

So, yesterday I have tried the panorama function out and I had to conclude, that a bunch of features are missing in order to use it in a professional context. I would be pleased to indicate which other features would be necessary to have a minimal version of what is needed in a more professional context. But next week, I'm in stress now.

Nevertheless, the pano function seems to be a nice tool when  a quick panorama generation for documentation or overview is needed.

Cheers
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: bigben on September 24, 2014, 04:52:50 PM
What exactly does the "Tie-Point limit" feature do? What does the default value of 1000 mean? And if you enter 0 (= infinite?) does this act the same as the previous version of PhotoScan?

http://support.esri.com/en/knowledgebase/GISDictionary/term/tie%20point (http://support.esri.com/en/knowledgebase/GISDictionary/term/tie%20point)
Setting it to 0 appears to behave the same (because if it actually used 0 tie points you wouldn't match any images  ;))
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: Alexey Pasumansky on September 24, 2014, 05:11:07 PM
Hello ThomasVD,

Tie-point limit defines the upper threshold for the number of projections present on each photo. So actually this parameter effects on the number of points in the sparse cloud. Using zero-value means no limit and the process in such case will work similar to version 1.0. However, if you input zero in Tools Menu -> Thin Tie-Points dialog all the points will be removed.

Note that in some cases the number of projections on some images can be slightly higher than limit.

Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: Alexey Pasumansky on September 24, 2014, 05:21:59 PM
Hello hengefjes,

And what is the output in the Console pane related to the tile export? In the export tiles dialog you need to specify export resolution, so the model should be properly referenced to fit these units.
Here's the console output:
Finished processing in 0 sec (exit code 1)
grid: 9x7x3 (5 levels)
Preprocessing images...
preprocessing images... done in 0.697 sec
Finished processing in 0.698 sec (exit code 0)
>>>


And what about the export settings and model referencing?
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: Patribus on September 24, 2014, 07:12:01 PM
Hello,

I found something that seams to be a bug. (at least I never saw this before).

When having a DPC on the display I see some points. When I now start to zoom in, they disappear gradually. You'll find a video of this here http://screenpresso.com/=Zbshe (http://screenpresso.com/=Zbshe)

Cheers
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: Mohammed on September 24, 2014, 08:10:40 PM
 Hi, there's a little problem with new version, i cant generate a mask from alpha channel i used all option without success. Is i'm doing some thing wrong, it works fine in version 1.0!! weird.
Thanks,,,   
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: Alexey Pasumansky on September 24, 2014, 08:35:27 PM
Hello Patribus,

Probably the points are closer to the viewpoint than the trackball (center of zoom and rotation)?
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: Alexey Pasumansky on September 24, 2014, 08:36:05 PM
Hello tornado2011,

Thanks, we'll check that. Is there any output in the Console pane?
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: Mohammed on September 24, 2014, 08:41:26 PM
Hi, Thanks Alexey for quick reply,

Here's it what appear in  Console pane!!

Loading photos...
Finished processing in 0.006 sec (exit code 1)
Generating masks...
Finished processing in 3.948 sec (exit code 1)
>>>
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: hengefjes on September 24, 2014, 10:46:18 PM
Hello hengefjes,

And what is the output in the Console pane related to the tile export? In the export tiles dialog you need to specify export resolution, so the model should be properly referenced to fit these units.
Here's the console output:
Finished processing in 0 sec (exit code 1)
grid: 9x7x3 (5 levels)
Preprocessing images...
preprocessing images... done in 0.697 sec
Finished processing in 0.698 sec (exit code 0)
>>>


And what about the export settings and model referencing?
The project is an interior with a local coordinate system. I thought the referencing was ok. I never really paid much attention to referencing, as I've used markers for scaling and external software for orientation - never understood how to work the referencing for my close range scenarios in Photoscan. I guess how to use the viewer will be explained in upcoming manuals - and what its intended to do.
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: nickponline on September 25, 2014, 05:57:36 AM
I'm just getting a Pinwheel after it starts. Using MacOS X 10.9.4 and PhotoScanPro :(
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: Alexey Pasumansky on September 25, 2014, 11:05:23 AM
Hello tornado2011,

We were unable to reproduce the problem with mask import from alpha-channel, all options work correctly.

Could you please check that original image contain alpha-channel and the Shading is turned on in the Photo view. If there are still problems please send the image file to support@agisoft.ru.
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: ThomasVD on September 25, 2014, 06:45:07 PM
Thanks Alex and BigBen for answering my question! So presumably setting a tie-point limit means photoscan only chooses the best matches and leaves out the others? Or is it purely a way to reduce processing time?
I guess what I'm asking is: what's the advantage of setting a tie-point limit :)
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: Kms1 on September 25, 2014, 11:39:55 PM
i have several education licenses of 1.04, will i be allowed to upgrade to 1.1.0 or will i have to repurchase??

thank you
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: bigben on September 26, 2014, 12:19:33 AM
Hello tornado2011,

We were unable to reproduce the problem with mask import from alpha-channel, all options work correctly.

I've experience this too. I'll do some testing when the current processing is finished.  I use LZW-compressed tif with single alpha channel from Photoshop.
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: bigben on September 26, 2014, 09:05:26 AM
I ended up exporting the alphas to PNG in Photoshop and then importing the masks. That worked OK.  I've sent a sample TIFF.
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: Alexey Pasumansky on September 26, 2014, 11:03:50 AM
Hello bigben,

Possibly the problem is due to the layer name. It seems to be Alpha 1 and may be incorrectly interpreted.
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: Alexey Pasumansky on September 26, 2014, 11:04:21 AM
Hello Kms1,

You can update the version freely up to versions 1.9.x.
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: Patribus on September 26, 2014, 11:38:46 AM
Hello Kms1,

You can update the version freely up to versions 1.9.x.

Hello Alexey,

maybe I missed it, but do you mean that starting from the 2.0 version I'll have to buy a new license? Or pay saome upgrade? How much would it be.
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: ppkong on September 26, 2014, 11:50:49 AM
Why can't export tiles feature use other formats? And cann‘t select the cubic export? And export time increase more than 20 times times
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: Alexey Pasumansky on September 26, 2014, 11:55:54 AM
Hello Patribus,

For the versions 2.0 there will be other license keys, but your current key will remain valid for the previous versions.
Currently I can't say anything about upgrade price, because it is a long way to the version 2.0.
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: ppkong on September 26, 2014, 12:15:16 PM
When I use the distributed processing tests, always prompt:can't load project
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: bigben on September 26, 2014, 02:22:31 PM
Hello bigben,

Possibly the problem is due to the layer name. It seems to be Alpha 1 and may be incorrectly interpreted.

Hi Alexey

I tested changing the name back to just alpha but that didn't work. Importing the masks from these images worked in 1.0, and I hadn't changed anything in the Photoshop action. I've tried old and new images but none worked.  I'll see if I can reproduce it on another computer.
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: Patribus on September 26, 2014, 02:43:41 PM
Hello,

I do not know if it was already reportet, but exporting the dense point cloud using PLY does not work for me.

I did now reinstall the old version and I did not have any problems exporting the DPC using the same project.

Cheers
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: Alexey Pasumansky on September 26, 2014, 09:44:45 PM
Hello Patribus,

Thank you for reporting, we'll fix it in the next update.
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: Alexey Pasumansky on September 26, 2014, 09:46:05 PM
Why can't export tiles feature use other formats? And cann‘t select the cubic export? And export time increase more than 20 times times
Hello ppkong,

TLS is intermeidate format with minimum settings, you can open it in Agisoft Viewer and convert to ZIP package, selecting settings that you've mentioned.
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: andyroo on September 28, 2014, 01:05:30 AM
I like the addition of the Export DEM and Export Orthophoto options, but one feature is missing that is critical to me - there is no way to select a coordinate system for export. I build the model in the native coordinate system for my GPS data (NAD 83 NSRS 2007 (which is the closest I can find to NAD 83 WA N CORS96), but export DEM in NAD83 UTM 10, and export ortho in WGS84.

It would be great if the export coordinate system could be specified. I am guessing that the project's default coordinate system is used.

Another feature that is missing from the DEM export (as far as how I use) is that there is no way to specify the cell interval. In other words, if I want multiple DEMs of the same area to all start on integer meters, or on 100s or 1000s meters, there is no way to control this through the batch dialog. This makes it impossible to export coincident (exactly overlapping) DEMs from the batch dialog.

But very cool addition. Could be a real time-saver if it fully supports the dialog box options.

Andy
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: Kiesel on September 28, 2014, 01:31:12 AM
Quote
Bisenberger: Can this version be installed alongside version 1.0.4, or does it overwrite it?

Yes you can, I have learnt this by Admir and I have just done it:

1. Copy your stable version folder "Photoscan" and rename it for example to "Photoscan_stable"
2. Deinstall Photoscan
3. Create a link to photoscan in the copied folder "Photoscan_stable"
4. Install pre-release

Now you have both versions parallel installed, you can try pre-release version and work with the stable version.


Karsten
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: mwillis on September 28, 2014, 02:22:00 AM
I can confirm that importing alpha channel masks is not working.

-Mark
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: Alexey Pasumansky on September 28, 2014, 07:55:39 AM
Hello Mark,

Then can you send any sample image with alpha on support@agisoft.ru?
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: bigben on September 28, 2014, 10:05:44 AM
I tested on 2 different systems, and also did a clean install. Tried images that had worked with PS1.0 but couldn't get alphas to import from tiffs.
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: slawek555 on September 28, 2014, 11:12:48 PM
Hi,
I`ve got problem in 1.1.0 build 1976 release with variable placeholders in path property, in export model batch process job. In 1.0.4 version things like {projectfolder} and {chunklabel} was working, it was really helpful then running longer renders with many chunks. Right now it doesnt work at all. Value for path like {chunklabel}.obj creates files {chunklabel}.obj, so it doesnt allow to batch process and export more than one chunk, because every of them except last one will be overwritten.
Should i use diffrent tokens for chunk label? Does that functionality changed? Im talking about standard version.
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: bigben on September 29, 2014, 10:28:23 AM
I tested on 2 different systems, and also did a clean install. Tried images that had worked with PS1.0 but couldn't get alphas to import from tiffs.

There is something weird going on here, although I'm not entirely sure what.  Working on the same project I updated my masks in Photoshop and tried re-importing them from PNG files.  Couldn't import for multiple files, but I could import for a single photo.

For multiple file imports console displays errors like this:

Can't load image:
c:\temp/filename.png

Note the forward slash before the file name.  Creating a new project and trying again, but now I can't get multiple PNGs to import the masks either.

Batch importing from alphas will clear any existing mask but not import the alpha, with no errors reported in the log
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: augeaz on September 29, 2014, 02:10:31 PM
Hi guys

I managed to get the beta on one of my computers.
I run one of the models on medium quality simultaneously on two PC one with stable PS and one with beta PS.
These are things I noticed so far.

1. beta is faster
2. beta can extract more points
3. beta has a lot of new useful tools
More points to come as I will keep exploring.

Below please find medium dense point cloud visual comparison stable vs beta.

(https://lh6.googleusercontent.com/-j-NGTy-Vk9E/VCk6n9hN3rI/AAAAAAAASk4/j2H9o5n5Hm4/s0/2014-09-29_11-55-28.png)
(https://lh4.googleusercontent.com/-vmmC3hxA-M0/VCk6hEoeunI/AAAAAAAASkw/C8SE8593-Mk/s0/2014-09-29_11-55-02.png)
(https://lh5.googleusercontent.com/-ovchXbgQwfc/VCk8I23gNPI/AAAAAAAASlE/OAGlOwzY9x8/s0/2014-09-29_12-01-56.png)
(https://lh6.googleusercontent.com/-NFVQEdU6jSw/VCk8Y18F_SI/AAAAAAAASlU/LaaBikgFe_0/s0/2014-09-29_12-03-01.png)

These gaps are all over the model using the same settings in beta and stable.

I hope it helps in bringing beta closer to RC.

Regards
Marcin
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: Alexey Pasumansky on September 29, 2014, 05:17:49 PM
I`ve got problem in 1.1.0 build 1976 release with variable placeholders in path property, in export model batch process job. In 1.0.4 version things like {projectfolder} and {chunklabel} was working, it was really helpful then running longer renders with many chunks. Right now it doesnt work at all. Value for path like {chunklabel}.obj creates files {chunklabel}.obj, so it doesnt allow to batch process and export more than one chunk, because every of them except last one will be overwritten.
Should i use diffrent tokens for chunk label? Does that functionality changed? Im talking about standard version.
Hello slawek555,

Thank you for reporting. Will try to fix it also in the next update.
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: andyroo on September 29, 2014, 09:29:31 PM
I caused a crash in beta build 1976 by running two instances exporting orthophoto tiles to two different directories.

Export properties were:

Projection: Geographic/WGS 84 (EPSG::4326)
Image blending mode: average
color correction: enabled
pixel size <default>
split in blocks (1024x1024)
region <unchecked>
write kml <unchecked>
write world file <checked>

No files were created.  Not sure if the crash would occur with a single instance, or with region  boundary set. Trying now with default region boundaries and one instance. Also occurred running a single instance, with region boundary set (threw two application errors). Here's my system event log and photoscan log:

Instance 1 (crash at 16:26:45)
Faulting application name: photoscan.exe, version: 1.0.0.1, time stamp: 0x541d54b3
Faulting module name: cholmod.dll, version: 0.0.0.0, time stamp: 0x53d15936
Exception code: 0xc000001d
Fault offset: 0x00000000000968e6
Faulting process id: 0x6dec
Faulting application start time: 0x01cfda9dbd0e61fb
Faulting application path: C:\Program Files\Agisoft\PhotoScan Pro\photoscan.exe
Faulting module path: C:\Program Files\Agisoft\PhotoScan Pro\cholmod.dll
Report Id: e87c742e-4766-11e4-9843-bc305bc9e488


Instance 2 (crash at 16:37:02)
Faulting application name: photoscan.exe, version: 1.0.0.1, time stamp: 0x541d54b3
Faulting module name: cholmod.dll, version: 0.0.0.0, time stamp: 0x53d15936
Exception code: 0xc000001d
Fault offset: 0x00000000000968e6
Faulting process id: 0xb564
Faulting application start time: 0x01cfda9f7edd5130
Faulting application path: C:\Program Files\Agisoft\PhotoScan Pro\photoscan.exe
Faulting module path: C:\Program Files\Agisoft\PhotoScan Pro\cholmod.dll
Report Id: 58385c1c-4768-11e4-9843-bc305bc9e488


Crash 3 (only one instance running, crash at 15:25:07 threw two errors)
Faulting application name: photoscan.exe, version: 1.0.0.1, time stamp: 0x541d54b3
Faulting module name: cholmod.dll, version: 0.0.0.0, time stamp: 0x53d15936
Exception code: 0xc000001d
Fault offset: 0x00000000000968e6
Faulting process id: 0x808c
Faulting application start time: 0x01cfdc109e8c61fc
Faulting application path: C:\Program Files\Agisoft\PhotoScan Pro\photoscan.exe
Faulting module path: C:\Program Files\Agisoft\PhotoScan Pro\cholmod.dll
Report Id: 76ce36a8-4827-11e4-9843-bc305bc9e488

and second error at same time
Windows cannot access the file  for one of the following reasons: there is a problem with the network connection, the disk that the file is stored on, or the storage drivers installed on this computer; or the disk is missing. Windows closed the program Agisoft PhotoScan because of this error.

Program: Agisoft PhotoScan
File:

The error value is listed in the Additional Data section.
User Action
1. Open the file again. This situation might be a temporary problem that corrects itself when the program runs again.
2. If the file still cannot be accessed and
   - It is on the network, your network administrator should verify that there is not a problem with the network and that the server can be contacted.
   - It is on a removable disk, for example, a floppy disk or CD-ROM, verify that the disk is fully inserted into the computer.
3. Check and repair the file system by running CHKDSK. To run CHKDSK, click Start, click Run, type CMD, and then click OK. At the command prompt, type CHKDSK /F, and then press ENTER.
4. If the problem persists, restore the file from a backup copy.
5. Determine whether other files on the same disk can be opened. If not, the disk might be damaged. If it is a hard disk, contact your administrator or computer hardware vendor for further assistance.

Additional Data
Error value: 00000000
Disk type: 0

Photoscan log
Code: [Select]
Calculating vertex colors...
processing nodes...  done in 0.772 sec
calculating colors... done in 123.381 sec
accumulating data... done in 12.571 sec
octree constructed in 0.182 sec
selected 5 cameras
preloading data... done in 0.788 sec
filtering depth maps... done in 5.751 sec
accumulating data... done in 2.397 sec
octree constructed in 0.001 sec
selected 22 cameras
preloading data... done in 2.649 sec
filtering depth maps... done in 36.8 sec
accumulating data... done in 12.986 sec
octree constructed in 1.211 sec
selected 8 cameras
preloading data... done in 0.839 sec
filtering depth maps... done in 6.818 sec
accumulating data... done in 4.008 sec
octree constructed in 0.323 sec
selected 22 cameras
preloading data... done in 2.328 sec
filtering depth maps... done in 54.172 sec
accumulating data... done in 9.154 sec
octree constructed in 0.4 sec
selected 39 cameras
preloading data... done in 3.925 sec
filtering depth maps... done in 145.937 sec
accumulating data... done in 19.667 sec
octree constructed in 0.423 sec
selected 10 cameras
preloading data... done in 1.138 sec
filtering depth maps... done in 20.698 sec
accumulating data... done in 4.029 sec
octree constructed in 0 sec
selected 1 cameras
preloading data... done in 0.284 sec
filtering depth maps... done in 0.03 sec
accumulating data... done in 0.941 sec
octree constructed in 0 sec
selected 2 cameras
preloading data... done in 0.432 sec
filtering depth maps... done in 0.834 sec
accumulating data... done in 1.125 sec
octree constructed in 0 sec
233898530 points extracted
Generating mesh...
generating 54671x15090 grid (0.00216833 resolution)
grid rasterized in 3.357 sec
filtering median... done in 6.523 sec
filtering idw... done in 16.098 sec
filtering median... done in 5.973 sec
constructed triangulation from 4010172 vertices, 8020338 faces
grid interpolated in 267.402 sec
 done in 774.076 sec
Saving project...
filtered borders in 82.66 sec
triangulating...saved project in 397.117 sec
Finished processing in 11221 sec (exit code 1)
 100000000 points 199995575 faces done in 1332.92 sec
Calculating vertex colors...
processing nodes...  done in 0.727 sec
calculating colors...  done in 420.568 sec
Finished processing in 12582.6 sec (exit code 1)
Finished processing in 0 sec (exit code 1)
Finished processing in 0 sec (exit code 1)
initializing renderer... initializing renderer... tessellating mesh...tessellating mesh...done (189783323 -> 189783323 faces)
done (196821131 -> 196821131 faces)
done in 573.358 sec
Raster size: 91872x29813
Estimating mosaic occupancy...
done in 584.312 sec
Raster size: 86752x22263
Estimating mosaic occupancy...
757 blocks used from 85x22 (40%)
Calculating color correction...
collecting control points... 963 blocks used from 90x30 (35%)
Calculating color correction...
collecting control points... collected 4555811 points in 1007.13 sec
collected 6001486 points in 1046.1 sec
analyzing 326 images... ************************************************************************************************************************************************************************************************************************************************************************************************************************************** done in 131.043 sec
estimating corrections...
disabled 108588 out of 4095380 points (rms error 0.082997)
bundle_adjust: analyzing 347 images... *********************************************************************************************************************************************************************************************************************************************************************************************************************************************************** done in 79.247 sec
estimating corrections...
disabled 49941 out of 4800762 points (rms error 0.0525449)
bundle_adjust:

Looks like I'll have to re-install the previous version and try...
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: Alexey Pasumansky on September 30, 2014, 05:53:33 PM
Hello Andy,

Have you submitted the crash report?

You can check the following folder if there are any pending crash reports: C:\Documents and Settings\<user-name>\Application Data\Agisoft\PhotoScan Professional Edition\Crash Reports\
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: xabierr on September 30, 2014, 11:11:57 PM
Hi Alexey,

Great new version! However, tried to use the fisheye support but the program crashed (no pending reports) while aligning (high quality) 173 14 Mpx photos on my laptop (i7 @ 2.8 GHz with 8 Gb RAM, Windows 7). Tried the same with 1.04 and worked (~5 hours). How much more memory does the fisheye support needs?

cheers,

Javier 
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: Alexey Pasumansky on September 30, 2014, 11:27:02 PM
Hello Javier,

Fisheye doesn't require any additional memory or processing time. So have you submitted the crash report, probably it is unrelated with the fisheye?
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: xabierr on October 01, 2014, 12:57:27 AM
no pending crash reports. just closes down just before alignment has finished.
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: andyroo on October 01, 2014, 03:30:32 AM
Hi Alexey, I am running Windows 7, and only found old crash reports in

C:\Users\[username]\AppData\Roaming\Agisoft\PhotoScan Professional Edition\Crash Reports\pending

(from may 2013)

Let me know if there's anything else I can do.

Andy
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: JMR on October 02, 2014, 02:34:10 PM
Please, dear friends, could you describe how do the so-called "non coded cross markers" should look like?
Thanks!
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: Alexey Pasumansky on October 02, 2014, 02:48:42 PM
Hello José,

It should look like the following sample:
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: macsurveyr on October 03, 2014, 01:09:32 AM
Using the new multiple photo tab functionality on a Mac is limited. I don't see any way of moving a tab to another tab group like I can on windows.

Am I missing something?

Tom
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: halonso on October 03, 2014, 05:42:30 AM
Hi,

The RSM after run Optimmize Photo Alignment not work as in version 1.0.4, made a change to the tool?

thank you

halonso
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: Alexey Pasumansky on October 03, 2014, 10:45:39 AM
Hello Tom,

Thank you for reporting, we'll check and fix that.
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: Alexey Pasumansky on October 03, 2014, 10:46:47 AM
Hello halonso,

Do you mean that the result of Optimization procedure is different based on the same camera alignment and with the same settings in 1.0 and 1.1?
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: ThomasVD on October 04, 2014, 06:01:28 PM
Two quick remarks on the new version:

1) Like someone already mentioned, ctrl + click to select multiple groups of pictures no longer works. Also in the previous version you could shift + click to select a whole series of photos, then ctrl + click on a next set without losing the ones you previously selected, and once again do shift + click to select a whole series. The result is that you could select certain groups of pictures together. This no longer works in the new version.

2) In the previous version you could add a marker to a chunk, select that marker in one picture, change the name, for instance from point 1 to point 100, and then all subsequent markers you added would automatically get names following from the highest number (ie next marker would automatically be 101 rather than 2). This was very useful when trying to align multiple chunks with marker-based align: the markers between chunk 1 and 2 would for instance be point 1-5, then for markers between chunk 1 and chunk 3 I would use points 101-105 etc. It was also useful for manually aligning pictures in different chunks, if you knew those chunks would later be merged, to avoid duplicate markers in different locations. In version 1.1 markers do not continue from the highest named marker, meaning you have to manually change the name of every single marker.
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: halonso on October 06, 2014, 04:39:43 PM
Hello halonso,

Do you mean that the result of Optimization procedure is different based on the same camera alignment and with the same settings in 1.0 and 1.1?

Hello Alexey,

Yes, if the same alignment.

Thank you.
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: Exhale on October 07, 2014, 04:59:37 AM
Hello Alexey,

When I import the camera positions from the latest version into beta version, it says  " Can't build point cloud "
So, is there any differences in their communication to each others ?
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: Alexey Pasumansky on October 07, 2014, 07:41:35 AM
Hello Exhale,

Are you sure, you are using build 1980?
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: Exhale on October 07, 2014, 03:37:50 PM
Are you sure, you are using build 1980?
Hi Alexey ,
Yes,  using build 1980 made a big difference. It works like a charm.   Thank you.

Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: augeaz on October 07, 2014, 10:59:51 PM
Hi

Did anyone try new batch command "export texture" and if so any luck using it as it always throw exit failed?

Regards
Marcin
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: andyroo on October 10, 2014, 10:21:43 PM
Looks like build 1980 is still crashing when trying to export tiled orthophotos with color correction and pixel averaging, as I reported before (http://www.agisoft.com/forum/index.php?topic=2883.msg15480#msg15480). This time I tried to build in batch using the default projection (although I really hope you add the option to set projection for the ortho and dem generation in batch). Again I didn't get any crash report generated in my AppData folder.  AppData folder is here:

C:\Users\[username]\AppData\Roaming\Agisoft\PhotoScan Professional Edition\Crash Reports

I searched my entire computer (all drives) for the report ID string (in the Error 1000 below). After that I deleted the pending reports and logfile in the crash reports folder, hoping that would re-start crash reporting. Let me know if you have any other ideas as to why Agisoft might not be generating a report...

When I look at what windows is telling me, with the two event errors together (ID 1000 and 1005 below) It looks like wondows closed Agisoft because cholmod.dll is trying to access/create a file with no name or on no disk (File: is blank and Error value is 00000000 and disk is 0).



Here's the last bit of the Agisoft Processing Log file:

-----------------------------------------------
initializing renderer... tessellating mesh...done (26990306 -> 26990306 faces)
done in 44.642 sec
Raster size: 39355x169802
Estimating mosaic occupancy...
1643 blocks used from 39x166 (25%)
Calculating color correction...
collecting control points... collected 14517763 points in 171.889 sec
analyzing 739 images... ******************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************* done in 154.04 sec
estimating corrections...
disabled 52479 out of 12387530 points (rms error 0.0596004)
bundle_adjust:
-------------------------------------------------


here's windows event log error report (ID 1000):

------------------------------
Faulting application name: photoscan.exe, version: 1.0.0.1, time stamp: 0x542eb65e
Faulting module name: cholmod.dll, version: 0.0.0.0, time stamp: 0x53d15936
Exception code: 0xc000001d
Fault offset: 0x00000000000968e6
Faulting process id: 0xd40
Faulting application start time: 0x01cfe424f6a7ffa8
Faulting application path: C:\Program Files\Agisoft\PhotoScan Pro\photoscan.exe
Faulting module path: C:\Program Files\Agisoft\PhotoScan Pro\cholmod.dll
Report Id: 60419174-5044-11e4-880e-bc305bc9e488
------------------------------------


The error 1000  was followed by a second event log error (ID 1005):

-------------------------------------
Windows cannot access the file  for one of the following reasons: there is a problem with the network connection, the disk that the file is stored on, or the storage drivers installed on this computer; or the disk is missing. Windows closed the program Agisoft PhotoScan because of this error.

Program: Agisoft PhotoScan
File:

The error value is listed in the Additional Data section.
User Action
1. Open the file again. This situation might be a temporary problem that corrects itself when the program runs again.
2. If the file still cannot be accessed and
   - It is on the network, your network administrator should verify that there is not a problem with the network and that the server can be contacted.
   - It is on a removable disk, for example, a floppy disk or CD-ROM, verify that the disk is fully inserted into the computer.
3. Check and repair the file system by running CHKDSK. To run CHKDSK, click Start, click Run, type CMD, and then click OK. At the command prompt, type CHKDSK /F, and then press ENTER.
4. If the problem persists, restore the file from a backup copy.
5. Determine whether other files on the same disk can be opened. If not, the disk might be damaged. If it is a hard disk, contact your administrator or computer hardware vendor for further assistance.

Additional Data
Error value: 00000000
Disk type: 0
---------------------------------/tt]

Note that I have been able to generate orthos after this with the previous version. I have no disk issue.

Andy
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: Alexey Pasumansky on October 16, 2014, 01:46:42 PM
Hello Andy,

Seems like the problem could be only reproduced on the older hardware.

The problem will be fixed in the next update, thank you for providing additional information.
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: aphextwin on October 16, 2014, 06:00:18 PM
Hi there,

on my two osx-machines I was not able to start a server or client-node by using the commands stated in the tutorial file. Is network-nodes not yet implemented for osx?

Thanks!
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: Alexey Pasumansky on October 16, 2014, 06:16:28 PM
Hello aphextwin,

On MacOS you need to do the following:

Code: [Select]
cd PhotoScanPro.app/Contents/MacOS/
./PhotoScanPro --node ...

Hope it works fine for you now.
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: mr map on October 17, 2014, 01:32:50 AM
Hello José,

It should look like the following sample:

Hi Alexay,
What will be minimum recognizable size of the four sector circle, in pixels?
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: MitoTheGreek on October 19, 2014, 12:56:10 PM
Hello,

Has anyone had any luck installing to a different drive?
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: r0xx on October 21, 2014, 12:21:17 PM
When I use the distributed processing tests, always prompt:can't load project

Having the same problem.... Any news on that?

Also it would be awesome to make individual nodes available between different times only... So for example to use 2 computers 24/7 to compute and to use 3 computers only between 7pm and 10am...
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: Alexey Pasumansky on October 21, 2014, 01:43:26 PM
Hello r0xx,

Could you please send the screenshots of the network settings on root and client to support@agisoft.com? Please also specify the OS you are using.
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: mwillis on October 21, 2014, 03:45:03 PM
Alexey, I just installed the latest build.  This time after install, it asks for my Activation Code. It hasn't done this since I purchased the software.  I have entered my code but it doesn't recognize it. I have tried several times and I'm sure there are not any typos.  Bug?

Mark
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: Alexey Pasumansky on October 21, 2014, 03:46:24 PM
Hello Mark,

Probably you've installed another edition?
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: mwillis on October 21, 2014, 04:28:13 PM
I have the stable version installed in another directory.  Would that cause it?
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: Alexey Pasumansky on October 21, 2014, 04:35:47 PM
Hello Mark,

Then please check that you are not using zero instead of O letter.
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: ppkong on October 22, 2014, 04:08:53 AM
Can I export model tiles in python script 1.1?
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: r0xx on October 22, 2014, 09:13:05 AM
Hello r0xx,

Could you please send the screenshots of the network settings on root and client to support@agisoft.com? Please also specify the OS you are using.

Will do right now! Thanks!
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: SuperNewb on October 23, 2014, 01:50:40 AM
Hi guys,

Maybe I'm missing something.  It seems that the markers are unable to be toggled on and off in this version.

Am I doing something wrong or is this purposefully shut down?
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: mwillis on October 23, 2014, 02:29:12 AM
My issue turned out to be a mistake on my part.  I downloaded the standard version of Photoscan by accident.  Sorry for my confusion.
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: Alexey Pasumansky on October 23, 2014, 07:45:49 AM
Hello SuperNewb,

Only markers with any source coordinate values can be checked/unchecked. As soon as any data is input for the marker it will be checked on automatically.
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: bmc130 on October 23, 2014, 03:08:26 PM
Is there any speed gains in 1.1 compared to the older version? I mean faster processing mesh and generating point clouds and so on?
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: SuperNewb on October 23, 2014, 05:41:04 PM
Hello SuperNewb,

Only markers with any source coordinate values can be checked/unchecked. As soon as any data is input for the marker it will be checked on automatically.

Thanks Alexey,

Another question though.  I use Tile export in obj format for use in Geoverse.  It works great for the converter package.  The Pre Release does not seem to offer the same export method, leaving only the option to export photoscan tiles for the viewer package. 

Is there any hope that the final release will hold on to the functionality to export the obj tiles that I need?

Thanks again
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: Alexey Pasumansky on October 23, 2014, 05:43:29 PM
Hello SuperNewb,

If you open TLS file in Agisoft Viewer, you will be able to convert it into one of the supported formats (like OBJ, COLLADA, OpenCTM and etc.) by choosing Convert option in the context menu after clicking on the *.tls line in the Playlist pane.
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: Alexey Pasumansky on October 23, 2014, 05:45:07 PM
Hello bmc130,

There were speed improvements for Estimating Scene Structure step for large datasets.
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: orpheas on October 25, 2014, 05:16:44 PM
Hi,

I have updated from Photoscan Pro 1.0.4 to version 1.1.0 in order to use my GPU, as version 1.0.4 was showing the same issue as describe here: http://www.agisoft.com/forum/index.php?topic=561.0

Once I have updated, photoscan was able to use the GPU but when I closed the application and restarted it, it no longer sees the opencl device and outputs the following in the console when I go to Preferences -> OpenCL
clGetPlatformIDs failed: error -1001

What I have tried so far is:
  - uninstall / reinstall photoscan (both version 1.0.4 and 1.1.0), same results
  - uninstall and purge old drivers and reinstall latest nvidia drivers (344.48), same results
  - found this related article in the forum, http://www.agisoft.com/forum/index.php?topic=2977.msg15682 , tried to install to a different path and still get the same results.

Since this happened when I updated to version 1.1.0 I thought I'd ask here.
I have had the same behavior on two systems and I was wondering if someone would have a suggestion on how to solve this.

Thanks in advance.


Orpheas
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: Alexey Pasumansky on October 25, 2014, 05:31:36 PM
Hello Orpheas,

Thank you for reporting. What graphic card you are using? Probably you can provide the log file from the beggining (open project and start dense cloud generation)?

We have tested latest nVidia drivers for several graphic cards with PhotoScan 1.1 and have not got such problems.
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: Helsky on October 25, 2014, 08:49:35 PM
Dear Agisoft Team,

I was very pleased reading "Added support for Cross (non-coded) target detection". However, do they need to be colored or does this work for gray scale images as well. Moreover, how many pixels should a target at least be in the image?
Thank you very much
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: orpheas on October 27, 2014, 01:26:23 PM
Hi Alexey,

Thanks for the quick response.
I have finished diagnosing this issue this weekend and it is not related to photoscan version 1.1.0.

This behavior is due to remote access of the computer via MS Terminal Services.

Sorry for reporting this before finishing the troubleshooting.


Orpheas
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: mwillis on October 31, 2014, 05:09:17 PM
In the current stable version of Photoscan Pro, you can "rotate object" on model that has ground control.  In the new beta, you can not rotate objects that have ground control.

I often assign arbitrary ground control to an object to establish scale and then rotate the object so it is in the proper orientation.  Would you please consider adding "rotate object" back as on option in future versions of PhotoScan?

Thanks
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: Alexey Pasumansky on October 31, 2014, 05:18:58 PM
Hello Mark,

If you are using scale bars to set up the reference distance, then you'll see [ S ] (scaled) sign next to the chunks' label in the Workspace pane, in this case it is possible to re-orient the model using Rotate Object tool.
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: mwillis on November 02, 2014, 04:36:52 PM
Hi Alexey, I'm using actual ground control points.  After the object is scaled using ground control, I rotate the object for best DEM extraction angle.  I'm not doing this with aerial photography (although it can be useful there as well).  I can email you and example, if that'll help.

Thanks,

Mark
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: Alexey Pasumansky on November 02, 2014, 05:53:09 PM
Hello Mark,

But probably it will be easier to user projection plane defined by markers or even use Current view?
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: Alexey Pasumansky on November 03, 2014, 06:07:26 PM
This time I tried to build in batch using the default projection (although I really hope you add the option to set projection for the ortho and dem generation in batch).
Hello Andy,

Build 1985 now allows to choose export coordinate system in the Batch export orthophoto/DEM.
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: kgrover on November 03, 2014, 11:41:06 PM
I am just getting into using the Pro version, and really like the new batch export capabilities for orthos, etc.

In looking at the new beta, it doesn't look like the classify ground function is available in the batch mode, nor is the option to use specific classifications only in the build mesh function.

I was looking at scripting in python, and it looks like the classification can be done this way, but not to limit the build mesh to ground classification only. It doesn't seem to be accessible.

With the datasets I am processing i was really looking for this functionality if there was a way.

Kevin
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: KoStyaN on November 04, 2014, 12:55:20 PM
Hi!
In version 1.1.0 kml generates with coordinates: 4.7254278327946643e+001
in 1.0.4 there was 47.254278327946643

Can you fix it?
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: Alexey Pasumansky on November 04, 2014, 03:22:46 PM
Hello Kevin,

Using Python you can classify dense cloud and build mesh base on certain classes. We'll also try to implement this functionality in Batch Process for the final release.
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: Alexey Pasumansky on November 04, 2014, 03:23:30 PM
Hello KoStyaN,

I think we'll fix that, but is there any practical difference or just user convenience?
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: mwillis on November 05, 2014, 07:33:36 AM
Hi Alexey, I sent a detailed email with my workflow and why rotating a model with a ground control is important.

Thanks,

Mark
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: kgrover on November 05, 2014, 11:06:05 PM
Hi Alexey,

You indicate the classifications are accessible by python when building a mesh, but I couldn't figure out how to do this, nor can I find much on classifications in the python manual. This what I have for building a mesh, but now want to only build with ground class.

chunk.buildModel( surface=PhotoScan.HeightField , face_count = PhotoScan.MediumFaceCount )

What would I add??

Kevin
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: Alexey Pasumansky on November 06, 2014, 12:18:10 AM
Hello Kevin,

Please check the following topic:
http://www.agisoft.com/forum/index.php?topic=2976.0

also please note that you can use autocomplete functionality in the Console pane (CTRL + Space) to get tips on the functions.
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: James Dietrich on November 06, 2014, 05:03:43 PM
Alexey,

Great work on the latest version. I came across a small bug in the latest posted version (1.1.0 build 1985), in the photo view the Next/Previous hotkeys ( Ctrl + ] , [ ) don't seem to be working. All of the other hotkeys for selection and navigation work just fine.

Thanks,
James
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: Alexey Pasumansky on November 06, 2014, 05:07:55 PM
Hello James,

We've changed these hotkeys to PgUp and PgDn.
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: kenwoods1 on November 06, 2014, 11:48:42 PM
So I think I'm seeing a bug in the linux version related to clustering.

I'm working on the node controller, open a bunch of images, do a save as..., then choose the "unpacked project" selection, and save the file to the shared location.

The file that saves does not have an extension.

If I then run the alignment or try to build a product, nothing is passed to the processing nodes.

However, if I
"cp project project.psx"
AND
"cp project project.psz"

and then try, the information is passed off to the processing nodes and works as expected.


There are no logs to report if the extensions are not there---it doesn't return anything.

Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: Alexey Pasumansky on November 07, 2014, 01:04:22 AM
Hello kenwoods1,

Thanks for reporting. Will add some error message.

Unpacked project really should have .psx extension.
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: KoStyaN on November 07, 2014, 09:25:35 AM
Is it possible save fisheye as default calibration?
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: anaana on November 07, 2014, 11:52:43 AM
Hello,
I have some problems with panorama view, when I create a new camera group put my photos there and aligning them i i see nothing at mt model display.... Did somebod already try this option?
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: Alexey Pasumansky on November 07, 2014, 12:02:50 PM
Hello anaana,

And have you switched camera group type to the Camera Station in the Workspace pane prior to alignment process?
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: anaana on November 07, 2014, 12:18:07 PM
Yes, i created the camera group and than ser the group type to Station, after i clicked to align photos and at the end of process i had nothing on me model display.
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: Alexey Pasumansky on November 07, 2014, 12:40:53 PM
Hello anaana,

Then maybe you can provide us this problematic dataset on support@agisoft.com, so that we can check the problem?
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: anaana on November 07, 2014, 12:54:59 PM
Ok, thank you.
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: eriks on November 11, 2014, 07:45:27 PM
Photoscan 1.1.0 build 1985 now gives the error shown below and a bluescreen "System_Service_Exception" when building a pointcloud out of 7 chunks.
a brand new PC(intel i7-5930) with windows 8.1 and 2x GeForce GTX 980 (NVIDIA driver 344.48)
have 64Gb ram, 10 of 12 cpu cores active, and the two graphics cards active as OpenCL.
is it software or hardware failure?


1 blocks: 170
calculating match counts... done in 0 sec
overlapping groups selected in 0 sec
1 blocks: 170
final block size: 170
adding 10951 points, 144 far (12.272 threshold), 0 inaccurate, 15 invisible, 15 weak
3 sigma filtering...
adjusting: xxxxxxxx 1.79733 -> 1.79721
point variance: 1.79934
adding 14 points, 779 far (5.39803 threshold), 0 inaccurate, 7 invisible, 5 weak
adjusting: xxxxxxxxxxx 1.26301 -> 1.24688
point variance: 1.24836
adding 107 points, 689 far (3.74508 threshold), 0 inaccurate, 6 invisible, 6 weak
adjusting: xxxxxxxxxxx 1.07205 -> 1.06824
point variance: 1.06955
adding 387 points, 726 far (3.20864 threshold), 1 inaccurate, 6 invisible, 5 weak
adjusting: xxxxxxxxxxx 0.996641 -> 0.995105
point variance: 0.996358
adding 595 points, 757 far (2.98908 threshold), 1 inaccurate, 5 invisible, 3 weak
adjusting: xxxxxxxx 0.965478 -> 0.964742
point variance: 0.965969
adding 709 points, 795 far (2.89791 threshold), 1 inaccurate, 5 invisible, 5 weak
optimized in 1.954 seconds
coordinates applied in 0 sec
Optimizing point cloud...
adjusting: xxxxxxxxxxx 0.883686 -> 0.844905
coordinates applied in 0 sec
Optimizing point cloud...
adjusting: xxxxxxxxxxx 0.910176 -> 0.89795
coordinates applied in 0 sec
Optimizing point cloud...
adjusting: xxxxxxxxx 0.929815 -> 0.925034
coordinates applied in 0 sec
Optimizing point cloud...
adjusting: xxxxxxxxxx- 0.94085 -> 0.929951
coordinates applied in 0 sec
Optimizing point cloud...
adjusting: xxxxxxxxxxxxxxx 0.938584 -> 0.932644
coordinates applied in 0 sec
Optimizing point cloud...
adjusting: xxxxxxxx 0.937024 -> 0.931951
coordinates applied in 0 sec
Optimizing point cloud...
adjusting: xxxxxxxxxxxxxx 0.947859 -> 0.941533
coordinates applied in 0 sec
Saving project...
saved project in 1.594 sec
clGetDeviceInfo(CL_DEVICE_GLOBAL_MEM_SIZE) failed: CL_OUT_OF_RESOURCES
clGetDeviceInfo(CL_DEVICE_GLOBAL_MEM_SIZE) failed: CL_OUT_OF_RESOURCES
ocl_engine.cpp line 177: clGetDeviceInfo(device_id, CL_DEVICE_MAX_MEM_ALLOC_SIZE, sizeof(max_mem_alloc_size), &max_mem_alloc_size, NULL) failed, error CL_OUT_OF_RESOURCES
clGetDeviceInfo(CL_DEVICE_GLOBAL_MEM_SIZE) failed: CL_OUT_OF_RESOURCES
clGetDeviceInfo(CL_DEVICE_GLOBAL_MEM_SIZE) failed: CL_OUT_OF_RESOURCES
ocl_engine.cpp line 177: clGetDeviceInfo(device_id, CL_DEVICE_MAX_MEM_ALLOC_SIZE, sizeof(max_mem_alloc_size), &max_mem_alloc_size, NULL) failed, error CL_OUT_OF_RESOURCES
clGetDeviceInfo(CL_DEVICE_GLOBAL_MEM_SIZE) failed: CL_OUT_OF_RESOURCES
clGetDeviceInfo(CL_DEVICE_GLOBAL_MEM_SIZE) failed: CL_OUT_OF_RESOURCES
ocl_engine.cpp line 177: clGetDeviceInfo(device_id, CL_DEVICE_MAX_MEM_ALLOC_SIZE, sizeof(max_mem_alloc_size), &max_mem_alloc_size, NULL) failed, error CL_OUT_OF_RESOURCES
clGetDeviceInfo(CL_DEVICE_GLOBAL_MEM_SIZE) failed: CL_OUT_OF_RESOURCES
clGetDeviceInfo(CL_DEVICE_GLOBAL_MEM_SIZE) failed: CL_OUT_OF_RESOURCES
ocl_engine.cpp line 177: clGetDeviceInfo(device_id, CL_DEVICE_MAX_MEM_ALLOC_SIZE, sizeof(max_mem_alloc_size), &max_mem_alloc_size, NULL) failed, error CL_OUT_OF_RESOURCES
clGetDeviceInfo(CL_DEVICE_GLOBAL_MEM_SIZE) failed: CL_OUT_OF_RESOURCES
clGetDeviceInfo(CL_DEVICE_GLOBAL_MEM_SIZE) failed: CL_OUT_OF_RESOURCES
ocl_engine.cpp line 177: clGetDeviceInfo(device_id, CL_DEVICE_MAX_MEM_ALLOC_SIZE, sizeof(max_mem_alloc_size), &max_mem_alloc_size, NULL) failed, error CL_OUT_OF_RESOURCES
clGetDeviceInfo(CL_DEVICE_GLOBAL_MEM_SIZE) failed: CL_OUT_OF_RESOURCES
clGetDeviceInfo(CL_DEVICE_GLOBAL_MEM_SIZE) failed: CL_OUT_OF_RESOURCES
ocl_engine.cpp line 177: clGetDeviceInfo(device_id, CL_DEVICE_MAX_MEM_ALLOC_SIZE, sizeof(max_mem_alloc_size), &max_mem_alloc_size, NULL) failed, error CL_OUT_OF_RESOURCES
clGetDeviceInfo(CL_DEVICE_GLOBAL_MEM_SIZE) failed: CL_OUT_OF_RESOURCES
clGetDeviceInfo(CL_DEVICE_GLOBAL_MEM_SIZE) failed: CL_OUT_OF_RESOURCES
ocl_engine.cpp line 177: clGetDeviceInfo(device_id, CL_DEVICE_MAX_MEM_ALLOC_SIZE, sizeof(max_mem_alloc_size), &max_mem_alloc_size, NULL) failed, error CL_OUT_OF_RESOURCES
Saving project...
saved project in 1.531 sec
Finished processing in 44855.2 sec (exit code 1)
Agisoft PhotoScan Version: 1.1.0 build 1985 (64 bit)
OpenGL Vendor: NVIDIA Corporation
OpenGL Renderer: GeForce GTX 980/PCIe/SSE2
OpenGL Version: 4.4.0 NVIDIA 344.48
Maximum Texture Size: 16384
Quad Buffered Stereo: not enabled
ARB_vertex_buffer_object: supported
ARB_texture_non_power_of_two: supported
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: r0xx on November 12, 2014, 01:05:04 PM
Is there any best practice to automatically close a node without causing errors? Is there any command to stop it, let it finish and then close without me having to force kill it?
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: Alexey Pasumansky on November 12, 2014, 01:33:46 PM
Hello eriks,

Could you please run any stress tests for OpenCL computations? Unfortunately, we still haven't yet got test configuration with GTX980, so can't check if the issue is reproducible.
Title: About tiles export
Post by: ppkong on November 13, 2014, 10:48:57 AM
It's very useful that add export tiles function in photoscan 1.1.But I think there are several points to continuous improvement.
1.Python Scripting should be support output tiles;
2.Output tiles in ps1.1 version speed significantly slower than the ps1.0;
3.After output tiles must be use Agisoft Viewer to open it and convert to other formats,and every time you can convert only one *.TLS file,and the number of tiles mesh cannot be based on actual model number of the output;
So I think it should support output data different format;
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: eriks on November 13, 2014, 12:53:06 PM
hi, yes, I have been running some stress-tests on the dual GTX980's getting their core temperature quite high above 80degrees with still no problems. But that test was   https://unigine.com/products/heaven/   which I think tests DirectX.
Do you have an recommended OpenCL stress test, or is    http://www.geeks3d.com/20140917/msi-kombustor-3-5-0-gpu-burn-in-stress-test-opengl-opencl-benchmark  possibly an good test? 
At the moment, There are some 55 hours remaining on another process on that computer so I am not touching it until Monday.

thanks, ErikS
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: Alexey Pasumansky on November 17, 2014, 06:31:16 PM
Hello Erik,

Since the problem is related to OpenCL it's better to run OpenCL test. We can't recommend any special test, so probably the one you've mentioned would be fine.

In the related topic you can find that GTX 980 works fine on the latest nVidia drivers with PhotoScan 1.1.0: http://www.agisoft.com/forum/index.php?topic=1868.msg16292#msg16292
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: StevenF on November 18, 2014, 01:14:34 AM
PhotoScan.Chunk.copy() is causing PhotoScan to crash on v 1.1.0 build 1985 (64 bit). I submitted a crash report.
Here is a simple work around in case anyone else working with the beta is having this problem:

doc = PhotoScan.app.doc

# create a copy of the document
doc2 = PhotoScan.Document()
doc2.open(doc.path)

# append to current document
doc.append(doc2)

# remove unwanted chunks if necessary
doc.remove(doc.chunks[-1])
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: Alexey Pasumansky on November 18, 2014, 12:37:00 PM
Hello Steven,

Thanks for reporting, however, we haven't been able to reproduce the problem with crashes.

But as for the creating duplicated copies of chunks and adding them to the existing document, we will try to implement this functionality in Python API.
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: James on November 18, 2014, 09:54:43 PM
I can't see any perceivable difference when either texturing or generating orthophoto, with or without colour correction enabled, in Photoscan Pro 64 bit build 1985 on windows 8.1.

At first I thought it was working because the colours seemed nice and even although the photos were fairly poor, but there were still some seams visible. So i tried with colour correction disabled and I couldn't see any difference. I tried both orthophoto and texturing with mosaic blending (4096x4). The processing time seems very similar too, which surpised me as colour correction used to take ages.

I am working with ~200 ~9MP TIF images.
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: StevenF on November 19, 2014, 01:53:12 AM
Hello Steven,

Thanks for reporting, however, we haven't been able to reproduce the problem with crashes.

But as for the creating duplicated copies of chunks and adding them to the existing document, we will try to implement this functionality in Python API.

Hi Alexey,
It could be my install. I'm working with the 64-bit Linux version which fails on the chunk.copy() command. I just downloaded the Windows 64-bit version and it worked fine. I load in a project and execute the following at the console:
import PhotoScan
doc = PhotoScan.app.document
chunk = doc.chunk
chunk2 = chunk.copy()
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: Alexey Pasumansky on November 19, 2014, 02:59:14 PM
Hello James,

I've just checked color correction option and it took much longer time in the latest pre-release than export without any correction. Do you have any log information saved related to the both processes?
Even in the version 1.1.0 there were some optimizations for the color correction (speed up gained on the AVX supported systems), the procedure still requires quite a lot time.
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: andyroo on November 24, 2014, 03:52:38 AM
I have had good success running a few jobs generating orthos and DEMs in batch mode and setting coordinate systems with build 1985. This is very nice for the color correction step, since it takes several hours on my machine with 1000 - 2000 images.

One thing still lacking is ability to control cell center/corner coordinates. This is critical to generate concurrent rasters (exactly overlapping cells), which is important for accurate surface comparison.

The simplest way that I can think of to implement that would be to round the DEM extent/corners to the resolution of the DEM (so that if for instance I select a 1 m cell size, the bounds would be rounded to the nearest integer, if I select a 0.5 meter cell size, the bounds would be rounded to the nearest 0.5 m, if I set a 0.1 degree cell size my bounds are set to the nearest 0.1 degree... etc.

The default resolution (0 in current beta) could be left as a way to not implement any rounding and use the maximum resolution from the data.

The other way I can think of would be to add an option (like a checkbox + value field) to specify the rounding interval for cell corners. If the box is unchecked, then default bounds would be used. Either of these options don't seem like they would limit current functionality at all.
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: andyroo on November 25, 2014, 03:07:43 AM
One other thought on batch processing, orthos, and DEMs - when the user selects "save project after each step" currently Photoscan saves after any batch step is complete.

This  doesn't seem necessary for batch "export" actions since they don't modify the project. In my case it can take around 30 minutes to save a project, so it would be more efficient to not save after export ortho and DEM.

Andy
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: augeaz on November 29, 2014, 07:58:23 PM
Hi Alexey

What are the chances of having an option to export cameras in batch same as import option please.

Regards
Marcin
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: stpu on December 01, 2014, 03:18:54 PM
Hi,

will it be possible in the final version to export undistorted images with more than 3 bands?

Thank you.

Stefano
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: ppkong on December 02, 2014, 11:27:17 AM
There are some problems in version 1995, the texture looks like it has some errors.
Another question about AgiSoft Viewer,When I save a playlist and reload playlist(Open Playlist),I can't see anything untill I press F5.
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: Alexey Pasumansky on December 02, 2014, 12:48:55 PM
Hello Andy,

We'll try to add this feature in the next update. As for the autosave operations, you can use Save task in the Batch Process dialog.


Hello Martin,

We'll check if it could be easily implemented for the next update.


Hello Stefano,

Next update will include the fix for the correct undistort of the multi-band files.
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: Alexey Pasumansky on December 02, 2014, 05:38:30 PM
Hello ppkong,

Maybe you can provide the project file for the further problem studying?
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: kenwoods1 on December 03, 2014, 02:15:08 AM
We have processed a set of aerial photos using Photoscan Pro Linux version and the same photo set with Photoscan Pro Windows version with completely different results. The main issue is that a large sections of the survey area was not constructed during dense point cloud generation in the Linux version, but was constructed completely and accurately in the Windows version (see attached screenshots). We went through many interations of processing, making subtle adjustments to the workflow, but in the end achieve the same unsatisfactory result in on the Linux system. The Linux DPC results makes it impossible to generate accurate DSM and orthophotos. 

The standard photoscan workflow was used in both projects. Camera position coordinates are in WGS84 (EPSG 4326).  Latitude = column 4, Longitude = column 5, Elevation = column 6. We used a 20 cm camera accuracy parameter and optimized with the default settings after running a high-quality alignment using our camera reference coordinates. After unchecking a few photos with high positional errors, we re-optimized and got total errors under 15 cm.


I can supply the images and more details----There's 1500, 23MB jpgs.
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: andyroo on December 03, 2014, 06:38:23 AM
I discovered an interesting issue with alignment that affects builds 1985 and 1995. I aligned photos, added control, then optimized alignment and saved/exited.

Later I added more GCPs at one of the ends of the flight and re-optimized, but I wasn't getting any change in calculated error of GCPs.

I saved the project as a version 1.0 file and ran the optimize step in 1.0 and the images were realigned to minimize the error (from 19 m and 13 m on the two additional GCPs down to 0.2cm or less), but when I ran the optimize step on the 1.0 file with 1.1 build 1995, there was no change.

I don't know why it's not further optimizing. Can share entire project or just project files.
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: James on December 03, 2014, 01:31:45 PM
I discovered an interesting issue with alignment that affects builds 1985 and 1995. I aligned photos, added control, then optimized alignment and saved/exited.

Later I added more GCPs at one of the ends of the flight and re-optimized, but I wasn't getting any change in calculated error of GCPs.

I saved the project as a version 1.0 file and ran the optimize step in 1.0 and the images were realigned to minimize the error (from 19 m and 13 m on the two additional GCPs down to 0.2cm or less), but when I ran the optimize step on the 1.0 file with 1.1 build 1995, there was no change.

I don't know why it's not further optimizing. Can share entire project or just project files.

I had the same problem, i learned that it was because there were some cameras in the reference pane which had 0 projections, as a result of either manually removing points from the sparse cloud or using the gradual selection tools.

you can sort the cameras by number of projections (it's the rightmost column and often not visible without scrolling horizontally), then select those cameras with 0 or very few projections, and either remove them or align them again (using align selected cameras).
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: chrismaclean on December 03, 2014, 06:16:23 PM
Hi Guys,

Testing the 1995 release and  OpenCL hard crashes my solve box when using it.  OpenCL works fine with 1.0.4.  Leaving OpenCL off in 1995 everything runs fine.

*Running Centos 6 and two Titans.  Is there a specific OpenCL version I should be testing with for Linux?

Thanks.
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: andyroo on December 03, 2014, 11:02:05 PM
I had the same problem, i learned that it was because there were some cameras in the reference pane which had 0 projections, as a result of either manually removing points from the sparse cloud or using the gradual selection tools.
I have one (disabled) camera with one projection, and a fair number of un-aligned cameras that are blank for projection, but nothing showing 0 projections. Since this behavior doesn't happen when I process the same project in v1.0, it seems like a bug in the current beta. Especially since I just saved the project file as a 1.0 format file, and optimized with 1.0 and it worked fine.
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: Alexey Pasumansky on December 03, 2014, 11:56:36 PM
I have one (disabled) camera with one projection, and a fair number of un-aligned cameras that are blank for projection, but nothing showing 0 projections. Since this behavior doesn't happen when I process the same project in v1.0, it seems like a bug in the current beta. Especially since I just saved the project file as a 1.0 format file, and optimized with 1.0 and it worked fine.

Hello Andy,

We suggest to reset camera alignment for all the cameras that have <5 projections prior to optimization.

Please also provide the console pane output related to the optimization that doesn't do anything in 1.1.
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: Alexey Pasumansky on December 04, 2014, 04:34:09 PM
Hello Steven,

Thanks for reporting, however, we haven't been able to reproduce the problem with crashes.

But as for the creating duplicated copies of chunks and adding them to the existing document, we will try to implement this functionality in Python API.

Hi Alexey,
It could be my install. I'm working with the 64-bit Linux version which fails on the chunk.copy() command. I just downloaded the Windows 64-bit version and it worked fine. I load in a project and execute the following at the console:
import PhotoScan
doc = PhotoScan.app.document
chunk = doc.chunk
chunk2 = chunk.copy()


Hello Steven,

Please check latest build 1995.

You can use doc.addChunk(chunk.copy()) for duplicating.
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: StevenF on December 04, 2014, 08:49:38 PM
Hi Alexey,
Copying chunks appears to work in the new build for Linux 64 bit Pro. Thank you.
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: andyroo on December 04, 2014, 09:09:07 PM
We suggest to reset camera alignment for all the cameras that have <5 projections prior to optimization.

Please also provide the console pane output related to the optimization that doesn't do anything in 1.1.

Hi Alexey,

If I try to optimize without resetting alignment for the cameras with no value in the  [Projections] column, I get this in the console:

Optimizing point cloud...
adjusting: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! 17.9803 -> 17.9803
coordinates applied in 0 sec
Finished processing in 50.109 sec (exit code 1)


I removed the single camera with one projection and got the same thing. Then I removed all of the cameras with blank projection values and successfully optimized in 1.1:

Optimizing point cloud...
adjusting: xxxxxxxxxxxxx- 17.9803 -> 1.14188
coordinates applied in 0 sec
Finished processing in 23.031 sec (exit code 1)


Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: ppkong on December 08, 2014, 04:28:32 AM
Hello ppkong,

Maybe you can provide the project file for the further problem studying?
I think this problem is caused because I used the distortion corrected image with black edges, by the way the black edge because when I distortion correction chose "Center principal point" caused.
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: eriks on December 08, 2014, 06:10:01 PM
This time I tried to build in batch using the default projection (although I really hope you add the option to set projection for the ortho and dem generation in batch).
Build 1985 now allows to choose export coordinate system in the Batch export orthophoto/DEM.

Can you please also allow us to choose coordinate system projection for exporting point clouds like we now can do for exporting orthophotos?
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: Alexey Pasumansky on December 09, 2014, 03:32:01 PM
Hello eriks,

We'll try to include this option in the final 1.1 release.
Meanwhile build 1998 has region selection option in the Batch Process -> Export DEM/Orthophoto. And split in blocks option for batch point cloud export has been added.
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: eriks on December 12, 2014, 02:08:45 AM
Thanks Alexey!
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: Kjellis85 on December 12, 2014, 05:14:59 PM
all of a sudden I can't import markers! I haven't done anything except from trying to detect some old markers, then after that failed I manually registered the markers, but when I try to import nothing happens in the marker section and the model is still not georeferenced. I tried the latest version 1998 but to no avail.

To be sure of the problem I tried an old job that I georeferenced yesterday, in the same version as the first try that failed, and now that won't get georeferenced with new data. I tried removing a marker and adding it from the same file but nothing happens.
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: Alexey Pasumansky on December 12, 2014, 05:19:13 PM
Hello Kjellis85,

Are you using Export/Import markers options in the Tools menu?

Are there any error messages in the console pane?
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: augeaz on December 12, 2014, 10:46:24 PM

Hello Martin,

We'll check if it could be easily implemented for the next update.


Thank you, looking forward it.
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: andyroo on December 12, 2014, 11:24:06 PM
Version 1998 still has the same issue/feature - I have to reset alignment on cameras with no projections before optimizing, or the optimization will fail.
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: Kjellis85 on December 15, 2014, 12:39:34 PM
Hello Kjellis85,

Are you using Export/Import markers options in the Tools menu?

Are there any error messages in the console pane?

I am using my regular workflow, import "button" in reference section. My GCPs are stored as plain text, like this:

6654,7742522.307,659135.905,14.606,target 43
6655,7742524.167,659137.788,14.861,target 45
6656,7742522.920,659140.087,14.950,target 47

I set column values to label: 5 easting: 3 northing: 2 altitude: 4

This has always worked, but after going up to version 1.1 it fails to import anything.
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: Alexey Pasumansky on December 15, 2014, 12:54:03 PM
Hello Erik,

I've tried to create sample text file with your data and got no problems with the coordinate information import to the Reference pane.

Do you see proper column segregation in the Import CSV dialog? Do you have already GCPs with the corresponding labels?
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: Kjellis85 on December 15, 2014, 12:59:47 PM
Ok... there must be something severely wrong with my computer. It suddenly worked! I did not change anything other that rebooting the computer. I will see if I can recreate the problem, but so far everything works fine.
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: Kjellis85 on December 16, 2014, 01:25:15 PM
Don't know if it is a bug or if it is a change, but photoscan won't detect any markers from pre 1.1 versions, or at least not any I have tried. Is this due to a change in markes? If so, would it be possible to include an option for compatibility with previous version markers? Otherwise it will make a lot of our previous work hard to reproduce from scratch.
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: Alexey Pasumansky on December 16, 2014, 01:39:13 PM
Hello Kjellis85,

Do you mean coded targets that were printed from older versions? If you do not wish to re-print new targets from latest 1.1.0 version, then you should check on "Disable parity" option in the Detect Markers dialog.
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: andrekje on December 18, 2014, 02:08:25 AM
Would you please fix the missing file extensions when saving in Linux ?
to reproduce:
save project , enter filename "test"  - and observe that there is no extension on the saved file.
This must be hell for new users that don't know what extension the file is supposed to have.
same problem for many, but not all, exports/other saved files.
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: andyroo on December 18, 2014, 11:56:25 PM
I think I noticed this before (earlier version) and forgot to mention, but when registering GCPs and moving from image to image with [PageUp]/[PageDn] keys, I can't turn my gray wisp into a green flag without moving the mouse/trackball. In other words, let's say I want to speed through a bunch of targets by hitting [PgDn]/<click> and I don't want to move the auto-positioned target at all. I have to carefully move my mouse off and back on the location of the gray wisp each time instead of just lifting my mouse off of the table and pressing [PgDn]/<click> [PgDn]/<click> [PgDn]/<click> [PgDn]/<click> [PgDn]/<click>.

Since for my current project I typically position around 2000 makers per flight, this painfully increases the time it takes.

But I think the same thing happens in 1.0, so I don't know if this is really a comment that belongs in the beta thread. Sorry if it doesn't.
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: andyroo on December 19, 2014, 04:42:04 AM
Batch Process/Save Job/Path defaults to <C:\Program Files\Agisoft\PhotoScan Pro> on my install each time. It would be great if the location of the previous Save Job path was remembered between sessions.
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: mirijovsky on December 21, 2014, 12:31:38 AM
Hello,

do you prepare any new functionalities for orthophoto exporting? Seam lines editor would be very, very helpful. Something similar as in Pix4D.

Best,
Jakub
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: Alexey Pasumansky on December 21, 2014, 02:23:15 PM
Build 2001 has been just published.

Main changes according to the latest requests:
- coordinate system selection in Batch Process -> Export Mode/Points dialogs,
- added world file option for Batch Process export options,
- added Classify Ground Points option for Batch Process,
- added class selection option for Batch Process -> Build Model,
- automatic alignment reset for cameras that could not be optimized (when Optimize feature is used).

Also tiled model export  is now optimized for network (distributed) processing option.
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: ppkong on December 22, 2014, 09:21:43 AM
Build 2001 has been just published.
^
I had download and found the version is 2002 ;)
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: Alexey Pasumansky on December 22, 2014, 11:11:44 AM
Yes, actually there were two updates yesterday :)
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: ppkong on December 24, 2014, 08:51:38 AM
Can I export model tiles use Python API?
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: Alexey Pasumansky on December 24, 2014, 07:09:33 PM
Hello ppkong,

Currently this export option is not yet implemented in Python API.
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: andyroo on December 25, 2014, 01:22:41 AM
Top progress bar on color correction doesn't show progress during individual steps.

I've attached a screenshot showing what my progress showed for I think the whole several hours of RBA. I don't know how many hours, but >3. I was largely through the RBA phase of color correction when I took the screenshot, but it showed 100% all through this phase, at least the several hours that were ongoing when I came in this AM.

This isn't a big issue but would help me get a better idea of the value vs timesink of color correction. I've been debating whether to include it or not, and I think I'll generate another ortho without when this is done to compare processing times. I've included the logfile excerpt, showing where I was as of when the pic was posted. Note that the top progress bar did reset to show progress during the rendering of individual tiles (ongoing now):

Code: [Select]
initializing renderer... tessellating mesh... done (486452588 -> 486452588 faces)
done in 1187.85 sec
Raster size: 7987x26779
Estimating mosaic occupancy...
1 blocks used from 1x1 (100%)
Rendering mosaic...
selected 486452588 faces
initializing renderer... tessellating mesh... done (486452588 -> 486452588 faces)
done in 1157.08 sec
Raster size: 49373x164680
Estimating mosaic occupancy...
1763 blocks used from 49x161 (22%)
Calculating color correction...
collecting control points... collected 16396632 points in 2409.05 sec
analyzing 2414 images... ************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************** done in 513.594 sec
estimating corrections...
disabled 0 out of 14148570 points (rms error 0.142296)
bundle_adjust: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx 0.126901 -> 0.0231729
bundle_adjust: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx 0.14267 -> 0.0237614
bundle_adjust: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx 0.143956 -> 0.0212
disabled 102613 out of 14148570 points (rms error 0.0227518)
bundle_adjust: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx 0.0216419 -> 0.0215288
bundle_adjust: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx 0.0220428 -> 0.0218924
bundle_adjust: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx 0.019221 -> 0.0190423
disabled 129508 out of 14148570 points (rms error 0.0214636)
bundle_adjust: xxxxxxxxxxxxxxxxxxxxxxxxxxxx 0.0213096 -> 0.0212986
bundle_adjust: xxxxxxxxxxxxxxxxxxxxxxxxxx 0.0216685 -> 0.0216544
bundle_adjust: xxxxxxxxxxx


This flight was something like 2557 12 and 16 megapixel images (2 cameras), and has taken roughly 5.5 days to process so far on a dual core Xeon 3.4 GHz with 192 GB RAM, an AMD 290x and NVidia GTX 670Ti. Dense pointcloud extracted 921 981 977 points (about 4 days), and I built a 486 452 588 face mesh from that. Which is probably overkill. Mesh generation and DEM extraction were pretty fast, but it looks like color correction took close to 24 hours.


Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: tforward2 on January 07, 2015, 08:03:44 PM
How did you fix this?

Hi Alexey,

Thanks for the quick response.
I have finished diagnosing this issue this weekend and it is not related to photoscan version 1.1.0.

This behavior is due to remote access of the computer via MS Terminal Services.

Sorry for reporting this before finishing the troubleshooting.


Orpheas
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: Cavi_Ing on January 08, 2015, 11:14:38 AM
Hi there,

today i have used the new version (1.1.0) for the first time. Have now performed the "Align Photos" for a aerial photogrammetry project with about 700 pictures.

My settings:

Key point limit: 75'000
Tie point limit: 1'000


I am surprised about the result. My point cloud counts only 70'000 points. For a such project i got with the previous version (Point limit: 75'000)  more than 10 Million points after the align process.

Have i done everything right?       

Can i expect the same accuracy as before with significatly fewer points after alignment?

Thx
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: Alexey Pasumansky on January 08, 2015, 12:44:16 PM
Hello Cavi_Ing,

Using Tie-point limit 1000 means that on every image there will be left not more than 1000 matching points. If you wish to reproduce the results of the version 1.0.4, you need to set up tie-point limit to zero, as in this case all found matching points will remain.
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: Cavi_Ing on January 08, 2015, 01:32:26 PM
Hello Alexey,

many thanks for the quick response.

If I understand you, i get the same results with:

v1.0.4:
point limit = 75'000

v1.1.0:
key point = 75'000
tie point   = 0

Are the TIE POINTS a specific selected quantity (best quality points) of te detected key points?

Or what is the different influence of Key and Tie - Points on the calculation?

THX for response
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: Alexey Pasumansky on January 08, 2015, 04:30:31 PM
Hello Cavi_Ing,

Tie points are actually sparse cloud points that you see in the Model view. They have at least two projections each, meaning that these are key-points that have been matched on two or more images (therefore "transferred" to tie-points).

When tie-point limit is used PhotoScan will leave only most reliable tie-points on each photo to fit the threshold, so it will results in lower number of sparse cloud points.

Using very high key-point and tie-point limits will result in longer processing time and may also affect the resulting alignment due to the fact that less reliable key-point could be matched.
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: Mohammed on January 15, 2015, 03:29:54 PM
Hello Cavi_Ing,

Tie points are actually sparse cloud points that you see in the Model view. They have at least two projections each, meaning that these are key-points that have been matched on two or more images (therefore "transferred" to tie-points).

When tie-point limit is used PhotoScan will leave only most reliable tie-points on each photo to fit the threshold, so it will results in lower number of sparse cloud points.

Using very high key-point and tie-point limits will result in longer processing time and may also affect the resulting alignment due to the fact that less reliable key-point could be matched.

Hi Alexexy,
So what number you suggest to put into Tie point limit?
and if i used 1000 tie point  limit is it will effect on the quality of 3d model?
other question,
what about if i put high number into Key point and put the tie point to Zero, then clean the sparse point cloud by using the Gradual Selection then optimize camera, Is it the same of using Tie point to 1000?


 
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: Alexey Pasumansky on January 15, 2015, 03:54:02 PM
Hello tornado2011,

The same thing can be achieved if you use Thin Point Cloud option in the Tools Menu after aligning with zero limit for the Tie points.

Using gradual selection removes points from the cloud based on the different criteria.
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: ThomasVD on January 20, 2015, 10:09:34 PM
This seems like it might be an error lol. Not sure if it's only since the new release but at least I've never seen it before :)

Processing 206% done!
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: Alexey Pasumansky on January 21, 2015, 12:55:23 AM
Hello Thomas,

This problem has been mentioned in the Bug Reports board: http://www.agisoft.com/forum/index.php?topic=3198
In the most cases it is related to the presence of the markers. The fix will be included in the next update of the version 1.1.
Title: Re: Agisoft PhotoScan 1.1.0 pre-release
Post by: ThomasVD on January 22, 2015, 11:19:06 AM
Ok thanks, indeed the same problem Pjenness was having: tried to align pictures with manual markers placed, and it just kept looping the same three console lines over and over :)