ohhh YEEEES. personal I never use this embedded option because all panos must be preloaded before getting displayed. and this makes no fun if more than 1 pano is used.
jpg level 8 is good for speed to. e.g. jpg level 12->10 reduces filesize on harddisc of the pano more than 50%. So here for fisheye panos I tend to use 10 and for 85mm panos I rather tend to jpg level 8 to keep quality and size in balance.

Georg

PS pixel size you mention: you mean 6000 x 3000 or really 3000 x 6000 (which should not work at least as full spherical pano)?
if you can put your demo tour online and provide a link than we could crosstest the speed...

Last edited by gkaefer (2012-04-22 16:19:00)

definitely don't embed all. my pano went from 20-30 seconds loading to 1-2 seconds per pano. when someone is trying to view your tour they will get bored with the initial wait, but will deal with a blurred loading for a second or two.

deedee7 wrote:

Here's the link to the tour: http://virtuastudio.pl/vir/restauracja% … in/rs.html

It's considerably faster than that for me (here in the rural UK) and my ADSL Net connection is at best about 1.5Mbps.

Getting rid of the little planet intro will probably speed up loading of initial pano.

When you say 'load time' at what point do you consider the pano to be 'loaded'?

deedee7 wrote:

Hey. Thanks for a quick reply. By load time I mean the time from the moment the little wheel in the middle appears to the moment it stops spinning.

I use an asynchronus xdsl link with 5mbit downlink.
From cklicking on link in thread until little planet has finished: 16 seconds.
... and my ADSL line is quit exotic: postal splitter & xdsl modem is in base level. from here its going via 10mbit via powerline link to my cellar where my firewall and wireless lan router is placed and with N band its going wireless to second level to my PC...

Liebe Gruesse,
Georg

Thanks everyone for your tests!
I've solved the problem by increasing the cutting size from 120 to 478. Panos load in just a few seconds now! I had no idea that cutting size can influence load time.

I did it, because simply not embedding XML didn't improve load times. I've read somewhere on this forum about cutting size and decided to experiment with it. There is a significant speed difference (at least from where I'm sitting) in pano load times both locally and online. I've put it online for you to verify.
http://virtuastudio.pl/vir/muzeum%20tec … uzeum.html   (faster)
http://virtuastudio.pl/vir/muzeum%20tec … ut120.html   (slower)
Parameters of both tours are identical: XML not embedded, jpg 8, source panos 6000x3000, "reduce distortion" used.
The only difference is that in the first tour cube face is 1904 and cutting 478 whereas in the second cube face is 1888 and cutting 120.
The way I do it is enter the cutting size manually and click  "reduce distortion" to get the optimum cube face size.

Last edited by deedee7 (2012-05-04 03:20:47)