You are not logged in.

> The forum rules have been updated. Please take a moment to read them.


#1 2011-03-31 09:39:26

mrterra2000
New member
Registered: 2011-03-29
Posts: 3

Poor documentation.

I am desperate here and feel like I have to post in this forum every single question.I find the documentation on this software to be very poor and the lack of a tutorial awful (the wiki looks more like a glossary to me...).It seems that developers are foreseeing the importance of teaching their clients a proper workflow.The software seems pretty nice but this issue is making me think that I was better off with pano2vr wich is a simpler soft. but has excellent tutorials...

Offline

 

#2 2011-03-31 10:21:31

mediavets
Moderator
From: Isleham, Cambridgeshire, UK.
Registered: 2007-11-14
Posts: 9818
Website

Re: Poor documentation.

Welcome to the forum....

mrterra2000 wrote:

I am desperate here and feel like I have to post in this forum every single question.

Ask away...I'll do my best to help.

I find the documentation on this software to be very poor and the lack of a tutorial awful (the wiki looks more like a glossary to me...).It seems that developers are foreseeing the importance of teaching their clients a proper workflow.

All the Kolor software products have been evolving quite rapidly of late and the developers decided to wait until things 'stabilised' before committing more resources to documentation.

The software seems pretty nice but this issue is making me think that I was better off with Pano2vr wich is a simpler soft. but has excellent tutorials...

I started off with Pano2VR too, and yes there are nice tutorials for it, but I've not used it for a long time now. I never did really get my head around creating hotspots and programming 'skins' for Pano2VR.

I find Panotour and Panotour Pro are much easier to use to produce virtual tours. And Panotour Pro makes it very easy to produce iDevice compatible tours.

Last edited by mediavets (2011-03-31 10:35:30)


Andrew Stephens
Nikon D40, Nikkor 10.5mm fisheye, Sigma 8mm f3.5 fisheye, Nikkor 18-55/50/35mm lenses, Nodal Ninja 5 Lite, Nodal Ninja 4 with R-D16, Agno's MrotatorTCS short.
Nikon P5100, CP5000, CP995, FC-E8, WC-E63,WC-E68, TC-E2, Kaidan Kiwi 995, Bophoto pano bracket, Agno's MrotatorA.
Merlin/Orion robotic pano head + Papywizard on Nokia 770/N800/N810 and Windows 8/XP/2K.

Offline

 

#3 2011-03-31 13:03:39

klausesser
Member
From: Düsseldorf, Germany
Registered: 2006-05-22
Posts: 6600
Website

Re: Poor documentation.

mediavets wrote:

I find Panotour and Panotour Pro are much easier to use to produce virtual tours. And Panotour Pro makes it very easy to produce iDevice compatible tours.

Yes - i fully agree. PTP is basically very intuitive - but of course you need some time to get used to it. Nevertheless a detailed documentation is essential.

best, Klaus


If you want something you´ve never had,
then you´ve got to do something you´ve never done.

Offline

 

#4 2011-03-31 14:30:13

mrterra2000
New member
Registered: 2011-03-29
Posts: 3

Re: Poor documentation.

thx guys! i will certainly make questions for now i will continue reading.One thing when I import a panorama stitched with ptgui pro i get a yellow ! sign inside the thumbnail ptp, is this normal?

Last edited by mrterra2000 (2011-03-31 14:30:38)

Offline

 

#5 2011-03-31 15:37:16

mediavets
Moderator
From: Isleham, Cambridgeshire, UK.
Registered: 2007-11-14
Posts: 9818
Website

Re: Poor documentation.

mrterra2000 wrote:

thx guys! i will certainly make questions for now i will continue reading.One thing when I import a panorama stitched with ptgui pro i get a yellow ! sign inside the thumbnail ptp, is this normal?

Yes, it is normal.

Images stitched and rendered with APP/APG have a special Kolor custom EXIF tag which describes the pano FOV and other things about the pano image.

PT/PTP will read this to set the pano FOV and vertical offset values automatically in the Panorama Properties/Projection/Input field of view tab..

PTP will display that yellow ! alert if that custom EXIF tag tag is not there - for example because the imported image was not created using APP/APG or because the custom EXIF tag has been lost through post-processing - to warn the user that he/she needs to check that the pano FOV and vertical offset values are set correctly.

If the custom EXIF tag is not found then PT/PTP will guesstimate the pano FOV as follows:

1. If the image is equirectangular then it will set the pano FOV to be 360x180; and it will most often be correct.

2. If the pano image is not equirectangular it will set the HFOV dimension to 360 (or in some instances set the VFOV to 180) and calculate the other dimension based on the aspect ratio of the image; and in many instances the values assigned will be incorrect. If the user corrects one of the values then the software will automatically calculate the other correctly.

Does this answer your question?

Last edited by mediavets (2011-03-31 15:48:46)


Andrew Stephens
Nikon D40, Nikkor 10.5mm fisheye, Sigma 8mm f3.5 fisheye, Nikkor 18-55/50/35mm lenses, Nodal Ninja 5 Lite, Nodal Ninja 4 with R-D16, Agno's MrotatorTCS short.
Nikon P5100, CP5000, CP995, FC-E8, WC-E63,WC-E68, TC-E2, Kaidan Kiwi 995, Bophoto pano bracket, Agno's MrotatorA.
Merlin/Orion robotic pano head + Papywizard on Nokia 770/N800/N810 and Windows 8/XP/2K.

Offline

 

Board footer

Powered by PunBB
© Copyright 2002–2005 Rickard Andersson