02Mar2015 Mobile settings for Pano2vr version 3.x & 4.1 only

[360Texas]

Update 02 March 2015 -> We have renamed this thread with the understanding that discussion will be for PANO2VR Version 3.x and 4.0 users

/s/s/s/
Dave, Jim and Martin

We have been testing the HTML5 /css3 screen sizes for various idevices. Here are the values we have found todate that seem to work.
HTML5/CSS3 Recommended: screen and cubeface/tile sizes for "mobile" tab

Mobile Phone devices: Updated 8 March 2012
iPod, iPhone 1,2,3 device screen 480 x 320 pixels 163 ppi. -> Screen 480 Cubeface/tile 416 On HTML tab click full screen [x] option
iPhone 4g device screen 960 x 640 pixels 326 ppi. -> Screen 960 Cubeface/tile 700 compression 70 On HTML tab click full screen [x] option

Updated 18Apr13
iPhone 5 logical screen size 500 x 320 in landscape
iPhone 5 typical screen size reported as 960 x 640 and logical screen size is discussed here : http://v-play.net/2012/10/supporting-iphone-5/
(thanks Martin for the iPhone 5 url link)

Samsung Tab 16/32 gb Android 3.1 10.1" 1280 x 800
Samsung Galaxy S II i9100 Screen size 800 x 400 218ppi ->

Samsung Galaxy S III Screen size 1280 x 720 306ppi ->10 August 2012 ->>300dpi = ppi almost printer resolution
Android O/s = 4.0.4 ICS, Browser is basic Webkit and no flash installed.
To see HTML5/css3 with Flash Fallback = Use 'Market' find and install robust Browser and Flash 11
Android O/s 4.1 upgrade works on most smart phones. Jelly Bean 4.3 will not support Flash however it does support HTML5/CSS3 output.

Samsung Galaxy Note 10.1 Screen size 1280 x 800 ->
Samsung Galaxy Note Screen size 1280 x 800 285ppi ->

HTC EVO Design 3G/4G 960 x 540 pixels 275ppi qHD Super LCD Adobe Flash enabled (11Nov11Thanks Dave for your feedback)
HTC EVO 4G LTE 4.7 inch screen 1280 x 720 pixels 312 ppi

Tablets updated 08 March 2012
Acer 16/32gb Android 3.1 Honeycomb 10.1" 1280 x 800
Archos 8gb Android 2.2 10.1" 1024 x 600
Asus Eee 16/32gb Android 3.0 Honeycomb 10.1" 1280 x 800
Blackberry Playbook QNX Blackberry OS 7" 1024 x 600
Coby Tablet Android 2.3 7" 800 x 480
Dell Streak Android 2.2 -> 3.0 7" 800 x 480
HP Touch Pad 16/32gb HP WebOS 3.0 9.7" 1024 x 768

iPad 1 and 2 device screen 1024 x 768 pixels 132 ppi. ->Screen 1024 Cubeface/tile 960 On HTML tab click full screen [x] option
iPad (3) device screen 24Nov2012 2048 x 1536 pixels 264 ppi. -> 1025 Cubeface/tile 960 On HTML tab click full screen [x] option
iPad Mini 7.9" screen 1024 x 768 pixels 163 ppi. similar to IPad 1 and 2 Screen 1024 Cubeface/tile 960 On HTML tab click full screen

Apple Mac Book Pro (Retina Display) 2880 x 1800 pixels 220 ppi 13Jun2012

Motorola Xoom Android 3.0 Honecomb 10.1" 1280 x 800 (160ppi)
Toshiba Thrive 8/16/32gb Android 3.1 10.1" 1280 x 800 (160ppi)

Flash Fall back
HTML TAB FLASH Fall back device screen variable -> specify file name .swf file size which might be about 1.5 - 1.8mb

IMPORTANT: Please also read https://ggnome.com/wiki/HTML5_Cube_Face ... le_Devices

This is work in progress so more as we learn more. If you wish to contribute your experience - pls contact me on SKYPE iam360texas (UTC/GMT -6) Monday - Friday unless we are out on photo session.

[MORE from Wim] Forum LINK http://gardengnomesoftware.com/forum/vi ... f=6&t=6812
Re: The positive impact of iOS 5 on the quality of iPad pano
by Wim.Koornneef » 13 Oct 2011 12:13

DemonDuck wrote:
Why would tile size affect image quality of output like that?????
I don't know, I can only guess what is going on.

When testing in steps (960-1100-1300-1500-1700-1900) I found out that the image quality slowly improves with each larger tilesize, this improvement suddenly stopped with 1500 px. After some more testing I found the sweet spot at 1440px.

It turns out that from 960px to 1440px the quality improves a bit with larger sizes, then it falls down at the lowest quality level at 1472 px and from there it improves again very slowly up to 1900+ (I stopped testing at 1900 px).

