Hi Garden Gnome team, as a whole, I find this very hard-working beta!!!
I have a few questions, maybe I missed something because it did not use never
1. Multiresolution HTML5
If this mode is enabled, it is not necessary now to use Mobile tab?
2. Multiresolution HTML 5
There is need to include mandatory - 1px overlap and all levels checkboxes - Load at Starup?
3. Multiresolution HTML5
Can I use a discrete value - Level tile size - 250px?
4. HTML5 template - normal.ggt
Been added to the template that any important changes? I modified the old "normal.ggt" 4.1.
Does this mean that I have to redo again a new template for my works?
5. I have a feeling that for multiresolution element pre-loader is not necessary.
Or should I include it as a standard element permanently?
6. When will be about native support for GIF?
I apologize if I will take you a little time with these questions
Some questions for 4.5 beta 2
Gumir J | VR Panoramic Photographer | mobile: +77055717171 | skype: gumirj
website: gumirj.com | google.com/+gumirj | facebook.com/gumirj | twitter.com/gumirj
website: gumirj.com | google.com/+gumirj | facebook.com/gumirj | twitter.com/gumirj
up
Gumir J | VR Panoramic Photographer | mobile: +77055717171 | skype: gumirj
website: gumirj.com | google.com/+gumirj | facebook.com/gumirj | twitter.com/gumirj
website: gumirj.com | google.com/+gumirj | facebook.com/gumirj | twitter.com/gumirj
Hi Gumir!
Although I am not a Gnome, will try to answer.
Load at startup - this means which level is loaded at startup, independently of screen size or zoom. I usually check the level about 2000pix, it fits most of screen sizes so during rotation of pano the sub-tiles are not downloaded
You can check all the level to be loaded at startup, but it increases initial loading time and fills device's memory.
Bug tracker says this shoul be fixed only in v5 http://gardengnomesoftware.com/bt/view.php?id=926
Although I am not a Gnome, will try to answer.
Yes, using html5 multiresolution forget the Mobile tabIf this mode is enabled, it is not necessary now to use Mobile tab?
1px overlap is recommended to avoid visible seams between tiles.There is need to include mandatory - 1px overlap and all levels checkboxes - Load at Starup?
Load at startup - this means which level is loaded at startup, independently of screen size or zoom. I usually check the level about 2000pix, it fits most of screen sizes so during rotation of pano the sub-tiles are not downloaded
You can check all the level to be loaded at startup, but it increases initial loading time and fills device's memory.
In my opinion, 250px is too small size. Then the total amount of sub-tiles is too high/ Optimal 400-600px.Can I use a discrete value - Level tile size - 250px?
It depends of the Load at startup settings and user's internet connection speed. Try to include loader and check yourself it's lifetime.I have a feeling that for multiresolution element pre-loader is not necessary.
Or should I include it as a standard element permanently?
When will be about native support for GIF?
Bug tracker says this shoul be fixed only in v5 http://gardengnomesoftware.com/bt/view.php?id=926
- JimWatters
- Posts: 329
- Joined: Thu Oct 07, 2010 6:16 pm
- Location: Saint John, New Brunswick
- Contact:
They look like good answers. Do you require more information?
- Jim Watters
http://photocreations.ca
http://photocreations.ca
@jare
Thank you, Brother!!!
Thank you, Brother!!!
Gumir J | VR Panoramic Photographer | mobile: +77055717171 | skype: gumirj
website: gumirj.com | google.com/+gumirj | facebook.com/gumirj | twitter.com/gumirj
website: gumirj.com | google.com/+gumirj | facebook.com/gumirj | twitter.com/gumirj
- Hopki
- Gnome
- Posts: 12999
- Joined: Thu Jan 10, 2008 3:16 pm
- Location: Layer de la Haye, Essex UK
- Contact:
Hi Gumir,
Just to expand on the level tile size question.
This should be a value that equally divisible in all the other levels to avoid odd sized tiles.
So this will change depending on your input image size.
Example:
Input Equirec 10500 x 5250, 10500 / 4 = 2625 cube face. (This is the default in the settings/preferences)
This will not divide down properly so may be better to resize to 10400 / 4 = 2600
This would give you the following possible levels:
2600
2275
1950
1625
1300
975
650
level tile size 325
So 325 is equal devisable in every level.
To reduce the amount of files you could use:
2600
1950
650
level tile size 650
Regards,
Hopki
Just to expand on the level tile size question.
This should be a value that equally divisible in all the other levels to avoid odd sized tiles.
So this will change depending on your input image size.
Example:
Input Equirec 10500 x 5250, 10500 / 4 = 2625 cube face. (This is the default in the settings/preferences)
This will not divide down properly so may be better to resize to 10400 / 4 = 2600
This would give you the following possible levels:
2600
2275
1950
1625
1300
975
650
level tile size 325
So 325 is equal devisable in every level.
To reduce the amount of files you could use:
2600
1950
650
level tile size 650
Regards,
Hopki
Garden Gnome Support
If you send an e-mail to support please send a link to the forum post for reference.
support@ggnome.com
https://ggnome.com/wiki/documentation/
If you send an e-mail to support please send a link to the forum post for reference.
support@ggnome.com
https://ggnome.com/wiki/documentation/
Hi Martin!
Can you explain, please, why to use 1950 instead of 1300 level size?
I've been always convinced that the level size should be half/twice of the next/previous level (650 - 1300 - 2600). This way the levels are added automatically.To reduce the amount of files you could use:
2600
1950
650
level tile size 650
Can you explain, please, why to use 1950 instead of 1300 level size?
- Hopki
- Gnome
- Posts: 12999
- Joined: Thu Jan 10, 2008 3:16 pm
- Location: Layer de la Haye, Essex UK
- Contact:
Well spotted, typo , should have been the default, so top level then half, then half agin.
2600 / 2= 1300
1300 / 2 =650
But you can always start with 650, then + 650 60 make each level
650 + 650 = 1300
1300 + 650 = 1950
1950 + 650 = 2600
Not that good as it generates far to many images to upload.
But high lights the point that the level tile size fits in all the other levels equally.
2600 / 2= 1300
1300 / 2 =650
But you can always start with 650, then + 650 60 make each level
650 + 650 = 1300
1300 + 650 = 1950
1950 + 650 = 2600
Not that good as it generates far to many images to upload.
But high lights the point that the level tile size fits in all the other levels equally.
Garden Gnome Support
If you send an e-mail to support please send a link to the forum post for reference.
support@ggnome.com
https://ggnome.com/wiki/documentation/
If you send an e-mail to support please send a link to the forum post for reference.
support@ggnome.com
https://ggnome.com/wiki/documentation/
-
- Posts: 96
- Joined: Wed Aug 29, 2007 9:33 pm
- Location: Milwaukee, USA
- Contact:
I wonder about this. For all the concern about using cube face sizes for mobile that are as large as possible without causing a crash, depending on HTML5 multi-rez would seem to guarantee problems. Zoom in and you are bound to load enough tiles to overload memory and cause a crash, aren't you?jare wrote:Yes, using html5 multiresolution forget the Mobile tabIf this mode is enabled, it is not necessary now to use Mobile tab?
Martin? Jim? What is the official position on this and if you can get away with HTML5 multi-rez on mobile how does it bypass the max face size / memory limits issue?
Scott Witte
http://www.tourdeforce360.com
http://www.tourdeforce360.com
- Hopki
- Gnome
- Posts: 12999
- Joined: Thu Jan 10, 2008 3:16 pm
- Location: Layer de la Haye, Essex UK
- Contact:
Hi Scott,
As you zoom in you are loading tiles for the area you are viewing not complete cube faces.
So if you keep zooming in you are replacing roughly the same amount of tiles each time, ok the file size does change depending on the content of the tile but for my test image which is over 3GB the tiles vary between 16, all black and 95KB detail image, not enough to crash a mobile.
As you pan around the the tiles that are moving off screen are unloaded from the browser in favour of the new so you should not get to a stage where there are lots of tiles in the cache.
Regards,
Hopki
As you zoom in you are loading tiles for the area you are viewing not complete cube faces.
So if you keep zooming in you are replacing roughly the same amount of tiles each time, ok the file size does change depending on the content of the tile but for my test image which is over 3GB the tiles vary between 16, all black and 95KB detail image, not enough to crash a mobile.
As you pan around the the tiles that are moving off screen are unloaded from the browser in favour of the new so you should not get to a stage where there are lots of tiles in the cache.
Regards,
Hopki
Garden Gnome Support
If you send an e-mail to support please send a link to the forum post for reference.
support@ggnome.com
https://ggnome.com/wiki/documentation/
If you send an e-mail to support please send a link to the forum post for reference.
support@ggnome.com
https://ggnome.com/wiki/documentation/
-
- Posts: 96
- Joined: Wed Aug 29, 2007 9:33 pm
- Location: Milwaukee, USA
- Contact:
Sounds very promising. I will have to see for myself with a crash prone iPod later. Thanks.Hopki wrote: not enough to crash a mobile.
Scott Witte
http://www.tourdeforce360.com
http://www.tourdeforce360.com
- 360Texas
- Moderator
- Posts: 3684
- Joined: Sat Sep 09, 2006 6:06 pm
- Location: Fort Worth, Texas USA
- Contact:
Our 3 spherical HTML5 with Flash fallback player option (no .swf file) MULTIRESOLUTION panorama tour (not using Mobile):
The Flash and HTML5 Multi Res setting are the same values.
--
originally used 2400, 1920, 1440, 960, 480 Level 480.
Resulted in 1011 files at 26.3mb upload to our server.
Review of the images/ folder revealed a lot of square tiles with a number of smaller image pieces.
--
I rebuilt our 3 spherical panorama tour using 2600, 1300, 650 with Level 650.
Resulted in 396 files at 15.4mb
Review of the images / folder revealed NO small image pieces. Each tile was 652 pixels square. Level was set to 650 with 1 pixel overlap each side edge.
--
Agree with Martin - too many tiles is not a good thing results in longer up load to server and excessive server file space. AND I think with few tiles we still retain panorama image quality. I suspect by using level at 650 instead of smaller 480 we are excluding smaller screen older devices.
The Flash and HTML5 Multi Res setting are the same values.
--
originally used 2400, 1920, 1440, 960, 480 Level 480.
Resulted in 1011 files at 26.3mb upload to our server.
Review of the images/ folder revealed a lot of square tiles with a number of smaller image pieces.
--
I rebuilt our 3 spherical panorama tour using 2600, 1300, 650 with Level 650.
Resulted in 396 files at 15.4mb
Review of the images / folder revealed NO small image pieces. Each tile was 652 pixels square. Level was set to 650 with 1 pixel overlap each side edge.
--
Agree with Martin - too many tiles is not a good thing results in longer up load to server and excessive server file space. AND I think with few tiles we still retain panorama image quality. I suspect by using level at 650 instead of smaller 480 we are excluding smaller screen older devices.
Thank you all, I find it as the best option for the current process as
- 450
1 - 1800
2 - 900
3 - 450
Only for multiresolution (without Mobile Option)
discarding quality for stability
also request an official answer for
- 450
1 - 1800
2 - 900
3 - 450
Only for multiresolution (without Mobile Option)
discarding quality for stability
also request an official answer for
4. HTML5 template - normal.ggt
Been added to the template that any important changes? I modified the old "normal.ggt" 4.1.
Does this mean that I have to redo again a new template for my works?
Gumir J | VR Panoramic Photographer | mobile: +77055717171 | skype: gumirj
website: gumirj.com | google.com/+gumirj | facebook.com/gumirj | twitter.com/gumirj
website: gumirj.com | google.com/+gumirj | facebook.com/gumirj | twitter.com/gumirj
Let me provide a 400MPix panorama for testing http://3dpano.pindora.com/panorama/tretyakovka/28.html Tile size is 570px.ScottWitte wrote: Sounds very promising. I will have to see for myself with a crash prone iPod later. Thanks.
In html5 multires panoramas builded in 4.5b2 there are ugly lines between cube faces at the startup.
- Attachments
-
- Untitled-1.jpg (85.52 KiB) Viewed 8654 times
- 360Texas
- Moderator
- Posts: 3684
- Joined: Sat Sep 09, 2006 6:06 pm
- Location: Fort Worth, Texas USA
- Contact:
I am using IE 11 Win 8.1
What browser and version are you using ?
For a small second during panorama loading I also saw the black cube face trace lines. They disappeared after the panorama is fully loaded.
Looks like black area in the 1 pixel overlay area.
Do you have the 1 pixel overlay enabled ?
I have been rebuilding our panoramas in Pano2vr 4.5b2 and not experience black lines.
What browser and version are you using ?
For a small second during panorama loading I also saw the black cube face trace lines. They disappeared after the panorama is fully loaded.
Looks like black area in the 1 pixel overlay area.
Do you have the 1 pixel overlay enabled ?
I have been rebuilding our panoramas in Pano2vr 4.5b2 and not experience black lines.