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.

Topics - Mariusz_M

Pages: [1] 2
Feature Requests / Pause/play button for background processing
« on: December 15, 2022, 04:23:07 PM »
I often process big projects and they run in the background for a few days. Every time I want to pause processing and use my computer for something else, I first need to re-open the project to pause it. It would be so much easier if I caould just pause/resume background processing with one click without loading the project abck into the memory.


It has actually been happening for the last few versions and sometimes is quite annoying. I have an integrated Intel UHD and Nvidia RTX 3070. So obviously I only want to use the Nvidia adapter and this is the only one switched on in the preferences. Hovewer, from time to time, quite randomly, I see in the console that Metashape uses both GPUs. Then I go to preferences and see both GPUs ticked. So I untick one and work on the project for several days and then it happens again.

Also, even when Intel GPU is switched on, it still seems to be used during depth maps generation alog with the NVIDIA GPU. Is it normal?

Feature Requests / Add UNDO support for accidently deselected selections
« on: February 01, 2022, 09:22:39 PM »
Sometimes I use the selection tools on a mesh, creating a quite complicated selection using SHIFT and CTRL keys. But if I accidently do not press either of the keys, all the selection gets lost and I need to start again. UNDO does not work in this case. Can you please change it? So next time I accidently deselect what I have spent 20 minutes on selecting, I will just undo deselection and continue selecting.

I use intelligent scissors a lot and I have a high DPI screen. So the points created with the tool are very small. It does not affect the process so much, but when I want to close the poligon, I actually need to zoom in a few times and it is still difficult to click exactly where the starting point is. If the points were bigger or it was possiible to click near the point to auto close, it would be so much easier.

Also, the auto close option should be available in the right click menu. So every time I wanted to close the selection created with the tool, I would just use the option auto-close and Metashape would just connect the last point with the first a straight line, even if they were far apart. So much easier.

I use the magic wand tool for maskig a lot. And since the beginning, to change the tolerance of the tool, I have to go to a separate tool/window, set the new value and come back to using maric wand. Can you please make the tolerance setting available every time the wand is used, so I can easily readjust the tolerance each time I need it?

Quite often, when processing textures, I end up with some low quality patches. It happens only because Metashape chooses a more distant photograph to use in that particular spot. Could you pleas add a tickbox to texture generation box that would prioritise the closest and therefore most detailed photos. It would save a lot of manual work I need to do with disabling the farthest photos at texture generating stage.

Bug Reports / Standard 1.8 crashes windows during mesh generation
« on: January 19, 2022, 11:26:57 PM »

I tried to proces a mesh(from depth maps) under Standard 1.8 in a project that I had processed multiple times under earlier versions. The project has 3652 photos aligned. It crashed windows twice exactly at the same stage of the process.

2022-01-19 19:30:55 Marching cubes: part #3/7...
2022-01-19 19:31:11 Data preloaded in 16.411 s (1381 MB -> 4738 MB, 288.766 MB/s)
2022-01-19 19:31:55 cubes part marched in 32 mini parts: 1.56597e+06 avg cubes -> 547732 avg faces -> 158021 avg decimated faces = avg ratio x3.46619, done in 60.381 s (28% cubes IO + 2% sorting + 50% marching + 19% decimating + 0% saving)
2022-01-19 19:31:55 Marching cubes: part #4/7...
2022-01-19 19:32:14 Data preloaded in 18.668 s (1663 MB -> 5703 MB, 305.517 MB/s)

The full log from that session is attached as a ZIP file, because it is over 5MB. The log from previous session is exactly the same. Crash happens during part #4/7.

There is no trace of a problem in Windows event log and at both times I was not looking at the screen when it happened. I just came back after an hour and my computer has already rebooted.

So I unistalled 1.8 and re-installed 1.7.5 and run the same process. The problem did not occur.

