Topics

1

Bug Reports / Performance degradation after optimization and alignment errors

« on: February 22, 2025, 05:00:24 PM »

Hi Alexey,

Some image sets are aligned incorrectly in version 2.2, but I only notice the misalignment after generating the DEM, so I use markers to manually realign.

So two things happen: if realignment optimization has already been applied, it takes an excessive amount of time to complete the manual alignment compared to a set that has not been optimized.

And another situation is that if a set has images without coordinates, they will almost always not be aligned with the others. I did a test in version 1.8.6 and the same dataset was aligned the first time and without any imperfections, with the DEM smooth and wrinkle-free.

Another test was activating the adaptive camera with a set that has more than one type of lens or camera model, the alignment always fails in version 2.2.1 requiring intervention with markers to correct even if they have precise coordinates, and again in 1.8.6 it passed perfectly the first time.

And when version 2.2.1 finishes the alignment, I notice that the global error is 0.23m and after optimization it reaches 0.048m. With filtering, we reach 0.02m. In version 1.8.6, the accuracy is 0.0186m the first time without needing to optimize after alignment.

2

Python and Java API / How to Synchronize Photo Advancing

« on: January 11, 2025, 07:35:27 PM »

Hi,

I’ve been trying to create a script that allows me to open multiple photos simultaneously in Metashape and advance through them together (synchronized). Currently, I can open multiple photos, but advancing to the next one only works individually.

Here’s the part of my script where I try to advance all selected photos:

Code: [Select]

for camera in current_cameras:
    try:
        current_index = all_cameras.index(camera)
        next_camera = all_cameras[current_index + 1]
        camera.selected = False
        next_camera.selected = True
    except IndexError:
        Metashape.app.messageBox("Reached the end of the photo list.")
        break

It works, but only advances one camera at a time. Is there a built-in function or better approach to synchronize advancing for all opened photos at once?

Thanks in advance for any suggestions!

3

Python and Java API / Issues with Camera Alignment in Metashape 2.2

« on: November 27, 2024, 04:53:56 PM »

Code: [Select]

def align_images(document, cameras_to_align):
    if cameras_to_align:
        chunk = document.chunk
        unaligned_cameras = [cam for cam in cameras_to_align if cam.transform is None]
       
        if not unaligned_cameras:
            print("No cameras to align: all are already aligned.")
            return
       
        chunk.matchPhotos(cameras=unaligned_cameras, downscale=1,
                          generic_preselection=True, reference_preselection=True)
        chunk.alignCameras(cameras=unaligned_cameras, reset_alignment=False)


Hi Alexey,

I am encountering an issue related to camera alignment in Metashape Professional, which appears to have been introduced in version 2.2.0. This issue was not present in version 2.1, where the same workflow functioned correctly.

Some cameras that were previously aligned in the project are being misaligned when new groups of cameras are processed. My workflow is designed to align only the unprocessed cameras while keeping the previously aligned ones intact, but this behavior is not being respected in version 2.2.0. I tried including reset align=False but that didn't work either.

4

Feature Requests / Command to Advance All Open Photos Simultaneously

« on: November 16, 2024, 11:13:03 PM »

Hi Alexey,

I would like to suggest a new feature for Agisoft Metashape.

When multiple photos are opened in the viewer, it is currently necessary to advance them one by one. This process can be time-consuming when working with a large number of images.

My suggestion is to implement a command or shortcut that allows all open photos to advance simultaneously, synchronizing the movement across all viewer windows. This feature would significantly streamline workflows involving the visual analysis of multiple images.

Thank you for your attention to this request! I would be happy to provide additional details if needed.

Best regards,

5

Bug Reports / Mask 2.2.0

« on: October 19, 2024, 10:58:17 PM »

Hi Alexey,

I generate my masks externally using AI, and in the latest version (2.2.0) of Agisoft, I’ve been facing issues when importing these masks. In version 2.1, I could easily import the first mask and then use the "union" option to add the rest. However, in the current version, the "union" option doesn’t seem to work at all, or I might be using it incorrectly.

