✏️ Job Creation
In the main window of Marso, enter the Job Name and path to Raw Files:
Job Name: A descriptive name that will be used to identify the scan throughout processing and once the results are ready. e.g Blue_Leather_Handbag
| Panel | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
When processing different versions of the same asset, use a naming system e.g object_v01 |
| Info |
|---|
Letters, numbers, hyphens, and underscores are allowed. Do not use special characters |
Raw Files: Specify the path to the raw images from the scan to be processed.
| Note |
|---|
Marso can only ingest camera RAW or DNG Files, it cannot read jpeg, png or exr Supported Files |
📷 Image Preparation
Once the above information has been entered, the Start button within the Raw Processing pane can be clicked to start the Prepare step.
The new job will appear in the lower pane as soon as it is started, and data preparation will run until its status changes from PREPARING to READY.
| Note |
|---|
If the status shows “Failed”, make sure that the selected Exposure Calibration in Settings is correct. Contact support if the issue persists. |
In addition to reading all data into Maraso, this step will also create ‘exr’ files that will be needed for the photogrammetry step.
When using a capture system that has multiple lights for each camera position or node, Marso will automatically create one ‘exr’ file for each group of lights as an averaged image
✅ When is a job ready?
When a job’s status is DO SOLVE, the Images button will open the photogrammetry images when clicked. The images in this directory must be used for photogrammetry for Marso to work correctly, however they can be adjusted as long as the name, shape, and orientation of each image is unaffected.
📐 Run your Photogrammetry
You can now proceed with your normal photogrammetry reconstruction workflow. You must use the exror jpg files created in the previous step.
We currently support Agisoft Metashape or Reality Capture as your photogrammetry application.
📝 Checklist
3D Mesh and camera solve
It is important to get a good solve of the cameras within the scene, poorly solved cameras can lead to artifacts in the material measurement later on. We recommend attempting to re-align any bad camera solves or removing those cameras from the 3D solve all together.
| Note |
|---|
A high number of polygons in the mesh may cause Marso to exceed the available VRAM on your system. If this occurs, simplify the mesh and reattempt the process. Marso does produce highly detailed normals even on medium to low poly meshes. See Examples |
When drawing a bounding box around your subject for mesh reconstruction, it is important to also include any stands or supports (if not using the mask mesh feature). This additional geometry will ensure that pixels are correctly traced onto this geometry and not onto the subject itself. Using one of the lower cameras (as shown below) can be a helpful reference to see how much geometry is required to avoid unwanted pixels being projected onto the subject.
| Info |
|---|
  |
| Warning |
|---|
  |
| Info |
|---|
Using a Mask Mesh will allow you to reconstruct just the subject, whilst avoiding occlusion issues by providing a Subject-Mesh & Mask-Mesh |
UV Unwrapped Mesh
The 3D mesh that Marso will create textures for will require a UV unwrap. By default, a 3D mesh within a photogrammetry application will not have a UV, so you must first run the texturing process within the application or UV unwrap manually. (The mesh must have a single unwrap not multiple)
| Info |
|---|
For optimal UVs we recommend generating the texture at the same resolution or lower resolution than what you wish to output from Marso. Example: A RealityCapture texture of 1024px can be used to create a Marso texture of 1024 > 8192px , but may create artifacts if Marso attempts to create a 512px texture. |
Scale the Scene
It is essential that the 3D scene is correctly scaled, we suggest using markers to automatically set the scale of a scene within RealityCapture or Agisoft Metashape Pro.
| Expand | ||
|---|---|---|
| ||
Agisoft Metashape Standard does not offer a way to automatically set scale. For best practice, we recommend using Blender (a free 3D application) to do this by hand.
Open a new ‘General’ blender scene and Delete all of the Default objects, you scene should look like this: To Import an Alembic file : After importing, the mesh and cameras should be in your scene. Create an empty object, this will be used to apply the same scale to the mesh and all the cameras: Select everything except the ‘Empty’: Then Shift+Drag the selected items into the empty: It should look like this: Using the measure too Then compare this distance to the real life distance. If you divide this distance by the real life distance you end up with a scale factor. On the object properties menu for the ‘Empty’, insert the computed scale factor into the three scale input boxes: Use the measure tool again to confirm the distance is now correct. Now select all cameras and the mesh, press Alt+P to bring up the Clear Parent dialog, and select Clear and Keep Transformation: Delete the ‘Empty’ from the scene, your outline should only have the cameras and mesh now: Now export the scaled alembic: This scaled alembic is the one you want to select during the run dialog in Marso. |
| Expand | ||
|---|---|---|
| ||
This can be done quite easily by using markers and setting a scale bar. |
| Expand | ||
|---|---|---|
| ||
This can be done quite easily by using markers and setting a constraint, then updating the alignment to apply the constraint. |
Export Alembic Mesh & ST Maps
Export an Alembicabcfile with cameras & normals enabled, also export an ST Map as anexrwhich will be used to account for lens distortion. It is important to use an ST map created within the photogrammetry application rather than
| Info |
|---|
It is important to use an ST map that has been created within the photogrammetry application you have used to solve the 3D scene to avoid any discrepancies. |
| Expand | ||
|---|---|---|
| ||
Exporting an ST MapIn Agisoft Metashapes, by default, all cameras should solve into a single group resulting in them all sharing the same lens distortion profile. Go to :  You should see a single-camera group on the left pane. 
Switch from the  Set the Save as Type to be :  Exporting an AlembicTo export the alembic :  After clicking save, an Export Model window will appear. You must enable :
 |
| Expand | ||
|---|---|---|
| ||
Exporting ST Maps:Go to
Exporting AlembicGo to
|
| Panel | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
Optional UV Editing Photogrammetry → .abc → UV Unwrap → .abc → Marso Just be sure to adhere to the following:
|
Starting Photogrammetry Process Materials ➡️