Re: new iPad
- Hi Trausti,
please be serious ;-) - there is technically nothing 'special' in your 'iOS player'.
You were only using progressive-encoded jpeg images to avoid the automatic downscaling on iOS.
A nice trick of course (btw - that works with PNG images too) but nothing special player specific.
That works in all other players too!
But using progressive jpegs has disadvantages:
- they don't work at all on all iOS versions lower than 5.0!
- the decoding of progressive jpegs needs more memory and is MUCH(!!!) slower!
- these big images and the slow loading/decoding are leading to more crashes and hangs on iPhone and iPad, especially when there also other images on the page, sometimes this goes that far that whole system hangs and even the home button doesn't react on the iPad - and this is really a bad experience when you need to restart your device after browsing to a page ;-)
Btw - using progressive jpegs works in krpano too of course (htmlrendermode=2 need to be used) - here your pano in krpano (I have used your cube images for a direct comparison, I hope this okay for you - but if you want I can remove them and use own ones of course):
It looks good of course (especially on the iPad 3), but that's unfortunately not stable and fast enough for full featured tours...
There are better ways for higher resolution images on the iPad... (details on the krpano 1.0.9 release ;-)).
- For iOS 6, the limit for downsampling the images has been lifted from 2 MB to 5 MB.... or rather upped to the 2289x2289 pixels that were possible by using progressively saved images.
Support for iPad1 has been dropped by Apple, and that does of course justify everyone else to ignore that piece of equipment. 2 years of official lifetime before it is dumped... not much, but understandable.