Messages

1

General / Re: Any tips for 360 photos for photogrammetry?

« on: January 26, 2019, 11:52:20 AM »

Thanks for the reply. Doesn't look like the Insta360 has the raw double fisheye images available. Their raw files are proprietary file formats, and once processed with the iOS or the desktop app they're already equirectalinear images. I know the quality might be subpar, but I find the ease of use interesting for some use cases where I don't want to have my dslr/fisheye/tripod + time. There's also the worry of not coverage when shooting with the fisheye. The 360 pictures or even video would be appealing with a quick walk through of a new space and getting a rough capture for dimensions or review in VR. Oh well.

This is mostly a hobby and experiments for me. I wanted to see if I could do it with Photoscan before I looked at some of these other services that do similar things.

2

General / Re: Any tips for 360 photos for photogrammetry?

« on: January 24, 2019, 06:57:53 PM »

I see now that it's only in the professional version's documentation that this is possible. Despite the features section of the website saying otherwise both Pro & Standard support it. The website mentions that Standard can do - Auto calibration: frame (incl. fisheye), spherical & cylindrical cameras.

hmm...

3

General / Any tips for 360 photos for photogrammetry?

« on: January 24, 2019, 06:46:56 PM »

I recently picked up an Insta360 One X - and through some searching of the forum realized that equirectangular photos CAN be loaded into Metashape for processing a point cloud?? Yay!

But I can't find Spherical as an option. "switch the Camera Type from Frame (default) to Spherical"

4

Feature Requests / Re: gizmo coordinate system

« on: July 20, 2018, 06:22:22 PM »

was a toggle ever made to switch between world/object rotating?

5

Feature Requests / Re: gizmo coordinate system

« on: August 04, 2017, 05:38:20 PM »

does this exist yet? I keep wanting this for model rotating when in front/top orthographic view to try and visually align things.

6

Feature Requests / Re: DNG format

« on: October 27, 2016, 02:45:12 AM »

I just wanted to say thanks for adding .dng as a file type to import! Insanely awesome and much easier than having to export a whole batch of images to a lower quality file type = saving me a lot of hard drive space.

Thanks again

7

Bug Reports / Re: Export Orthomosaic 8 bit with DNG

« on: October 20, 2016, 11:50:27 PM »

Has this been fixed? I just now tried exporting the texture as .EXR and got a 32-bit float image (compared to the 16-bit fixed that I see when viewing a .dng photo). Given this is what I'm seeing when viewing the metadata in Nuke - no idea if it's correct.

8

General / Re: save different model orientation

« on: September 08, 2016, 05:41:51 PM »

Hey Alexey, is it possible to reset the rotating gizmo to switch between model and world space? Or somehow reset it at its current orientation?

9

Face and Body Scanning / Re: Turntable based Full body capture rig

« on: June 17, 2016, 10:38:22 PM »

That sounds right. I had a 5 camera setup with a motorized turntable and would roughly take 200 pictures total. The quick selection brush in Photoshop worked surprisingly well in quickly masking some shoots where I didn't setup a green screen.

10

General / Re: Not Enough Memory!!!

« on: February 04, 2016, 05:50:02 PM »

I see. So the various mesh face counts in the Mesh Build are a bit arbitrary as there's still a higher number above 'High' that the point cloud is being processed to. That max poly number is what seems to be the limiting factor in processing and getting memory errors. Am I following correctly?

So the solution with not enough memory is always to try processing a less dense point cloud, or process in sections.

11

General / Re: Not Enough Memory!!!

« on: February 04, 2016, 04:16:47 PM »

Alexey,

One last question
The max possible number of faces during Build Mesh. Is that the 'High' Face count? Or is there possibly a higher number that the program is then decimated to that High, Medium, Low, or custom number?

So far I've had luck in re-processing the dense point cloud at High instead of Ultra High, and then running Low mesh build. No memory issue. I'm assuming since that worked I could also process the high. But I also want to try processing Interpolation Extrapolated vs. Enabled

Thanks

12

General / Re: Not Enough Memory!!!

« on: February 02, 2016, 07:32:49 PM »

Thanks for all this info Alexey! This will be a great reference.
I'm sure the old processing uses less points, hence why it worked back then. I wasn't aware that the mesh building was dependant on the points and that setting a 100k poly limit wouldn't help with the processing. Time to tinker with the scene some more and see what I can I achieve.

13

General / Re: Not Enough Memory!!!

« on: February 02, 2016, 07:12:18 PM »

Split your chunk into smaller pieces before mesh generation, there are scripts that can do this for you

Scripting is a pro feature that I can't afford for my hobby scans... You did have me excited until I found that out.

I wish I could select cameras after an initial alignment, so I can see the best clusters of photos to move into a new chunk. What bothers me most is I had no issue processing all of this years ago with an older version of Photoscan.. I thought maybe I'd get an improved version re-processing this time around.

Hello bcoyle,

Number of polygons in the target model doesn't matter, as in Arbitrary mode PhotoScan will generate the mesh with the max possible number of faces and then will decimate it to the user-defined number.

So what is the number of points in the dense cloud (and quality used for dense cloud generation), number of images and their resolution?

That's interesting to know that the mesh target wont matter. So when having meshing issues it's better to go back and reduce the point cloud. There's no way to limit the points used in the meshing is there? I'd have to go and re-process again at a different quality level?

# of points in sparse cloud: 33,226
# of points in dense cloud: 463,155,348
quality used for generation: Ultra High, Aggressive filtering
number of images: 316
image resolutions: 5616 x 3744 (shot with Canon 5D mk II) - each image is roughly 100mb .tif

At what point would it help me to double my RAM to 64gig? Or would it help at all? Is there a way to calculate photos + point cloud = memory needs?

thanks

14

General / Re: Not Enough Memory!!!

« on: February 02, 2016, 04:36:29 PM »

I have almost the exact same rig, and just went through the same steps, ie. highest accuracy and highest dense point cloud. The project file/folder is now 8gigs. First time I got an 'Index overflow', and after reboot I've been getting 'Not enough memory'. Even when processing 1mil or 500k poly for the mesh. Settings are:

Surface type: Arbitrary
Source data: Dense cloud
Face count: 500,000

Interpolation: Enable (default)

- I'll try Height field, but isn't that mostly for aerial scanning?

ps: Would it even help if I doubled my memory? My CPU would only support 64gig if I was to upgrade further.

15

General / fisheye processing in agisoft standard

« on: January 05, 2016, 07:51:41 PM »

Thanks for adding this! I'd been wanting to use my fisheye lens for photogrammetry for so long. I love this software.