Messages

1

General / Re: Generating depth maps...blocked

« on: July 10, 2025, 06:09:12 PM »

I am not sure if the camera numbers in log (e.g.  2025-02-08 08:58:47 [GPU 3] group 1/1: estimating depth map for 1/34 camera 16 (1 neighbs)...) corresponds to number order in photo list in workspace.
You can tray also reconvert all photos to jpeg in apps like irfan view, or XnView MP, ...or similar where you can use batch convert function. It should resolve the issue. Keep during conversion EXIF info.

2

General / Re: Generating depth maps...blocked

« on: July 10, 2025, 02:06:14 PM »

JPEG image should start with 0xFFD8 and end with 0xFFD9 , if you use some hex editor utility.

From google gemini AI:

To check the integrity of JPG files within a directory, you can use the jpeginfo utility, available on most Linux distributions and also for Windows. This tool specifically targets JPEG files and can detect various types of corruption and errors, including those caused by transmission or incomplete downloads.
Here's how to use jpeginfo:

1. Installation:
If jpeginfo is not already installed, you can typically install it using your distribution's package manager (e.g., sudo apt-get install jpeginfo on Debian/Ubuntu or sudo yum install jpeginfo on CentOS/RHEL).

2. Basic Usage:
To check all JPG files in the current directory, navigate to the directory in your terminal and run the command jpeginfo *.jpg. This will print information about each file and indicate if any errors are found.

3. More Detailed Output:
For more detailed information, including specific error messages, you can use the -v (verbose) or -c (check) options: jpeginfo -v *.jpg or jpeginfo -c *.jpg. The -c option will display more detailed error messages, while -v will show more information about the file's structure.

4. Handling Corrupt Files:
If you encounter corrupt files, you can use jpeginfo with the -d (delete) option to automatically remove them. Be cautious with this option and ensure you have backups before using it, especially with -mall (delete all). For example: jpeginfo -d *.jpg to delete files identified as corrupt or jpeginfo -d -mall *.jpg to delete all the files in the directory.

5. Alternative Method:
Another option is to use identify from ImageMagick, which can also check if a file is a valid JPEG. It's used like this: identify -format '%f' your_image.jpg.

6. Graphical Tools:
For a graphical interface, you can use tools like Autopsy or Beyond Compare to check file integrity. Autopsy, for example, uses the MD5 algorithm for image validation. You can also use graphical utilities like MD5 & SHA Checksum Utility or HashMyFiles to calculate checksums and compare them to known good values.

7. Checksums:
Another approach is to calculate the checksum (e.g., SHA256) of a file and compare it with a known good checksum. This method is more reliable for detecting tampering but requires a reference checksum.

Note: If you are dealing with a large number of files, consider processing them in smaller batches or using more advanced scripting techniques to handle potential errors gracefully.

3

General / Re: Generating depth maps...blocked

« on: July 10, 2025, 11:11:44 AM »

Does this only happen using High detail level? Can you post the logs, or at least several last lines before it stalls? Do you see any GPU/CPU/disk utilization after it reaches 80%?

4

General / Re: Managing non-aligned photos

« on: July 09, 2025, 01:50:38 PM »

Hi, 81 and 71 points are pretty low numbers of total matches. You should have hundreds of points on 20Mpix photos. What alignment settings are you using? Did you try also Guided image matching, which is designed for forest scenarios?

5

General / Re: Processing Hung up

« on: July 05, 2025, 11:52:13 AM »

If you see zero activity on gpu/cpu on depth maps stage, then no need to wait 7 hours. Just restart this stage and it will be probably finished without issue.
Something similar happened to me at another stage and after restart MS it was OK.

6

General / Re: Tiled model generation stalls

« on: July 02, 2025, 10:30:14 PM »

Yes, using crossover ethernet cable, or if you do not have crossover cable, then use normal and set something like Auto-MDIX option on network card(maybe the cards can set it automatically).

7

General / Re: Threadripper 5995 vs 7995 (and some other build questions)

« on: July 02, 2025, 01:20:46 PM »

Here is the tip for processing large projects https://www.youtube.com/watch?v=BYRIC-qkZJ8
Instead of buying threadripper, you can buy another PC(similar performance you have) with another MS pro license and you can split the project between two computers. And not only that, you can run more than one local worker node for better utilization(CPU/GPU) during certain stages.

7995 is more expensive, because except for the fact that it has more cores, it is also manufactured on newer process, so its performance per watt is better.
You can buy RTX 5090, its vram is worth and also performance.
Best advice before buy new HW is to monitor CPU/GPU/RAM/VRAM utilization during whole process on your current PC. Then you will know if you need more CPU cores, more ram/vram, faster GPU... it depends also of your project settings you are using.

8

General / Re: Tiled model generation stalls

« on: July 02, 2025, 12:53:40 PM »