Wim
Wim.Koornneef

Information we will need to know - device manufacturer and model name - device screen size. Your tested SCREEN and Cubicface/tile pixel values.

It was learned 23Nov12 that Windows 8 IE 10 does support HTML5/CSS3. Windows 8 uses 'TOUCH' on the START but once viewing a Panorama.. looses Touch ability.

Thanks in advanced for your help

[360Texas]

I added the cell phone below to the list

This Wi Max (as compared to an LTE radio) Phone released October 2011
HTC EVO Design 3G/4G 960 x 540 pixels qHD Super LCD

[dallasrab]

Hello 360Texas,

Do you have or know where I can find a tutorial or template on creating an index.html file that automatically directs a user to the correct virtual tour needed to play on their device?

What I'm trying to do is create a "flash" and a "HTML5" virtual tour, but with the "HTML5" having two different skins, one for the iPad and one for the iPhone...like the one here: http://gardengnomesoftware.com/samples/pano2vr_3/ntour.

I've already created my tour for "flash" and "HTML5" (iPad), and now I want to create a separate "HTML5" version for the iPhone. Once I do this I would like to create the index.html file that automatically directs the user to the correct version needed for their device (flash, iPad, or iPhone)...just like Hopki and Thomas did with this example they've posted. I've downloaded their project files but unfortunately I am not knowledgeable enough to figure out exactly what I "do" and "do not" need from them to make my project a success. Any help here would be great.

Thank for your time and help. I appreciate it.


Dallas

[360Texas]

Hi Dallas (where in Dallas are you located? DFW is a big place)

Yes, we created an index.html demo page when you click a link it goes over and starts up an html page for the panorama.
IF you are creative, you can just right mouse click and save page as.

Also depending if you are using a

windows pc and IE 9 and have flash player installed it will deliver the .swf to your machine

If you are using a mac or an ipad2 with Safari it will deliver an html 5

The way you can tell if you are looking at the pano with flash.swf or html5 rotate /tilt down... if you see numbers like 960 you are seeing html5. No numbers ? you are looking at the .swf

Click to view http://360texas.com/services/sr/dbu/index.htm



Dave still over here in Fort Worth, Texas

[dallasrab]

360Texas,

Thanks for all of the information. Actually I'm located in South Carolina...but my name is Dallas. I've never lived in Texas, but my father lived there for 30 yrs...in Dallas and Houston. He actually lived on Southfork Ranch for 5 years or so while working there...which was pretty cool.

Anyway, I'm still not quite sure this is what I need though. I'm just trying to create a virtual tour using three skins (1 flash and 2 html5) in which the ipad skin will have a map, and the iphone skin won't . Do you have any suggestions on where I should look or search for direction in creating such?

Thanks again for your help!

Dallas

[360Texas]

Martin (our Host Gnome) creates skins... not sure if any are for flash/html5 flavor.

Might book mark his website page: http://hopkimedia.co.uk/

[dallasrab]

Thanks Dave, I appreciate your time and help.

Dallas

[Vestland]

Please be patient with me ...
I am quite bewildered by all the suggested settings for iDevices. I have tried to make panos with these settings. Is that overkill or OK?
I guess there is a reason to why there is no standard default settings, for everybody to use...

Mobile-settings.jpg (85.61 KiB) Viewed 34439 times

[360Texas]

For only idevices - settings from list above

iPad 1 and 2 device screen 1024 x 768 pixels 132 ppi. ->Screen 1024 Cubeface/tile 960 On HTML tab click full screen [x] option

iPhone 4g device screen 960 x 640 pixels 326 ppi. -> Screen 960 Cubeface/tile 800 On HTML tab click full screen [x] option
iPod, iPhone 1,2,3 device screen 480 x 320 pixels 163 ppi. -> Screen 480 Cubeface/tile 416 On HTML tab click full screen [x] option

Hope this helps

[Vestland]

Thank you.
But what are the settings if I want to make my panos viewable by as many mobile devices of any kind as possible?

[360Texas]

Ah so using Pano2vr version 3.1.2 we have to deal with browsers and delivery techiques. Little bit more complex work flow.. but still easy.

Two browser categories: Those that are html5 aware and those that are html5 UNaware
As of December 2011 [anyone feel free to add in your browser and configuration comments] you might use the following work flows. Using generalized tile sizes should improve delivering the proper tile sized images suitable for the devices screen sizes while offering reasonable delivery download speeds. Would not want to deliver a full screen 2mb image to a small 320 pixel screen smart phone 3g speed connection... would take too long and your visitor would bolt out the door.

-- /Mulitresolution tab
HTML5 UNAWARE flavor and use Adobe Flash Viewer most PC desktops and tablets, Android O/S with flash plugin installed smart phones 3g and 4g download speeds. IE 8 and 9, Mozilla Firefox, Google Chrome

