Messages

16

General / Re: Real time reconstruction with Metashape

« on: April 17, 2023, 03:13:07 AM »

I'm guessing one thing stopping a real-time calculation is how Metashape calibrates the camera during the first alignment step? So what if you used a fixed camera calibration that was determined previously? I've been very interested in the theory of real-time mapping. DJI Terra did this on the P4 but has kept this feature from the Mavic 3 Enterprise. I've even seen recently that some UAV LiDAR payloads have started to offer real-time geocoding. Is adding any type of real-time processing on the future road map for Metashape possibly? It would be an amazing tool for checking data while in the field.

17

General / Recovering data after a computer crash

« on: March 18, 2023, 10:39:11 PM »

How do I regain the data that took many hours to create? I can see the many GB of files in file explorer so how do I get Metashape to use them?  The processing had finished and I didn't manually save it yet. The crash isn't related to Metashape, I plugged in my Mavic after just getting back home and the driver was the reason for the crash. How is there not an auto-save option available? When doing batch processing why isn't the save after every step checkbox not on by default? This is a very important checkbox that needs to be switched on every time.

Thanks

18

Camera Calibration / Re: Filename extension "V" - What does it mean?

« on: March 18, 2023, 08:37:43 AM »

I'm guessing he's referring to this. It's what DJI names the images by default. I thought the V was given to the nadir photos during a smart oblique flight route. That's not the case though.

19

Feature Requests / List photos in order of altitude photo was captured.

« on: January 24, 2023, 05:15:08 AM »

If this has already been requested I apologize, I searched but was shocked that I couldn't find anything. Like the title says I'd like a way to order photos by altitude. I'm using an M3E to model a 400 foot radio tower and this would be very handy. The altitude is very easy to see in the photo's metadata. My mesh is missing sections towards the top as you can see in the image. Listing them in this order would make it easier to address these problem areas.

20

Feature Requests / Re: Import Video - Drone location metadata

« on: January 14, 2023, 09:10:40 AM »

You can. With subtitles enabled DJI saves a separate SRT file that holds the location and gimbal orientation metadata. If you have this SRT file in the same folder as the video when Metashape imports, then it'll take advantage of it.

21

General / Re: Yet Another Thin Object Scanning Thread

« on: January 10, 2023, 11:23:38 PM »

More photos

22

General / Yet Another Thin Object Scanning Thread

« on: January 10, 2023, 11:22:38 PM »

I'm finding it impossible to successfully finish my model of DJI M300 UAV. The thin prop blades are a nightmare for Metashape to do. I've tried several different settings and added the tweak that is discussed here- https://agisoft.freshdesk.com/support/solutions/articles/31000163220  and here- https://www.agisoft.com/forum/index.php?topic=14010.msg61763#msg61763


These attached images are all from different settings I've tried. Any further tips are appreciated.

23

General / Re: Problem with using depth maps of smartphones

« on: December 21, 2022, 05:47:45 AM »

I don't understand why this wouldn't work? The iPhone LiDAR sensor has the same resolution as my V60's? I know Apple has many different 3D Scanning apps to choose from. Android has only one that takes advantage of depth sensors. How does Apple handle the LiDAR metadata in photos? Maybe that's where the issue is, I don't know.

Source- https://www.techinsights.com/blog/apple-iphone-14-image-sensor-preliminary-analysis#:~:text=The%20iPhone%2014%20Pro%2FMax%20LiDAR%20camera%2C%20with%20a%200.3,Max%20LiDAR%20(Figure%2010).

24

General / Re: Problem with using depth maps of smartphones

« on: December 09, 2022, 10:38:23 PM »

Yes those depth maps were imported with the original image. I was expecting a black and white depth map, like Photopea shows too. I guess Metashape is upscaling the depth map upon import automatically..? The ToF sensor has a much lower resolution of the 16 MegaPixel RGB photo.

25

General / Re: Problem with using depth maps of smartphones

« on: December 09, 2022, 06:25:48 AM »

Metashape

26

General / Re: Problem with using depth maps of smartphones

« on: December 09, 2022, 06:24:24 AM »

This isn't addressing the issue you're having...

 It seems us two are determined to help Agisoft implement this depth map feature in the best way possible. I took some test shots today and wanted to show what my LG V60's portrait mode looked like in Photopea and Metashape. It's sad that when imported into Lightroom or Photoshop it's just a single layer photo and you'd never know about the depth map layer. A free browser based editor shows you 3 extra layers within the image though. I haven't had a chance to collect a whole dataset to see what the outcome is but will soon.

27

General / New Import Depth Image feature

« on: December 07, 2022, 08:24:18 AM »

Being able to import photos with a depth map image in the meta data is what I've been asking for since I first started using Metashape. It works and it works very well, however, it has a few things I'd like to bring to the devs attention hopefully.
I'm using an LG V60 with the ToF sensor. The only way I know how to capture the depth data needed is by using the portrait mode on either the stock camera app or a GCam app that's been ported over from the Pixel phones. This mode does some heavy post processing on the main photo captured. My V60 has a top notch manual mode with great results but no way to use it and capture depth data with it. This isn't Agisoft's fault by any means but something I had to mention.
What could be done differently is during the import process though. I've found that if an object is too close to the ToF sensor at the time the image is taken, the depth data isn't saved but the normal photo is. You have no way of knowing which photos in your dataset have a depth map along with it or not. So when importing a large group of photos and a few mixed in didn't capture the depth data... Instead of just not importing those few images it refuses to import any of them. Good luck sifting through the 100's of photos to find the few rotten apples.

I love the new feature and I'm not complaining a bit. I'm just wanting to help make it reach it's full potential.

Thank you!

28

General / Re: Cloud Server

« on: December 06, 2022, 12:47:57 AM »

This won't be the answer you're looking for but I thought I'd chime in.

With my current home Spectrum upload speeds (10mbps) it would take 40 days 17 hours 46 mins to upload 4TB. I've requested a feature here in the past to remotely upload to the cloud. That way people like me with crazy slow upload speeds could take an external HD to greener pastures and do it.

Pricing wise (may not matter in your case) it's going to cost you $500 for storage alone. Add in all the hours for processing, you could buy a high end desktop PC for near the same price of one project.

Something to consider.

29

Feature Requests / Re: Sort Photos by Quantity of Markers Detected

« on: August 31, 2022, 06:28:39 AM »

That worked perfectly. Thank you.

30

General / Re: Georeference missing in .mov video frames (?)

« on: August 19, 2022, 05:06:20 AM »

Thank you very much, Agisoft support has been very helpful. I shall give this all another go and save the SRT file this time around.