Package Details: agisoft-metashape-pro 2.1.1-1

Git Clone URL: https://aur.archlinux.org/agisoft-metashape-pro.git (read-only, click to copy)
Package Base: agisoft-metashape-pro
Description: Photogrammetric processing of digital images and 3D spatial data generation software. Professional edition
Upstream URL: https://www.agisoft.com/
Licenses: custom, custom:Agisoft EULA
Provides: agisoft-metashape-pro, agisoft-network-monitor, agisoft-viewer
Submitter: dobedobedo
Maintainer: dobedobedo
Last Packager: dobedobedo
Votes: 3
Popularity: 0.000003
First Submitted: 2020-03-10 05:20 (UTC)
Last Updated: 2024-04-15 06:31 (UTC)

Dependencies (10)

Required by (0)

Sources (7)

Pinned Comments

dobedobedo commented on 2021-08-18 20:55 (UTC) (edited on 2021-08-20 12:40 (UTC) by dobedobedo)

I encountered an issue the licence becomes invalid and cannot be deactivated. Here's the reply from agisoft support:

Please note that during the license activation of node-locked license an additional so-called "rehostable" directory is created. It is used later to validate the available license and stores the system parameters, that why it is important to deactivate the license before applying any major changes to the system, such as OS upgrade/re-install or hardware components replacement. 
The default location of the "rehostable" directory differs depending on the OS used:
on Windows - C:/ProgramData/Reprise/agisoft/photoscan-pro/
on Linux  -  /var/tmp/agisoft/photoscan-pro/
on macOS - /Library/Application Support/Reprise/agisoft/photoscan-pro/
It is possible to alter the default location by setting up AGISOFT_REHOST_PATH environment variable prior to the license activation. Use only safe location that wouldn't be cleared by any background services, as any modification of the "rehostable" directory contents including its removal will lead to the license invalidation.
During the activation and application utilization, please make sure that current user has access rights to the rehostable directory and folder where from Metashape Pro is started (the license file will be written to that folder).

If you decide to customize the rehsotable id folder location, make sure to do that prior to the license activation (set up env. variable, reboot and then activate Metashape license).