I have Nvidia 3070 and 32GB of RAM. I have successfully used this setup for projects that have 45000+ photos under 1.7.5 and earlier vesrions. So it is not the matter of my computer or the number of photos. It is just some issue with version 1.8. I cannot be more precise, because there is no trace what went wrong.

General / Processing a massive underwater photoset without GPS
« on: October 23, 2021, 09:57:39 AM »

I am processing a massive underwater photoset (so far 50 000 photos) and I keep taking 10 000 photos every day. There is no GPS data and I am looking for a solution to speed up the matching part of the process. Therefore, I need to understand how each of the following work.

1. Reference preselection set to sequential + generic preselection. What is it going to do? Will the program do the sequential preselection first and only the photos that have no pair will have generic preselection applied? Or will it do the generic preselection for all photos, finds all matches and then also add sequential preselection on top to find even more matches and actually extend the length of the process?

2. Reference preselection set to seqential while every second photo disabled, so only half of the photos are being aligned. Provided that they will align somehow... Then I enable the other half of the photos and what are my options then? Sequential again? Or perhaps Estimated? With generic preselection on or off?

Any other ideas how to match only the photos that should be matched?

Bug Reports / 1.7.1 Mesh colour disappears when closing holes
« on: January 29, 2021, 12:07:11 AM »
Now when I now close holes on a coloured mesh, the colours disapear and I have to reprocess them again. It used to close the hole and the new faces had colours from neighbourhood triangles. But now all colours are gone and I need to colorize again.

Feature Requests / Lock photos/jobs/console window location
« on: January 27, 2021, 06:17:02 PM »
It would  be great to have a small paddlock icon on the photos/jobs/console window which would allow me for locking the windows in place as they are, so it would be impossible to acidently move them when masking photos.

Bug Reports / Avi file wrong duration when exporting animation in 4K
« on: January 27, 2021, 05:54:27 PM »
There is a problem in Metashape Standard version 1.66 (and probably 1.7.1, as there is no mention in the changelog about it) with generating AVI files in 4K. In 1080 I can easily export 2-minute MJPEG videos at 60 fps, but when I switch to 4K 60 fps I end up with a 15 GB AVI video that every program sees as 1 second long and it is impossible to convert. But the correct video stream is there and it plays normally on the build in Windows 10 player. It just has wrong duration and every converter stops converting after the first second.


I am workng on a relatively small project for me, less than 2000 photos (I usually process bigger). Up until yesterday, everything worked smoothly under Metashape Standard 1.6.6. Then I updated to the newes release as suggested by the software. Since then I cannot process depth maps. Every time depth map generation is in progress, Metashape closes itself. But there is no error message in the log.

2021-01-06 21:40:35 [GPU 1] Camera 1694: level #4/4 (x4 downscale: 998x561, image blowup: 1996x1121) done in 1.331 s = 33% propagation + 61% refinement + 2% filtering + 0% smoothing
2021-01-06 21:40:35 [GPU 1] group 1/1: estimating depth map for 21/39 camera 1761 (40 neighbs)...
2021-01-06 21:40:37 [GPU 1] Camera 1761 samples after final filtering: 89% = 100% - 2% (not matched) - 1% (bad matched) - 0% (no neighbors) - 2% (no cost neighbors) - 5% (inconsistent normal) - 1% (estimated bad angle) - 0% (found bad angle) - 1% (speckles filtering)
2021-01-06 21:40:37 [GPU 1] Camera 1761: level #4/4 (x4 downscale: 998x561, image blowup: 1996x1121) done in 1.159 s = 33% propagation + 60% refinement + 3% filtering + 0% smoothing
2021-01-06 21:40:37 Peak VRAM usage updated: Camera 1761 (40 neihbs): 507 MB = 160 MB gpu_tmp_hypo_ni_cost (32%) + 128 MB gpu_neighbImages (25%) + 34 MB gpu_depth_map (7%) + 34 MB gpu_cost_map (7%) + 34 MB gpu_coarse_depth_map_radius (7%) + 34 MB gpu_coarse_depth_map (7%) + 25 MB gpu_normal_map (5%) + 12 MB gpu_neighbMasks (2%) + 12 MB gpu_tmp_normal (2%) + 8 MB gpu_mipmapNeighbImage (2%)
2021-01-06 21:40:37 [GPU 1] group 1/1: estimating depth map for 22/39 camera 1762 (38 neighbs)...

