Photosynth stuck a "Publishing" phase.

Agree, I have the same issue, 2 synths, 1 appears on the site, 1 doesn't, both have the same in the log... "VtApp: Collection completed (X% synthy), but isn't avialable for viewing yet."
(p.s. did someone think to check the spelling of available!) ( Delete or Edit)

Same issue, how patient... it's been 14 hours now since "VtApp: Collection completed (X% synthy), but isn't avialable for viewing yet." appeared in the log. ( Delete or Edit)

Thank you, i have calmed down and understand that it's over loaded. But now every time i try to explore other people completed synths it tells me to install. I shut down firefox 3 and reinstalled(clicked on repair photosynth), restarted and got the same thing. ( Delete or Edit)

what does the last line of your log file say?
C:\Documents and Settings\username\Local Settings\Temp\Photosynther\filename.log ( Delete or Edit)

Okay, they are beginning to show up, though apparently in reverse order (first in, last out). ( Delete or Edit)

I had to wait 16 hours :p

My log said "22:15:30 VtApp: Collection completed (x% synthy), but isn't avialable for viewing yet."
And I can view it now; so if you'v got that message; I think you just have to wait ;-) ( Delete or Edit)

That first synth still hasn't published, it's been 15 hours.
- But, since then I've had 15 synths published, and one more failure.

Not bad I guess. 15 for 17. On Photosynth's first weekend in public! ( Delete or Edit)

I just completed a 3 hour synth, which showed up directly (300+ photo's).
Looks like the problem is really solved :-) ( Delete or Edit)

But there must be some luck involved. I uploaded precisely the same synth twice (apart from the name) and just one of them showed up. And all my photos came directly out of the camera, so I guess all of them had the same amount of meta data. ( Delete or Edit)

Oh what. About five seconds after I posted that, it finished, apparently successfully. So the nature of the enquiry changes - what's with the hangup, and why did the progress bar stay at 80-ish % for so long before jumping instantly to "finished"? :) ( Delete or Edit)

OK finally got to load it, and it's worked about as well as could be expected for such a mediocre set of pics (rather coarse angles between them, some rather poorly related positions, a few un-rotated portrait shots (STILL not auto detecting these? :) and a model that was turned whilst the background stayed still...) ---- but one further annoyance. When I clicked the "view" button in the synther, it asked me to log in (I thought I already was?!) before I could view it, and then started going on about encrypted pages. Thing is, this is a - supposedly - publically viewable synth. Shouldn't it just dump me right on the page regardless of login and not need any encryption?

Thanks
MP/SNAU ( Delete or Edit)

You need to be patient...

The original problem had been fixed a long time ago. If the process hung, it was much faster to run the second time.

Initially it does upload all of your images so if you run a second synth with the same set of photos (say you add more to "get" them to be more connected) it will NOT upload what is already on the server. It knows what is using the photos too, so if you have three synths that share the same photos (their names are the key) and delete two of the synths, the photos for the third synth will not be removed.

Uploading the photos can take awhile. So can generating the maps and the point clouds. Fast(er) computers tend to be only marginally faster than the older ones; rarely do you see a 2 or 3 times increase in performance in computers built within a few years of each other.

As far as the privacy, there is now an option to make a synth private, but after you login it takes you to your account to allow you to manage your synth since there are additional options that you can add to it after uploading it. If you don't want to login, you can try to perform a search to find it (good luck).

Remember, if you are taking a photo of an object that you are rotating, keep in mind that photosynth buids the point cloud based upon distinct points that are shared between photos. So if your camera is stationary and you are rotating an object without the background changing, then you will not get a good synth. Best thing to do is to try to minimize the background as much as possble: put up a sheet, curtain, ect... Improve the lighting on the object that you are rotating to improve the contrast and have it FILL the photo as much as possible. As a rule of thumb, there MUST be at LEAST a 33% overlap between two photos for the software to link them. If you cannot go back and reshoot a subject, I have found that if you take two photos and start to crop them down to a common point, creating new photos, then sometimes that is enough of a hint for the software to link the originals (if there is still enough of a resolution). To increase the point cloud on your object, try taking more photos from a different perspective of the image; ie... move the camera 3 feet up/down and take another full spin of the object.

Enjoy... Once you figure out how Photosynth works, you will find it easy to generate synths at 100% with 400+ photos like what I have been able to do.

Scottt ( Delete or Edit)

Thanks Scott... it did eventually work. However there was a LOT of waiting, and it DID look for all the world that it had hung - there was no indication of ANY kind of activity going on (not even any significant CPU, disk or network use via task manager), and I wasn't far off killing the process and starting over. Has the progress bar maybe been simplified too far? Would there be any mileage in providing a secondary "this task" progress meter (and expositionary text) as seen in various other programs that could show, e.g. that the small 78-82% (or whatever it is) range on the "floating duck" main bar represents an awful lot of leg-thrash below the surface, and it IS slowly counting up the hundreds-of-megs, waiting for server response, etc? (For that matter, the progress is very uneven, though I know this is a universal and probably intractible issue... it goes with reasonable pace up to this point ....... hangs for an age ...... then ZAP, suddenly it's 100% complete!)

For the record I am a time served previous synther on a personal account, I've been through various problems before and I know you tend to sort them out given time. And I also know that doing each one takes quite a bit of processing... but usually the bit it was "stuck" on doesn't take so long as the rest of it, which is why I was somewhat confused at this "new" machine's extra-fast progress in the early stages (it was definitely several times quicker than what I'd have previously expected, about 50 minutes vs many hours - whether this is due to severe improvements in CPU efficiency for relevant instructions (horrible old Celeron -> Core 2 Duo) or just your programmers reaching the next stage of eliteness I can't say) culminating in an apparent grinding halt at what had previously been a comparitively speedy step (upload... I'm on a 100mbit line and it was a quiet period).

Quite cool to hear about that photo de-dupe thing, though. A very good idea, is that new? I'm thinking if it applies retroactively I might log into my awhile-dormant personal account and find I've got an extra few gigs free now, what with all my multiple "ok, does THIS work instead?" synths.

I'm not entirely sure what you're meaning by the privacy; I had set this to be a public synth and intend to leave it as such for now (and, without tweaking anything, can successfully get to & use it in the guise of J Random Websurfer). I was somewhat confused instead by the BROWSER coming up with security, encryption etc warnings, asking for login etc. Surely that shouldn't happen for a public one? In any case, that hasn't happened since the first time, so who knows.

And I did try to do the synth pics pretty much as you've explained there... Early attempts with putting the model we're using for this first one on a makeshift turntable with a steady - albeit effectively featureless - background (and in some cases, a steady floor plane) really didn't work so well, though this was kind of expected. For those ones, I was just getting the shots while I could because we didn't expect to have use of the model for very long, and intended to ruthlessly crop and edit them to blank any confusing details. In the end, what's worked far better is putting the stand in a fixed location with plenty of room around it, lining up what background boards we had to be straight behind the "main" view... then taking the camera off the tripod, and taking baby steps around it, trusting in my own hand and Canon's excellent image stabiliser function. Wierd. Now, to find an HDR merging thing to produce some extended range pics from the tripod/turntable based ones that I did bracketing for then do the background manipulation and see if they can be convinced to properly synth in. Too bad the "on the ground" and "flyby" shots didn't really come out. Need a proper model-shooting camera for that really... nice and narrow with large depth of field when close up, kind of like........... oh.... hmm! Like the webcam I've got in the cupboard! I wonder if PS will run screaming from its 1.3mpx, high ISO images, or eat them up happily? ( Delete or Edit)