Topic: Tell us how synthy a synth is before we upload it

Report Abuse Report Abuse
jamiet (Over 1 year ago)
There are many synths on here that have a low "synthy" rating, that is the constructed scene isn't particularly good.

The photosynth client goes through a number of steps (e.g. reconstructing scne, generating image tiles) and this leads me to think it knows what the "synthyness" of a synth is before we upload it.

hence, why not display the synthyness in the client while the images are uploading and then give us the option to cancel the upload if we choose to because the synth doesn't meet our own "synthy" quality gates. Better still, let us specify a minimum "synthyness" that our synths should adhere to before they are uploaded.

opefully this would reduce the relative number of low-quality synths on the site.


jamiet (Over 1 year ago)
Ah, I've just nhoticed that you DO tell us how synthy a synth is while it is uploading. I guess you can ignore this :)
TonyErnst (Over 1 year ago)
Jaimiet - yes all the work to construct the synth is done by the synther so it does how synthy it is.  There are a couple reasons why we don't do this.  First, it can take quite some time for the synther to work, and requiring you to sit at your compture and wait for it to finish so you can hit a upload button would be frustrating for most people.  Another reason is that we actually begin uploading images while the syther is doing the reconstruction in order to save time as the upload usually takes much longer than the synthing.  Hope this makes sense.
Nathanael (Over 1 year ago)
Jamie, just one hopefully insightful note: The synther is actually uploading your photos from the moment that the first photo is converted into a deep zoom image and zipped up. 

If you type %temp%\photosynther into your Run command or Windows Explorer address bar when a synth is being made, you'll be able to see the parts of a synth as they're made. You'll see:
1) a log file for each synth processed, 
2) an 'images' folder, filling with one .dziz file per input photo, and 
3) at the very end of the scene reconstruction the deep zoom collection file [collection.dzcz] and the binary synth.bin file outside of the images folder.

Now, if you make a COPY (I don't recommend MOVING files while Photosynth is making them =) of any of the DZIZ files or the DZCZ and change their file extension to .zip, you'll be able to look inside with 7zip, WinRar, WinZip, or even Windows itself to see just what a Seadragon deep zoom image or deep zoom collection is really made of.
Nathanael (Over 1 year ago)
Now the dziz files are what is going to be the largest part of the synth to upload, and as soon as the image tile generation is complete, every last dziz is available to be uploaded. From this point onward, they will continue to upload as the computer vision part of synthing begins.

At the very end of scene reconstruction, the deep zoom collection and binary synth data such as camera positions, image feature positions (the points in the pointclouds), and which images belong in which clusters will be saved out into their appropriate files.
Nathanael (Over 1 year ago)
It's been a while since I dissected a synth, but I remember there being a JSON (Javascript Object Notation) file, the pointcloud files which are saved with a maximum number of points per file and numbered according to which group of photos in the synth they belong to as well as which piece of that pointcloud it is... sort of a 'pointcloud 1, piece 3' type syntax, that actually looks more like synth_0_0.bin, synth_0_1.bin, synth_1_0.bin, and so on.

A deep zoom collection is relatively simple and can be roughly thought of as a thumbnail system for the entire group of images for viewing in 2D grid mode. I think that in their application to synths, their generation must take place after scene reconstruction, because which photos stick together will determine the image order within the collection, but I could be mistaken about that.
Nathanael (Over 1 year ago)
Ah... Tony beat me to that one. I got interrupted by LOST and didn't bother to refresh before I was pasting my answer back into the page.