Messages

346

Bug Reports / Re: Region/Bounding Box being ignored on Smooth Build Geometry

« on: March 05, 2012, 04:49:36 PM »

Thanks for the reply. Is there anyway to get Smooth to recognize the Bounding Box better? is it not wasting processing time on building areas outside the Bounding Box?

347

Feature Requests / Re: Cull/Cut by Low-Density tool.

« on: March 05, 2012, 03:16:41 PM »

It seems that Meshlab http://meshlab.sourceforge.net/ is able to delete Garbage polygons by their edge size or Area, using "select polys by edge length"



thanks to Carolina Larsson, Paolo Cignoni, Lehel Seres for their suggestions.

348

Bug Reports / Re: Region/Bounding Box being ignored on Smooth Build Geometry

« on: March 05, 2012, 03:02:20 PM »

It looks like Agisoft ends up wasting allot of time building parts of the scene that don't need to be built when using Smooth setting.

The 2.5 Million Polygon setting looks like allot of that was used to build the walls and floor.

349

Bug Reports / Region/Bounding Box being ignored on Smooth Build Geometry

« on: March 05, 2012, 02:52:14 PM »

I just wanted to mention that it seems the Region/Bounding Box that can be assigned and positioned in Agisoft Photoscan only seems to work on Sharp Build Geometry and not Smooth Build Geometry.

On a 40x 18MP scene Build, I have noticed a 2 hour Build time with Smooth and a 1 hour Build time with Sharp.

Whether this is because the Region/Bounding Box is being taken into account? or if it is because no extra Geometry fill has to take place I am not sure.

Alexey do you know why Region/Bounding Box is ignored on Smooth?

350

Feature Requests / Re: Cull/Cut by Low-Density tool.

« on: March 03, 2012, 06:29:37 PM »

Hi Mike, thanks yeah I have done that previously in ZBrush using masking tools to paint the areas I want to remove. Which is a bit more precise but even then can lead to user error, removing useful areas, or even miss bad areas.

Like your suggestion it's time consuming. Being able to automate the process with a one button click can save hours in a day if you have dozens of captures to process.

The idea being here that the software can analyse the mesh data to find areas that are low density and accurately (not by eye or by hand) remove them.

Does that make sense? It would make the process more accurate and very quick.
Lee

What you could try is the following:

• Roughly select the area you don't want, don't have to be much just a little part/bit
• Now use the page up and page down buttons to control the size of the selection(you'll see the selection grow or shrink)
• And press delete when you have the desired area that you want te get rid off

Hope that makes your process a bit easier

best,
Mike

351

Feature Requests / Re: Split depth generation as separate task?

« on: February 29, 2012, 02:25:33 PM »

Sounds like a good idea, 2 stage process. Save after each one and be able to re-use depth pass, should you need to.

352

Feature Requests / Folder Import, Autoname Chunk as Folder + Batch Export

« on: February 28, 2012, 10:51:37 PM »

Hi Alexey,

My last suggestion, that's a promise.

I recently did some work on a project for a big client and we had a huge FACS Face Capture list to go through. Each folder was correctly named to match the expression.

So, I'm proposing a way to import images by single selection and multiple selection on folders into Agisoft via Add Photos, not just by selecting images. This would allow the user the ability to import a folder with it's images inside and the folders name will auto name the Chunk to match the folder name. As well as being able to do multiple Folder/Chunk import. With each Chunk matching the folder name.

Then after Batch Align and Build, we have Batch Export, so that Agisoft looks for the folders import location and can export and rename there as .obj or what ever, as well as maybe a copy of a single .psz there also.

Currently I have to do this one by one..



..importing, naming each chunk, batch process, then export one by one. A very lengthy procedure when you have dozens and dozens of captures to get through.

Just an idea 

Best,
Lee

353

Bug Reports / Re: Standard Edition Geforce GTX 580's not being utilized despite being checked.

« on: February 28, 2012, 02:07:26 PM »

Very useful thread, thanks for the information listed here.

From my tests I have found RAM is the biggest must have on the list. If your using a minimum of 24 x18MP images for example, at HIGH that amount RAM should be sufficient. At Ultra however even with 24GB at some point it will go to Page Disk, increasing the Geometry stage a great deal. Perhaps 48GB is better suited to 24 x18MP at Ultra.

354

General / Re: Stair Step effect

« on: February 28, 2012, 12:35:57 PM »

I overcame this a whole back using more Cameras. It usually happens when you are only using 1 stereo Pair. The same as just taking 2 images of a subject.

355

General / Re: Graphics cards and memory

« on: February 25, 2012, 05:06:30 PM »

Is there any gain for Photoscan to have a card with 3.0GB RAM instead of 1.5GB

For example you can get the GTX580 in 1.5 and 3.0 GB flavors

Often the 1.5 cards are clocked higher then the 3.0 cards so that would impact this as well.

What is the gain if any?

I would also be interested to know. Also the different between GTX580 to GTX590 and maybe even the next range that will be out soon?

Also I found the Quadro 4000 to have less Cores and be slower than the GTX570 for example.

356

Feature Requests / Re: Cull/Cut by Low-Density tool.

« on: February 25, 2012, 02:05:39 PM »

Cool to hear another user like this idea : ) You can see on the geometry build how it kind of fades in from REALLY dense to sparse. Even if we got some kind of polygon group addition to the sparse geometry area, or black and white grey scale clip map built when the texture phase is created as an alpha, it would help. I'm sure there must be a way to calculate a smooth fall off between the two, and find a way to keep the desirable geometry, rather than rely on masking and cutting.

