Forum

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - jenkinsm

Pages: [1] 2 3 4
1
For me, it's faster to enable it during the alignment phase, and then disable it for meshing and texturing.

2
General / Re: Weird banding/noise pattern in mesh from depth maps
« on: November 03, 2022, 02:09:19 AM »
Yes, I was able to reproduce the problem with a subset of 299 images and 3 GCPs.

The banding is present both when creating a mesh from depth maps and from a dense cloud, but the banding is sharper and narrower from the dense cloud vs wide and blurry from the depth maps.

I created example chunks with various settings and will email a compressed archive shortly.

3
General / Re: Weird banding/noise pattern in mesh from depth maps
« on: November 01, 2022, 08:51:31 PM »
The project has over 7TB of images, so I'll try to reproduce the banding in a new project later today with a small subset of images and send that over.

4
General / Weird banding/noise pattern in mesh from depth maps
« on: October 28, 2022, 02:52:25 AM »
Does anyone know what is causing this weird banding pattern in my mesh? (See attached image)

I generated the mesh from depth maps using a set of 22,785 images that were well-aligned.

I'm wondering if Optimizing Cameras caused this.

It's a big problem because it shows up in my normal maps and looks terrible in-game.

Open to hearing all suggestions. Thanks!


5
General / EXR support in Metashape
« on: April 23, 2022, 07:45:30 AM »
I was able to successfully import EXR files into Metashape, however, the gamma looks incorrect. The image is much brighter than in Mac's Preview and Finder, and also DaVinci Resolve where the EXRs were exported from. It could be a color space flag that needs to be changed in Resolve, but since the image looks right in Finder and Preview, I'm assuming Metashape is the culprit here.

Does anyone know why this is happening? The attached pic shows Metashape on the left and Preview on the right.

6
General / Re: Boost computation speed for photo subalignment
« on: April 19, 2022, 11:41:53 PM »
I'm doing something similar and there is one setting that I ignored until recently, but setting this value has made my alignment process much faster and more accurate: Capture Distance. Try setting that and see if it speeds up the next alignment you attempt.

You should also be using Estimated preselection in addition to Generic preselection.

7
General / Re: Error message "Incompatible keypoints"
« on: April 19, 2022, 11:39:04 PM »
I'm getting the same error in 1.8.2. I did merge two chunks and I'm no longer able to align new photos to the merged chunk. This is a huge problem and a big waste of time if it's not able to be resolved easily.
They replied to my email with my report and confirmed it's caused by having a chunk made of merged chunks. I had thought Alexey was asking if my new photos were in a chunk, but the problem is apparently caused by any previous merges

Figured. Did they give any workarounds or an ETA on a bugfix?

No, I sent my logs from when I did the merges so maybe they'll come up with a fix.

My fix was to do align photos with Reset Alignments checked to re-align everything again. I guess if you have your previous unmerged chunks you can add photos to one of them, then merge afterward

I managed to make it work by rebuilding the tie point cloud but without realigning all the photos. It still took an entire day to fix :(

8
General / Re: Error message "Incompatible keypoints"
« on: April 18, 2022, 10:14:08 PM »
I'm getting the same error in 1.8.2. I did merge two chunks and I'm no longer able to align new photos to the merged chunk. This is a huge problem and a big waste of time if it's not able to be resolved easily.
They replied to my email with my report and confirmed it's caused by having a chunk made of merged chunks. I had thought Alexey was asking if my new photos were in a chunk, but the problem is apparently caused by any previous merges

Figured. Did they give any workarounds or an ETA on a bugfix?

9
General / Re: Error message "Incompatible keypoints"
« on: April 18, 2022, 09:07:59 PM »
I'm getting the same error in 1.8.2. I did merge two chunks and I'm no longer able to align new photos to the merged chunk. This is a huge problem and a big waste of time if it's not able to be resolved easily.

10
Bug Reports / Changing color levels produces red/cyan shift
« on: April 18, 2022, 08:50:23 PM »
I am trying to use the "Adjust Color Levels..." tool that you open by right-clicking on an image, but when I change all the values by the same amount (150 in my case) the image becomes dramatically Red. If I reduce below 100, then it shifts toward Cyan.

(See attached image)

Weirdly, the thumbnail shows the correct image, but not the large viewer.

What's going on here?

11
I'm trying to merge two large chunks into one and I thought it would be quick, but I'm surprised to see that it's going through the "Selecting pairs..." process which is taking a long time. Does anyone know why it's doing this? I didn't align the chunks, I'm just trying to merge them.

13
A nice find however is that initial match&align is much faster when you activate "Use CPU when performing GPU acc. processing" in the Metashape GPU preferences. This speed improvement is likely a M1Max design side effect and likely also applies to the Mi1Max 24C version.

Hate to burst your bubble, but this has nothing to do with the M1 architecture. The same is true on my Intel Core i9 10900K RTX 3090 desktop. I highly recommend always enabling it on the alignment stage.

14
I was wondering about these attributes that affect alignment. I want to make sure I am using all the best settings to get the highest number of aligned images in a single alignment operation, while still being reasonably fast.

1) Focal Length - Will I get a higher number of correctly aligned photos by entering the 35mm focal length (in my case, 16mm) or by leaving it blank so Metashape can estimate it? And how does this affect speed?

2) Capture distance - Same as above - will I get a higher number of correctly aligned photos by entering the capture distance? And how does this affect speed?

3) Rolling shutter compensation - I know this slows down alignment. But does it affect the number of correctly aligned photos? And/or does it affect the quality of the resulting mesh?

Thanks in advance!




15
a6000 is higher resolution so that will be better than D7000

Phone cameras have extremely small pixels compared to larger DSLRs and mirrorless cameras. This produces sub-optimal results with Photogrammetry. If you had to use a phone camera, you'd be better off with 12 MP than 64 MP.

Since you have a better lens for your Nikon than your Sony, consider getting an adapter that will let you use the 85mm prime lens on the Sony body. That said, 85mm is very tight and it will mean you need to take a lot more photos to capture your full object. But that would also result in higher quality.

I'd probably put the light on the camera and have it move with you around the object. A ring flash would be ideal. And you could also experiment with cross-polarization!

Pages: [1] 2 3 4