 |
|
|
|
|
|
 |
| ||||||||
 |
 
|
|
|
|
|
|
|
|
|
| ||||||||
|
|
| 
| User list | Rules | You are not logged in.
Muzza wrote:
Can anyone help with the best settings for ensure fast loading times. Currently I'm finding its over 20 secs.
Some more information might be helpful . . . . 
Besides there is NO Flash on iPads - i guess it depends on the resolution you choose. We use 5000x2500px for iPad and iPad2. The new iPad we did some Panos for a magazine-app. They ("Der Spiegel") wanted 10000x5000px.
The result looked brilliant on the new iPad.
It also depends - of course - on the kind of connection. W-Lan usually is faster than the cell-phone net . . which is not very surprising 
So at which conditions you have 20sec.?
best, Klaus
Offline
Hi Klaus
Test this link and tell me how long it takes to load. I'd also be interested in how long it takes to load from the thumbnails:
http://focus360.co.nz/focus360/tekapo/mtjohn/tour.html
It is the Mt John Astronomical Observatory at Lake Tekapo in New Zealand. The University of Canterbury wants it available to be viewed in both Flash and iPad / iPhone.
BTW the mountain range in the distance with all the snow is the Southern Alps of New Zealnd's South Island. You might have seen this range as the Misty Mountains from the Lord of the Rings.
settings jpeg quality 8, image size 1.5 Mb
Hey thanks for the help.
Best regards
Offline
Muzza wrote:
Hi Klaus
Test this link and tell me how long it takes to load. I'd also be interested in how long it takes to load from the thumbnails:
http://focus360.co.nz/focus360/tekapo/mtjohn/tour.html
I'm in the UK on a relatively low bandwidth ADSL connection which at best delivers about 1.5Mbps.
About 15 seconds before preview image first appears.
Switching via thumbnail to another pano I see the preview in about 8 seconds.
OTOH the spinning loading animation sems to run for a very long time indeed. Perhaps you should switch it off?
Also it appears you allow zooming in beyond the resolution of the image, it's better IMO not to allow this.
Last edited by mediavets (2012-07-29 11:07:21)
Offline
Hey thanks Andrew
That result is quite encouraging.
The spinning loading animation intrigues me why it stays for so long. I will turn it off - any idea why this is the case? This tour is a draft and yes to not not zooming beyond resolution 
Muzza
Offline
Hi Muzza... loads very quick here... about 5 secs.. Interesting tours... ADSL 2..
Destiny...
Last edited by Destiny (2012-07-29 12:03:54)
Offline
Muzza wrote:
Hi Klaus
Test this link and tell me how long it takes to load. I'd also be interested in how long it takes to load from the thumbnails:
http://focus360.co.nz/focus360/tekapo/mtjohn/tour.html
It is the Mt John Astronomical Observatory at Lake Tekapo in New Zealand. The University of Canterbury wants it available to be viewed in both Flash and iPad / iPhone.
BTW the mountain range in the distance with all the snow is the Southern Alps of New Zealnd's South Island. You might have seen this range as the Misty Mountains from the Lord of the Rings.
settings jpeg quality 8, image size 1.5 Mb
Hey thanks for the help.
Best regards
Speed is ok here (32000 cable). But i agree to Andrew - the spinningwheel spins rather long related to the very small amount of data. And i also suggest to limit the zoom to 1:1 and max. 90° fov.
Beautiful location - and most interesting! Did i see Gandalf on the hills out there?
best, Klaus
Offline
klausesser wrote:
Besides there is NO Flash on iPads - i guess it depends on the resolution you choose. We use 5000x2500px for iPad and iPad2. The new iPad we did some Panos for a magazine-app. They ("Der Spiegel") wanted 10000x5000px.
best, Klaus
Can I ask you, which cube face size and cutting size did you use?
Offline
Spelican wrote:
klausesser wrote:
Besides there is NO Flash on iPads - i guess it depends on the resolution you choose. We use 5000x2500px for iPad and iPad2. The new iPad we did some Panos for a magazine-app. They ("Der Spiegel") wanted 10000x5000px.
best, KlausCan I ask you, which cube face size and cutting size did you use?
I usually use what the app suggests by clicking on "reduce distortions". Depending on the resolution of the equirectangular image the app chooses a good value i found.
best, Klaus
Offline
Thank you, Klaus. But the app always gives tablet_face 1024x1024 in my case, do I need to change it and where?
Offline
Spelican wrote:
... the app always gives tablet_face 1024x1024 in my case, do I need to change it..?
No.
Offline
Hi Klaus
Cube face size 864
Cutting size 56
Any ideas why the loading wheel animation persists as long as it does?
You might be interested in these to see some of the actual sites where the movie was filmed - to find Gandalf. Left to right and all are from the South Island, New Zealand:
http://focus360.co.nz/focus360/LoR/virtualtour.html
1. Flight to the Ford. 20 km out of Wanaka on the state highway to Queenstown
2. Fangorn Forest. 2 km from the South Mavora Lake
3. Isengard. 15km north of Glenorchy (zoom across riverbed)
4. Ithlium Camp. 5km from Queenstown.
5. Nen Hithoel: South Mavora Lake.
6. Nen Hithoel Forest: 2 min walk from South Mavora Lake (couldn't find Boromir)
7. Pillar of the Kings. Shotover River by A. J. Hackett Bungy Jumping next to Queenstown.
8. River Anduin. 10 km north of Manapouri.
Best
Muzza
Offline
If I test it from Austria is real slow. endless loading too.
If I do a traceroute on cmd line I see that the hop from German Telekom to Hongkong increaqses from 30ms to 300ms so this may explain why its very slow from Europe...
C:\Users\gkaefer>tracert focus360.co.nz Routenverfolgung zu focus360.co.nz [111.65.227.152] über maximal 30 Abschnitte: 4 12 ms 15 ms 12 ms SAX-NO03.highway.telekom.at [195.3.93.1] 5 16 ms 18 ms 19 ms 195.3.118.233 6 17 ms 17 ms 22 ms 195.3.70.162 7 20 ms 21 ms 18 ms 193.159.227.13 --> 8 279 ms 279 ms 281 ms hkg-sb1-i.HKG.HK.NET.DTAG.DE [62.154.14.58] 9 316 ms 318 ms 316 ms i-0-10-1-0-2201-peer.hkhh01.pr.telstraglobal.net [134.159.127.153] 10 307 ms 306 ms 309 ms i-3-1-0.hkhh-core01.bi.telstraglobal.net [202.84.154.217] 11 368 ms 369 ms 367 ms i-0-4-1-0.sydp-core01.bx.telstraglobal.net [202.84.141.209] 12 374 ms 373 ms 382 ms i-0-7-2-0.sydo-core02.bi.telstraglobal.net [202.84.223.22] 13 371 ms 370 ms 369 ms i-2-2-1.hptw-core01.bx.telstraglobal.net [202.84.142.150] 14 370 ms 367 ms 370 ms 203.167.233.14 15 377 ms 371 ms 374 ms 111-69-27-66.core.snap.net.nz [111.69.27.66] 16 * * * Zeitüberschreitung der Anforderung. 17 382 ms 381 ms 381 ms snap-chc-state2-rtr01.snap.net.nz [202.124.114.81] 18 380 ms 384 ms 381 ms net24.snap.net.nz [202.124.114.82] 19 388 ms 387 ms 394 ms hwnode3.lnx.vps.isx.net.nz [210.5.50.198] 20 383 ms 385 ms 381 ms vps658.lnx.vps.isx.net.nz [111.65.227.152] Ablaufverfolgung beendet
Georg
Last edited by gkaefer (2012-07-29 21:30:13)
Offline
Muzza wrote:
settings jpeg quality 8, image size 1.5 Mb
Why have you made the input image so small?
krpano/Panotour support multi-resolution tiling so viewing performance is almost independent of image resolution.
When you choose to create a mobile-compatible version of a tour PTP will create a separate set of tiles for the mobile device(s) which again will be independent of the resolution of the input images.
Offline
Muzza wrote:
Cube face size 864
Cutting size 56
Where do those numbers come from - did you decide on these values or did PTP offers these numbers?
In particular why is the Cutting size such a low value - that might explain the 'endless' display of the loading animation.
Last edited by mediavets (2012-07-29 21:43:38)
Offline
PTP produced those values after clicking Reduce Distortion. Thought the input image required to be small to flow smoothly in iPad. Can you suggest a better Cutting size and image size?
Offline
Muzza wrote:
PTP produced those values after clicking Reduce Distortion.
I see - what was the resolution of the input images?
Thought the input image required to be small to flow smoothly in iPad.
No, that's not correct.
Krpanop/PTP use multi-resoltion tiling with large input images, and as I mentioned before PTP creates separate sets of tiles for mobile devices.
Can you suggest a better Cutting size and image size?
The resolution of the input images will have no impact at all on the tile sizes created for mobile devices and hence will have no impact on load times for tours veiwed using iDevices.
So IMO you might as well use higher res. input images to improve the viewing experience for those viewing from Flash-enabled platforms. Multi-res. tiling means that viewing perfirmance on Flash-enabled platforms is almost independent of input image resolution.
Just click the Reduce Distortion option and then leave the program to do it's stuff.
Offline
Image data, approx values: 3500 by 1500 pixels, 1.5 MB, 72 dpi.
Any thoughts on the loading animation?
Thanks for this feedback its really very good.
Muzza
Offline
Muzza wrote:
Image data, approx values: 3500 by 1500 pixels, 1.5 MB, 72 dpi.
That's really very low res. for a good quality display on a modern desktop monitor.
10k x 5k pixels is probably the lowest res. to use for spherical (360x180) input images.
Offline
At higher resolutions well you not get stickyness / jerkiness of the image flow? I have found that the image stops momentraily when panning with these larger resolutions? With lower files sizes the smoother it moves. Unless this is something different again?
BTW this is a very good PC with solid state drives and 32GB of RAM, i7 core etc.
Offline
Muzza wrote:
At higher resolutions well you not get stickyness / jerkiness of the image flow? I have found that the image stops momentraily when panning with these larger resolutions? With lower files sizes the smoother it moves. Unless this is something different again?
BTW this is a very good PC with solid state drives and 32GB of RAM, i7 core etc.
In terms of iDevices: there are no tiles created for iDevices because they can´t handle tiles. PTP creates one mobile-face for iPhones and another mobile-face for iPads.
Actually there´s some irritation relating to the face-size for the new iPad´s resolution of 2048x1536px.
Basically: for displaying a pano in good quality i suggest to use an equirectangular image of 10000x5000px - without deep zooming.
3500x1500px has the wrong proportions - ist has to be 2:1=3500x1750px. Anyway that´s much too small for having it displayed on actual sreen-sizes
in sufficient quality.
Working for the iPad-apps of some magazines we experienced to use 5000x2500px at least (!) for the use on iPad/iPhone 1 and 2. The clients want
10000x5000px for the use on the new iPad (3) - they found a way to deal with it . . . . inside their apps! You can see our Grecopan in the "Spiegel" app -
when you buy it. Outside the app the display-quality on iPad (3) isn´t that well to be honest - the iPad interpolates . . Hans Nyberg some weeks ago
stated some interesting points here.
best, Klaus
Offline
