Adrien F wrote:Hello Michael,
If you use the krpano unlimited licence, you should try to set a smaller cutting size in Pictures parameters (512 seems ok to me) to take advantage of multiresolution. Play also a bit with jpeg quality and you should be good.
Most of the time the un-smoothness of visits is due to a too big picture size.
Adrien
klausesser wrote:setting the cube-face size to 512 for taking "advantage of multiresolution"? Or what do you mean with "smaller cutting size"?
Adrien F wrote:So what is the cutting size? It is the maximum size a patch can have. When loading pictures APT uses approximations of the panorama, at different level of zoom, cut in patches. Choosing to have a high cutting size means loading biggers parts of the scene, but in little number. A low cutting size means having a lot of small pictures to load, thus ensure a "smoother" loading
Adrien F wrote:Note : what I call patch is also known as tile
digipano wrote:klausesser wrote:P.S.: where in hell is an item named "cutting size" in APT?
Panorama properties> Picture parameters> compute optimal size> cutting size (2nd row)
Adrien F wrote:If you use the krpano unlimited licence, you should try to set a smaller cutting size in Pictures parameters (512 seems ok to me) to take advantage of multiresolution. Play also a bit with jpeg quality and you should be good.
Most of the time the un-smoothness of visits is due to a too big picture size.
Adrien
Which field relates to "cutting size"?
MTK wrote:Which field relates to "cutting size"?
In reading your recommendation, which field should I enter "512"?
Thank you in advance for your help.
Michael T. Kleven
DrSlony wrote:Hey klausesser, although I don't use krpano, from what I know about other pano viewers I infer that the cube size limits the resolution of the panorama - the equirectangular pano, regarless of its size, gets converted to 6 cube faces and each one is as large as you set them. I typically use about 1500-2000px for fullscreen viewing (no multires, but its sharp fullscreen on a 1680x1050 screen). From the definitions given here, cutting size I guess is how many tiles each cube face gets divided into. The more tiles you have, the less off-screen data has to be downloaded if you zoom in at such a distance that the whole cube face doesn't fit on the screen. For example if you shot a giga pano and use tiles 2000px wide but your flash window is only 800px wide, you're loading extra 1200px in width for nothing.
So why not make small tiles 10x10 px by default? I don't know, I'd like someone from krpano to answer that, but my guess is that its about overhead and worse performance when flash has to move many little pieces instead of one large one.
Adrien F wrote:Hello Michael,
If you use the krpano unlimited licence, you should try to set a smaller cutting size in Pictures parameters (512 seems ok to me) to take advantage of multiresolution. Play also a bit with jpeg quality and you should be good.
Most of the time the un-smoothness of visits is due to a too big picture size.
Adrien
BrianLR wrote:I also get this performance problem and tried using a cutting size of 512 rather than 1200. It did not improve performace and doubled the amount of storage space used, although the actual folder size was the same, probably due to all those tiny files.
digipano wrote:Yes it means that you cut the tiles to specified size for a multires panorama, smaller the tile size faster the loading can be (My guess) bcoz only those number tiles will be downloaded.
DrSlony wrote:So why not make small tiles 10x10 px by default? I don't know, I'd like someone from krpano to answer that, but my guess is that its about overhead and worse performance when flash has to move many little pieces instead of one large one.
Users browsing this forum: No registered users and 1 guest