Now, after importing the first mask, the process already takes longer, and then I have to manually use the "merger masks" option to create the final mask. This additional step significantly increases the time spent on the task, more than doubling the time compared to version 2.1.

Could you clarify if I’m missing something regarding the "union" option, or if there is a fix in progress? It would be very helpful to restore the previous workflow, as it was much more efficient for handling large numbers of masks.

Thank you for your help!

6

Bug Reports / VIDEO IMPORT

« on: June 07, 2024, 03:25:57 PM »

Hi,

I am facing an issue with frame positioning when using metashape with videos captured by the GoPro 11. When I import videos from the GoPro 7, the frame positions are proportional to reality and everything works correctly. However, when importing videos from the GoPro 11, this correct positioning association does not occur, resulting in frames being hundreds of meters off from the correct location.

I would like to emphasize that the telemetry analysis of the GoPro 11 video has excellent positional accuracy, and the paused frame of the video corresponds exactly to the real location. The problem specifically occurs when generating the JPGs or PNGs in Agisoft, which do not match the correct location.

Has anyone else experienced this issue or knows how to correct this positioning discrepancy when using the GoPro 11 in Agisoft?

7

Feature Requests / CHECK/UNCHECK API (SOLVED)

« on: March 16, 2024, 03:04:27 PM »

Hi,

I'm reaching out to suggest a potential addition to the Metashape API that I believe could benefit many users. While the current API offers great flexibility, including enabling/disabling cameras (enabled) and selecting/deselecting them (selected), it seems there's no direct way to programmatically "uncheck" images for processing based on specific criteria (e.g., location accuracy).

Many of us automate workflows where pre-selecting images based on metadata or quality metrics is crucial before proceeding to resource-intensive processing steps. For instance, being able to automatically uncheck images with location accuracy below a certain threshold could save significant time and enhance the quality of project outputs.

Could we consider adding a method to the API to control the "check" state of images in the Reference Panel or before processing? This feature would provide even greater control over automated workflows and potentially improve processing efficiency and outcomes.

Code: [Select]

import Metashape
doc = Metashape.app.document
chunk = doc.chunks[0]
for camera in chunk.cameras:
    # Checks if the camera has a defined reference and location accuracy
    if camera.reference and camera.reference.location_accuracy:
        accuracy = max(camera.reference.location_accuracy.x, camera.reference.location_accuracy.y,camera.reference.location_accuracy.z)
        print(f"Camera {camera.label}: Accuracy = {accuracy}") # Prints the accuracy
        if accuracy > 9:
            camera.selected = False
            print(f"Camera {camera.label} unselected due to high accuracy.") # Print the action

Best,

8

Bug Reports / Infinite values in transform V.2.1.0.17526

« on: January 25, 2024, 07:06:29 PM »

Code: [Select]

