Yes, 1px overlap enabled.
Saw the lines both in Firefox and Chrome.
Some questions for 4.5 beta 2
- JimWatters
- Posts: 329
- Joined: Thu Oct 07, 2010 6:16 pm
- Location: Saint John, New Brunswick
- Contact:
Jare,
I am seeing black on the sides of the preview level.
http://3dpano.pindora.com/panorama/tret ... l5_0_0.jpg
http://3dpano.pindora.com/panorama/tret ... l5_0_0.jpg
I could not reproduce images with borders in the preview using your same tile schema.
Where all these tiles freshly generated with 4.5b2?
What OS are you using?
I am seeing black on the sides of the preview level.
http://3dpano.pindora.com/panorama/tret ... l5_0_0.jpg
http://3dpano.pindora.com/panorama/tret ... l5_0_0.jpg
I could not reproduce images with borders in the preview using your same tile schema.
Where all these tiles freshly generated with 4.5b2?
What OS are you using?
- Jim Watters
http://photocreations.ca
http://photocreations.ca
Hi Jim,
yes, done with 4.5b2. Windows 7 64bit
You are right, there are black borders in the preview images.
My panorama has levels 570-1140-2280-4560-9120.
Also other panoramas with levels 638-1276-2552 and 637-1274-2548 shows the black lines.
Tried set levels to values 600-1200-2400 and 580-1160-2320, then there is no black lines. Also with 538 and 537 level tile size panoramas are ok.
yes, done with 4.5b2. Windows 7 64bit
You are right, there are black borders in the preview images.
My panorama has levels 570-1140-2280-4560-9120.
Also other panoramas with levels 638-1276-2552 and 637-1274-2548 shows the black lines.
Tried set levels to values 600-1200-2400 and 580-1160-2320, then there is no black lines. Also with 538 and 537 level tile size panoramas are ok.
- JimWatters
- Posts: 329
- Joined: Thu Oct 07, 2010 6:16 pm
- Location: Saint John, New Brunswick
- Contact:
Jare,
I have created bug Issue #976
Looks like If the bottom tile is divisible by 4 then there is no black border in the preview.
I have created bug Issue #976
Looks like If the bottom tile is divisible by 4 then there is no black border in the preview.
- Jim Watters
http://photocreations.ca
http://photocreations.ca
Ok, thank you for this tip. Will this rule take into account.JimWatters wrote:Jare,
Looks like If the bottom tile is divisible by 4 then there is no black border in the preview.
My first experience for multires, I can only guess how it works well on mobile devices
http://gumirj.com/test_ml/index.html
main 2000
MR
450
no 1px overlap (all he needed or not needed?)
levels
1800
900
450
http://gumirj.com/test_ml/index.html
main 2000
MR
450
no 1px overlap (all he needed or not needed?)
levels
1800
900
450
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
360 Texas,
What would you use for mobile?
Above you wrote:
"Our 3 spherical HTML5 with Flash fallback player option (no .swf file) MULTIRESOLUTION panorama tour (not using Mobile)"
Also, is Flash fallback swf no longer necessary with Multires for both Flash and Html5 in V4.5?
What would you use for mobile?
Above you wrote:
"Our 3 spherical HTML5 with Flash fallback player option (no .swf file) MULTIRESOLUTION panorama tour (not using Mobile)"
Also, is Flash fallback swf no longer necessary with Multires for both Flash and Html5 in V4.5?
Kristin
- 360Texas
- Moderator
- Posts: 3684
- Joined: Sat Sep 09, 2006 6:06 pm
- Location: Fort Worth, Texas USA
- Contact:
I think multires and mobile are almost duplicate functions... sizing the cube face tiles to fit on a mobile [smartphone, tablet or desktop] screen.
more tiles, more local hard drive storage space, longer it takes to upload to server, more server space required.
So I make Flash fallback, and HTML5 outputs. it creates 1 set of files that both flash and html5 use.
Here is my site.
Notice when you click the link below you arrive at my Gallery. The gallery page is just a stock html page. Click the [View Details >>] button for the 7th Street Bridge Tour. The link is just a standard hyperlink. It goes to /OUTPUT/Bridge/bridge.html. This bridge.html is the html page created with Pano2vr. If THIS Bridge.html page is your desired behavior [goes directly to full screen] then your in luck.
In the pano2vr project file: I created Multires for both flash and html5 outputs with level tile size 650 px. Width 2600, 1300, 650. This creates 1 file set of 133 tiles with about 6 mb file size.
you should have 2 output types:
FLASH /html tab\ do not select [_] enable.
HTML5 output /html tab\ select [x] enable | Template [normal.ggt] | [x] Fullscreen | [x] Flash fallback player. All other items on this page are deselected. On page bottom: Output file should be output\yourpanoname.html .
Then rebuild your project. Copy the OUTPUT folder to the server.
Make sure on your main page... make your link to your pano .... OUTPUT\yourpanomane.html.
Link to my demo page for 7th Street Bridge fullscreen version:
http://360texas.com/services/new360/gallery.html
more tiles, more local hard drive storage space, longer it takes to upload to server, more server space required.
So I make Flash fallback, and HTML5 outputs. it creates 1 set of files that both flash and html5 use.
Here is my site.
Notice when you click the link below you arrive at my Gallery. The gallery page is just a stock html page. Click the [View Details >>] button for the 7th Street Bridge Tour. The link is just a standard hyperlink. It goes to /OUTPUT/Bridge/bridge.html. This bridge.html is the html page created with Pano2vr. If THIS Bridge.html page is your desired behavior [goes directly to full screen] then your in luck.
In the pano2vr project file: I created Multires for both flash and html5 outputs with level tile size 650 px. Width 2600, 1300, 650. This creates 1 file set of 133 tiles with about 6 mb file size.
you should have 2 output types:
FLASH /html tab\ do not select [_] enable.
HTML5 output /html tab\ select [x] enable | Template [normal.ggt] | [x] Fullscreen | [x] Flash fallback player. All other items on this page are deselected. On page bottom: Output file should be output\yourpanoname.html .
Then rebuild your project. Copy the OUTPUT folder to the server.
Make sure on your main page... make your link to your pano .... OUTPUT\yourpanomane.html.
Link to my demo page for 7th Street Bridge fullscreen version:
http://360texas.com/services/new360/gallery.html
Thank you for clarifying this, Dave.
The multiresolution tile sizes still confuse me. It seems the 650 size would be too big for mobile phones?
Please tell me if I am on the right track with this workflow.
Original Panos 8432x4216
Downsize to 7800x
In HTML5 Settings tab, set cube face size to 1950
In Multires, Level Tile size 325, then levels 1300, 650, 325
I am creating my tests for an museum project. It will have numerous panos and rooms, so clarity and optimization for various users will be key.
Would the "Load at Startup" for the 650 size be advisable or would users experience some wait time?
The multiresolution tile sizes still confuse me. It seems the 650 size would be too big for mobile phones?
Please tell me if I am on the right track with this workflow.
Original Panos 8432x4216
Downsize to 7800x
In HTML5 Settings tab, set cube face size to 1950
In Multires, Level Tile size 325, then levels 1300, 650, 325
I am creating my tests for an museum project. It will have numerous panos and rooms, so clarity and optimization for various users will be key.
Would the "Load at Startup" for the 650 size be advisable or would users experience some wait time?
Kristin
- 360Texas
- Moderator
- Posts: 3684
- Joined: Sat Sep 09, 2006 6:06 pm
- Location: Fort Worth, Texas USA
- Contact:
OK.. I agree... and I do need to reconstruct the cube face tiered tile dimensions. I think the html5 setting should be 1440. The size you mentioned 1950 is too large.
From above Martin said:
Replace his 10500px equirec with your 7800px and use his math process.
http://ggnome.com/wiki/HTML5%20Cube%20F ... %20Devices
From above Martin said:
Replace his 10500px equirec with your 7800px and use his math process.
Here is a handy GGS reference page you might want to book mark.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
http://ggnome.com/wiki/HTML5%20Cube%20F ... %20Devices
- JimWatters
- Posts: 329
- Joined: Thu Oct 07, 2010 6:16 pm
- Location: Saint John, New Brunswick
- Contact:
Once you enable the multiresolution you can ignore the cube face size on the first tab.KWimberg wrote:It seems the 650 size would be too big for mobile phones?
Please tell me if I am on the right track with this workflow.
Original Panos 8432x4216
Downsize to 7800x
In HTML5 Settings tab, set cube face size to 1950
In Multires, Level Tile size 325, then levels 1300, 650, 325
I am creating my tests for an museum project. It will have numerous panos and rooms, so clarity and optimization for various users will be key.
Would the "Load at Startup" for the 650 size be advisable or would users experience some wait time?
Multiresolution tab needs to include the largest cube size.
650 pixels cube faces might exclude the older less robust mobile devices.
7800/4 = 1950
1950 /2 /2 /4 = 121.875
round up to 122
122 * 4 = 488 for the tile size
488 * 2 * 2 = 1952 for highest and 976 for middle.
=====
488 tile
1952, 976, 488 tiles
Add a preview track of 1/4 to have something immediate
Check 488 as load at startup to ensure that entire level is loaded before loading higher resolution tiles.
- Jim Watters
http://photocreations.ca
http://photocreations.ca
Hi!
It seems I´ve been missing something. Why all the use of those strange numbers and elaborated calculations? Why not start downsizing to 8000 (only to work with a round number). Then with a level tile size of 500 and levels of 2000, then 1500, 1000 and finally the smallest 500 using that as the one to be loaded at startup. Does it make any difference using a tile size of 488 against one of 500. At least the maths are easier.
Should one need a smaller tile size then use 400 and levels of 2000, 1600, 1200, 800, 400. That should cover almost all devices and resolutions on the market. Am I wrong or even confused?
I hope someone could make me understand.
Regards, Martin
It seems I´ve been missing something. Why all the use of those strange numbers and elaborated calculations? Why not start downsizing to 8000 (only to work with a round number). Then with a level tile size of 500 and levels of 2000, then 1500, 1000 and finally the smallest 500 using that as the one to be loaded at startup. Does it make any difference using a tile size of 488 against one of 500. At least the maths are easier.
Should one need a smaller tile size then use 400 and levels of 2000, 1600, 1200, 800, 400. That should cover almost all devices and resolutions on the market. Am I wrong or even confused?
I hope someone could make me understand.
Regards, Martin
- JimWatters
- Posts: 329
- Joined: Thu Oct 07, 2010 6:16 pm
- Location: Saint John, New Brunswick
- Contact:
No need to have levels other than 1/4 the previous size by halving the width. Creating extra levels for every factor of the tile size is a waste.
if 8000 is your ideal cube width, then use:
8000, 4000, 2000, and 1000
and cube faces of 500
Making cube sizes of 500, 1500, 3000, and 6000 is just a waste of bandwidth for the user, and storage space for the content creator.
No need to downsample to a nice round equirectangular size before letting Pano2VR create cube faces.
The calculations are pretty simple.
Estimate cube size based on a value of Equirectangular width divided by 4 or Pi
divide by 2 until less than or equal to 512
to accommodate preview track of 1/4 width divide by 4,
round to nearest whole number
multiply by 2 until you are close to the starting estimate.
Using 500 instead of 488, when 488 is ideal, means you are going to waste 5% bandwidth and storage.
if 8000 is your ideal cube width, then use:
8000, 4000, 2000, and 1000
and cube faces of 500
Making cube sizes of 500, 1500, 3000, and 6000 is just a waste of bandwidth for the user, and storage space for the content creator.
No need to downsample to a nice round equirectangular size before letting Pano2VR create cube faces.
The calculations are pretty simple.
Estimate cube size based on a value of Equirectangular width divided by 4 or Pi
divide by 2 until less than or equal to 512
to accommodate preview track of 1/4 width divide by 4,
round to nearest whole number
multiply by 2 until you are close to the starting estimate.
Using 500 instead of 488, when 488 is ideal, means you are going to waste 5% bandwidth and storage.
- Jim Watters
http://photocreations.ca
http://photocreations.ca
Thank you all. It seems clear now.
I wonder if a tutorial might be written about this, particularly since the new version with HTML5 multiresolution does change the workflow quite a bit. Jim's suggestion to create a preview tile setting is particularly helpful.
I am a new user since December. The workflow for optimal output on all devices is not easy for a beginner to understand. I read many forums in order to get it straight in my head. And, there was a lot of conflicting information - at least it appeared that way to me.
That said, now I'm wondering how to get my panoramas to move smoothly. The multiresolution output, with all its load time, is not a smooth solution. Does this mean I go back to a standard HTML5 output with mobile settings and Flash Fallback Player?
I wonder if a tutorial might be written about this, particularly since the new version with HTML5 multiresolution does change the workflow quite a bit. Jim's suggestion to create a preview tile setting is particularly helpful.
I am a new user since December. The workflow for optimal output on all devices is not easy for a beginner to understand. I read many forums in order to get it straight in my head. And, there was a lot of conflicting information - at least it appeared that way to me.
That said, now I'm wondering how to get my panoramas to move smoothly. The multiresolution output, with all its load time, is not a smooth solution. Does this mean I go back to a standard HTML5 output with mobile settings and Flash Fallback Player?
Kristin
html5 bug in last pano2vr 4.5
if resolution 1:4 then no problem
if resolution 1:4 then no problem
- Attachments
-
- Untitled-1.jpg (50.84 KiB) Viewed 7826 times
-
- index.jpeg (154.8 KiB) Viewed 7826 times