New features, updated old ones and general news from the Photosynth team.
I created a synth of one of my tableau images (http://www.bettgallery.com.au/artists/kozka/bestyears/images/02bedtime.jpg), I then set up a computer at the gallery loaded you the synth, set it to full screen and hit the play button, so people would get an idea and be encouraged to look at the work, grab the mouse etc. The problem is the gallery called me after a few days an said there download limit had been reached and 6 gig was downloaded in a few days...the synth was the only thing different on the system....
The response from people and the galleries was really good BUT this is a real problem if trying use & promote photosynth as an art form.
My synth can be see at http://bronekkozka.foliosnap.com/#goto=project-space
This is really a case for why the Photosynth viewer should cache tiles locally instead of dumping them as soon as you navigate away from the photo.
I'll grant that with photos as high quality as bronekkozka usually uses, the synth may still be a few gigabytes even if you only downloaded it once, but caching so that you don't redundantly download the same bits over and over would be hugely appreciated, especially for those countries where ISPs do not sell internet access with unlimited bandwidth.
In addition to economical reasons listed above, it seems as though it would also be less strain on the Bing Maps servers as well as faster performance for users. Why can't we just cache the data already?
I just got a reply on the old Photosynth forum that could potentially solve this for you, Bronek.
Here's the link for you:
the viewer uses the browser cache, so multiple requests for the same image should only cause 1 network request. In your case maybe the browser cache was too small to contain all the synth information so eventually images were deleted from the cache causing multiple requests for the same image. I would suggest you increase the size of the browser cache so that the amount of network usage is limited, hopefully that will not cause continual viewer playing to use too much network. To increase in IE go to tools->options->general->browser history settings and you can increase the browser cache size there.
I'm assuming this only applies to the Silverlight viewer. Am I wrong?
@Nate: Wow, I'm quite surprised to see fduch just replied, considering the last post was "1 year ago." Sounds promising. Let's hope, and see what time brings...
Maybe a "synth catcher" app can be written to automatically capture the synth files before they get uploaded and out of reach.
increasing the browser cache should also work for the D3D viewer.
Well this is great news. Somehow I was completely ignorant of being in control of my own caching. I've now bumped my Firefox cache up to a couple of Gigabyes... I'm off to test.
Thanks for the tip, Mark.