2024-01-25 12:57:59 1 blocks: 4593
2024-01-25 12:58:05 block: 3 sensors, 4593 cameras, 4506674 points, 14742630 projections
2024-01-25 12:58:05 block_sensors: 0.00254059 MB (0.00254059 MB allocated)
2024-01-25 12:58:05 block_cameras: 1.78713 MB (1.78713 MB allocated)
2024-01-25 12:58:05 block_points: 206.299 MB (219.429 MB allocated)
2024-01-25 12:58:05 block_tracks: 17.1916 MB (17.1916 MB allocated)
2024-01-25 12:58:05 block_obs: 674.864 MB (674.864 MB allocated)
2024-01-25 12:58:05 block_ofs: 34.3832 MB (34.3832 MB allocated)
2024-01-25 12:58:05 block_fre: 0 MB (0 MB allocated)
2024-01-25 12:58:05 final block size: 4593
2024-01-25 12:58:06 adding 3996297 points, 0 far, 789281 inaccurate, 10436 invisible, 916 weak
2024-01-25 12:58:06 (3 px, 2 3d) sigma filtering...
2024-01-25 12:58:08 adjusting: - nan -> nan
2024-01-25 12:58:19 point variance: 1.69192 px, threshold: 5.07577 px
2024-01-25 12:58:21 adding 767565 points, 133804 far (5.07577 px threshold), 758903 inaccurate, 8020 invisible, 1168 weak
2024-01-25 12:58:22 adjusting: - nan -> nan
2024-01-25 12:58:32 point variance: 1.05102 px, threshold: 3.15307 px
2024-01-25 12:58:33 adding 736792 points, 123068 far (3.15307 px threshold), 729916 inaccurate, 6026 invisible, 1065 weak
2024-01-25 12:58:35 adjusting: - nan -> nan
2024-01-25 12:58:44 point variance: 0.788759 px, threshold: 2.36628 px
2024-01-25 12:58:45 adding 715358 points, 96357 far (2.36628 px threshold), 709650 inaccurate, 4868 invisible, 1301 weak
2024-01-25 12:58:46 adjusting: - nan -> nan
2024-01-25 12:58:54 point variance: 0.677631 px, threshold: 2.03289 px
2024-01-25 12:58:56 adding 702639 points, 65034 far (2.03289 px threshold), 697230 inaccurate, 4266 invisible, 1423 weak
2024-01-25 12:58:57 adjusting: - nan -> nan
2024-01-25 12:59:05 point variance: 0.623643 px, threshold: 1.87093 px
2024-01-25 12:59:06 adding 695379 points, 40811 far (1.87093 px threshold), 690054 inaccurate, 3981 invisible, 1525 weak
2024-01-25 12:59:06 optimized in 59.735 seconds
2024-01-25 12:59:13 Error: Infinite values in transform are not allowed
2024-01-25 12:59:13 processing failed in 75.271 sec
Hi Alexey,

I've never seen this before. I checked the coordinates, none were out of range. What I only noticed is that after version 2.0 some images are aligning with astronomical displacements, something that didn't happen before in previous versions.

9

Bug Reports / Can't Select Tile Size - Dual GPU V2.1.0.17526

« on: January 13, 2024, 11:23:08 PM »

Hi Alexey,

On the network, in the "Match photos" processing step, if the GPU mask "Use default GPU mask" and have Dual GPU, I get the message "Can't select tile size", I checked msg and it was there, GPU with memory zero.

Code: [Select]

2024-01-13 16:32:55 Free VRAM: 0 MB, maximum allocation required: 2047 MB, memory required: 0 MB
2024-01-13 16:32:55 [GPU] photo 5608: 40000 points
2024-01-13 16:32:55 Error: Can't select tile size
2024-01-13 16:32:55 processing failed in 9.154 sec

But the GPU drivers were updated.
 
Solution, I had to isolate the GPUs and defined Nmask "1,0" and "0,1" for each GPU and there was no more error message, completing the step without memory overflow.

Code: [Select]

2024-01-13 17:17:31 Found 2 GPUs in 0.182 sec (CUDA: 0.127 sec, OpenCL: 0.055 sec)
2024-01-13 17:17:32 Using device: NVIDIA GeForce RTX 2080, 48 compute units, free memory: 7110/8191 MB, compute capability 7.5
2024-01-13 17:17:32   driver/runtime CUDA: 12030/10010
2024-01-13 17:17:32   max work group size 1024
2024-01-13 17:17:32   max work item sizes [1024, 1024, 64]
2024-01-13 17:17:32   got device properties in 0 sec, free memory in 0.76 sec
2024-01-13 17:17:55 211487 matches found in 24.065 sec
2024-01-13 17:17:56 matches combined in 0.057 sec
2024-01-13 17:17:56 filtered 95567 out of 148497 matches (64.3562%) in 0.105 sec
2024-01-13 17:17:56 saved matches in 0.093 sec
2024-01-13 17:17:56 processing finished in 124.34 sec

Version 2.1.0 build 17526, in previous 2.0.3 same dataset without problems.

10

Bug Reports / Vertical Datum Issue Network

« on: January 04, 2024, 09:59:44 AM »

Code: [Select]

