Please report any new bugs you find here:
http://sourceforge.net/tracker/?group_id=77506&atid=550441
A few are already known:
http://sourceforge.net/tracker/?group_id=77506&atid=550441&keyword=[layout]
The main new features are:
* Image positions (XYZ parameters).
* Layout mode (see connections between images in the fast
preview)
* Images may have their positions linked differently to their lens
variables. (This doesn't work well yet, as the optimizer
generally fails when there are position linked images.)
The layout mode shows images with the correct centre position, but
otherwise undistorted and scaled down. It connects the images with
straight lines. Clicking lines opens the connected images in the control
point editor.
* A grey line indicates there are no control points, but the image
pair overlaps.
* A green line indicates good alignment.
* A red line indicates poor alignment.
It doesn't work well with bracketed sets yet as the images and their
lines overlap.
Important:
Now trunk Hugin will accept pto files where an image has variables that
link to different other images. For example, you can now link position
variables (yaw, pitch, roll, X, Y, and Z) independently from lens
variables. Previously this was not the case. If you link stacks, you
will be unable to open your pto file in a different version of Hugin
(including 2010.0) without editing it first.
-James
--
You received this message because you are subscribed to the Google Groups "hugin and other free panoramic software" group.
A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ
To post to this group, send email to hugi...@googlegroups.com
To unsubscribe from this group, send email to hugin-ptx+...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx
Using the Hugin Windows SDK I've been able to build recent versions of
Hugin from 0.8 to 2009.2. It has taken me most the day, but I have
been able to build your merged layout model changes from the trunk
(svn 4827) for Windows 32bit using MSVC C++ 9.0 Express Edition.
Comments, don't think these all relate to your changes.
(1) Boost seems to have been increased to version 1.41.0, but the old
version seems to work 1.39.0?
I can't find a pre-compiled version of boost 1.41.0 for Windows, tried
(http://www.boostpro.com/download)
(2) Now I've got it, don't really know what to do with it, I can see
the new layout button on the preview screen and new stack buttons on
the images tab.Are there any instructions/documentation for the layout
model?
(3) The buttons are on the GPU preview screen are too wide, the show
control points button is lost from the window.
(4) Error when calling Autopano.exe
"Could not execute command "<hugin>\files\bin\autopano.exe" /allinone /
path:C:\DOCUME~1\Stephen\LOCALS~1|temp /keys:10 /project:oto /
name:ap_CC.tmp /size:1024 /f "<path>/img1.jpg" "<path>/img2.jpg"
If it helps anyone else I've included my notes from todays effort
below.
Regards
Stephen
Download hugin source and just try exisiting pre-merge MSVC project:
Error in huginbase:
4>..\..\..\hugin\src\hugin_base\panotools\PanoToolsInterface.cpp
(497) : error C2039: 'trans_x' : is not a member of 'correct_Prefs'
Think this means I need latest version of panotools13, downloaded
panotools libpano13-2.9.15_beta3. Could not get cmake to run for this:
CMake Error at C:/Program Files/CMake 2.7/share/cmake-2.7/Modules/
FindPackageHandleStandardArgs.cmake:57 (MESSAGE):
Could NOT find wxWidgets (missing: wxWidgets_FOUND)
Call Stack (most recent call first):
C:/Program Files/CMake 2.7/share/cmake-2.7/Modules/
FindwxWidgets.cmake:782 (FIND_PACKAGE_HANDLE_STANDARD_ARGS)
CMakeLists.txt:50 (FIND_PACKAGE)
Four components of WxWidgets shown as not found.. E.g. wx_dbgrid.
Try using old vc project file in libpano download regardless, remember
to set enviroment variables for wxwidgets and Java SDK, from panotools
wiki: http://wiki.panotools.org/Build_pano12_from_sourcecode_MSVC
Get panotool's windows specific files not in source tarball from
sourceforge.
tools/compat_win32/getopt.h|c
Bogged down in missing external symbols.. then realised that the
actual build configuration I needed was "RELEASE CMD LIB" and these
missing symbols are related to GUI DLL builds.
Have created a static libpano.lib .. needs renaming to pano13.lib?.
Go back and build hugin, I got an error message ">CMake is re-running
because generate.stamp.list is missing."
Looks like I did not understand how cmake works, and trashed my hugin
build.
Could not get Boost options to configure in CMAKE, go back to Boost
1.39.0, now cmake will complete.
Open hugin solution, and build, finally copy various files to get
package to build.
Have a working build of Hugin from the trunk, which includes layout
model, and enblend 4.0
On Dec 23, 8:40 pm, James Legg <lankyle...@gmail.com> wrote:
> I have merged the gsoc2009_layout branch with trunk.
> ...
Not yet, most of the changes are in the backend:
The layout mode lets you view the project as an undirected graph
with links representing control points.
The stack buttons are related to new functionality allowing
different photos to be grouped together by sharing image parameters.
Previously this was only available within the lens number system,
but now it is possible to link positions (roll, pitch & yaw) of
photos - In the future other groupings will be possible such as
sensor response curve or XYZ positions.
>(3) The buttons are on the GPU preview screen are too wide, the show
>control points button is lost from the window.
This is being worked-on, see the discussion from a week or two ago.
>Think this means I need latest version of panotools13, downloaded
>Get panotool's windows specific files not in source tarball from
>sourceforge.
>tools/compat_win32/getopt.h|c
This will be fixed in the next libpano13 beta (which will be soon).
--
Bruno
I'm using boost 1.38, I don't think updating it is necessary.
> (4) Error when calling Autopano.exe
> "Could not execute command "<hugin>\files\bin\autopano.exe" /allinone /
> path:C:\DOCUME~1\Stephen\LOCALS~1|temp /keys:10 /project:oto /
> name:ap_CC.tmp /size:1024 /f "<path>/img1.jpg" "<path>/img2.jpg"
Have you built Autopano and copied the binary to that path? This
shouldn't have changed in the merge.
-James