Messages

1

Feature Requests / Please update date of main project file with each save

« on: December 03, 2017, 10:27:37 PM »

Like the title says:
While this can be avoided with a strict naming regime, it could avoid possible mixups and mistakes if the main project file was updated with each saving progress.
Point in case: I just suffered a minor heart attack when I had to kill the Photoscan process and the last modified date of the project file seemed to be from hours ago. But it could also happen that people continue to work with the wrong version of their file.

(Using the beta, here, didn't double check with an older version.)

2

Feature Requests / Re: Photoscan Professional "Artist" Edition

« on: December 03, 2017, 10:21:59 PM »

Agreed

3

General / Re: Agisoft PhotoScan 1.4.0 pre-release

« on: November 29, 2017, 05:52:29 AM »

Please see the following tutorial...

Thanks for the tutorial, Alexey!
Will the two mesh construction modes always be offered as options (not talking about the strict volume mask but the two meshing modes)
It seems like they both have advantages and disadvantages, so I would vote for offering both.

I'd also add my voice to the ones who'd like to see delighting functionality in the standard version of the software. Right now the price difference between standard and professional is huge (I guess because the latter is used by institutions and for all kinds of important things) and there is zero chance I'll ever buy it, but built in delighting would be practical for use in games. Perhaps a slightly more expensive third option would make sense?

4

General / Re: very Slow to build mesh pass

« on: November 19, 2017, 07:53:13 PM »

Just a shot in the dark, but do you use the same settings for the windows swap as before the rebuild?
Had the impression in the past that windows starts to swap RAM with a big swap file even if there is plenty of RAM left.

5

General / Re: Photoscan 1.4.0 - New Feature Comparisons

« on: November 18, 2017, 02:06:49 AM »

At the top of this forum.

6

General / Re: Photoscan 1.4.0 - New Feature Comparisons

« on: November 16, 2017, 04:32:03 AM »

Thanks for the comparison!
I didn't even know that function existed, despite toying around with the beta for a bit.

7

General / Re: Flush memory between batch steps

« on: June 30, 2017, 12:16:39 PM »

It might have been a bit better with default view switched to sparse cloud and making sure to start with a sparse cloud view, but I didn't have precise data over time for the older runs.

I let another batch run with new data/chunks and recorded the RAM usage this time for the mesh creation phase  and there is less and less RAM freed with each consecutive job/chunk. Got again to an about 10 GB  footprint from a 3,5 GB one.
Didn't record other steps since they went through without problems, but that might be because the require less RAM in general.

8

General / Re: Flush memory between batch steps

« on: June 29, 2017, 10:53:59 AM »

I'm doing a dense cloud (ultra high -> high would probably be good enough and save some RAM, but that's not the point, here) of a preexisting sparse cloud, high mesh and 8k texture for 16 chunks (so even small increases add up). Had no problems with the dense clouds, but that could simply be because the overall RAM footprint was still relatively low. Problems then occurred during the mesh generation, with some jobs running out of memory that don't when I clear the RAM bei saving, closing and reopening the scene.

I can also suggest to switch the default view in the General Preferences tab to Point Cloud, so that dense cloud and mesh models wouldn't be loaded, if they are in the batch processing pipeline.

I'll give that a try!

9

General / Re: Flush memory between batch steps

« on: June 29, 2017, 10:01:26 AM »

Thanks a lot for the quick reply, Alexey!

 I'm already using psx. (Photoscan 1.3.2)

It might very well be that the behavior is as intended, but I definitely see an increase in the memory footprint while the batch process is working through the chunks, and that memory is only partially released when the next chunk is processed. E. g. after a while I have a 10 GB RAM footprint (just the open scene with the chunks, no job running) while after saving the file and reopening it I have a 3 GB footprint (including Windows etc.) I'll take another look at it today in order to see if it happens generally or only with certain jobs.

10

General / Flush memory between batch steps

« on: June 29, 2017, 07:19:06 AM »

Hello,

Is there a possibility in the none pro version to do some kind of garbage collection or flush the memory between batch processing steps? Delete the undo buffer or cache?
Agisoft seems to eat memory over time or at the very least isn't releasing part of what it used for previous steps, which makes sense if I want to access the parts again shortly, but when I have a file with several chunks and try to process them in a row, the baseline of RAM used is continuously rising. job after job, ultimately leading to failed jobs. If I close and reopen the file, it uses a lot less RAM again.

11

Feature Requests / Re: Gradual Selection as part of the batch process...

« on: May 30, 2017, 03:26:39 AM »

Would love to have that as well.

12

General / Re: RAW processing

« on: November 17, 2016, 11:28:22 PM »

I've heard good things about Affinity Photo, but I haven't tried it myself.
The Windows version is currently in open beta.

13

General / Re: Method For Masking Out Sharp Pixels?

« on: November 16, 2016, 07:54:38 PM »

Glad it worked! 

14

General / Re: Method For Masking Out Sharp Pixels?

« on: November 15, 2016, 09:51:03 PM »

If you have very little noise, you maybe could try to use a slightly blurred copy with difference blending mode.
(The idea being that a slight blur would change an already blurry area less.)

15

General / Re: Photo aligning with two groups, but not at the same time

« on: November 15, 2016, 09:37:44 PM »

You could try to align by cameras.
You'll need at least three overlapping cameras which are named identically, as far as I can tell. (So the chunks seem to be aligned by camera position and not orientation.)