You might also use the -- /HTML tab/ Template 'flash_html5_fullscreen.ggt . Then your image would stretch to fit the device screen.

Create Output Format for:
"Flash" and Muliresolution [ Enable this function and say OK to use default tile size 1500, 750, 375 ]

--- /mobile tab
HTML5 AWARE flavor and use HTML5 using Flashfall back option for one of the above flash .swf's
Safari browser

Create Output Format for:
iPad 1 and 2 screen 1024 and tile 960
iPhone 4 and 4s screen 960 and tile 640
iPhone 1,2,3 screen 480 and tile 416

After a short SKYPE discussion with Martin we agree, the above technique might best render your panoramas on most devices.

[Vestland]

Whoa! Maybe a bit slower
I make a tour which are to be watched on both PC/Mac and mobile devices.

For the PC/Mac I make flash files and multiresolution tiles
Cube face size 2624 (the equirect picture is 10635px wide)
Multiresolution tab/Basic Settings enabled/ Level tile size 512, three levels: 2644, 1322, 661,330 (the three first were automatically generated, the 661 is loaded at startup, the 330 is embedded. Are these choices good ?)
By embedding level 330 the tiles load on the page as the viewer watches them, but I find this preferable to first loading the whole set before displaying it. The viewer does not have to wait that long to see some action. What is your experience concerning this assumption?

For the mobile devices I make HTML5
Cube face size 1440, window size 640x480 (?).
At the Mobile tab I use the settings you suggests, 1024/960, 960/800, 480/416
At the HTML-tab I choose normal.ggt (there are no fullscreen.ggt option there), and a checkmark at "Fullscreen" and "Include gyroscope control"

From your answer I see that I need to make another Flash file/multiresolution tile folder directed at the mobile users who don´t use HTML5 (and the fallback file used when html5 is not supported in the device). I don´t know what to use for the Cube face size here, what is your suggestion? Does the window size settings matter? Do Flash-based mobile devices take advantage of multiresolution?
I named the Output swf-file (the fallback) to make it separate from the PC/Mac-version
For the Multiresolution levels I put the tiles in another folder (under Filename) to separate it from the Tiles folder for the PC/Mac. I used your suggested values 1500/750/375 and embedded level 375. The resulting swf file size is 350kb, is that too large?

[Vestland]

I am probably getting this wrong, but having to make seamless solutions for both PC and mobile devices with and without html5/flash is getting to be a major hassle. Especially when, like me, you are not scripting-savvy and develop your main web-pages and the tour maps for PCs in another web-page application (I use Freeway).

My panos use both a map (made in Freeway) and hotspots for maneuvering. In P2V the hotspot urls are set equal for all the versions (flash/html5/mobileflash). When a user on a mobile device clicks a hotspot he is therefore led to the PC-flash-page which directs the mobile device to the html5-page which finds that this particular mobile device does not support html5 and sends the viewer to the fallback-swf file (which is a scaled down version of the PC flash page). This is an invisible digital merry-go-round for each picture the viewer wants to visit. This might lessen the viewers interest as it probably involves waiting.

Another challenge:
A viewer (Ann) with a mobile device using flash might share an interesting url with somebody else (Ben). If Ben is using a mobile device using html5 his device will get confused as it finds a page made for flash. The flash-page therefore must include a script to detect what kind of device is asking, and redirect to the correct version being it a PC or html5-savvy device.

I am working on a 90-picture tour and can probably not justify the work that seems necessary to make this automatically viewable on mobile devices. There is the problem of writing the scripts (the hardest part for me), but also the time consumed setting up all the versions in P2V and then uploading all the files to the server.

I do hope somebody can tell me that there are simple answers

[Hopki]

HI
This sounds like a lot of work with all this redirecting...
To simplify it a bit more you could just have one HTML page and have that serve up the best output for the device viewing.

Example.
Input Image 6000 x 3000px but you can use any size even giga pix.

Flash output, multiresolution: Levels 1500, 750, 375.
Level tile size 375. (this divides equaliy in all the levels)
Do not produce an HTML page.

HTML5 output, settings tab, 1500,
Mobile settings,
Max: 1024, Tile: 1440 80% iPad 1&2 (possible since IOS5)
Max: 960, Tile: 700 80% iPhone 4
Max: 480, Tile: 416 70% iPhone 3

Produce an HTML page from the HTML5 output and add the SWF from the Flash output to the Flash fullback input text box.
And that should be that.

Android devices with small screens using flash will get smaller tiles and quicker downloads over the mobile network. Computers with larger screens will get better quality and with the HTML5 output all the iDevices are also sorted, job done.
Regards
Hopki

[360Texas]

Thanks Martin, You did simplify the work flow.

Thanks