Get all your questions answered about our latest Photosynth Technical Preview.
One of my favorite things is to load up any given synth in the various Photosynth viewers and use the strengths of each viewer.
I suspect that the new synths are likely formatted differently than original synths (aside from the obvious lack of a deep zoom collection file and the addition of the depth maps), but I must admit that when I first loaded up the Tech Preview one of the very first things I did after loading several new synths was to copy the collection ID of new synths and paste them into the URL of the old viewers and vice versa to see if anything would load and was sad to see that they didn't in either direction.
The new synths each have a point cloud, camera positions, and a deep zoom image representation so there's no real reason why those components couldn't be served to the older viewers.
Similarly, original synths' primary point cloud, camera positions, and DZIs could all be loaded in the preview viewer, even though there's no depth maps or smoothed paths for original synths.
I know that 2D view would be unavailable when viewing new synths in the older viewers (due to the lack of a DZC in new synths) or original synths in the Preview viewer (due to OpenSeadragon's lack of DZC support) and similarly no depth maps would be available when viewing original synths in the Preview viewer at this point, but that's par for the course with different viewers.
Just for the record, I'm not talking about stitched panoramas at all. That's why the title says 'synths' and not 'synths and panos'.
On that topic, though, while you're still working on getting a WebGL panorama viewer up and running, I don't think you'd hurt anyone's feelings by serving up a fullscreen HTML5 pano viewer when adding '/preview' to a panorama's URL to reliably load up panoramas in the HTML 5 viewer without switching browser user agents or deactivating one's Silverlight plugin, etc.