Paulo, here is the video describing how to use local network processing https://www.youtube.com/watch?v=BYRIC-qkZJ8  - commands has changed a little bit, so check MS manual
- this should for you get rid of the bad allocation error
- for connecting 2 laptops use at least 1Gbit switch/router
- you can spawn/run more than one worker node on one laptop, it depends on task(and its memory requirements)

9

General / Re: Tiled model generation stalls

« on: July 01, 2025, 01:45:59 PM »

Is it true that Vexcel Osprey has 247 MPix sensor?
CPU texture blending will be veeeeery slow.
I don't remember how much resource hungry is building tiled model.
Try local network processing on your laptop.

10

General / Re: Ryzen AI max+ pro 395 compatibility/performance?

« on: June 25, 2025, 12:22:50 PM »

If you will run it at 120W and with LPDDR5x-8000 memory modules, then it will be really good choice. CPU performance according Cinebench is outstanding and GPU performance is on ~RTX2070 performance level.
I did not test it, but it should be supported out of the box without problems.

11

General / Re: Shooting scenarios (or tips) for making 3D model of building on narrow street

« on: May 12, 2025, 11:24:11 AM »

How do the scans look if you change the View Mode to Model Confidence?
I'm guessing it'll be a series of 'good' hotspots along the walls corresponding to the shooting positions?

Oblique angles contribute to several nearby shooting positions, so whole facade is easily in dark blur color in confidence view mode, which means ~100 combined depth maps.

12

General / Re: Shooting scenarios (or tips) for making 3D model of building on narrow street

« on: May 11, 2025, 10:51:14 PM »

From manual:
Interior(Correct) picture - there is one big downside - this will work only for small rooms e.g. 3x4m and only if you need just basic shape of room. If you want to capture also details from walls you need to be closer to that wall you are shooting, not on the opposite side of the room(that is too far for getting details from walls).

Facade(Correct) - this approach is advised, because it comes mostly from drone scenario where the most important is capture position of objects and how tall they are is slightly less importatn. Keeping 60% overlap is critical. If you miss that, you lose continuity...small downside.

Facade(Incorrect) - angles which are parallel with wall are useless(for facade itself). But angles 30-45° from nadir angle are very useful for capturing holes/window deep niches, because those angles can capture better the depth. These angles are also great as a fix for 60% overlap, which is in this case not needed. All shots are in focus and with aperture f7 and more are also sharp in corners, so not problem at all, it is faster solution and also more comfortable. Better than use wide angle lens.

Interior(Incorrect) - that example with only 2 positions and shots at 45°steps will also work in small room, but is not advised, because people could start to think that several shots in 360° from one place is enough for photogrammetry  .

There are also scenarios, where 360° shots from several positions are the best choice. It depends on the environment, the objects, and also the time you have for shooting. Metashape is very powerful and flexible, so it is not always necessary to follow the recommended practices exactly .

13

General / Re: Shooting scenarios (or tips) for making 3D model of building on narrow street

« on: May 11, 2025, 01:59:35 PM »

@jkova96
Check this video  https://drive.google.com/file/d/1xYyYWlCdZf_9hIYI_eBCAQwtl9y5Jk-T  , it is from my project. Most of the time I am shoothing facades. There is 1m grid, so ~2m distance between positions and ~2m far from facade. I always use this approach. If you can't get 2m far from facade in narrow street, then distances between positions will be shorter ~1.5m...it depends also on the lens you are using. I am using 24mm lens.

14

General / Re: Shooting scenarios (or tips) for making 3D model of building on narrow street

« on: May 07, 2025, 11:08:56 AM »

In user manual the 360 degree method is marked as incorrect mostly from reason that it cannot produce enough photos from different angles from only few shooting positions.
There is universal rule: every surface part you want to have in pointcloud in good quality should be taken from at least 3 different angles. Distance from surface also matters and it depends on how big is the resolution of photos, what is the lens focal distance and how precision final pointcloud you need.
In your case you are limited by the narrow street between buildings. If you need only one building, then set the drone position as close as possible to the opposite building facade and take only 5 shots in range <90°(at 18°steps), another 5 shots in the same range but looking slightly up, and another 5 looking slightly down. Then move horizontaly and verticaly 1-1.5m to next shooting position.

According to the screenshots you provided, F2.8 and 1/15 - 1/30s might be not ideal. Try to increase ISO to 200 or 400 and set F to 4.0 for sharper images in corners. Sparse pointcloud is already looking good so far.

15

General / Re: How to best scan leaves/fern laying on a surface

« on: May 05, 2025, 08:56:30 AM »

Put that fern leaf on something like black/white news paper, so Metashape can better calculate camera positions and automatic lens distortion, because now the misalignment comes mostly from white grid uniform pattern surface and very simillar structure of fern leaves.