Windows event log shows only a general application crash, nothing speficic. But is has something to do with: C:\WINDOWS\System32\ucrtbase.dll.

I have tried on other similar projects and the result is the same - a quiet unexpected crash.
I have just tried on a project that has 58 cameras and everything worked. So the problem might have something to do with the number of cameras.

You might need my system info:

2021-01-06 21:59:02 Agisoft Metashape Standard Version: 1.7.0 build 11736 (64 bit)
2021-01-06 21:59:02 Platform: Windows
2021-01-06 21:59:02 CPU: Intel(R) Core(TM) i7-4790K CPU @ 4.00GHz (desktop)
2021-01-06 21:59:02 CPU family: 6 model: 60 signature: 306C3h
2021-01-06 21:59:02 RAM: 32.0 GB
2021-01-06 21:59:03 OpenGL Vendor: NVIDIA Corporation
2021-01-06 21:59:03 OpenGL Renderer: GeForce GTX 980M/PCIe/SSE2
2021-01-06 21:59:03 OpenGL Version: 4.6.0 NVIDIA 460.89
2021-01-06 21:59:03 Maximum Texture Size: 16384
2021-01-06 21:59:03 Quad Buffered Stereo: not enabled
2021-01-06 21:59:03 ARB_vertex_buffer_object: supported
2021-01-06 21:59:03 ARB_texture_non_power_of_two: supported

2021-01-06 21:59:11 Found 1 GPUs in 0.095 sec (CUDA: 0.02 sec, OpenCL: 0.075 sec)

I wish I could give you  more specific information, but there is no info whatsoever what is wrong. It just stops working while processing depth maps on bigger projects that worked with no issues for many years under previous versions.

Please fix the problem as soon as possible. For now I have downgraded Metashape to 1.6.6 until this issue is resolved. If you want me to test some tweaks on 1.7 I kept it as well. I can test some things out as long as I have clear instructions from you.

Bug Reports / Impossible to switch off markers in Standard Edition
« on: March 03, 2020, 04:15:29 AM »
Hi. I have a project that was initially made with the Pro eIition and now I loaded it back into Standard edition. The project has a few makers I no longer need, but they seem to be impossible to hide/remove in the Standard version. Can you please add an option to hide/remove markers under the Standard Edition?

Every time I want to quickly capture view I need to remember to switch off info, region, trackball and all other stuff that is needed for editing, but not always for publishing. It would be nice if show/hide switches/tickboxes were as options in the Capture View window.

Feature Requests / Remove duplicate camers
« on: January 06, 2020, 04:59:13 PM »
When working witch chunks and merging I often end up having duplicates of the same cameras. I would like to have a button to quickly ane easily remove duplicate cameras from the project.

So I think an option to find and compare duplicates is needed. It would display a list of photos that are used more than once within one project with their preview and info about:
1. Tie points (with preview)
2. Key points from this photo (with preview)
3. Location in 3d space with preview.

There are a few situations to consider before removing a duplicate:

1. When the duplicate camera has exactly the same key points/tie points - simple remove of the duplicate
2. When the duplicete camera has different key points/tie points  - option to choose which ones to keep or to merge key points/tie points
3. When the duplicate camera has different masks - option to choose or merge
4. When the duplicate camera is not exactly in the same place - option to chose which location to keep or to move remainging camera somewhere in between the  current duplicates are (based on some weight calculated using projection/reprojection errors) . After removing duplicates it would be recommended to run camera optimisation again.
5. Probably something else, but sorting out these 4 situations would be a good beginning.

Pages: [1] 2