357

Feature Requests / Cull/Cut by Low-Density tool.

« on: February 25, 2012, 01:09:27 AM »

Hi Alexey,
 
I’ve been trying to think of an elegant way to easily solve masking and cutting with the more volumetric type captures.
 
It dawned on me looking at some High and Ultra builds today, maybe there is a solution inside Agisoft before export and after build.



Notice how dense the “important” areas are and how sparse the useless “garbage” areas are. The important areas are so well formed it seems like it would be an ideal way to cull the garbage data based on the low-density of the mesh? what do you think? does that sound like a feasible thing to implement?
 
This would make aligning and handling 360 data so much easier, by having to hand very quick culling tools.
 
Interested to hear your thoughts on yet another topic : )

358

Feature Requests / Re-Point to Folder Path for missing Images.

« on: February 21, 2012, 11:03:05 PM »

Hi Alexey,

Last suggestion for today I promise  would it be useful to integrate a path pointing tool? So you can right click on a Chunk and re-point missing photographs by selecting the folder location using Explorer? the refresh so they reappear or load back into Agisoft?

Currently I find I have to move .psz builds, or align files around allot, renaming folders, moving across networks, sometimes Agisoft cant find the images, as it is pointing to a different directory and there is no way to re-point to find them. Being able to guide the Chunk to reload them would be most useful.

Thanks, Lee

359

Feature Requests / Batch "Automatic Colour Key" tool for masking and cutting

« on: February 21, 2012, 10:59:06 PM »

Hi Alexey,

I have another suggestion for Agisoft Photoscan. Would it be possible to think about the addition of a Batch "Automatic Colour Key" tool for masking and cutting.

Say you have 10-20 photographs, with a well lit Chroma Key Background, Green, Blue, White or Black etc. Being able to use a "Color Picker" to choose which colour you want Auto Masking to mask. Choose your colour and it cycles through the images in Agisoft, masking them. Then at the end of the build it auto cuts away those masked areas when using Object type: Arbitrary and Geometry type: Smooth.

This would be a fantastic addition to processing 4D by masking and cutting at the source in Agisoft after each build.

Thanks, Lee

360

Feature Requests / Lasso tool

« on: February 21, 2012, 10:53:43 PM »

Hi Alexey, I was wondering if it might be possible to add in a Lasso tool to the currently group of selection tools? i.e. a free hand drawing select tool.

The box select and circle are good but it means multiple clicks sometimes and navigating in the viewport around a model to cut it.