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

Pages: [1]
General / Re: Why is the space between the grid holes filled with black?
« on: November 29, 2023, 03:52:14 PM »
Hello Alexey,
thanks for getting back to me. I'm using Metashape standard Version 2.0.1

I always use depth maps for the model creation. I assumed that this behaviour is linked to the depth maps. Would we have been better off, placing a checker map behind the bars?

I use 'gradual selection' ( in the way this guy explains here : ) a lot.

General / Why is the space between the grid holes filled with black?
« on: November 29, 2023, 02:25:23 AM »
One element of my subject is a grid( shot before black). The tie points look nice, but when the mesh is created all the holes are filled with black. Can somebody please explain this/how to avoid this?
Thanks a million

Feature Requests / Re: keyboard shortcut to disable camera in Photos pane
« on: September 13, 2023, 06:59:41 PM »

4. The missing Undo. Should this be flagged as abug?

Thank you.

General / Standard Version- Aligning model to grid and transform controls
« on: September 08, 2023, 11:56:42 AM »
Hi, I'm using the standard version of Metashape and I am encountering several obstacles aligning the object.
1. The Grid. Why isn't it possible to set the grid to centimeters? Not all of us are scanning landscapes.
2. The Transform controls. It would be incredible useful to have a more sophisticated gizmo. To be able to switch between world and object coordinate system and to move, rotate, scale in screen space.
3. Why is the scale gizmo so different? I am not able to get the object smaller. For an instant I can get a number below 1, but not able to 'catch' it. In other words: When I click and drag; the scale is only getting bigger, not smaller. Couldn't find it in the manual either.
4. Why there is no Undo on move/rotate/scale?
5. Numeric input would be nice for move/rotate/scale

Thank you.

Feature Requests / Re: Allow grid sizes of less than one meter
« on: September 08, 2023, 10:04:27 AM »
Yes, that would be super helpful: +1

General / Re: blurry regions in both mesh and texture
« on: August 04, 2023, 07:03:32 PM »
the 'patches' seen in the results- is the reason we haved used 2 different focal lenghts?

General / Re: blurry regions in both mesh and texture
« on: August 02, 2023, 09:56:33 PM »
Hello Alexey,
thank you so much for coming back to you. Thanks for the 'confidence view'- I overlooked that.
I'll attach screenshots for this, camera alignment in viewport and the camera calibr dialog.
thank you

General / blurry regions in both mesh and texture
« on: August 01, 2023, 08:39:01 PM »
we have shot this model with a crosspolarized flash-light setup. I would be pretty happy with the results, but there are strange blurry patches which I can't explain.
What I did.
- aligned photos with these settings(s. attachement)
- used gradual selection for higher certainty
- build mesh from depth maps; ultra high settings; mild filtering.

Please help. What is the reason of these patches? What can I check? What can I improve?

PS: Is there any feature in metashape where the point cloud is coloured to tell the user what area are covered good by the photos(green) and what areas not(red). Like in Reality Capture...

Hi folks. We're scanning some sets and props for our animated movie( and I would love to have feedback on our approach and ask some questions about it.
For this example we shot 248 jpegs with a Canon EOS RP with some strong (bounce)-lights to avoid shadow-casting. We're on the latest Metashape standard version
- est. image quality about 30 pics around 0.5. ~125 pics above 0.7
- focal length: 50
- iso: 100
- F-stop: F/20
- shutter: 1/3.33

- aligning photos
- build dense cloud
- build mesh
- build texture
Everything's pretty much default. I chosed highest/ultra-high in the quality settings and went for 3 UDIM tiles at 4k.

The result is very good in some areas and poor in the other. For example the small cupboard came out rather bumpy. We assume that this is because its surface is rather shiny. We know about the need of cross-polarizing and will implement this in future shootings.

But on the floor there are some noisy areas, too. If you zoom in you'll see that there are mesh parts 'floating' over other parts. What is the reason for this? There are some areas that will be difficult to capture because there are indeed little spikes pointing out like here. But we do have quite a few photos of the floor with out-of-focus-areas: Is this the reason? Better leave them out? Use masking to mask out the out-of-focus areas? Better shoot that angles with shorter focal length?

In general: I have the feeling that generated texture could be sharper. Are the pictures with out-of-focus-areas the reason for this? What other factors contribute to texture quality?

A question about masking: As I understand it: masking will speed up processing because Metashape know where to NOT look at. But does it improve the quality of the mesh?

A question about the selection tools: After aligning the images I use the selection tools to delete the points of no interest. But after the mesh-building there are all back and I do it again. What is it I do not understand?

Are there workflows(on the horizon) enhancing the photogrammetry result with machine learning tools and/or lidar images?

- Processing is rather slow with that settings and amount of photos. I have a couple of machines here. Currently latest metashape is on my WS: Intel(R) Core(TM) i7-5960X CPU @ 3.00GHz, 64 gb Ram and geforce1070( will upgrade to 3070ti) on win10pro.
I could install metashape on a 24-core-Xeon-machine( but with no GPU). If I put the old 1070 to this machine: Would that be the better metashape-machine?

Any feedback greatly appreciated- thank you!

The last test we did 1/2 second exposure at 400 ISO. We will have a look to bring down the ISO. Thank you so much.

We're shooting on a Canon RP in a (small!) studio environment. I checked the spec and C3-Raw should deliver 14bit. I don't see the point of rendering tonemapped jpgs from that. The question remains: Rendering 16bit tiffs or exrs from that raw-footage. Does this help Metashape in aligning cameras, conserving more details in mesh?
Thank you, guys!

General / 16bit instead of 8bit source images- better mesh quality?
« on: April 13, 2022, 09:22:36 PM »
Hi guys, I couldn't find a clear answer to this question. We did some tests with Agisoft, feeding in over 300 images from a Canon and a Cell phone. We used jpgs on the Canon as well. If we would shoot RAW images and convert them to 16bit: Would this help the software to build a better mesh with more details? Thank you.

Pages: [1]