Recent Posts

11

Feature Requests / Batch Jobs [Apply to] support current chunk option

« Last post by howcanoewang on April 18, 2024, 07:18:50 AM »

I am wondering if it possible to support the drop down menu of batch jobs with  [current chunk] or [active chunk]

My current batch job workflow needs to apply for the last new added chunk after data collection each day. However, I tried the [unprocessed chunks] option but it sometimes run all chunks rather than the new chunk. Manual editing [selected] every time is an option but a little bit time-consuming and frustrating.

I do understand that using python script is possible to completely control and apply to the active chunk, but writing python code is not so efficient and clear compare to the batch Job UI setting (and for other collages who are not familiar with API), especially for these jobs with dozens of parameters.

In this case, personally believe supporting the Apply to [current chunk] could be a better option for this senenario.

Any ideas or comments for this feature request?

12

Python and Java API / Model vertex coordinate to camera frame

« Last post by SamT on April 18, 2024, 07:01:08 AM »

Hi all!

Just looking for the method to project a model vertex to spherical camera u,v coordinates for a non-georeferenced model. Having a hard time figuring out the transforms.

Appreciate any help.

13

General / Diffuse Texture isn't "seamless" after Photoshop adjustments...?

« Last post by JohnyJoe on April 18, 2024, 04:32:00 AM »

Photogrammetry (3D Scanning) Diffuse Texture isn't "seamless" after Photoshop adjustments (Shadows/Highlights) - WHY ?
Hello

Im doing a scan of smaller object (orange (fruit); but it doesnt matter, could be anything and the problem happened on and off previously with various scanned models). Im doing the diffuse texture in Agisoft Metashape from the original photos that were used for point cloud, mesh etc. generation ( i dont use another special, separate set of photos (adjusted) just for diffuse texture generation (as is often the case/recommended in a more proper photogrammetry workflow)).

I just use the Photoshop feature/function "Shadows/Highlights" (Image - Adjustments - Shadows/Highlights) to "somewhat" remove highlights and shadows from the Diffuse texture.

(I use indoor scanning setup on a rotating lazy susan with 2 softboxes for lighting so the lighting is "quite" (well... somewhat) even to begin with)


It usually works ok for me (for my "quality  level demand"), but SOMETIMES, as happened currently the (in photoshop) adjusted texture (if applied on the 3d object (in 3ds max)) suddenly gives/shows seams among the UV unwraped islands, picture:
https://prnt.sc/PVMLKlufpM0G

Original Diffuse texture (UNaltered in photshop in any way) doesnt have the seams:
https://prnt.sc/pMKC5ZcR6yKo

I dont know... I vaguely remember that it might have happened before sometimes (maybe..?)  but usually i dont see any problems... Now i do... My understanding is that the shadows/highlights function in Photoshop should work on the whole image "equally" so no "showing seams" problem should occur... Its like if your original diffuse texture doesnt show seams, and you for example, whatever... brighten, darken, add contrast, add color tint, change color balance etc. whatever you do with the texture in Photoshop, if there were no seams in the original diffuse texture, there should be NO seams visible even on the new adjusted one...? Right..? And it doesnt show AFAIK with brightening, darkening, changing color balance whatever...  BUT for some reason it shows (suddenly?) with Shadows Hightlights...? Why is that?

Again i think i MIGHT have gotten this problem MAYBE before but it was NOT often, i cannot even remember it really... But suddenly it shows with the newest model i work on... ( i didnt play with photogrammetry for months really)?

14

Python and Java API / Mesh export world origin

« Last post by vkam on April 18, 2024, 04:22:08 AM »

Hello,

I am generating a mesh from a multi-camera capture. I supply the camera extrinsic file, which has a world coordinate reference near the central camera in array. The mesh generates correctly, but the world reference for the mesh has been moved. So now, my camera extrinsic data and mesh object no longer have a common world coordinate reference.

How do I a) avoid movement of world coordinate reference or b) dump new camera extrinsic information. Using chunk.exportReference() did not work when invoked as follows:

mchunk.exportReference(path=<my_path>, format=Metashape.ReferenceFormatXML, items=Metashape.ReferenceItemsCameras, columns='nxyzabcuvw')

Thanks in advance for your help!

VKam

15

General / Re: Automatic GCP identification

« Last post by fsg on April 17, 2024, 05:23:31 PM »

Very interesting discussion.

Is there any progress on this topic? Is there a better solution now or any other news?

Normally we are working with sprayed crosses, but i would try it with Metashape Markers if its work reliable now when im flying above 30 m.

16

General / Re: DEM Fill Tool

« Last post by Alexey Pasumansky on April 17, 2024, 03:46:30 PM »

Hello Dave,

We are currently working on fixes in DEM editing tools behavior and few are to come in the next version update, however, we were not able yet to reproduce the fill issue, when by default you get the value larger than max DEM value.

If you are working in Metashape Pro 2.1.1, maybe then you can share a sample project, where this issue can be reproduced: PSX project file that includes camera alignment results, DEM and drawn shapes.

17

General / Re: Splitting up a multicam rig after the alignment process?

« Last post by HaydenMartin on April 17, 2024, 01:48:30 PM »

Well ideally both! Haha

Would be awesome to know how to split up the master/slave cameras after alignment

And would also be awesome to edit the script so it works with multicams

18

General / Re: Large error for the estimated yaw/pitch/roll

« Last post by Alexey Pasumansky on April 17, 2024, 12:09:59 PM »

Hello Jacky,

In case you are using different convention for XYZ axis orientation, I think you should expect that camera orientation angles estimated in Metashape would not correspond to your expectations in this case.

But if you use Z-up, Y-north, X-east orientation, then you need also to check, the rotation order and direction convention defined in Metashape for yaw, pitch, roll angles, see pages 97-98 of Metashape Pro manual:
https://www.agisoft.com/pdf/metashape-pro_2_1_en.pdf
You may need to input some offset values to Camera Calibration -> GPS/IMU Offset tab for the camera orientation angles to fit the expected convention. For example, if in your case pitch=0 means that camera is looking straight forward, you need to use 90 degree offset, as pitch=0, roll=0 in Metashape means that camera is looking vertically down.

19

General / Re: Splitting up a multicam rig after the alignment process?

« Last post by Alexey Pasumansky on April 17, 2024, 12:00:48 PM »

Hello HaydenMartin,

Do you actually need to "split" master+slave systems into independent calibration groups, or whether you require any modification to Gaussian splatting script so that it could work with multi-camera systems?

20

Python and Java API / Re: Metashape model.pickPoint issue in version 2.1

« Last post by Fabio Cassinelli on April 17, 2024, 11:38:12 AM »

Hello Alexey

Sorry, I missed your reply.

I run a separated Python script. This problem is present also in 2.1.1 version.

This is the function in a loop that is very slow:

Code: [Select]

chunk.model.pickPoint(camera.center, camera.transform.mulp(sensor.calibration.unproject(Metashape.Vector(i))))

Also adding

Code: [Select]

Metashape.app.model_view.view_mode = Metashape.DataSource.ModelData

outside the loop does not solve the problem.

Fabio Cassinelli