2024-01-04 03:53:56 loaded camera partition in 0.001 sec
2024-01-04 03:53:56 Error: Vertical datum missing: WSG84 to LOCAL
2024-01-04 03:53:56 processing failed in 0.364 sec
Hello Alexey,

I'm working with local vertical data. On the PC where creation works fine on the network and local, but the nodes print this error.

11

Bug Reports / Batch not work script over network

« on: January 03, 2024, 11:02:19 PM »

Code: [Select]
import Metashape
import sys, os, time

chunk = Metashape.app.document.chunk
chunk.reduceOverlap(overlap = 5, use_selection = False)

Metashape.Model.clear(chunk.model)

This simple script does not work in batch process run over network, in local batch process it works fine. In 2.0.4 it works on local and network. Current V. 2.1.0.17526

12

Feature Requests / Shortcut and Functionality Update for Advancing Multiple Image Tabs

« on: January 02, 2024, 01:11:54 AM »

Hi Alexey,

Currently, the "Photos>Open Next Photo" shortcut is limited to advancing to the next image only when there is a single tab at a time, i.e. only the active tab of the photo open. We would like to request an update to this shortcut, allowing it to work when more than one image tab is open and they all move forward or backward together.

Additionally, it would be beneficial if the user could keep a reference tab, such as the "Ortho" tab, visible while multiple image tabs are loaded. When calling the shortcut, we expect all images to advance simultaneously, providing a more efficient viewing experience.


Best Regards,

13

Bug Reports / Import Laser issues

« on: December 26, 2023, 09:13:17 PM »

Hi,

Trying to import 1365 laz, totaling 13 gb, after metashape creating the dense_cloud.500 folders this problem appears and the import does not continue. However, it continues creating the folders but generates an empty file, you need to stop, delete the empty ones, reopen, merge and continue the import.

Code: [Select]

2023-12-26 14:52:45 Importing point cloud...
2023-12-26 14:52:45 processing 1879121 points...
2023-12-26 14:52:45 Analyzing points...
2023-12-26 14:52:45 processing 1879121 points...
2023-12-26 14:52:49 saved point cloud in 0.137 sec
2023-12-26 14:52:49 Calculating normals...
2023-12-26 14:52:49 Warning! Calculating normals without known scanner position. Normals orientation may be broken for a complex geometry.
2023-12-26 14:52:49 Required 116.7627 GB RAM for extended block
2023-12-26 14:52:49 Available: 101.8174 GB
2023-12-26 14:52:49 Using small block
2023-12-26 14:52:49 Using 36 threads
2023-12-26 14:52:49 Expected max memory usage: 20.4346 GB
2023-12-26 14:52:58 computed normals in 8.02 sec
2023-12-26 14:52:58 Error: Can't open file: too many files open (24): F:/02 Process/lasers.files/0/0/dense_cloud.509/dense_cloud.oc3
2023-12-26 14:52:58 Peak memory used: 1.81 GB at 2023-12-26 14:52:56


14

Bug Reports / When the server is closed, all hosts go down together

« on: December 26, 2023, 04:41:46 PM »

Hello Alexey,

When the server needs to be closed, for some reason, such as to clear the host error list, we save the process list for a new import, restart the Server and all hosts reconnect and we move on.

In version 2.1 I noticed that when closing the Server all hosts are closed, which would require restarting each host. In 2.0 it was not necessary and earlier, it kept showing "can't connect" and when the server command was activated all connections were reestablished. As there have been changes, how can I avoid terminating the hosts' connection when closing the server and leaving them on standby.

Best regards,

15

Feature Requests / batch process optimization

« on: December 12, 2023, 10:17:12 PM »

Hi Alexey,

1. It often happens that there are images wrongly aligned with absurd distances, is there a way to select only those images with an error greater than "x" meters and reset the alignment?

2. There are also images that do not align automatically and for that I need to manually select them and ask them to align them in small groups. Is there a way to automate this selection and ask them to align the selected group again?

3. As the region box was wrong, I need to reset region, as I use batch for the processes, but I cannot use the reset region on network option, is there a way to implement it easy?

Best regards,