Agisoft Metashape
Agisoft Metashape => General => Topic started by: Dmitry Semyonov on May 12, 2020, 08:38:46 PM
-
Pre-release version of Agisoft Metashape 1.6.3 is available for download.
This pre-release is considered as unstable and is not recommended for production use.
Please use the links below for download:
Agisoft Metashape Standard edition
Windows 64 bit (http://download.agisoft.com/metashape_1_6_3_x64.msi)
Windows 32 bit (http://download.agisoft.com/metashape_1_6_3_x86.msi)
Mac OS X (http://download.agisoft.com/metashape_1_6_3.dmg)
Linux 64 bit (http://download.agisoft.com/metashape_1_6_3_amd64.tar.gz)
Agisoft Metashape Professional edition
Windows 64 bit (http://download.agisoft.com/metashape-pro_1_6_3_x64.msi)
Windows 32 bit (http://download.agisoft.com/metashape-pro_1_6_3_x86.msi)
Mac OS X (http://download.agisoft.com/metashape-pro_1_6_3.dmg)
Linux 64 bit (http://download.agisoft.com/metashape-pro_1_6_3_amd64.tar.gz)
Agisoft Metashape Python 3 Module (requires Professional edition license)
Windows 64 bit (http://download.agisoft.com/Metashape-1.6.3-cp35.cp36.cp37-none-win_amd64.whl)
Windows 32 bit (http://download.agisoft.com/Metashape-1.6.3-cp35.cp36.cp37-none-win32.whl)
Mac OS X (http://download.agisoft.com/Metashape-1.6.3-cp35.cp36.cp37-abi3-macosx_10_8_x86_64.whl)
Linux 64 bit (http://download.agisoft.com/Metashape-1.6.3-cp35.cp36.cp37-abi3-linux_x86_64.whl)
Agisoft Metashape Java Library (requires Professional edition license)
Download (http://download.agisoft.com/metashape-java-api-1.6.3.zip)
Metashape 1.6.3 Change Log (http://www.agisoft.com/pdf/metashape_changelog.pdf)
Metashape 1.6.3 Python API Reference (http://www.agisoft.com/pdf/metashape_python_api_1_6_3.pdf)
Please let us know if you have any problems using this version.
Please post problems and/or questions concerning other Metashape version in separate topics.
This topic will be removed when the final 1.6.3 version is released.
EDIT:
Updated to version 1.6.3 build 10711.
-
change log is up to 1.6.2 - no info about 1.6.3
-
change log is up to 1.6.2 - no info about 1.6.3
Log is up to 1.6.3, not sure what you're seeing.
-
Firefox cache... ;)
-
I downloaded 1.6.3 Professional, Mac OS X and copied the MetashapePro.app to the applications folder. When I try to open, I get a message that "MetashapePro.app" is damaged and can't be opened.
I redownloaded and tried again with same results. Perhaps the dmg is corrupt?
Tom
-
Hello Tom,
What is the exact message that you are observing, can you please provide the screenshot or just the text of the message?
-
This is the message in case the screenshot does not show.
"MetashapePro.app" is damaged and can't be opened. You should move it to the Trash.
Tom
-
So with 1.6.3 I get some hard reboots when building meshes from depth maps, it seems to trash the GPU driver and Win10 reboots.
Windows log:
The Desktop Window Manager process has exited. (Process exit code: 0xc00000fd, Restart count: 1, Primary display device ID: NVIDIA GeForce RTX 2080 Ti)
Log Name: Application
Source: Dwminit
Date: 12/05/2020 14:18:36
Event ID: 0
Task Category: None
Level: Warning
Keywords: Classic
User: N/A
Computer: titan64
Description:
The Desktop Window Manager process has exited. (Process exit code: 0xc00000fd, Restart count: 1, Primary display device ID: NVIDIA GeForce RTX 2080 Ti)
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Dwminit" />
<EventID Qualifiers="32770">0</EventID>
<Level>3</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2020-05-12T12:18:36.827132700Z" />
<EventRecordID>10782</EventRecordID>
<Channel>Application</Channel>
<Computer>titan64</Computer>
<Security />
</System>
<EventData>
<Data>0xc00000fd</Data>
<Data>1</Data>
<Data>NVIDIA GeForce RTX 2080 Ti</Data>
</EventData>
</Event>
-
This is the message in case the screenshot does not show.
"MetashapePro.app" is damaged and can't be opened. You should move it to the Trash.
Tom
Try to switch off Gatekeeper or SIP temporarily. No problem here with 10.15.4.
-
Interesting. I always Right-Click on the app the first time to temporarily bypass Gatekeeper but for some reason that is not working. I never get the warning and the option to open anyway - only the message that the app is damaged.
Also running 10.15.4 and I have tried downloading and opening on two different machines.
Anybody got any other advice?
Tom
-
Hello Tom,
Have you copied the license file to the app bundle contents before running it for the first time?
-
Hello Alexey,
I have done so in the past but in the recent past, that has actually caused the issue so no, I did not do so with 1.6.3.
I have tried rebooting and a few other things and finally tried using the terminal command "xattr -cr /Applications/MetaBeta/MetashapePro.app" and that has worked.
I am not sure I want to have to continue to do so, but perhaps it helps troubleshoot what may be going on.
Tom
-
The 1.6.3 seems to be not properly signed/notarized:
❯ spctl -a -vv MetashapePro.app
MetashapePro.app: invalid signature (code or signature have been modified)
-
Hello Tom,
The signature of Mac OS packages should be fixed in Metashape 1.6.3 build 10638. Can you please try the updated version?
-
Hello Willi,
Can you please check if mesh generation from depth maps works fine in the updated Metashape 1.6.3 build 10638?
If GPU driver still crashes, please let us know exact NVIDIA driver version you are using.
Also it will be helpful if you could provide a Metashape processing log up to the moment of the driver crash. You can save it by enabling Write log to file option in the Metashape Preferences dialog before starting processing.
-
Hello Tom,
The signature of Mac OS packages should be fixed in Metashape 1.6.3 build 10638. Can you please try the updated version?
Hello Dmitry,
Everything works now as expected. Thank you.
Tom
-
Fixed export of large AVI files (>4GB)
Since I was the one who reported this bug : thanks for taking a look at this issue !
If it's not too late in the development process, any chance you could take a look at this bug and feature request, which are also related to the export of animations ?
- Feature request : UHD-2 / 8K export (7680x4320 pixels) would be awesome : aliasing can cause some flickering issues. Exporting 8K videos, then converting then in 4K-UHD outside Metashape, would be an easy way to avoid most of those artifacts.
This would probably be an easy improvement, since it might only require to add a "7680x4320 (16:9)" option in the "Resolution" drop-down menu (see attachment dropdown.jpg).
- Bug : If I'm not mistaken, when exporting a video, it seems there's one unnecessary frame included. https://www.agisoft.com/forum/index.php?topic=12183.0
Additional info about this issue if you want to check it : export a 24fps, 1 second video, open the file in Virtual Dub. It will show that
a) the number of frames is 25 and the video is 1.042 second long, not 1 second long ;
b) the last frame seems empty (using 1.6.3 : if I'm not mistaken, with 1.6.2, the frame was not empty).
See attached file frame-bug.jpg : on the top, frame 24, on the bottom, frame 25, nothing is shown.
-
There seems to be a bug in coordinate import from EXIF data in pictures coming from DJi UAV's. The longitude column has all zeros. Version 1.6.2 works fine.
To use 1.6.3 I had to import the pictures, save the project and then open it into 1.6.3.
Best Regards.
-
Is it possible to add the ability to read Angle elements?
-
Hello Shadow,
The reported issues should be fixed in the next update.
Hello RHenriques,
There seems to be a bug in coordinate import from EXIF data in pictures coming from DJi UAV's. The longitude column has all zeros. Version 1.6.2 works fine.
It will be also fixed in the next version update. It seems that DJI has finally fixed the typo in GPSLongtitute tag and it is correct now.
Hello ruyi7952,
Is it possible to add the ability to read Angle elements?
Please clarify your request.
-
Hello Shadow,
The reported issues should be fixed in the next update.
Awesome, thanks !
-
Hi
The release 1.6.3 version manages well the X and Y coordinates from the Latest DJI UAVs. However it breaks the EXIF data import from Phantom 4 Pro, Inspire one and other older ones. The latest 1.6.3 beta had the problem, identified in a previous post, with longitude using newer UAVs. Now the final version has problems with latitude and longitude in older UAVs - Both return zero.
Version 1.6.2 deals well with older and newer machines.
Best Regards
-
Hello RHenriques,
Can you provide an example of the image which EXIF is not properly loaded in Metashape 1.6.3?
-
Hi Alexey,
here is an example of loading 3 images from P3Standard, P3Pro and P4Pro all with their lat, long incorrectly read from exif as 0,0....
Will send the images by private mail.
Looking at photo metadata from DJI P3Standard image, it seems latitude, longitude are correctly stored in camera.photo.meta() but not in reference pane info... see 2nd attachment....
-
Hello RHenriques,
Can you provide an example of the image which EXIF is not properly loaded in Metashape 1.6.3?
Hi Alexey
I've just sent a few images by email.
Best Regards
-
The issue with reading DJI coordinates should be resolved in the version 1.6.3 build 10723 released today.
-
Perfect now!