- How "cutting size" affect the final panorama?

cutting size cuts the pano images into smaller tiles for (multires panos only) so if a user is looking for a specif area of 128 by128 pix then the tile of that area will be downloaded from the server.

What's the practical difference on using 512 or 256 or 128 or 64...

as per above example the specific area tile needs to be downloaded & if the user is viewing the area of 128x128 pix & your tiles are 512 pix it will have to be downloaded a much bigger tile which maybe not user friendly to the bandwidth, so smaller tiles will render tours faster when fully zoomed in.

As for the krpanotools droplets:
- can I input the cutting size parameter?
- can I change jpeg compression of the autogenerated tiles of a multires pano?

Yes you can change the various parameters in kmakemultires.config file, open the file in text editor & ensure you save it as .config file not as text file.

"MAKE PANO (TILED)" and "MAKE PANO (MULTIRES)"

they both are self explanatory, make pano will create only 6 cubes with limited resolution whereas make pano multires will tile & cut those tiles (1024-64) & make multres tour.

Smaller the tiles such as 64x64 faster tour rendering will happen on slower connection of gigapixel images.

Last edited by digipano (2010-11-23 03:23:08)

digipano wrote:

Smaller the tiles such as 64x64 faster tour rendering will happen on slower connection of gigapixel images.

This is true, but...

marco.lanciani wrote:

So viewing in fullscreen resolution, using tiles bigger than 1024 seems useless.

This is false. Be aware that Krpano player allocates some memory overhead (RAM) for each tile it loads. This means limiting tiles number is a way to reduce memory consumption used by the browser and in certain cases, it's a way to prevent him from crashing. To limit tiles number, you can increase tile cutting size to 1024 for example. Using a high cutting size is recommended for gigapixels tours.