Posts Tagged ‘photosynthtoolkit’

PhotoSynthToolkit 11

May 23rd, 2012

I’ve for some reason extra time to kill so I’ve updated PhotoSynthToolkit (SFMToolkit will follow soon). I’ve been only focusing on PMVS2 for this release: I’ve integrated Nghiaho optimization, fixed white-space folder handling in PMVS2 using boost::filesystem and fixed the timing output in the console. Thus there is no need for the ugly temporary z drive anymore :-) .

Nghiaho optimizations are disabled by default as I’ve found that it generates a point cloud less dense. You can enable the optimization by adding:


as last PMVS2.exe parameter in your command prompt or just activate the optimization by modifying the following files:

  • 3 – Prepare for PMVS2.wsf line 49 -> var USE_OPTIMIZED_PMVS = true;
  • 4 – Prepare for CMVS.wsf line 46 -> var USE_OPTIMIZED_PMVS = true;

You can download


PhotoSynthToolkit 10

May 1st, 2012

What do you think of this concept: a new PhotoSynthToolkit version almost everyday? :-) .

This version introduce a new feature that will allow you to process a PhotoSynth without needing to wait for the end of the upload. In fact you can even cancel your synth as soon as the computation is complete. But be aware that all pictures uploaded in the meantime will stay on photosynth server (AFAIK).

How to proceed:
- wait for synth to be processed (but not fully uploaded).
- copy the 2 following files from %temp%\Photosynther to another folder (d:\my_synth for example)

  • collection.dzcz
  • collection.synth.bin

- then you can launch the step 1 of the PhotoSynthToolkit by providing your folder (d:\my_synth).
- you’ll need then to copy your original jpegs to the distort folder and you’re done!

You can download


PhotoSynthToolkit 9

April 29th, 2012

This is a quick post to announce the new version of the PhotoSyntToolkit with 2 new features:

  • CMVS support finally integrated :-)
  • proper handling of folder with white space

How to use CMVS with PhotoSynthToolkit:

  1. As usual run step 1 and move pictures from “hd” to “distort” folder.
  2. You need to run first “Prepare for PMVS2″ then do NOT launch the generated bat file.
  3. You can run “Prepare for CMVS” and run the generated bat file.

Warning: I’ve fixed all my programs to handle folder with white space (thanks to boost::filesystem). Sadly PMVS2/CMVS don’t handle them. The fix is trivial but instead of recompiling a new version I’ve found a bad workaround. I’m creating a temporary virtual drive z: pointing to your synth folder during the execution of PMVS2/CMVS using SUBST. The downside are that if you already have a z: drive it won’t work and if you kill PMVS2/CMVS you’ll have to manually remove the z: drive. To remove the z: drive type “subst z: /d” in your console.

If you need XSI/3DS max integration you’ll have to use the old version: otherwise is the latest version.


PhotoSynthToolkit 8

April 14th, 2012

I’ve finally decided to release the new version of my PhotoSynthToolkit. This new version has bundle.out output support: this was indeed easy to add as I’ve already implemented it in my WebGL chrome extension. I’ve also rewritten the network part of the downloader by using libcurl. PhotoSynthDownloader is now replaced by my new tool PhotoSynthGrabber. BTW thumbnail/HD pictures downloading should be really much faster ;-) .

New feature coming:

  • CMVS support (coming very soon)
  • White space handling in the toolkit scripting (PhotoSynthGrabber is already ready)
  • Expose HTTP Proxy parameters for the downloader

You can download the new version: or keep the previous one in case you miss some advanced feature (vis.dat generation, SoftImage XSI / 3DS Max scripting for example):


Moving on

September 26th, 2011

I’ve spent almost 4 years at but it was time for me to move on. I’ve quit my job and I’ve started to work at Acute3D in September: they are working in the structure from motion and dense 3d reconstruction field. You can try their dense mesh creation technology by using Autodesk Photofly. Photofly is calibrating the cameras using Autodesk implementation and then the mesh is generated using Acute3D technology (Autodesk has bought a license of their meshing technology).

I’m working on the development of a calibration system (like bundler) at Acute3D. I’ve decided to work with them as I think that they do have the best technology available and I wanted to work with very skilled people working in computer vision.

I don’t know if I’ll be able to continue writing on this blog as this new job is really more interesting and challenging for me.