piccure+ was not developed for and is not aimed towards photographers with limited experience or with subpar equipment. In fact, piccure+ was developed for photographers with a lot of experience and knowledge about technology and technique.
We know that many of you use Adobe Lightroom, Adobe Photoshop CC, DxO Optics Pro, or PhaseOne Capture One. This is why we have optimized piccure+ to integrate seamlessly as a plugin to ensure that your workflow changes are minimal. piccure+ can even be called directly from DxO Optics Pro or PhaseOne CaptureOne. Our handbook provides details on how to integrate piccure+ efficiently into your existing workflow (e.g. Actionscript support). The larger the optical aberrations are, the less useful your current tools will be.
Piccure 3.1.0.0 Standalone
The standalone application is capable of processing RAW images as well as processing batches of images. We recommend using the standalone version if you have a large number of images to process and would prefer to have the images processed overnight.
We recommend using piccure+ at the very beginning of your workflow. Ideally you should import the RAWs through piccure+ or work directly on the imported RAW files. We recommend shooting in RAW since JPG introduces compression artifacts and cameras often artificially sharpen JPGs. We also recommend not applying any cropping and/or adjustment to the brightness, color, etc.
A quick note on using piccure+ in conjunction with other software solutions. This is absolutely no problem. You can pre-process the image before using piccure+ with the following operations:> Process the RAW file.> Correct chromatic aberrations (thus saving piccure+ processing time).> Correct vignetting.> Correct lens distortion.> Correct noise with DxO PRIME (several users found the results very good).
piccure+ uses sophisticated algorithms that dynamically adapt and does not rely on any profiles or the like. The advantage of this approach is better image quality. Among the disadvantages are less robust image correction, longer computation time, and an increase in digital noise (unless denoising is activated).
Feel free to send us an email if you have any questions or run into problems. However, we would greatly appreciate it if you took a look at the handbook before submitting a support ticket. The handbook can be downloaded here (Link) or simply accessed through piccure+. To submit a support ticket, please send an email to: .
Download Hashxvm-3.1.jar - SHA256: 3a490880f10c62bd3a6d0a82e3ed9ade5c55df802e2b4cb301aa52157038abde
xvm-3.0.jar - SHA256: a33ce87e848bc2cc51bd63ac316a35615d46eb14872984d7e66d779c92c6e586
xvm-2.6.jar - SHA256: b6020bbcd046b5fcc2b7d9c3e62beafb4d9f906658b710630687b7b06d575474
Requirements vCenter Server 6.0 Update 3 or above (ESXi hosts must also be 6.0u3+
Java Runtime Environment 1.8-10
Web Browser
Please review for Cross vCenter vMotion requirementsInstructionsRun the utility jar file from a shell window. To use the plugin UI add the details of the vCenter Server 6.7U1+ which will be used to access the vSphere Client.Java 8:$ java -jar xvm-3.0.jar --vcenter.fqdn=VCENTER-IP-OR-FQDN --vcenter.user=ADMIN-USER --vcenter.pass=ADMIN-PASSWORDJava 9/10:java --add-modules java.se.ee -jar xvm-3.0.jarDefault app port is 8443 which can be changed (e.g., 31000) by providing an additional flag:$ java -jar -Dserver.port=31000 xvm-3.0.jarNote: If you wish to just use the standalone client, you can simply omit the vCenter Server registration and then access the standalone UI using : (default port 8443)$ java -jar xvm-3.0.jarAccess the UI of the utilityTo use the plugin go to -IP-OR-FQDN/ui in the browser and login.To use the standalone UI (deprecated) connect to the app from the browser by using IP address/hostname of the machine (127.0.0.1 for localhost) where the utility is running as 'host' :<port>Register vCenter servers for migration operationsfrom 'vCenter Servers List' view of the pluginfrom 'Register' tab of the standalone UI.Provide required parameters:Sitename: a name to identify the vCenter servervCenter Hostname/IP address, username, passwordTrust server: select to skip SSL certificate verification during VC connectionAfter a restart of the utility, enter password and re-establish connection for previously registered sites.Initiate VM migration operationsfrom the vSphere Client pluginFor experience integrated with the inventory tree use the 'Import VMs' action on a selected target Host or Cluster.For the general source-to-target scenario use the 'Migrate VMs' wizard from 'vCenter Servers List' view.from the 'Migrate' tab of the standalone UI. Progress of migration tasks can be monitored on the home page.Provide required parameters (select values from menu):Operation type: supported operations are relocate/cloneSource and target sites: select sites from already registered sitesSource VMs: select datacenter and VMs from the source site for migrationPlacement target: select target compute resource (host or cluster)Target datastore: select target datastore for placementNetwork mappings: select networks to map from source to target sites(Optional) Target pool and folder: select target VM folder/resource poolAPIsREST APIs for automating migration tasks can be accessed/executed from the API reference link under the help menu which links to the Swagger UI. Here are examples of site registration and performing migration task through the API:Site registrationcurl -X POST :8080/api/sites -H "Content-type: application/json" -d '"sitename":"my-vc", "hostname":"vcenter.server.com","username":"administrator@vsphere.local","password":"mysecret","insecure":false'Migration taskcurl -X POST :8080/api/tasks -H "Content-type: application/json" -d '"operationType":"relocate","sourceSite":"site1","targetSite":"site2","sourceDatacenter":"Datacenter","vmList":["vm1", "vm2", "vm3"],"targetDatacenter":"Datacenter","targetCluster":"Cluster","targetHost":null,"targetDatastore":"Datastore","networkMap":"Private Network":"Internal Network", "VM Network":"VM Network"'NotesApplication logs are stored in xvm.log file.
Site connection details (excluding password) are stored in xvm.dat file on disk.
SSL keys for vCenter servers are stored in xvm.ks keystore file.
The app stores migration task state in memory, implying a restart of the app loses information about migration tasks.
Please refer to this KB article for supported configurations for Cross vCenter vMotion
A detailed blog by William Lam on the utility -vm-migration-using-new-cross-vcenter-vmotion-utility-fling.html
A demo of an earlier version of the utility can be found at =r_kG8ny-qss
ChangelogVersion 3.1, January 22, 2020 2ff7e9595c
Comments