Metashape is using a 3rd party activation system developed by Reprisesoftware (https://reprisesoftware.com/). As far as we are aware, the following changes in hardware configuration would likely affect the activated license: adding/removing hard drive (HDD, SSD), adding/removing RAM modules, adding/removing GPU, replacing network card. Additionally MAC-address changes would affect the license, as well as major OS upgrades.

Therefore we recommend to deactivate Metashape license before any of these operations are applied to the system.

So make sure to deactivate the licence before any major system upgrade and then reactivate it.

To deactivate the licence, use

sudo agisoft-metashape-pro --deactivate

dobedobedo commented on 2020-09-08 02:42 (UTC)

Check the forum thread here:
https://www.agisoft.com/forum/index.php?topic=10943.0
There is a workaround for installing external python modules.

dobedobedo commented on 2019-10-01 15:23 (UTC) (edited on 2020-07-29 05:21 (UTC) by dobedobedo)

Run the following command to activate the product

sudo agisoft-metashape-pro --activate 11111-22222-33333-44444-55555

NOTE: the number after "--activate" is your node-locked license

Latest Comments

« First ‹ Previous 1 2 3 Next › Last »

harpium commented on 2021-08-18 22:51 (UTC) (edited on 2021-08-18 22:56 (UTC) by harpium)

If anyone is having issues with their AMD GPU not showing up on the GPU preferences tab, then install opencl-amd.

dobedobedo commented on 2021-08-18 20:55 (UTC) (edited on 2021-08-20 12:40 (UTC) by dobedobedo)

I encountered an issue the licence becomes invalid and cannot be deactivated. Here's the reply from agisoft support:

Please note that during the license activation of node-locked license an additional so-called "rehostable" directory is created. It is used later to validate the available license and stores the system parameters, that why it is important to deactivate the license before applying any major changes to the system, such as OS upgrade/re-install or hardware components replacement. 
The default location of the "rehostable" directory differs depending on the OS used:
on Windows - C:/ProgramData/Reprise/agisoft/photoscan-pro/
on Linux  -  /var/tmp/agisoft/photoscan-pro/
on macOS - /Library/Application Support/Reprise/agisoft/photoscan-pro/
It is possible to alter the default location by setting up AGISOFT_REHOST_PATH environment variable prior to the license activation. Use only safe location that wouldn't be cleared by any background services, as any modification of the "rehostable" directory contents including its removal will lead to the license invalidation.
During the activation and application utilization, please make sure that current user has access rights to the rehostable directory and folder where from Metashape Pro is started (the license file will be written to that folder).

If you decide to customize the rehsotable id folder location, make sure to do that prior to the license activation (set up env. variable, reboot and then activate Metashape license).

Metashape is using a 3rd party activation system developed by Reprisesoftware (https://reprisesoftware.com/). As far as we are aware, the following changes in hardware configuration would likely affect the activated license: adding/removing hard drive (HDD, SSD), adding/removing RAM modules, adding/removing GPU, replacing network card. Additionally MAC-address changes would affect the license, as well as major OS upgrades.

Therefore we recommend to deactivate Metashape license before any of these operations are applied to the system.

So make sure to deactivate the licence before any major system upgrade and then reactivate it.

To deactivate the licence, use

sudo agisoft-metashape-pro --deactivate

dobedobedo commented on 2021-04-28 16:51 (UTC)

Hi @JeppeX, could you please confirm if installing 'glu' resolves the issue?

JeppeX commented on 2021-04-28 16:36 (UTC)

It seems that metashape depends on "extra/glu" (which is a Mesa OpenGL lib) in order to run. Otherwise running metashape gives: /opt/agisoft/metashape-pro/metashape: error while loading shared libraries: libGLU.so.1: cannot open shared object file: No such file or directory

I think it would be helpful to add this "glu" pkg to dependencies.

pyroclast commented on 2020-11-11 01:59 (UTC)

Thanks @dobedobedo, I ran the simplified version to make the correction:

sudo chmod -R 755 /opt/agisoft/metashape-pro/ /usr/share/licenses/agisoft-metashape-pro/licenses/

dobedobedo commented on 2020-11-11 01:20 (UTC) (edited on 2020-11-11 01:39 (UTC) by dobedobedo)

I updated the post-upgrade script to fix the permission issue. Please update.

pyroclast commented on 2020-11-10 16:41 (UTC)

Having permission issues after upgrade. Output from upgrade had many permission warnings, example of top warning:

warning: directory permissions differ on /opt/agisoft/metashape-pro/
filesystem: 755  package: 700

When I try to run the program:

$ agisoft-metashape-pro 
/usr/bin/agisoft-metashape-pro: line 2: /opt/agisoft/metashape-pro/metashape.sh: Permission denied

Updating permissions to match system allowed the program to run as expected.

dobedobedo commented on 2020-09-08 02:42 (UTC)

Check the forum thread here:
https://www.agisoft.com/forum/index.php?topic=10943.0
There is a workaround for installing external python modules.

dobedobedo commented on 2020-07-31 01:16 (UTC)

Hi @theodore, yes I got the same error message on my Arch WSL. Haven't tried it on my Manjaro machine as I'm away from it at the moment, but the python module installation worked on my another Ubunt 18.04 workstation.
I tried manually compile the pyOpenSSL module into the agisoft python packages directory, but didn't change anything. May need to recompile the python with libssl option. Hope that Agisoft can provide some solutions soon.

theodore commented on 2020-07-30 12:06 (UTC)

Hi @dobedobedo, I've seen this thread on the agisoft forum when I was looking for a solution on my own and I was hoping that it was only ubuntu related since as they say the current workaround was to downgrade the ubuntu instalation. However it seems that apparently it is not. In any case thanks for commenting there.

So I assume that you are also getting the same error when you run the command, right?