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
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.

2
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.

3
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 :(

4
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?

5
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.

6
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?

7
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.

9
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.

10
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!




11
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!

12
If I understand, your output is TIFF image sequence from DaVinci Resolve and then you add all those 200.000 files into metashape project?
How big are those TIFF files?

Yes, that is correct. Currently, I am using 8-bit compressed TIFF images which are 13.6 MB each. In the future, I plan to use a better camera to capture with, which would warrant exporting 16-bit TIFF images which are 86.7 MB (I think that's for uncompressed files).

13
Alexey, could you post here (not just email Juan directly) when you have figured out the problem or found a solution? I (and likely others) would like to learn as much as possible about networked rendering and the situation Juan posted about is something that I will need to consider when I eventually move towards networked rendering for my projects.

Thanks!

Hello Juan Shimmin,

Can you please provide the log from the node, which failed with the error? Via the Network Monitor you can open the list of disconnected nodes and through Details command of the context menu open the node log up to the node termination.

14
I am working on several gigantic projects with well over 200,000 TIFF images each. I would like to know if there are any tips or hidden secrets that would allow me to import all of my photos much faster.

The slow importing happens on my Windows machine where the photos are stored on a 32 TB RAID 0 (2 drives), whereas my M1 Max MacBook Pro loads photos from an external SSD almost instantly. Granted, I haven't tried 100k at once on the MacBook, and I know it's faster partly because of the SSD, but I'm still surprised by how long it takes on the PC.

Putting the photos on an SSD is not an option, as each project uses several TB of photos. Converting to PNG or JPEG is not ideal because that's an extra step I don't want to include, and my workflow can only output TIFF/DPX/EXR frames directly (I'm capturing roads on video and using DaVinci Resolve to mask out the sky, adjust the contrast/midtone detail, and mask out the capture vehicle).

Any tips or tricks I should try?

15
General / Re: butterfly Mesh Full Of Holes
« on: March 30, 2022, 12:35:22 AM »
Hi Alexey,

I captured an object that is quite fat in some areas but very thin in others. The normal depth maps method results in a hole in the thin area and some missing mesh around the thin edges, but enabling this tweak dramatically affects the mesh quality overall so it's not a viable solution for me.

Do you have any tips on how to handle a situation like this?

Thanks!

Hello,

We have just published the article that may be helpful, when working with such thin surfaces:
https://agisoft.freshdesk.com/a/solutions/articles/31000163220

The approach assumes adding two tweaks via Advanced Preferences tab prior to the mesh from the depth maps generation:
Code: [Select]
BuildModel/ooc_surface_blow_up = 0.95
BuildModel/ooc_surface_blow_off = 0.95

After using these tweaks do not forget to disable them (set to zero value) or remove from the tweaks list, in order to not have further projects affected, when it wasn't necessary.

Pages: [1] 2 3 4