Re: [hugin-ptx] Hugin 2022.0 Black blotches on final stitches

[Robert Mahar]

Yeah, thats whats forcing me to stick with enblend and "jiggle the handle" 
till the black tiles go away.  This 240 tile project gives 1 - 4 black 
areas every stitch if the images are in order ( right to left / top to 
bottom ).   I was going to dig into this, but I've always had issues 
building enblend from source owing to vigra, but I guess I need to figure 
that out to look under the hood.   FWIW I do see this issue when there is a 
regular overlap in the shooting pattern as there is in this project.  
Unfortunately the tool I'm working on as a substitute for cpfind needs the 
order of the images to be preserved at the moment - once thats fixed 
somehow then I can permute the image order and sidestep this. 
On Monday, November 13, 2023 at 10:21:02 AM UTC-5 bruno...@gmail.com wrote:

> The black shadows are an enblend bug, they don't appear if you use the 
> built-in Hugin blender (which is not as sophisticated as enblend, but is 
> more stable) - Bruno
>

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/430b6057-4fb3-4f29-acb3-9cb3030a1713n%40googlegroups.com.

Re: [hugin-ptx] opencv based CP detector for use with Hugin?

[Robert Mahar]

Looking at the opencv feature detection, the only painful thing will be 
making something that "just works" with stock opencv packages, as the 
feature detection are in 3rd party modules so not normally available if you 
just grab opencv pre-built RPM.   Not so sure how easily sharable such a 
solution would be for average Hugin users if "step one" is build their own 
opencv libraries from source.   But the rest is just a lot of boilerplate 
and it should be easy to wrap it in a way that looks like a typical 
panotools utility.  "cvfind" LOL.

On Thursday, September 7, 2023 at 12:30:46 PM UTC-4 hvd...@gmail.com wrote:

> Yes, it is already there in opencv and works pretty well.
> There are multiple algorithms can do the "control point find" and multiple 
> algorithms like the MergeMertens that can be combined as well.
> And it also contains blending algorithms.
>
> I did some work in Python. Not in C.
>
> Take a look at 
> https://www.opencvhelp.org/tutorials/advanced/panorama-creation/
>
> Harry
>
> Op do 7 sep 2023 om 17:07 schreef Robert Mahar :
>
>> Hi,
>>
>> I've been using Hugin for a decade and for the most part can get it to do 
>> even difficult projects pretty easily.But I have a couple microchip 
>> photography projects for which cpfind either finds no control points or a 
>> pile of extraneous ones.
>>
>> Before I go crazy trying to make a cpfind like tool that speaks .pto 
>> files, and so on, I'm wondering if such a thing already exists to enable 
>> the use of the feature detection / mapping built into opencv.   I cannot 
>> imagine I am the first person on the planet to want to do this.   ( If I m 
>> I guess I should start coding. )
>>
>> -- Bob
>>
>> -- 
>>
> A list of frequently asked questions is available at: 
>> http://wiki.panotools.org/Hugin_FAQ
>> --- 
>> You received this message because you are subscribed to the Google Groups 
>> "hugin and other free panoramic software" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to hugin-ptx+...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/hugin-ptx/6e8fafa1-2884-4bfb-8f5f-ab973b0ba669n%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/hugin-ptx/6e8fafa1-2884-4bfb-8f5f-ab973b0ba669n%40googlegroups.com?utm_medium=email_source=footer>
>> .
>>
>

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/4cb2b439-1879-4c7a-a65b-8822cfef751en%40googlegroups.com.

[hugin-ptx] opencv based CP detector for use with Hugin?

[Robert Mahar]

Hi,

I've been using Hugin for a decade and for the most part can get it to do 
even difficult projects pretty easily.But I have a couple microchip 
photography projects for which cpfind either finds no control points or a 
pile of extraneous ones.

Before I go crazy trying to make a cpfind like tool that speaks .pto files, 
and so on, I'm wondering if such a thing already exists to enable the use 
of the feature detection / mapping built into opencv.   I cannot imagine I 
am the first person on the planet to want to do this.   ( If I m I guess I 
should start coding. )

-- Bob

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/6e8fafa1-2884-4bfb-8f5f-ab973b0ba669n%40googlegroups.com.

Re: [hugin-ptx] libpano13-2.9.22 release candidate rc2

[Robert Clausecker]

Hi Bruno,

The RC builds fine, but there are some warnings you might want to check
out in the future:

/usr/home/ports/fuz.ports/graphics/libpano13/work/libpano13-
2.9.22/bmp.c:313:36: warning: taking the absolute value of unsigned
type 'uint32_t' (aka 'unsigned int') has no effect [-Wabsolute-value] 
im->dataSize = im->bytesPerLine * abs(im->height);
  ^   

/usr/home/ports/fuz.ports/graphics/libpano13/work/libpano13-
2.9.22/file.c:1743:30: warning: result of comparison of con
stant -1 with expression of type 'uint16_t' (aka 'unsigned short') is
always false [-Wtautological-constant-out-of-rang
e-compare]
if( chid[i*5 +k] == -1 )// found an alpha channel 
 ^  ~~

/usr/home/ports/fuz.ports/graphics/libpano13/work/libpano13-
2.9.22/PTcommon.c:528:52: warning: taking the absolute valu
e of unsigned type 'unsigned int' has no effect [-Wabsolute-value]
x_jump = (y==0 || y==TrPtr->src->height || abs(y - TrPtr->src-
>height/2)<=5) ? 1 : TrPtr->src->width/2;
   ^  

/usr/home/ports/fuz.ports/graphics/libpano13/work/libpano13-
2.9.22/resample.c:1265:24: warning: comparison of array 'bu
f' not equal to a null pointer is always true [-Wtautological-pointer-
compare]  
while( !feof(fp) && buf != NULL ) {   
^~~   
/usr/home/ports/fuz.ports/graphics/libpano13/work/libpano13-
2.9.22/resample.c:1481:33: warning: initializing 'char *' with an
expression of type 'unsigned char *' converts between pointers to
integer types where one is of the unique plain
 'char' type and the other is not [-Wpointer-sign]
char*   ptr = &(dest[ coeff ]);   
^ 
/usr/home/ports/fuz.ports/graphics/libpano13/work/libpano13-
2.9.22/resample.c:2465:33: warning: initializing 'char *' w
ith an expression of type 'unsigned char *' converts between pointers
to integer types where one is of the unique plain
 'char' type and the other is not [-Wpointer-sign]
char*   ptr = &(dest[ coeff ]);   
    ^ 

Yours,
Robert Clausecker

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/5bd824a0c41be4eb56f32b575cae7dd0edb3e08f.camel%40gmail.com.

Re: [hugin-ptx] Re: libpano13-2.9.22 release candidate rc1

[Robert Clausecker]

I strongly recommend not changing the function ABIs.  Instead, provide
a new symbol without the extra argument or document tha the argument is
now ignored.

Failing that, bump the soname and make this a major or at least a minor
release so it's clear that this release has an ABI break.  ABI breaks
in patch-level releases are not a good move.

Yours,
Robert Clausecker

Am Samstag, dem 22.07.2023 um 17:33 +0200 schrieb Bruno Postle:
> Thanks, and I am a little ignorant about these details: since no
> known tools actually use these functions, will leaving the soname
> unchanged be a problem for tools that use other parts of the library
> eg. Hugin, nona etc..? My testing seems to be ok.
> 
> We could bump the soname, or we could replace these functions with
> no-op stubs to quieten the abi checkers. What do you think?
> 
> -- 
> Bruno
> 
> On Sat, 22 Jul 2023, 13:36 Andreas Metzler, wrote:
> > On 2023-07-18 Bruno Postle wrote:
> > > libpano13 is the PanoTools library for panoramic imaging.
> > 
> > > A libpano13-2.9.22 rc1 tarball has been uploaded to sourceforge,
> > > this is
> > > a release candidate for testing that may become the final
> > > release:
> > 
> > Hello,
> > 
> > This breaks the ABI:
> > 
> > a)        Removed ShowScript and LaunchAndSendScript function
> > b)
> > -PANO13_IMPEX int       WriteScript                     ( char*
> > res, fullPath* scriptFile, int launch );
> > +PANO13_IMPEX int       WriteScript                     ( char*
> > res, fullPath* scriptFile );
> > 
> > -PANO13_IMPEX void      WriteResults            ( char* script,
> > fullPath *sfile, AlignInfo *g, double ds( int i) , int launch);
> > +PANO13_IMPEX void      WriteResults            ( char* script,
> > fullPath *sfile, AlignInfo *g, double ds( int i) );
> > 
> > 
> > I have not found any users on codesearch.debian.net but still a
> > soname
> > bump is required. This should do the trick:
> > --- libpano13-2.9.22~rc1+dfsg.orig/CMakeLists.txt
> > +++ libpano13-2.9.22~rc1+dfsg/CMakeLists.txt
> > @@ -286,7 +286,7 @@ if(NOT WIN32)
> >    # Create and install shared library on non-windows
> >    add_library(pano13 SHARED ${pano13_hdr} ${pano13_src})
> >    target_link_libraries(pano13 ${_common_libs})
> > -  set_target_properties(pano13 PROPERTIES VERSION "3.0.0"
> > SOVERSION "3")
> > +  set_target_properties(pano13 PROPERTIES VERSION "4.0.0"
> > SOVERSION "4")
> >    install(TARGETS pano13 LIBRARY COMPONENT libraries)
> >    set(_pano_target pano13)
> >    #create and install static library
> > @@ -299,7 +299,7 @@ else()
> >      ADD_DEFINITIONS(-DPANO13_DLL)
> >      add_library(pano13 SHARED ${pano13_hdr} ${pano13_res}
> > ${pano13_src})
> >      target_link_libraries(pano13 ${_common_libs})
> > -    set_target_properties(pano13 PROPERTIES VERSION "3.0.0"
> > SOVERSION "3")
> > +    set_target_properties(pano13 PROPERTIES VERSION "4.0.0"
> > SOVERSION "4")
> >      IF(MINGW)
> >        set_target_properties(pano13 PROPERTIES PREFIX "")
> >      ENDIF()
> > 
> > cu Andreas
> -- 
> A list of frequently asked questions is available at:
> http://wiki.panotools.org/Hugin_FAQ
> --- 
> You received this message because you are subscribed to the Google
> Groups "hugin and other free panoramic software" group.
> To unsubscribe from this group and stop receiving emails from it,
> send an email to hugin-ptx+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/hugin-ptx/CAJV99ZjU4jCd_fbvQC7qY%3DdgXc8pUm311HQ6iw%2BVNidrx%3D1FXQ%40mail.gmail.com
> .

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/8510f4b78507b394ca59026d408ddba6e1cb91db.camel%40gmail.com.

Re: [hugin-ptx] lux image and panorama viewer: version 1.1.5 released

[Robert Clausecker]

Hi Kay,

Am Samstag, dem 11.02.2023 um 12:39 +0100 schrieb 'Kay F. Jahnke' via
hugin and other free panoramic software:
> Am 10.02.23 um 15:50 schrieb Kay F. Jahnke:
> > 
> > You *can* fix it.
> 
> Not convinced? Here's my reasoning: You're build relies on the
> freeBSD 
> highway package. Fulfilling the dependency means that highway will be
> installed in a specific location (e.g. /usr/local). Therefore you
> know 
> that highway is available and accessible, and you don't need the
> CMake 
> code to locate it.

The location of dependencies is configurable when building the port, so
I cannot rely on just /usr/local.  While it is probably possible to
hack something for this, I'm not too keen on messing around with your
already fairly complex build scripts.  Will wait for the next Highway
release (I've already tested with the latest git commit of Highway;
your port works fine with it).

Yours,
Robert Clausecker

> Kay
> 

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/502a1bd1726c1a4dc6b841dbae5bcb8c0f57b753.camel%40gmail.com.

Re: [hugin-ptx] lux image and panorama viewer: version 1.1.5 released

[Robert Clausecker]

Okay, I checked again: the feature you depend on is not part of Google
Highway 1.0.3, which is the newest published version.  Looks like it
went in just a few days after the release. I will therefore not be able
to package lux 1.1.5 until a Google Highway version with this feature
has been released.

I cannot fix this as I'm not going to bundle a second copy of Highway
just to build your package.  We'll have to wait until a new Highway
version is released.  Please avoid depending on unreleased features in
dependencies.  Makes it much harder to actually use your software.

Yours,
Robert Clausecker

Am Freitag, dem 10.02.2023 um 08:09 +0100 schrieb 'Kay F. Jahnke' via
hugin and other free panoramic software:
> Am 09.02.23 um 22:16 schrieb Robert Clausecker:
> 
> > How is this information “deployed” if not by placing a file
> > somewhere?
> > CMake specifically asks for a file to be provided in the error
> > message.
> > Here is the list of files installed for the devel/highway package:
> > 
> > https://cgit.freebsd.org/ports/tree/devel/highway/pkg-plist
> > 
> > Where is this information deployed?  If it is not there, where
> > would it
> > be if it was there?
> 
> The list above does not contain all the files which should be
> deployed 
> on the target machine. If I do a 'make install' on my machine with
> hwy 
> master, it installs these files as well:
> 
> -- Installing: /usr/local/lib/cmake/hwy/hwy-config-version.cmake
> -- Installing: /usr/local/lib/cmake/hwy/hwy-config.cmake
> -- Installing: /usr/local/lib/cmake/hwy/hwy-config-
> relwithdebinfo.cmake
> 
> This is what I mean by 'deploy'. If you like, I can send you the
> files. 
> Maybe you can ask the maintainer of the highway port to look at the 
> matter - I suspect that these three files have to be added to the
> list. 
> When they are present, CMake should find your highway install with 
> CONFIG mode, as it's done in may lux CMakeLists.txt
> 
> > The default location stuff is too fragile.
> 
> I agree, that's why I requested the addition of code to make highway 
> findable with CMake. I'd like to stick with CMake for configuration.
> lux 
> 1.1.4 did rely on the default location, and the patch I proposed to
> you 
> off-list yesterday evening would do just the same. Once the hwy port
> is 
> updated, you can switch back to the unpatched version. I did not mean
> to 
> propose a permanent solution, it's just to get you going with the
> 1.1.5 
> build if the finding-hwy issue can't be resolved otherwise.
> 
> Kay
> 
> 
> 

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/7e116729acd4d37bef202aee231707ef1687ae31.camel%40gmail.com.

Re: [hugin-ptx] lux image and panorama viewer: version 1.1.5 released

[Robert Clausecker]

Am Donnerstag, dem 09.02.2023 um 20:01 +0100 schrieb 'Kay F. Jahnke'
via hugin and other free panoramic software:
> Am 09.02.23 um 19:20 schrieb Robert Clausecker:
> > FreeBSD's package is 1.0.3, which is the most recent version,
> > released 
> > Jan 19.
> > However, it does not ship this file.  Maybe I can just grab it from
> > upstream.
> 
> It's not a file, cmake deploys the necessary information when you do
> a 
> 'make install' on the target machine. The separate find-file was 
> dismissed as superfluous when deploying like that. I think it would
> be 
> easier if you simply patch out the bit in may CMakeLists.txt which
> looks 
> for highway.

How is this information “deployed” if not by placing a file somewhere?
CMake specifically asks for a file to be provided in the error message.
Here is the list of files installed for the devel/highway package:

https://cgit.freebsd.org/ports/tree/devel/highway/pkg-plist

Where is this information deployed?  If it is not there, where would it
be if it was there?

The default location stuff is too fragile.  I would strongly prefer to
avoid having to do that.  Can't you just use pkg-config to find the
highway library?

> Kay


Yours,
Robert Clausecker

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/593605e827f060c0fc399f608033d4141323534d.camel%40gmail.com.

Re: [hugin-ptx] lux image and panorama viewer: version 1.1.5 released

[Robert Clausecker]

FreeBSD's package is 1.0.3, which is the most recent version, released 
Jan 19.
However, it does not ship this file.  Maybe I can just grab it from 
upstream.


Yours,
Robert Clausecker

On 09.02.23 18:40, 'Kay F. Jahnke' via hugin and other free panoramic 
software wrote:

Am 09.02.23 um 18:30 schrieb Robert Clausecker:
One problem I noticed: the configuration fails to find the HWY cmake 
file.


CMake Error at CMakeLists.txt:602 (find_package):
   Could not find a package configuration file provided by "HWY" with 
any of

   the following names:

 HWYConfig.cmake
 hwy-config.cmake



To clarify further: this is the discussion leading to the decision to 
adopt finding with config mode in highway:


https://github.com/google/highway/issues/1084

The code went into their repo as of:

commit 2ea983105e69f0d8daa7b5e8ea1bcf8fb8ecaea3
...
Date:   Tue Jan 17 11:33:20 2023 +0100

    Generate and install a HWYConfig.cmake file

    This will be needed by cmake user consuming HWY.

    Also remove FindHWY.cmake since not needed in a cmake-based
    build tool setup.





--
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups "hugin and other free panoramic software" group.

To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/5912250b-6c41-b0e2-489d-f3d1707a9343%40gmail.com.

Re: [hugin-ptx] lux image and panorama viewer: version 1.1.5 released

[Robert Clausecker]

One problem I noticed: the configuration fails to find the HWY cmake file.

CMake Error at CMakeLists.txt:602 (find_package):
  Could not find a package configuration file provided by "HWY" with any of
  the following names:

    HWYConfig.cmake
    hwy-config.cmake

  Add the installation prefix of "HWY" to CMAKE_PREFIX_PATH or set 
"HWY_DIR"

  to a directory containing one of the above files.  If "HWY" provides a
  separate development package or SDK, be sure it has been installed.


-- Configuring incomplete, errors occurred!

You don't ship this file and neither does FreeBSD's highway package.  
Will check if I can

just grab it from somewhere.

Yours,
Robert Clausecker

On 09.02.23 17:42, 'Kay F. Jahnke' via hugin and other free panoramic 
software wrote:

Am 09.02.23 um 16:49 schrieb Robert Clausecker:

I was planning to update the FreeBSD package today, but noticed that 
you didn't upload the source code for 1.1.5 anywhere.
If this was not intentional, please let me know once you got around 
to do so!


Robert, the master in the repo and the binaries are already 1.1.5 (see 
pv_version.h), but I wanted it to 'hang around' for a little while 
before I assign the 1.1.5 tag, in case anyone notices bugs. I've just 
assigned the tag, does it now work for your build?


Kay



--
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups "hugin and other free panoramic software" group.

To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/0671af4b-5d08-63c3-2134-2acb3ee220f3%40gmail.com.

Re: [hugin-ptx] lux image and panorama viewer: version 1.1.5 released

[Robert Clausecker]

Hi Kay,

I'll check if it works.  The usual convention if you want to have a
version hang out before you make it final is to tag a release candidate
(e.g. 1.1.5-RC1).  Once it is finalised, you tag 1.1.5.  But without a
tag, it is not clear for packagers which commit to base the package on.

I'll let you know when the test build is complete.

Yours,
Robert Clausecker

On 09.02.23 17:42, 'Kay F. Jahnke' via hugin and other free panoramic 
software wrote:

Am 09.02.23 um 16:49 schrieb Robert Clausecker:

I was planning to update the FreeBSD package today, but noticed that 
you didn't upload the source code for 1.1.5 anywhere.
If this was not intentional, please let me know once you got around 
to do so!


Robert, the master in the repo and the binaries are already 1.1.5 (see 
pv_version.h), but I wanted it to 'hang around' for a little while 
before I assign the 1.1.5 tag, in case anyone notices bugs. I've just 
assigned the tag, does it now work for your build?


Kay



--
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups "hugin and other free panoramic software" group.

To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/e2de5a37-5984-725a-f031-9e6b3b2368c9%40gmail.com.

Re: [hugin-ptx] lux image and panorama viewer: version 1.1.5 released

[Robert Clausecker]

Hi Kay,

I was planning to update the FreeBSD package today, but noticed that you 
didn't upload the source code for 1.1.5 anywhere.
If this was not intentional, please let me know once you got around to 
do so!


Yours,
Robert Clausecker

On 05.02.23 21:58, 'Kay F. Jahnke' via hugin and other free panoramic 
software wrote:

Dear all!

I've released lux 1.1.5. Again, most changes are 'behind the scenes', 
but there is important new functionality as well: lux now looks at the 
EXIF metadata of 'ordinary' rectilinear photographs and figures out 
the field of view. With that datum, 'normal' camera images are now 
displayed *with automatic perspective correction*. This is especially 
useful for panorama work: If you take out snapshots from rectilinear 
images, these snapshots will now automatically be geometrically 
correct and can be 'fed back into' a panorama. This is good for, e.g. 
nadir patches. lux will also recognize a range of panoramic images 
made with the 'panorama' function of smartphone camera apps, using a 
heuristic to recognize such images, which typically don't have the 
required metadata and, therefore, were displayed as flat stripes up to 
1.1.4. Introducing such features is, of course, a gamble - there's 
bound to be images where the detection doesn't work or goes wrong, but 
I've tested it with all image types I could get hold of and hope that 
it will work 'most of the time'. Of course you can still override the 
automatics.


Another feature worth mentioning is the .lux.ini file. If you put a 
file with that name (yes, it has a leading dot!) in your home folder, 
lux will look for parameters which it will adopt for the entire 
session, just as if you had passed them on the command line. The 
syntax is simple - in every line, you put one long option name, 
followed by '=' and the intended value, without any white space around 
the '=' sign. This is standard .lux syntax, as described in the 
documentation.


Apart from these new features, a great many small improvements and bug 
fixes should improve the user experience, while the user interface 
hasn't changed very much.


There's good news for Mac users: I was given an intel Mac, and so I 
could now do building and packaging for the mac myself, and I've made 
some progress - I could build a lux 1.1.5 package for intel-based 
Macs. I already mentioned with the release of 1.1.4 that lux can now 
use highway for time-critical rendering code, and this made it 
possible to build a lux version for 'apple silicon', which uses native 
ARM NEON SIMD instructions for speed similar to AVX2 on intel 
machines. A friend has built lux 1.1.5 with this backend on an *M1 
mac* and made a package, which you can find alongside the i86 package 
on my download page:


https://bitbucket.org/kfj/pv/downloads

There are also a windows installer, a ZIP file with a portable windows 
version, a .deb file for ubuntu 20.10 and one for debian11, plus 
updated documentation in HTML format.


The MacOS versions are still not well-integrated with the system, and 
I haven't yet managed to create a 'universal binary' which will run on 
all macs. Finder integration is also largely missing: using 'open with 
lux' on images won't pass the filenames on to lux, so it's best to 
start lux and use it's own file select dialog. When running lux in 
full-screen mode, the file select dialog may be hidden behind lux' 
display - you may have to switch to it's window manually. lux on macs 
will use automatic rendering quality adjustment by default to cope 
with the typically high resolution on macs.


Enjoy!






--
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups "hugin and other free panoramic software" group.

To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/7f554356-3fa9-3404-1e46-6572b3df01f9%40gmail.com.

Re: [hugin-ptx] lux FOSS panorama and image viewer: 1.1.0 pre-release available

[Robert Clausecker]

Hi Kay,

I've now started working on the packaging.

Could you tell me which git commit your prerelease is based on?  I need 
something to work off.
I noticed that your master branch is still on a 2021-12-15 state and 
development seems to be
happening on the associated_alpha branch.  Which branch or commit should I use 
for the packaging?
Ideally you could tag a prerelease so I can directly work off that.

Yours,
Robert Clausecker

Am 28.02.22 um 17:41 schrieb 'Kay F. Jahnke' via hugin and other free panoramic 
software:

Am 28.02.22 um 12:11 schrieb Robert Clausecker:


I am interested in packaging this software for FreeBSD.  Unfortunately,
we already have a package named lux (www/lux) in our Ports collection,
so I cannot name yours lux.  What package name do you think would be
most appropriate?


How about lux-pv? For lux panorama viewer - that's if you're into short package 
names. Or lux-viewer for something longer and less cryptic. But bear in mind 
that what I've uploaded today is just a development snapshot, so bear with me a 
little longer until I release 1.1.0 proper. I just did a lot of internal 
rewiring, so it may take a while to settle. The code is becoming fiendishly 
complex. I hope to see a bit of use and maybe the odd bug report. Just viewing 
images and panoramas should be unproblematic, though, because the changes were 
more to the PTO processing part of the code.

Have you built the code on freeBSD already? I think this shouldn't be too hard, 
with the CMake process and few dependencies. If you have, please let me know - 
it would be the fourth OS running lux! I made the .deb using CMake, maybe it 
can also build packages for freeBSD? By all means, use the clang++ C++ compiler 
- so far it's made a big difference speed-wise. And if you want to recreate 
today's binaries, they are made from the associated_alpha branch, which I 
haven't merged back into master yet.

Keep us posted on how it goes, thanks for your interest in lux!

Kay



--
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups "hugin and other free panoramic software" group.

To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/29e01d1c-2eda-0419-cc01-7ab5feb2e0f8%40gmail.com.

Re: [hugin-ptx] lux FOSS panorama and image viewer: 1.1.0 pre-release available

[Robert Clausecker]

Hi Kay,

Am 28.02.22 um 17:41 schrieb 'Kay F. Jahnke' via hugin and other free panoramic 
software:

Am 28.02.22 um 12:11 schrieb Robert Clausecker:


I am interested in packaging this software for FreeBSD.  Unfortunately,
we already have a package named lux (www/lux) in our Ports collection,
so I cannot name yours lux.  What package name do you think would be
most appropriate?


How about lux-pv? For lux panorama viewer - that's if you're into short package 
names. Or lux-viewer for something longer and less cryptic. But bear in mind 
that what I've uploaded today is just a development snapshot, so bear with me a 
little longer until I release 1.1.0 proper. I just did a lot of internal 
rewiring, so it may take a while to settle. The code is becoming fiendishly 
complex. I hope to see a bit of use and maybe the odd bug report. Just viewing 
images and panoramas should be unproblematic, though, because the changes were 
more to the PTO processing part of the code.


lux-viewer sounds good.  Will try that one.


Have you built the code on freeBSD already? I think this shouldn't be too hard, 
with the CMake process and few dependencies. If you have, please let me know - 
it would be the fourth OS running lux!


I have not made any attempts in this regard, but I want to start in the next 
few days.  If I find any problems, I'll go ahead and report these to you so you 
can maybe add patches in time for the 1.1.0 release.


I made the .deb using CMake, maybe it can also build packages for freeBSD? By 
all means, use the clang++ C++ compiler - so far it's made a big difference 
speed-wise. And if you want to recreate today's binaries, they are made from 
the associated_alpha branch, which I haven't merged back into master yet.


FreeBSD ports are compiled with the system's compiler, which is clang these 
days.  The ports build system is external to the packages and hooks into your 
CMake build scripts, so no changes on your part will be required.  I'll let you 
know once I get something done.


Keep us posted on how it goes, thanks for your interest in lux!

Kay


Yours,
Robert Clausecker

--
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups "hugin and other free panoramic software" group.

To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/ed443cf1-a282-5fde-1fe8-ef280010e4d6%40gmail.com.

Re: [hugin-ptx] lux FOSS panorama and image viewer: 1.1.0 pre-release available

[Robert Clausecker]

Hi!

I am interested in packaging this software for FreeBSD.  Unfortunately,
we already have a package named lux (www/lux) in our Ports collection,
so I cannot name yours lux.  What package name do you think would be
most appropriate?

Yours,
Robert Clausecker

Am Montag, dem 28.02.2022 um 02:54 -0800 schrieb 'kfj' via hugin and
other free panoramic software:
> Dear all!
> It's been a while since I have released new binaries! So today I'm
> offering binaries of a development snapshot which has - roughly - the
> feature level which I intend for lux 1.1.0.
> Development has been intense - I rewrote a lot of code in the
> rendering engine, switching processing to associated alpha RGB pixel
> pipelines, which are better suited to deal with interpolation and
> masking. These code chages did mostly affect the processing of
> synoptic data (stitching, exposure fusions), but 'ordinary' image and
> panorama viewing should also benefit.
> Probably the most important new features are processing of PTO files
> with source image cropping and masks (limited to exclude masks) - and
> processing of panoramas with stacks. My own panoramas make use of
> these features, and I found it frustrating that lux could not handle
> them, so I 'scratched my itch'.
> I hope that this will make lux more useful for the community - give
> it a try, everything is set up to work with sensible defaults. To see
> masked and stacked panoramas on-screen will take a fair while. And
> lux is - as ever - memory-hungry in the default setting, so don't
> overdo the number/size of images in the panoramas. Snapshots are now
> done with the plain 'E' button for screen-sized snapshots and Shift+E
> for 'source-like' snapshots, and will automatically render
> panoramas/exposure fusions for data which are displayed as such, and
> there are more UI changes - I've tried to be conservative, but
> development goes on and the new features have to 'find room' somehow.
> Find a debian package and a windows portable ZIP file here:
> https://bitbucket.org/kfj/pv/downloads/lux-1.1.0-pre.deb
> https://bitbucket.org/kfj/pv/downloads/lux-for-windows-portable-1.1.0-pre.zip
> -- 
> A list of frequently asked questions is available at:
> http://wiki.panotools.org/Hugin_FAQ
> --- 
> You received this message because you are subscribed to the Google
> Groups "hugin and other free panoramic software" group.
> To unsubscribe from this group and stop receiving emails from it,
> send an email to hugin-ptx+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/hugin-ptx/4b723106-07ed-4fe5-87be-f2b54420d5aan%40googlegroups.com
> .

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/45b029240b5be2ac3200e23c16bd3f85df351f40.camel%40gmail.com.

Re: [hugin-ptx] HEADS UP: Don't use gmail! (was: Control Point dialog features)

[Robert Krawitz]

On 2/6/22 20:09, Greg 'groggy' Lehey wrote:
> It seems that Google is going over the top in trying to control spam,
> and in the process it is rejecting valid mail.  I'm seriously
> considering giving up my Gmail account.  If you have a Gmail account,
> you should at least check the spam folder daily to see what surprises
> Gmail has in store for you.

A lot of email services are doing this.  My alma mater uses Outlook Online, and 
about half of my
spam folder was real email (and conversely, a lot of junk email made it 
through).  I finally fixed
this by using fetchmail to inject mail into my own mail server.

A couple of important email messages I sent have also gotten lost.  Junk email 
is a problem, but the
cure (server-side junk filters that cannot be turned off) is worse than the 
disease.

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/9529c519-3c74-075f-bd4b-a802f3d25b85%40alum.mit.edu.

Re: [hugin-ptx] Opinions on warping to fine tune the results of control point optimization?

[Robert Krawitz]

On 1/31/22 11:41, johnfi...@gmail.com wrote:
> The most important use case for this idea would also depend on support for 
> low priority control
> points, which IIUC is in a fork of Hugin that I haven't had time to look at 
> yet.
> 
> Assume that control points are very accurately placed, but still don't 
> optimize very well.  So the
> remapped images don't align very well.  For high contrast areas, anything 
> worse than a single pixel
> of misalignment is a very poor alignment.  The usual Hugin answers to that 
> seem to be based on
> avoiding blending high contrast areas.  Sometimes that is a good solution.  
> Sometimes it isn't.
> 
> One cause of major misalignment is the combination of translation (moving the 
> point of view between
> images, rather than using a tripod with a perfectly adjusted nodal slide) 
> with subjects of the photo
> being at significantly varying distance.

That happens to me a lot because of my shooting style.  Any time I see an 
interesting scene I'll
shoot a pano sequence, and it's almost always hand held, much less a pano head 
(which I don't even
have).  And to make matters more fun, there's often both near-field and distant 
objects.

> The translation optimization necessarily depends on all connections between 
> two images (including
> indirect connections through other images) being at the same distance from 
> the camera.  For multiple
> subject distances, there is no correct remapping for translation.

My way of dealing with that is to shoot lots of extra shots, throw out all of 
the near field control
points, and then use masks to ensure to the degree possible that only one frame 
will contain the
offending (close) object.  When I can't do that, I either have to accept the 
problem, crop the
panorama down, or not use it.  It's a somewhat tedious process, because I have 
to build it many
times, but usually I manage to get something clean enough.  I have on occasion 
resorted to manually
warping the result in GIMP, which is really tedious.

> Assume either user action (or maybe some automation I haven't though of) 
> lowers the priority of all
> control points that connect two images at other than the most important 
> subject distance.  Then the
> alignment for that distance is great, but other distances are a problem.
> 
> If high contrast important features at other than the preferred distance are 
> continuous beyond the
> width of an image, there is no decent solution:  warping would distort the 
> shape, while any other
> approach would blur the seams.

I'd have to see examples of what the distortion would look like.

> Some reshaping is fundamentally necessary for that combination of viewpoint 
> shift plus
> multi-distance.  Blurring across a seam can concentrate the reshaping where 
> it matters least.  But
> in many cases I think warping would do a better job with less user effort.

If I understand what you're saying, yes.

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/c2c73353-f787-b82c-aa7e-7c75a9073a06%40alum.mit.edu.

Re: [hugin-ptx] Re: Unit tests fail with libpano13-2.9.21_rc2

[Robert Clausecker]

Hi Bruno,

I can confirm that the tests pass on armv7 and arm64 FreeBSD 13, too.

Yours,
Robert Clausecker

Am Mittwoch, dem 15.12.2021 um 00:30 + schrieb Bruno Postle:
> Tests pass ok on Linux arm7, i386, x86_64, arm64 with this latest
> change.
> 
> -- 
> Bruno
> 
> On Mon, 13 Dec 2021 at 16:28, T. Modes wrote:
> > 
> > Thanks, I committed the necessary changes.
> 

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/aec17c40865f51b68a911aee766e75b5970c3e70.camel%40gmail.com.

[hugin-ptx] Re: Unit tests fail with libpano13-2.9.21_rc2

[Robert Clausecker]

Hello,

The architectures I tested were armv7 and arm64 on FreeBSD 13.  The 
compiler is clang 11.0.1.
FreeBSD defines _BYTE_ORDER but not __BYTE_ORDER.  Likewise, it defines 
_BIG_ENDIAN but not __BIG_ENDIAN.
You should be able to make your code work with something like this:

#if defined(_BYTE_ORDER) && !defined(__BYTE_ORDER)
# define __BYTE_ORDER _BYTE_ORDER
#endif

I recommend patching the endianess detection code so it checks for the 
presence of the macros you want to test
in addition to using them (the C preprocessors substitutes 0 for undefined 
macros).  For example, try this:

#if !defined(__BYTE_ORDER) || !defined(__BIG_ENDIAN)
# error cannot determine byte order
#endif

Also consider checking both for big and little endian instead of just 
assuming little endian if the big endian case does not apply.
This makes the code robust against architectures where the byte order is 
neither big nor little endian.

Also consider writing endian agnostic code instead of having separate code 
paths for both endianesses.  This also has
the effect of making the code compliant with the strict aliasing rule which 
your code does not seem to be.  For example,
you can use functions like these for accessing fields in files with a 
defined endianess without having to make assumptions
about the endianess of the architecture you are programming for:

https://github.com/clausecker/memf/blob/master/src/fiddle.h

This implementation compiles to reasonable code with modern gcc and clang 
and allows you to completely avoid
having to detect and deal with host endianess.

Yours,
Robert Clausecker

T. Modes schrieb am Donnerstag, 9. Dezember 2021 um 17:39:12 UTC+1:

> fuz... schrieb am Dienstag, 7. Dezember 2021 um 00:34:10 UTC+1:
>
>> Greetings! 
>>
>> While preparing the FreeBSD port for libpano13 in preparation of the 
>> upcoming 2.9.21 release, I noticed that the unit tests fail. 
>
>
> On which architecture, which compiler? Where there warning during 
> compiling?
>
> Between 2.9.21 rc1 and rc2 there were code added to automatically deduce 
> the endianess of the system to fix test failures on different architectures.
> After searching the internet there were already special code added for 
> FreeBSD in panorama.h:
> #if defined(__GNUC__) && !defined(__MINGW32__)
> #if defined(__FreeBSD__)
> #include 
> #else
> #include 
> #endif
>
> Could you check if sys/endian.h (or files included from there) defines 
> __BYTE_ORDER  
> and __BIG_ENDIAN.
> If not, are they defined in machine/endian.h?
>
> TIA
>

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/e9511f7a-82d8-4731-bc37-12cd1d7c8682n%40googlegroups.com.

[hugin-ptx] Unit tests fail with libpano13-2.9.21_rc2

[Robert Clausecker]

Greetings!

While preparing the FreeBSD port for libpano13 in preparation of the
upcoming 2.9.21 release, I noticed that the unit tests fail.  This is
regardless of whether suitesparse is used or not.  This is a regression
from 2.9.21_rc1 were all unit tests still passed.  Please fix the unit
tests or the code before making the final release.

Yours,
Robert Clausecker

Test project /usr/home/fuz.ports/graphics/libpano13/work/.build
Start 1: simpleStitch
1/8 Test #1: simpleStitch    Passed0.74 sec
Start 2: simpleTiff16
2/8 Test #2: simpleTiff16    Passed1.12 sec
Start 3: simpleTiff2psd-1-layer
3/8 Test #3: simpleTiff2psd-1-layer ..***Failed0.12 sec
Start 4: simpleTiff2psd-2-layers
4/8 Test #4: simpleTiff2psd-2-layers .***Failed0.12 sec
Start 5: simpleTiff2psd-1-layer-uncropped
5/8 Test #5: simpleTiff2psd-1-layer-uncropped ***Failed0.13 sec
Start 6: simpleTiff2psd-2-layers-uncropped
6/8 Test #6: simpleTiff2psd-2-layers-uncropped ...***Failed0.13 sec
Start 7: simpleTiff16-16bit-1-layer
7/8 Test #7: simpleTiff16-16bit-1-layer ..***Failed0.13 sec
Start 8: simpleTiff16-16bit-2-layers
8/8 Test #8: simpleTiff16-16bit-2-layers .***Failed0.13 sec

25% tests passed, 6 tests failed out of 8

Total Test time (real) =   2.64 sec

The following tests FAILED:
  3 - simpleTiff2psd-1-layer (Failed)
  4 - simpleTiff2psd-2-layers (Failed)
  5 - simpleTiff2psd-1-layer-uncropped (Failed)
  6 - simpleTiff2psd-2-layers-uncropped (Failed)
  7 - simpleTiff16-16bit-1-layer (Failed)
  8 - simpleTiff16-16bit-2-layers (Failed)

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/a095f172641ea6f6f4de99010effcb280cec4383.camel%40gmail.com.

Re: [hugin-ptx] libpano13-2.9.20 unit tests fail on FreeBSD

[Robert Clausecker]

Hi Bruno,

Thanks for the quick response.  We'll go ahead and update the port without 
worrying too much about the failed unit tests.

Yours,
Robert Clausecker

bruno...@gmail.com schrieb am Sonntag, 12. September 2021 um 22:59:02 UTC+2:

> The tests seem to have been broken since this commit, which suggests a
> problem with the test suite:
>
> changeset: 844:d71285db01f0
> user: tmodes 
> date: Thu Sep 06 17:45:24 2018 +0200
> files: version.h
> description: Bump up some more version numbers
>
> diff -r 415deb81168f -r d71285db01f0 version.h
> --- a/version.h Sun Mar 25 10:45:16 2018 +0100
> +++ b/version.h Thu Sep 06 17:45:24 2018 +0200
> @@ -31,13 +31,13 @@
> #define VERS2 0x00
>
> //version of preferences file, used to verify data
> -#define PREF_VERSION "2.9.19 "
> +#define PREF_VERSION "2.9.20 "
>
> // String style of global version
> -#define VERSION "2.9.19 "
> +#define VERSION "2.9.20 "
>
> // Numeric style of global version, same as VERSION with more precision
> -#define PTVERSION_FILEVERSIONNUMBER 2,9,19,0
> +#define PTVERSION_FILEVERSIONNUMBER 2,9,20,0
> #define PTVERSION_NAME_LONG "LongVersion"
> #define LONGVERSION VERSION ", Copyright (c) 1998-2006, H. Dersch,
> d...@fh-furtwangen.de"
>
>
> On Sun, 12 Sept 2021 at 19:57, Robert Clausecker  wrote:
> >
> > While working on updating the FreeBSD port for graphics/libpano13 to 
> 2.9.20 (cf. FreeBSD PR #258354), FreeBSD contributor Daniel Engbert 
> encountered a series of unit test failures. After converting from TIFF to 
> PSD, the image files no longer match the reference files. Full test logs 
> can be found in this paste: https://paste.debian.net/1211512/
> >
> > Are these test failures known or benign? If not, please let us know what 
> we can do to help you debug the issue further.
>

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/accbfad0-751a-4639-b78c-36182fab4820n%40googlegroups.com.

[hugin-ptx] libpano13-2.9.20 unit tests fail on FreeBSD

[Robert Clausecker]

While working on updating the FreeBSD port for graphics/libpano13 to 2.9.20 
(cf. FreeBSD PR #258354), FreeBSD contributor Daniel Engbert encountered a 
series of unit test failures.  After converting from TIFF to PSD, the image 
files no longer match the reference files.  Full test logs can be found in 
this paste: https://paste.debian.net/1211512/

Are these test failures known or benign?  If not, please let us know what 
we can do to help you debug the issue further.

Yours,
Robert Clausecker

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/557aff93-e9d4-4f65-83be-9488dc6f363an%40googlegroups.com.

Re: [hugin-ptx] Trying to use Hugin, and...

[Robert Krawitz]

On 2/8/21 8:13 AM, Monkey wrote:
> 
> Thanks for trying. That is about as good as I would have expected from the 
> input images. I had
> another go myself, starting from scratch and placing the images manually 
> before running optimise.
> 
> Once I'd run optimise, however, the images weren't displaying properly in the 
> preview again. Does
> anyone know why this happens? Is it an OpenGL problem?

They display properly in the "slow" preview (I've seen this for years).  It 
only seems to happen (to
me, at least) stitching images using a very wide angle lens; using a normal or 
moderately wide lens,
even with a very wide panorama, is fine.

> Some images turn into jagged strips, some don't appear at all (they do appear 
> in the little "sphere"
> preview to the left).

Yup, same symptoms.  It makes fine grained control over output challenging.

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/78ceb365-1b72-8e3f-6323-bb2e83047f18%40alum.mit.edu.

[hugin-ptx] Re: Hole in panorama

[Robert Simpson]

I don't have any masks set. I tried Enblend but no difference.

On Friday, May 1, 2020 at 8:59:55 AM UTC+1, Monkey wrote:
>
> I think it's either a stitching problem or you've inadvertently masked out 
> that section of the image. Switch from enlblend to built-in or vice versa, 
> or check the Masks tab.
>

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/e2214fa1-06d0-4a55-88e0-44d649e17685%40googlegroups.com.

Re: [hugin-ptx] Hole in panorama

[Robert Simpson]

I think that's a comparator rather than an op-amp. Yes, there is a missing 
sliver but I think it's very thin. I had to manally add the control points. 
I don't understand how any of this results in a chunk of the original 
images being removed.

On Friday, May 1, 2020 at 2:32:00 AM UTC+1, aks wrote:
>
> Others might explain the best Hugin procedure to stitch these and also 
> explain why you have that void but you are missing a sliver between the 2nd 
> and 3rd images. That missing sliver contains how the feedback circuit, if 
> any, is accomplished at the op amp that is partially shown in the 3rd 
> image. It looks like you need another image to fill in that missing 
> information. 
>
> On Apr 30, 2020, at 3:46 PM, Robert Simpson  > wrote:
>
> I'm attempting to stitch some scans of a schematic. The scans are quite 
> poor quality and have some distortions. I have no idea what was used to 
> make them.
>
> I manually added control points and stitched them but the resulting image 
> has a chunk missing. See attached images. Any ideas on how to fix it?
>
> Thanks,
>
> Rob.
>
>
> -- 
> A list of frequently asked questions is available at: 
> http://wiki.panotools.org/Hugin_FAQ
> --- 
> You received this message because you are subscribed to the Google Groups 
> "hugin and other free panoramic software" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to hugi...@googlegroups.com .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/hugin-ptx/c6f91fa9-a8f4-430d-923f-f00389eab9b1%40googlegroups.com
>  
> <https://groups.google.com/d/msgid/hugin-ptx/c6f91fa9-a8f4-430d-923f-f00389eab9b1%40googlegroups.com?utm_medium=email_source=footer>
> .
> 
>
>
>

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/6d2c4c6d-60e7-4242-a095-bccb4bab4ab6%40googlegroups.com.

Re: [hugin-ptx] assistance needed: Hugin w/ 12mm lens on a mirrorless camera

[Robert Krawitz]

On Sat, 2 Feb 2019 04:57:38 -0800 (PST), Bob Hanson wrote:
> I am a semi-professional photographer based in Chicago who is having a 
> difficult time getting my photos to stick together properly, with a visible 
> seam or two in my photos. I've tried many times to adjust the parallax point 
> on my nodal ninja and no matter what I do, I cannot make a photo without a 
> seam. I do a fair amount of traveling to NY/NJ/TX/WI/MN/GA/MO/TN, as well as 
> up to Toronto, Ottawa and Montreal. 
>
> I am looking for someone who can meet me at a *public* place and help 
> validate my settings, as well as that I am using the software correctly. My 
> issue is one or both of these problems. When I see seams in Hugin, I try to 
> add control points but it doesn't seem to do anything. I am willing to pay 
> for this service; I just need help.
>
> Look at the triangle window and the ceiling in the attached file and you'll 
> see what I mean. Please help. 

I'm not in Chicago...but...

The right hand triangular window shows a seam, but it doesn't look so
much like alignment problems as it does focus or problems near the
edge of the lens.  The triangular window on the left does show
alignment errors, as does the ceiling to the right of that window and
the ceiling fan and the chair below it.

How much overlap did you use between images?  My experience with
panoramas with close-in elements (where even small parallax errors are
problematic) is that the more overlap the better.  I'd estimate that
it's not uncommon to have 80% overlap between the frames I use.  The
more overlap, the less effect any residual parallax errors or lens
distortion will have.  It does mean that processing will take longer,
but I've found (after doing a few hundred of them over the years) that
it does help reduce stitch errors.

Finally, with control points, I find it works best to delete control
points that are close by and try to get ones on the most distant
objects in the scene.  Any parallax errors will be magnified close in,
and if you force Hugin to map image based on those, everything else
will be off.  And similarly, I avoid using control points close to the
edge/corners of the frame, because lens distortions beyond what Hugin
can correct for will similarly introduce errors.

I seldom use a tripod, and don't have a panorama head (I normally
shoot panoramas outdoors, but not necessarily only distant
landscapes), but I can uusually get a good stitch.

Also, if you haven't already done so, you might want to try using
multiblend rather than enblend.
-- 
Robert Krawitz 

***  MIT Engineers   A Proud Tradition   http://mitathletics.com  ***
Member of the League for Programming Freedom  --  http://ProgFree.org
Project lead for Gutenprint   --http://gimp-print.sourceforge.net

"Linux doesn't dictate how I work, I dictate how Linux works."
--Eric Crampton

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/20190202154117.1512D1418D3%40localhost.
For more options, visit https://groups.google.com/d/optout.

[hugin-ptx] Distortion with very wide angle lenses

[Robert Krawitz]

Reference original image, taken with an 8 mm lens on a 1.6x crop body
(Sigma 8-16 on Canon 7DmkII) [1]

I should note that initially everything is fine -- the mapped photos
look reasonable.  However, at some point during the optimization
process, and I have not managed to track down when, the below behavior
manifests itself if I'm using a very wide angle lens.  I tried to
reproduce it from scratch, but wasn't successful -- I didn't find the
exact point at which things went off the rails.

It appears that Hugin is cutting off the corners of the frame [2].
I'm presuming that that's to avoid severe distortion, which is
nevertheless still visible near said corners.  When Nona remaps the
images, that corner distortion is still present.  Enblend seems to be
able to avoid using those areas [3], but multiblend (which is
otherwise preferable for the most part) doesn't [4].

I also note -- and I've mentioned this previously, in 2014 [5] -- that
the OpenGL preview shows some really weird errors [6], which the slow
preview doesn't [2].  However, in 2014 the corners were not cut off [7].

[1] https://rlk.smugmug.com/Photography/Hugin-demo/n-NbPQS/i-24vkc6v

[2] https://rlk.smugmug.com/Photography/Hugin-demo/n-NbPQS/i-Tz5fLgw

[3] https://rlk.smugmug.com/Photography/Hugin-demo/n-NbPQS/i-zbWZbTC

[4] https://rlk.smugmug.com/Photography/Hugin-demo/n-NbPQS/i-tzdPc87

[5] https://rlk.smugmug.com/Photography/Hugin-demo/n-NbPQS/i-vSbVSWP

[6] https://rlk.smugmug.com/Photography/Hugin-demo/n-NbPQS/i-SG9bZrM

[7] https://rlk.smugmug.com/Photography/Hugin-demo/n-NbPQS/i-tmdKB7J

-- 
Robert Krawitz 

***  MIT Engineers   A Proud Tradition   http://mitathletics.com  ***
Member of the League for Programming Freedom  --  http://ProgFree.org
Project lead for Gutenprint   --http://gimp-print.sourceforge.net

"Linux doesn't dictate how I work, I dictate how Linux works."
--Eric Crampton

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/20180927144036.108E71433A3%40localhost.
For more options, visit https://groups.google.com/d/optout.

Re: [hugin-ptx] Re: RAW support with hugin ?

[Robert Krawitz]

On Thu, 12 Jul 2018 06:57:26 -0700, Albert Szostkiewicz wrote:
>> PTGui uses only a fraction of that possibilities. I'd never shoot raw
>> only for PTGui's raw import. It's not worth the hassle at all.
>
> What is your suggested workflow then ?

To be clear, you're using PTGui not merely to develop the raw images,
but also to stitch/fuse them, correct?

> On Thu, Jul 12, 2018 at 12:18 AM Erik Krause  wrote:
>
>> Am 12.07.2018 um 08:46 schrieb Albert Szostkiewicz:
>> > I know that PTGui is using dcraw, and there is nothing wrong with it. It
>> is
>> > also not true that dcraw will strip all dynamic range data. You can check
>> > its possibilities here (https://www.cybercom.net/~dcoffin/dcraw/)
>>
>> PTGui uses only a fraction of that possibilities. I'd never shoot raw
>> only for PTGui's raw import. It's not worth the hassle at all.

-- 
Robert Krawitz 

***  MIT Engineers   A Proud Tradition   http://mitathletics.com  ***
Member of the League for Programming Freedom  --  http://ProgFree.org
Project lead for Gutenprint   --http://gimp-print.sourceforge.net

"Linux doesn't dictate how I work, I dictate how Linux works."
--Eric Crampton

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/20180712145744.239FC1431FD%40localhost.
For more options, visit https://groups.google.com/d/optout.

Re: [hugin-ptx] Re: RAW support with hugin ?

[Robert Krawitz]

On Wed, 11 Jul 2018 14:15:19 +1000, Greg 'groggy' Lehey wrote:
> On Tuesday, 10 July 2018 at  8:10:08 -0700, Albert Szostkiewicz wrote:
>> As much as I wish to stay with Linux (which is my main operating
>> system) and Hougin Open software, currently I am forced to run PtGui
>> via wine to do my job as expected.
>
> Note that the Unix (and thus Linux) way is to have multiple programs,
> each able to perform one function and perform it well.  It looks like
> you're looking for the opposite.

The "UNIX/Linux way" also allows for scripts and other ways to combine
separate tools into one from the user perspective.  If I have a
complex pipeline of operations I want to perform I don't have to
remember them and run them all by hand; I can use a script to do that
for me.  And indeed if I look in /usr/bin, about 25% of the programs
there are in fact scripts -- programs that hide the fact that they are
actually multiple programs being combined.

>> It streamlines simple work that has to be done without requirement
>> of 3rd party software in the process.
>
> It still requires mouse pushing.  If you're looking for automatic raw
> conversions, you can do that too with UFRaw, which has a batch mode.
> Read in your images, run ufraw-batch on them to produce TIFF output
> files, and you're ready to go.

One less step, though.  Other than the work required (which may be
non-trivial, balanced against the fact that the Hugin developers have
other things they want to do, not to mention lives outside of Hugin),
there's no reason Hugin couldn't do the same thing.

> Just checked https://www.ptgui.com/features.html: yes, PTGui uses
> dcraw to convert the images.  That's the same program that's behind
> UFRaw.  The difference with Linux is that you have a choice of raw
> conversion tools, and that's one of the main reasons for using raw
> images in the first place.

False dichotomy; there's nothing preventing someone from using a
separate tool to convert the RAWs into TIFFs or JPEGs and invoking
PTGui on those.
-- 
Robert Krawitz 

***  MIT Engineers   A Proud Tradition   http://mitathletics.com  ***
Member of the League for Programming Freedom  --  http://ProgFree.org
Project lead for Gutenprint   --http://gimp-print.sourceforge.net

"Linux doesn't dictate how I work, I dictate how Linux works."
--Eric Crampton

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/20180711122920.5777414351E%40localhost.
For more options, visit https://groups.google.com/d/optout.

Re: [hugin-ptx] Re: Adding new lenses to the lensfun database and implementing other users requests

[Robert Lounsberry]

thank you

On Tue, Jun 12, 2018 at 11:52 AM, Alex M  wrote:

> Robert, the lensfun email list is hosted on sourceforge.
> lensfun-us...@lists.sourceforge.net
> https://sourceforge.net/p/lensfun/mailman/lensfun-users/
>
> Thanks,
> Alex
>
> On 06/12/2018 07:12 AM, Robert Lounsberry wrote:
> > Thank you. I've emailed him a week or so ago but didn't hear back so I
> > posted here. I've emailed him again today.
> >
> > On Tue, Jun 12, 2018 at 9:58 AM, zarl  wrote:
> >
> >> Hi Robert,
> >>
> >> hugin doesn't use lensfun for some time, see the changes section in
> >> http://hugin.sourceforge.net/releases/2015.0.0/en.shtml
> >>
> >> First of all, did you try to contact Torsten Bronger? I think contact
> >> information should be available here: http://wilson.bronger.org/
> >> calibration
> >>
> >> You mentioned a user request repositor. Did you try the "bug reports"
> link
> >> on http://lensfun.sourceforge.net/ ?
> >>
> >> Also I think darktable.org <https://www.darktable.org/> uses lensfun so
> >> maybe you can contact darktable's user and developer community.
> >>
> >> I hope that helps,
> >> Carl
> >>
> >> Am Freitag, 8. Juni 2018 17:17:30 UTC+2 schrieb Robert Lounsberry:
> >>>
> >>> This seems to be the only Google group where lensfun is discussed.. If
> >>> not please point me to the right place.
> >>>
> >>> I have submitted several corrections and would like to get access to
> the
> >>> user request repository so I can work on corrections for the submitted
> RAW
> >>> images.
> >>>
> >>> How do I go about getting my stuff in the development versions even if
> I
> >>> have to do it myself? And how can I gain access to the submitted RAW
> files
> >>> so I can work on some distortions in my spare time?
> >>>
> >> --
> >> A list of frequently asked questions is available at:
> >> http://wiki.panotools.org/Hugin_FAQ
> >> ---
> >> You received this message because you are subscribed to the Google
> Groups
> >> "hugin and other free panoramic software" group.
> >> To unsubscribe from this group and stop receiving emails from it, send
> an
> >> email to hugin-ptx+unsubscr...@googlegroups.com.
> >> To view this discussion on the web visit https://groups.google.com/d/
> >> msgid/hugin-ptx/d3e73d61-6fd9-4901-8151-79e6093195ef%40googlegroups.com
> >> <https://groups.google.com/d/msgid/hugin-ptx/d3e73d61-6fd9-
> 4901-8151-79e6093195ef%40googlegroups.com?utm_medium=
> email_source=footer>
> >> .
> >>
> >> For more options, visit https://groups.google.com/d/optout.
> >>
> >
>
>

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/CAK65kiGe2p2o%3Df-ciC%2B%2Bu03RSFVMbbsPF-Cm65rayYNKf5JD3Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [hugin-ptx] Re: Lens correction with Hugin

[Robert Lounsberry]

I'm really comfortable making corrections with horizontal lines. Based on
Torsten's tutorial I translated to the new version of Hugin and where the
image jumps after you make a control point. In a horizontal image you just
know that you can click on both sides of the image just at the inside edges
and continue. That's where he says "you can just turn your brain off" in
the tutorial video. In an image where the subject is vertical or angled
lines, I'm not sure how that would work. The corrections I get from
multiple horizontal lines seem to work fine for everything, but I want to
understand how to use vertical or oblique lines.

Torsten, I emailed you a couple times. I'm looking to contribute by making
corrections for user submissions.

Thanks everyone for the assistance.

On Thu, May 17, 2018 at 5:13 PM, Frederic Da Vitoria 
wrote:

> 2018-05-17 22:45 GMT+02:00 Robert Lounsberry :
>
>> I was asking that if I had to also use vertical lines, how would I line
>> them up on top of each other like two portrait orientation images and match
>> a vertical line top to bottom. Since I don't have to use vertical lines and
>> can use only horizontal lines then it's a moot question. I just wasn't sure
>> how to, if I had to. Thank you.
>>
>> On Thu, May 17, 2018 at 4:38 PM, Torsten Bronger <
>> bron...@physik.rwth-aachen.de> wrote:
>>
>>> Hallöchen!
>>>
>>> Robert Lounsberry writes:
>>>
>>> > Just to make sure I understand correctly, you don't need to do
>>> > both vertical and horizontal lines to create a proper lens
>>> > distortion correction. You only need to use horizontal
>>> > linesright?
>>>
>>> Yes, because they are longer usually.
>>>
>>> > And if you do need to do vertical lines, how would you line them
>>> > up in Hugin since they wouldn't be touching like in horizontal
>>> > test images.
>>>
>>> I don't understand this.  You need to do vertical lines becasue you
>>> have a test image in portrait mode?  Or because the subject only had
>>> vertical lines?
>>>
>>> Tschö,
>>> Torsten.
>>>
>>> --
>>> Torsten Bronger
>>>
>>
> I may be wrong, but I believe you shouldn't set lines as horizontal or
> vertical in Hugin for calibration. Just declare them as "normal" lines, no
> matter if they are actually vertical or horizontal. I guess it could help
> calibration if you find vertical lines as well as horizontal. For that
> matter, you could use oblique lines too.
>
> --
> Frederic Da Vitoria
> (davitof)
>
> Membre de l'April - « promouvoir et défendre le logiciel libre » -
> http://www.april.org
>
> --
> A list of frequently asked questions is available at:
> http://wiki.panotools.org/Hugin_FAQ
> ---
> You received this message because you are subscribed to the Google Groups
> "hugin and other free panoramic software" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to hugin-ptx+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/hugin-ptx/CANe_y9STba_H_EOAZb%2BC%2B2KCyo%2Bb4inY8WhLe3D9pLTebPhzVA%
> 40mail.gmail.com
> <https://groups.google.com/d/msgid/hugin-ptx/CANe_y9STba_H_EOAZb%2BC%2B2KCyo%2Bb4inY8WhLe3D9pLTebPhzVA%40mail.gmail.com?utm_medium=email_source=footer>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/CAK65kiH_csevU15w-dJ4BSNdccH5x%2BfrJpJ_h3isQz3AN%2BsCVw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [hugin-ptx] Re: Adding new lenses to the lensfun database and implementing other users requests

[Robert Lounsberry]

Thank you. I've emailed him a week or so ago but didn't hear back so I
posted here. I've emailed him again today.

On Tue, Jun 12, 2018 at 9:58 AM, zarl  wrote:

> Hi Robert,
>
> hugin doesn't use lensfun for some time, see the changes section in
> http://hugin.sourceforge.net/releases/2015.0.0/en.shtml
>
> First of all, did you try to contact Torsten Bronger? I think contact
> information should be available here: http://wilson.bronger.org/
> calibration
>
> You mentioned a user request repositor. Did you try the "bug reports" link
> on http://lensfun.sourceforge.net/ ?
>
> Also I think darktable.org <https://www.darktable.org/> uses lensfun so
> maybe you can contact darktable's user and developer community.
>
> I hope that helps,
> Carl
>
> Am Freitag, 8. Juni 2018 17:17:30 UTC+2 schrieb Robert Lounsberry:
>>
>> This seems to be the only Google group where lensfun is discussed.. If
>> not please point me to the right place.
>>
>> I have submitted several corrections and would like to get access to the
>> user request repository so I can work on corrections for the submitted RAW
>> images.
>>
>> How do I go about getting my stuff in the development versions even if I
>> have to do it myself? And how can I gain access to the submitted RAW files
>> so I can work on some distortions in my spare time?
>>
> --
> A list of frequently asked questions is available at:
> http://wiki.panotools.org/Hugin_FAQ
> ---
> You received this message because you are subscribed to the Google Groups
> "hugin and other free panoramic software" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to hugin-ptx+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/hugin-ptx/d3e73d61-6fd9-4901-8151-79e6093195ef%40googlegroups.com
> <https://groups.google.com/d/msgid/hugin-ptx/d3e73d61-6fd9-4901-8151-79e6093195ef%40googlegroups.com?utm_medium=email_source=footer>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/CAK65kiGHo_LFqqAg%3DmXdMtQ%2BgPR75xhkG57VLo%3DbHSDMH3GVJw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[hugin-ptx] Adding new lenses to the lensfun database and implementing other users requests

[Robert Lounsberry]

This seems to be the only Google group where lensfun is discussed.. If not 
please point me to the right place. 

I have submitted several corrections and would like to get access to the 
user request repository so I can work on corrections for the submitted RAW 
images. 

How do I go about getting my stuff in the development versions even if I 
have to do it myself? And how can I gain access to the submitted RAW files 
so I can work on some distortions in my spare time?

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/f2519727-c40d-4381-9603-6ba8e71726eb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[hugin-ptx] New tutorial for Lensfun distortion calibration

[Robert Lounsberry]

Recently I had to translate from the old to the new version of Hugin. 
Having never use the old one I had to figure it out without that knowledge. 
I was wondering how useful people would find a new updated tutorial for the 
latest version of Hugin, for those that want to do lens distortion 
correction? I was thinking about making one but only if you think it might 
be useful...or is there one already out there that I couldn't ever find. 

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/912b0f5a-10a0-4f61-a916-da92700b0f15%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [hugin-ptx] Re: Lens correction with Hugin

[Robert Lounsberry]

I was asking that if I had to also use vertical lines, how would I line
them up on top of each other like two portrait orientation images and match
a vertical line top to bottom. Since I don't have to use vertical lines and
can use only horizontal lines then it's a moot question. I just wasn't sure
how to, if I had to. Thank you.

On Thu, May 17, 2018 at 4:38 PM, Torsten Bronger <
bron...@physik.rwth-aachen.de> wrote:

> Hallöchen!
>
> Robert Lounsberry writes:
>
> > Just to make sure I understand correctly, you don't need to do
> > both vertical and horizontal lines to create a proper lens
> > distortion correction. You only need to use horizontal
> > linesright?
>
> Yes, because they are longer usually.
>
> > And if you do need to do vertical lines, how would you line them
> > up in Hugin since they wouldn't be touching like in horizontal
> > test images.
>
> I don't understand this.  You need to do vertical lines becasue you
> have a test image in portrait mode?  Or because the subject only had
> vertical lines?
>
> Tschö,
> Torsten.
>
> --
> Torsten Bronger
>
> --
> A list of frequently asked questions is available at:
> http://wiki.panotools.org/Hugin_FAQ
> ---
> You received this message because you are subscribed to the Google Groups
> "hugin and other free panoramic software" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to hugin-ptx+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/hugin-ptx/87y3gi9fw6.fsf%40wilson.bronger.org.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/CAK65kiH6jq%3Dc_b-3-odJ0Qhj0a8FpBehrndPZ6eOr_kSbvdYAw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[hugin-ptx] Re: Lens correction with Hugin

[Robert Lounsberry]

Just to make sure I understand correctly, you don't need to do both 
vertical and horizontal lines to create a proper lens distortion 
correction. You only need to use horizontal linesright? And if you do 
need to do vertical lines, how would you line them up in Hugin since they 
wouldn't be touching like in horizontal test images. 

On Wednesday, May 16, 2018 at 4:11:15 PM UTC-4, Torsten Bronger wrote:
>
> Hallöchen! 
>
> Robert Lounsberry writes: 
>
> > [...] Is that a realistic goal? To be able to get close to those 
> > numbers? 
>
> Even without having looked at the video yet I can say: No.  Very 
> different coefficients can yield rather similar functions in the 
> respective interval.  The actual question is whether your 
> coefficients lead to a good-looking correction. 
>
> Tschö, 
> Torsten. 
>
> -- 
> Torsten Bronger 
>
>

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/cd643d2c-79e0-4c5c-b2e6-925ac0ed7b11%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [hugin-ptx] Re: Lens correction with Hugin

[Robert Lounsberry]

Thank you very much. I was working toward what seems an impossible end.
Disregarding the difference in the numbers, I was finally able to arrive at
the proper corrections for the 16 and 20mm focal lengths for the zoom lens
I'm testing. Thank you very much for your help and kindness.

Best regards,
Robert Lounsberry

On Wed, May 16, 2018 at 4:10 PM, Torsten Bronger <
bron...@physik.rwth-aachen.de> wrote:

> Hallöchen!
>
> Robert Lounsberry writes:
>
> > [...] Is that a realistic goal? To be able to get close to those
> > numbers?
>
> Even without having looked at the video yet I can say: No.  Very
> different coefficients can yield rather similar functions in the
> respective interval.  The actual question is whether your
> coefficients lead to a good-looking correction.
>
> Tschö,
> Torsten.
>
> --
> Torsten Bronger
>
> --
> A list of frequently asked questions is available at:
> http://wiki.panotools.org/Hugin_FAQ
> ---
> You received this message because you are subscribed to the Google Groups
> "hugin and other free panoramic software" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to hugin-ptx+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/hugin-ptx/878t8j4b12.fsf%40wilson.bronger.org.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/CAK65kiGYsodg_5SFHcRUdavsCJ6PNyT2gTJi2sHsd9Ptj4QDeg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[hugin-ptx] Re: Lens correction with Hugin

[Robert Lounsberry]

Thanks for the reply. I redid everything making sure I added a new line 3, 
4, and 5 for the lines I was using. I've included a video of the process 
after I added the lines. I'll show that each line is it's own number yet 
when I optimize them all the numbers I arrive at are vastly different than 
those currently in lensfun. I am doing this as a test to see if I can get 
close to the numbers in lensfun (also shown at the end of the video). Is 
that a realistic goal? To be able to get close to those numbers? I'm 
evaluating this entire process so that I may start contributing to lensfun. 

Video of my settings and output. 
https://www.screencast.com/t/QPKZheBcOYLb

Thanks,
Robert Lounsberry

On Tuesday, May 8, 2018 at 3:45:12 PM UTC-4, Robert Lounsberry wrote:
>
> I am trying to figure out if this is expected or if I can make a change so 
> that the post 2014 version of Hugin works like the pre-2014 version when 
> doing lens correction.
>
> In the old version as you would place control points they would only 
> appear on one side of the image (left side for the left image and right 
> side for the right images) as seen here in this screenshot - 
> https://www.screencast.com/t/HSWzBkoPB
>
>
> In the post 2014 new version of Hugin you get these lines that go across 
> the entire image on both sides as seen here - 
> https://www.screencast.com/t/RVRV1srhI2
>
>
> Whenever I put all the control points down I am able to optimize and get a 
> set of lens correction numbers but they are always way off and still don't 
> fully correct the image. 
>
>
> If the UI is just different and not part of my issue, can someone help me 
> understand where I'm going wrong when creating the lens distortion control 
> points? I follow the steps here 
> http://hugin.sourceforge.net/tutorials/calibration/en.shtml as well as 
> this video here https://vimeo.com/51999287 and I can arrive at the 
> numbers assigned to a, b, and c, but they are always way off. 
>

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/eb8412bc-8b94-4cbe-971a-e219a1cd5577%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[hugin-ptx] Lens correction with Hugin

[Robert Lounsberry]

I am trying to figure out if this is expected or if I can make a change so 
that the post 2014 version of Hugin works like the pre-2014 version when 
doing lens correction.

In the old version as you would place control points they would only appear 
on one side of the image (left side for the left image and right side for 
the right images) as seen here in this screenshot - 
https://www.screencast.com/t/HSWzBkoPB


In the post 2014 new version of Hugin you get these lines that go across 
the entire image on both sides as seen here - 
https://www.screencast.com/t/RVRV1srhI2


Whenever I put all the control points down I am able to optimize and get a 
set of lens correction numbers but they are always way off and still don't 
fully correct the image. 


If the UI is just different and not part of my issue, can someone help me 
understand where I'm going wrong when creating the lens distortion control 
points? I follow the steps 
here http://hugin.sourceforge.net/tutorials/calibration/en.shtml as well as 
this video here https://vimeo.com/51999287 and I can arrive at the numbers 
assigned to a, b, and c, but they are always way off. 

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/b8f52b17-fdf1-4c05-bf66-a7c76d45273b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[hugin-ptx] Action menu not showing?

[Robert Krawitz]

With the current hg repo, I don't have an Action menu (not sure just
how long that has been the case).  As you can see from the attached
CMakeCache.txt, BUILD_HSI is enabled.  Also, Edit menu does have a Run
Python Script entry, and /usr/share/hugin/data/plugins exists and is
populated.

I must be missing something obvious, but it's not apparent just what.

-- 
Robert Krawitz <r...@alum.mit.edu>

***  MIT Engineers   A Proud Tradition   http://mitathletics.com  ***
Member of the League for Programming Freedom  --  http://ProgFree.org
Project lead for Gutenprint   --http://gimp-print.sourceforge.net

"Linux doesn't dictate how I work, I dictate how Linux works."
--Eric Crampton

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/20170806205615.2E3B5141934%40localhost.
For more options, visit https://groups.google.com/d/optout.
# This is the CMakeCache file.
# For build in directory: /home/rlk/sandbox/hugin/hugin
# It was generated by CMake: /usr/bin/cmake
# You can edit this file to change values found and used by cmake.
# If you do not want to change any of the values, simply exit the editor.
# If you do want to change a value, simply edit, save, and exit the editor.
# The syntax for the file is as follows:
# KEY:TYPE=VALUE
# KEY is the name of a variable in the cache.
# TYPE is a hint to GUIs for the type of VALUE, DO NOT EDIT TYPE!.
# VALUE is the current value for the KEY.


# EXTERNAL cache entries


//Python Scripting Interface
BUILD_HSI:BOOL=ON

//The directory containing a CMake configuration file for Boost.
Boost_DIR:PATH=Boost_DIR-NOTFOUND

//Boost filesystem library (debug)
Boost_FILESYSTEM_LIBRARY_DEBUG:FILEPATH=/usr/lib64/libboost_filesystem-mt.so

//Boost filesystem library (release)
Boost_FILESYSTEM_LIBRARY_RELEASE:FILEPATH=/usr/lib64/libboost_filesystem-mt.so

//Path to a file.
Boost_INCLUDE_DIR:PATH=/usr/include

//Boost library directory DEBUG
Boost_LIBRARY_DIR_DEBUG:PATH=/usr/lib64

//Boost library directory RELEASE
Boost_LIBRARY_DIR_RELEASE:PATH=/usr/lib64

//Boost system library (debug)
Boost_SYSTEM_LIBRARY_DEBUG:FILEPATH=/usr/lib64/libboost_system-mt.so

//Boost system library (release)
Boost_SYSTEM_LIBRARY_RELEASE:FILEPATH=/usr/lib64/libboost_system-mt.so

//suffix of boost root dir.
Boost_root_suffix:STRING=_1_54_0

//Path to a program.
CMAKE_AR:FILEPATH=/usr/bin/ar

//Choose the type of build, options are: None Debug Release RelWithDebInfo
// MinSizeRel.
CMAKE_BUILD_TYPE:STRING=Release

//Enable/Disable color output during build.
CMAKE_COLOR_MAKEFILE:BOOL=ON

//CXX compiler
CMAKE_CXX_COMPILER:FILEPATH=/usr/bin/g++

//Flags used by the compiler during all build types.
CMAKE_CXX_FLAGS:STRING=

//Flags used by the compiler during debug builds.
CMAKE_CXX_FLAGS_DEBUG:STRING=-g

//Flags used by the compiler during release builds for minimum
// size.
CMAKE_CXX_FLAGS_MINSIZEREL:STRING=-Os -DNDEBUG

//Flags used by the compiler during release builds.
CMAKE_CXX_FLAGS_RELEASE:STRING=-O3 -DNDEBUG

//Flags used by the compiler during release builds with debug info.
CMAKE_CXX_FLAGS_RELWITHDEBINFO:STRING=-O2 -g -DNDEBUG

//C compiler
CMAKE_C_COMPILER:FILEPATH=/usr/bin/cc

//Flags used by the compiler during all build types.
CMAKE_C_FLAGS:STRING=

//Flags used by the compiler during debug builds.
CMAKE_C_FLAGS_DEBUG:STRING=-g

//Flags used by the compiler during release builds for minimum
// size.
CMAKE_C_FLAGS_MINSIZEREL:STRING=-Os -DNDEBUG

//Flags used by the compiler during release builds.
CMAKE_C_FLAGS_RELEASE:STRING=-O3 -DNDEBUG

//Flags used by the compiler during release builds with debug info.
CMAKE_C_FLAGS_RELWITHDEBINFO:STRING=-O2 -g -DNDEBUG

//Flags used by the linker.
CMAKE_EXE_LINKER_FLAGS:STRING=

//Flags used by the linker during debug builds.
CMAKE_EXE_LINKER_FLAGS_DEBUG:STRING=

//Flags used by the linker during release minsize builds.
CMAKE_EXE_LINKER_FLAGS_MINSIZEREL:STRING=

//Flags used by the linker during release builds.
CMAKE_EXE_LINKER_FLAGS_RELEASE:STRING=

//Flags used by the linker during Release with Debug Info builds.
CMAKE_EXE_LINKER_FLAGS_RELWITHDEBINFO:STRING=

//Enable/Disable output of compile commands during generation.
CMAKE_EXPORT_COMPILE_COMMANDS:BOOL=OFF

//Install path prefix, prepended onto install directories.
CMAKE_INSTALL_PREFIX:PATH=/usr

//Path to a program.
CMAKE_LINKER:FILEPATH=/usr/bin/ld

//Path to a program.
CMAKE_MAKE_PROGRAM:FILEPATH=/usr/bin/gmake

//Flags used by the linker during the creation of modules.
CMAKE_MODULE_LINKER_FLAGS:STRING=

//Flags used 

Re: [hugin-ptx] Hugin 2017.0 rc2 released

[Robert Lesac]

On 17.06.2017. 18:14, T. Modes wrote:



Am Samstag, 17. Juni 2017 16:21:18 UTC+2 schrieb Robert Lesac:

Another thing, when adding an equirectangular image into Hugin, it
automatically gets assigned a yaw of 180 degrees. 

I can't reproduce this. Oh wait, this happens on when using add images 
in the fast preview window.

Drag'n'drop on the photos tab is how I usually add images.


It's been that way for
year.
Could that be changed to 0 degrees?

And why has this not reported before?


Good question. I just learned to live with it and it got committed to 
muscle memory.

It didn't occur to me to report it.
I'll get more involved with Hugin, I promise! :D


I committed a fix to the default branch. But it will probably not make 
its way into 2017.0.


Great!


I do have another pet peewee, when using the edit cp in the fast
preview, it automatically runs optimisation with no option to change
the
behavior. It would be great if it could be changed through options.
The optimization after every edit just slows the whole process down.

Preferences>misc tab>After "edit cp" tool


Oh! Must have been blind. Thanks!
--

Pano/VR/Gigapixel photography: http://robertlesac.com

---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus

--
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups "hugin and other free panoramic software" group.

To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/506471af-8566-440d-28dc-7c3f6a1b30b5%40robertlesac.com.
For more options, visit https://groups.google.com/d/optout.

Re: [hugin-ptx] Hugin 2017.0 rc2 released

[Robert Lesac]

Thank you for the prompt fix!

Another thing, when adding an equirectangular image into Hugin, it 
automatically gets assigned a yaw of 180 degrees. It's been that way for 
year.

Could that be changed to 0 degrees?
I do have another pet peewee, when using the edit cp in the fast 
preview, it automatically runs optimisation with no option to change the 
behavior. It would be great if it could be changed through options.

The optimization after every edit just slows the whole process down.

Robert

On 17.06.2017. 16:05, T. Modes wrote:



Am Samstag, 17. Juni 2017 13:47:59 UTC+2 schrieb Robert Lesac:

Testing the release, but it seems it dropped support for Adobe tiff
compression:
  > AdobeDeflate compression support is not configured.

Is that on purpose or just an omission?


Just an omission. It was configured with deflate support. But somehow it 
does not make it into the lib.


I uploaded an updated installer: 
https://sourceforge.net/projects/hugin/files/hugin/hugin-2017.0/Hugin-2017.0rc2-win64-b.msi/download

md5 434db5bb989a02b528eeb613ff0fe729

--
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ

---
You received this message because you are subscribed to the Google 
Groups "hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send 
an email to hugin-ptx+unsubscr...@googlegroups.com 
<mailto:hugin-ptx+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/0c0b3f34-1db0-415d-8405-84a67cc4c71f%40googlegroups.com 
<https://groups.google.com/d/msgid/hugin-ptx/0c0b3f34-1db0-415d-8405-84a67cc4c71f%40googlegroups.com?utm_medium=email_source=footer>.

For more options, visit https://groups.google.com/d/optout.



--

Pano/VR/Gigapixel photography: http://robertlesac.com

---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus

--
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups "hugin and other free panoramic software" group.

To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/59713eb8-9074-f634-8c62-64de6bcc7dd3%40robertlesac.com.
For more options, visit https://groups.google.com/d/optout.

Re: [hugin-ptx] Hugin 2017.0 rc2 released

[Robert Lesac]

Hi!
Forgot to mention, it's the Windows x64 build.

Robert

On 17.06.2017. 13:47, Robert Lesac wrote:

Hi!

Testing the release, but it seems it dropped support for Adobe tiff 
compression:

 > AdobeDeflate compression support is not configured.

Is that on purpose or just an omission?

Robert

On 17.06.2017. 09:41, T. Modes wrote:

Hi all,

today we are releasing release candidate 2 of Hugin 2017.0.

Source tarball can be downloaded
at sourceforge: 
https://sourceforge.net/projects/hugin/files/hugin/hugin-2017.0/hugin-2017.0rc2.tar.bz2/download 

or at launchpad: 
https://launchpad.net/hugin/2017.0/2017.0rc2/+download/hugin-2017.0rc2.tar.bz2 



Verify its checksums:
md5: 3b49a905da8ee395774347ee6b3903b0  hugin-2017.0rc2.tar.bz2
sha1: 4ba7f5bf5afdadbea9cf10d15aa14e644ef94ed3  hugin-2017.0rc2.tar.bz2

This is a source code release.
Users communities produce executables for their respective platforms. 
Please announce them here.


(The rc 2 correspond to changeset eac5e8cc546e in our repository, 
which is also tagged as 2017.0 rc2).


Changes since 2017.0 rc 1
* Updated Hungarian and Dutch translation.
* Fixes message for failed assistant.
* Fixes deleting last mask in mask editor.
* Added some more checks for information in lens db.

Changes since 2017.0 beta 1
* Updated translations.
* Provide workaround for Wayland systems. It needs to be activated at 
compile time.

* Fixes crash with user defined sequences in menu.
* Don't show warning about unlinked images when loading lens settings 
for lens with only one image.

* Also accept cmd+A as select all in photo and optimizer tab (Mac only)
* User defined output sequences: Find also programs in bundle

Changes since 2016.2.0
The version 2017.0 is mainly a bug fix release. The biggest fixes regard:
* Several fixes for working with HDR images (display in GUI, 
photometric optimizer, handling of under/over exposured pixels in 
merging code).
* Fixes handling of masks in cpfind when images needs remapping for cp 
finding.
* Sometimes unsaved changes were disregarded without asking the user 
(e.g. when loading a project via the recently used projects list). 
Unsaved changes should now always require user confirmation.


Besides the bug fixes some smaller improvements have been implemented.
* Optimizer tabs uses now checkboxes instead of bold underlined font 
for marking of variables to be optimized.
* Use wxWidgets help windows instead of default browser (Linux 
only, this provides table of content, index and full text search in 
help files).

* Added special assistant variant for single image projects.
* Display of final panorama dimensions on stitcher tab.
* Extended the user defined output sequences:
** The shipped user defined output sequences are exposed in the 
GUI as own sub-menu.
** Added some more user defined output sequences (layered TIFF, 
cube faces).
** Added new placeholder %sourceimage% to user defined output 
sequence.


Upgrading from previous versions of Hugin should be seamless. If you 
do have problems with old settings, these can be reset in the 
Preferences window by clicking 'Load defaults'.


A first draft of release notes can be found at 
http://hugin.sourceforge.net/releases/2017.0.0/en.shtml 
<http://hugin.sourceforge.net/releases/2017.0.0/en.shtml>


Know issues
Hugin does not run native on Wayland because of a bug in the 
underlying wxWidgets library.
The source code contains a workaround which forces the usage of the 
XWayland emulation layer.
This workaround has be activated during compiling (add 
-DUSE_GDKBACKEND_X11=on the the CMake command)


--
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ

---
You received this message because you are subscribed to the Google 
Groups "hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send 
an email to hugin-ptx+unsubscr...@googlegroups.com 
<mailto:hugin-ptx+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/6c753a10-fb84-4603-85b6-e0a3e3a8fbc7%40googlegroups.com 
<https://groups.google.com/d/msgid/hugin-ptx/6c753a10-fb84-4603-85b6-e0a3e3a8fbc7%40googlegroups.com?utm_medium=email_source=footer>. 


For more options, visit https://groups.google.com/d/optout.






--

Pano/VR/Gigapixel photography: http://robertlesac.com

---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus

--
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups "hugin and other free panoramic software" group.

To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/dbb46a67-5d6c

Re: [hugin-ptx] Hugin 2017.0 rc2 released

[Robert Lesac]

Hi!

Testing the release, but it seems it dropped support for Adobe tiff 
compression:

> AdobeDeflate compression support is not configured.

Is that on purpose or just an omission?

Robert

On 17.06.2017. 09:41, T. Modes wrote:

Hi all,

today we are releasing release candidate 2 of Hugin 2017.0.

Source tarball can be downloaded
at sourceforge: 
https://sourceforge.net/projects/hugin/files/hugin/hugin-2017.0/hugin-2017.0rc2.tar.bz2/download
or at launchpad: 
https://launchpad.net/hugin/2017.0/2017.0rc2/+download/hugin-2017.0rc2.tar.bz2


Verify its checksums:
md5: 3b49a905da8ee395774347ee6b3903b0  hugin-2017.0rc2.tar.bz2
sha1: 4ba7f5bf5afdadbea9cf10d15aa14e644ef94ed3  hugin-2017.0rc2.tar.bz2

This is a source code release.
Users communities produce executables for their respective platforms. 
Please announce them here.


(The rc 2 correspond to changeset eac5e8cc546e in our repository, which 
is also tagged as 2017.0 rc2).


Changes since 2017.0 rc 1
* Updated Hungarian and Dutch translation.
* Fixes message for failed assistant.
* Fixes deleting last mask in mask editor.
* Added some more checks for information in lens db.

Changes since 2017.0 beta 1
* Updated translations.
* Provide workaround for Wayland systems. It needs to be activated at 
compile time.

* Fixes crash with user defined sequences in menu.
* Don't show warning about unlinked images when loading lens settings 
for lens with only one image.

* Also accept cmd+A as select all in photo and optimizer tab (Mac only)
* User defined output sequences: Find also programs in bundle

Changes since 2016.2.0
The version 2017.0 is mainly a bug fix release. The biggest fixes regard:
* Several fixes for working with HDR images (display in GUI, photometric 
optimizer, handling of under/over exposured pixels in merging code).
* Fixes handling of masks in cpfind when images needs remapping for cp 
finding.
* Sometimes unsaved changes were disregarded without asking the user 
(e.g. when loading a project via the recently used projects list). 
Unsaved changes should now always require user confirmation.


Besides the bug fixes some smaller improvements have been implemented.
* Optimizer tabs uses now checkboxes instead of bold underlined font for 
marking of variables to be optimized.
* Use wxWidgets help windows instead of default browser (Linux only, 
this provides table of content, index and full text search in help files).

* Added special assistant variant for single image projects.
* Display of final panorama dimensions on stitcher tab.
* Extended the user defined output sequences:
** The shipped user defined output sequences are exposed in the GUI 
as own sub-menu.
** Added some more user defined output sequences (layered TIFF, cube 
faces).

** Added new placeholder %sourceimage% to user defined output sequence.

Upgrading from previous versions of Hugin should be seamless. If you do 
have problems with old settings, these can be reset in the Preferences 
window by clicking 'Load defaults'.


A first draft of release notes can be found at 
http://hugin.sourceforge.net/releases/2017.0.0/en.shtml 
<http://hugin.sourceforge.net/releases/2017.0.0/en.shtml>


Know issues
Hugin does not run native on Wayland because of a bug in the underlying 
wxWidgets library.
The source code contains a workaround which forces the usage of the 
XWayland emulation layer.
This workaround has be activated during compiling (add 
-DUSE_GDKBACKEND_X11=on the the CMake command)


--
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ

---
You received this message because you are subscribed to the Google 
Groups "hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send 
an email to hugin-ptx+unsubscr...@googlegroups.com 
<mailto:hugin-ptx+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/6c753a10-fb84-4603-85b6-e0a3e3a8fbc7%40googlegroups.com 
<https://groups.google.com/d/msgid/hugin-ptx/6c753a10-fb84-4603-85b6-e0a3e3a8fbc7%40googlegroups.com?utm_medium=email_source=footer>.

For more options, visit https://groups.google.com/d/optout.



--

Pano/VR/Gigapixel photography: http://robertlesac.com

---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus

--
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups "hugin and other free panoramic software" group.

To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/0eef1bea-ad1e-aaaf-d4ca-70b97d21d4d0%40robertlesac.com.
For more options, visit https://groups.google.com/d/optout.

[hugin-ptx] Re: Can Hugin change the projection of a video?

[Robert Giordano]

First, thanks to everyone for their suggestions and tips!! I'm going to 
describe my procedure and test results in detail for the benefit of people 
reading this post in the future. 

Here's my current setup:

*Computer: *
Macbook PRO 2.3 GHz i7
OS X 10.9.5

*Test Video:*
clip0076.mov
- 1080p 59.94fps
- movie is approx. 1 min 52 sec, 6,711 total frames
- file size is 419.9 MB


I'm using Hugin 2014.0.0 installed in /Applications/Hugin

I created a file named "hugin" in my paths.d folder with these paths:
/Applications/Hugin/Hugin.app/Contents/MacOS
/Applications/Hugin/Hugin.app/Contents/Resources
/Applications/Hugin/Hugin.app/Contents/Resources/HuginStitchProject.app/Contents/MacOS

This lets me run nona from the command line without having to type the full 
path

I installed FFmpeg using Homebrew:
https://trac.ffmpeg.org/wiki/CompilationGuide/MacOSX



*TEST RESULTS:*

1. Use FFmpeg to split the movie into a folder of numbered images:


METHOD 1 - lossless PNG

ffmpeg -i clip0076.mov frame-%05d.png

- 21 minutes to create 6,711 PNG files totaling 29.81 GB (70X the original 
file size!) 


METHOD 2 - high quality JPG

ffmpeg -i GOPR0076clip.mov -qscale:v 2 frame-%05d.jpg

- LESS THAN 2 minutes to create 6,711 JPG files totaling 3.88 GB (more 
reasonable)


2. Use Hugin to convert all of the images to Equirectangular Panini:

Here's the bash script (slightly modified from Carlos Cartola's suggestion):

# loop on the frames
for number in $(seq 1 $total); do
  n=$(printf %05d $number)
  echo $n
  nona -o out-$n /Users/design215/Video/_hugin/test.0001.pto frame-$n.jpg
done


test.0001.pto is a Hugin .pto file that I edited. I'm using this single 
.pto file to modify all of my images because the loop feeds each filename 
to the .pto file. 

- 1 HOUR, 4 minutes to create 6,711 corrected JPG images
- Images are all 2250x1362. I prefer to crop in Premiere, not Hugin


3. Use FFmpeg to combine the corrected images back into a movie:

ffmpeg -framerate 59.94 -i out-%05d.jpg -pix_fmt yuv420p -c:v libx264 -crf 
16 output.mp4

- 8 minutes to create output.mp4
- These settings give me the original framerate, and high quality output

output.mp4:
- 2250x1362p 59.94fps
- file size is 703.6 MB
- quality looks good!




*CONCLUSION:*The total time to do the conversion with my 2 minute clip = 1 
hour, 33 minutes using PNG images, or 1 hour, 14 minutes using JPG images.

Hugin gives me complete control over the projection and I can do exactly 
what I want.

The downsides to method are:
- My test clip was less than 2 minutes. Imagine the space you need for a 10 
minute clip.
- The images are re-compressed multiple times. Even if you start with PNG 
images, they are compressed once by Hugin, and again by FFmpeg when merging 
the images back to video. I know I could have Hugin output PNGs but then I 
would need at least 60 GB just to process 2 minutes of footage!

Don't get me wrong, the final video quality is VERY GOOD!

But, I can do almost the same thing in Photoshop CS6 with fewer steps and 
no folders with thousands of files.

The downsides to using Photoshop are:
- It takes just over 2 hours to process the same 2 minute clip.
- I have much less control than I have with Hugin. I can get close but not 
exactly what I want. 

My feeling is- There HAS to be a better, more efficient way to do this. 



-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/c3de8513-ca76-470d-8e8b-05832106043d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[hugin-ptx] Re: Can Hugin change the projection of a video?

[Robert Giordano]

Hi Monkey,

Avisynth looks very interesting. I'm on a Mac but I have access to Windows 
machines. I do my editing in Adobe Premiere/After Effects CS6. The only 
reason I'm using Hugin is because it does *exactly* what I need, but only 
to single frames, one at a time. It would be nice to convert an 8 minute 
video shot at 60fps without having to convert it to 28,800 JPEGS and then 
convert it back to video. 

I really appreciate all the help given here so far and I'm currently 
experimenting with FFMPEG as suggested above by Cartola

Also, I'd like to point out that I want a PANINI equirectangular projection 
(or an adjustable Panini), not a plain Equirectangular projection. It just 
so happens that in the Hugin drop-down menu of projections, there is 
"Equirectangular Panini" and it does exactly what I want, given the lens 
horizontal field of view (HFOV) that I input.

Here is a link with TONS of stuff about the panini projection: 
http://tksharpless.net/vedutismo/Pannini/

At one point he seems to have built a video converter but it hasn't been 
supported for years and I couldn't get it to work on two different Windows 
machines. 

I'm REALLY surprised I couldn't find a plugin for Premiere that does this. 

thanks,

Robert


On Monday, July 11, 2016 at 6:55:10 PM UTC-4, Monkey wrote:
>
> I have to say I* really *think Hugin is the wrong tool for this job!
>
> If someone can help me out with the maths behind converting Fisheye to 
> Equirectangular, there is an Avisynth pluging called xyremap (written by 
> me!) which will do this in near realtime.
>
> (I seem to remember there is an .exe in the distribution which will give 
> individual transform coordinates on request, from a PTO - but I don't 
> recall finding out a way to give a full map of coordinates in one call. If 
> that could be done I could modify my plugin to read the map and apply it to 
> the video)
>
> -Monkey
>
> On Sunday, 10 July 2016 10:39:32 UTC+1, Robert Giordano wrote:
>>
>> I want to change the projection of all frames in a video from Fisheye to 
>> Equirectangular Panini. I'm not trying to stitch any images. I'm not doing 
>> a 360 video. I'm just trying to do a lens correction. I've exported a 
>> single frame from my video and Hugin changes the image perfectly. Is it 
>> possible to use Hugin to change all of the frames in the video?
>>
>> thanks,
>>
>> Robert
>>
>>
>>
>>
>>

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/5a74bf02-3610-4556-8974-87206bf3ab2b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [hugin-ptx] Re: Can Hugin change the projection of a video?

[Robert Giordano]

Carlos, that is excellent!!

Since I'm passing each filename to nona in the loop, can I just use a 
single test.pto instead of test.$number.pto ??

Thanks again!!

On Monday, July 11, 2016 at 7:44:17 AM UTC-4, Cartola wrote:
>
> There are many documentation on the Internet on how to make a bash script. 
> Here 
> is one example .
>
> I guess here you will need basically a loop:
>
> ---
> #!/bin/bash
>
> for number in $(seq -w 1 18000); do
>   /Applications/hugin.2014.0.0/Hugin.app/Contents/MacOS/nona -o output 
> test.$number.pto test.$number.png
> done
> ---
>
> And if you install ffmpeg you can automate all the job
>
> ---
> #!/bin/bash
>
> # split the video in frames using 5 digits
> ffmpeg -i yourVideo.mp4 -qscale:v 2 frame-%05d.jpg
>
> # count the frames
> total=$(ls frame-*.jpg | wc -l)
>
> # loop on the frames
> for number in $(seq -w 1 $total); do
>   /Applications/hugin.2014.0.0/Hugin.app/Contents/MacOS/nona -o output 
> test.$number.pto frame-$number.jpg
> done
>
> ffmpeg -i output%05d.jpg final_output.mp4
> ---
>
> Bests,
>
>
>
> Carlos E G Carvalho (Cartola)
> http://cartola.org/360
> http://www.panoforum.com.br/
>
>
>

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/251a7660-5a54-42d5-ba52-9489b9878721%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [hugin-ptx] Re: Can Hugin change the projection of a video?

[Robert Giordano]

Unfortunately, there is no "doc" directory in my installation (maybe 
because I'm on a Mac?)

>
> There should be a nona.txt file inside the "doc" directory of your Hugin 
> installation which explains the options in a .pto file. 
>
>

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/34596474-8e65-4659-be02-9d0ea0cf964d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [hugin-ptx] Re: Can Hugin change the projection of a video?

[Robert Giordano]

Thanks!! That works!! I was playing with the "Write PTStitcher Script" 
option in the Hugin File menu and now I have this:
 

# PTStitcher script, written by hugin

p f16 w2250 h1362 v111  n"JPEG q94"
m g1 i0 f0 m2 p0.00784314

# output image lines
o w1920 h1080 f2 Tpp0 Tpy0 TrX0 TrY0 TrZ0 a0 b0 c0 d0 e0 g0 p0 r0 t0 
v102.88718987 y0  n""


I changed to the JPEG option and added q. Now I just have to figure out how 
to make a batch script.

Thanks everyone, this has been very interesting so far!!

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/7f4e0d42-e5a6-4490-b845-6dd3e4bcae76%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [hugin-ptx] Re: Can Hugin change the projection of a video?

[Robert Giordano]

Sorry about that!!

On Monday, July 11, 2016 at 5:37:13 AM UTC-4, Tduell wrote:
>
> On Mon, 11 Jul 2016 18:52:04 +1000, Robert Giordano <rob...@gmail.com 
> >   
> wrote: 
>
> > Okay, here's my .pto file: 
> > 
>
> ...and a 4.6MB file and a 6.4MB in your next post. 
> This is not good etiquette. 
> If you need to provide large files please do it via Dropbox or similar so 
>   
> that only those that need to access the files can do so. 
>
> Cheers, 
> -- 
> Regards, 
> Terry Duell 
>

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/0e4989b2-bf88-46fa-8e13-06cd71b979b0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [hugin-ptx] Re: Can Hugin change the projection of a video?

[Robert Giordano]

Sorry about that

On Mon, Jul 11, 2016 at 5:37 AM, Terry Duell <tdu...@iinet.net.au> wrote:

> On Mon, 11 Jul 2016 18:52:04 +1000, Robert Giordano <rob2...@gmail.com>
> wrote:
>
> Okay, here's my .pto file:
>>
>>
> ...and a 4.6MB file and a 6.4MB in your next post.
> This is not good etiquette.
> If you need to provide large files please do it via Dropbox or similar so
> that only those that need to access the files can do so.
>
> Cheers,
> --
> Regards,
> Terry Duell
>
> --
> A list of frequently asked questions is available at:
> http://wiki.panotools.org/Hugin_FAQ
> ---You received this message because you are subscribed to a topic in the
> Google Groups "hugin and other free panoramic software" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/hugin-ptx/m3Ow9lIEh_A/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> hugin-ptx+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/hugin-ptx/op.ykfjn6u4rs0ygh%40localhost.
>
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Design215 Inc.
Commercial Photography, Advertising and Media
www.Design215.com

Robert Giordano, President
+1 954 461 7340 mobile
+1 954 630 3695 office
+1 954 566 6155 fax

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/CAHSzGQsGsuvyQsR_DF3fdYs%2B7dpB8b0GTvXwPz_vean_cnD%3D%2BQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [hugin-ptx] Re: Can Hugin change the projection of a video?

[Robert Giordano]

Okay this worked:

/Applications/hugin.2014.0.0/Hugin.app/Contents/MacOS/nona -o output 
test..pto test..png

and it produced output.tif

I'll have to figure out why it created a .tif instead of a .jpg



-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/a80b1b86-5147-4fb2-8596-45c0eaf235d0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [hugin-ptx] Re: Can Hugin change the projection of a video?

[Robert Giordano]

Thanks again Sean,

The methods you suggest are logical. That's pretty much how I attack
problems anyway. I was hoping there was a direct command to transform the
projection of an image. That would be a lot simpler (and probably faster as
far as CPU cycles go) than using the entire Hugin program.

I will try making a .pto and inspect it. It might give me some clues.

I also want to mention that I found a way to do what I want in Photoshop
CS6 but its also a bit inefficient. I could not find a way to do the
equirectangular panini directly in PS so I used several filters to achieve
a similar result. Since the images are all the same size and shape (they're
all video frames) my sequence of adjustments can be repeated across all of
them.
- I open the video file in PS and make it a "smart layer"
- I apply my sequence of filters to it (they are not applied immediately)
- I select "render video" and choose my video output options
- Then I wait just over 2 hours for PS to process 2 minutes of footage
(7200 frames) but then I have a complete .mov file.

So, the drawbacks of using PS are
1) its close but not exactly what I want, while Hugin does exactly what I
want in a single step, and
2) it takes forever and I have a fairly fast Mac.

I haven't timed how long it will take to export a video to 7200 separate
images from Premiere but that will play a factor.

I've also wondered how hard it is to make a plugin for Premiere. With all
of the thousands of things you can do in Premiere (or After Effects) I was
surprised I couldn't find a plugin that would let me change the projection
of a video. Maybe there is but I wasn't able to find it after 2 solid days
of searching.

I'll post what I find as I experiment with the .pto file in case it can
help others in the future.

Robert

On Sun, Jul 10, 2016 at 10:37 PM, Sean Greenslade <s...@seangreenslade.com>
wrote:

> On Sun, Jul 10, 2016 at 09:29:41PM -0400, Robert Giordano wrote:
> > Thanks Sean and Zoilo
> >
> > I'm doing video editing on several Mac computers, OSX 10.9.5. I won't be
> > able to install PHP on them so I'm guessing I will need a bash script?
>
> PHP is not typically used for this sort of thing, so don't worry about
> it.
>
> Unfortunately, I'm not very familiar with OSX. I do believe it has bash,
> so pretty much any bash tutorial should help you. I like this one:
>
> http://tldp.org/LDP/abs/html/
>
> > I'm not an expert at command line scripting. Is there a place where I can
> > read about command line options for Hugin? For example, is there a direct
> > command to change the projection of an image, given the lens and HFOV
> > parameters? Or do I have to create a .pto file just for this single
> > operation?
>
> My best advice here is to make a project with Hugin that does what you
> want, then save the .pto file and inspect it. Then either turn that file
> into a template or model your pto generation code after it.
>
> > I could probably look up how to get a list of files in a folder but then
> I
> > might need some help after that.
>
> Best way to tackle something like this is to draw out the overview of
> what you want to happen. e.g.:
>
> loop over files:
> generate pto with current file name
> run nona / hugin_executor / whatever
> move file to destination folder
> delete pto file
>
> Once you have that, then start implementing a bit at a time. Breaking
> the problem up makes exploring unfamiliar territory easier.
>
> --Sean
>
> --
> A list of frequently asked questions is available at:
> http://wiki.panotools.org/Hugin_FAQ
> ---
> You received this message because you are subscribed to a topic in the
> Google Groups "hugin and other free panoramic software" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/hugin-ptx/m3Ow9lIEh_A/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> hugin-ptx+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/hugin-ptx/20160711023721.GA16247%40coach.home
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Design215 Inc.
Commercial Photography, Advertising and Media
www.Design215.com

Robert Giordano, President
+1 954 461 7340 mobile
+1 954 630 3695 office
+1 954 566 6155 fax

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/CAHSzGQunwROxbmnHx64vNL5XzPTzwOC0Gemzn5j7ka0UCwYsug%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [hugin-ptx] Re: Can Hugin change the projection of a video?

[Robert Giordano]

Thanks Sean and Zoilo

I'm doing video editing on several Mac computers, OSX 10.9.5. I won't be
able to install PHP on them so I'm guessing I will need a bash script?

I'm not an expert at command line scripting. Is there a place where I can
read about command line options for Hugin? For example, is there a direct
command to change the projection of an image, given the lens and HFOV
parameters? Or do I have to create a .pto file just for this single
operation?

I could probably look up how to get a list of files in a folder but then I
might need some help after that.

thanks,

Robert

On Sun, Jul 10, 2016 at 9:13 PM, Sean Greenslade <s...@seangreenslade.com>
wrote:

> On Sun, Jul 10, 2016 at 05:14:30PM -0700, Robert Giordano wrote:
> > Hi Zoilo,
> >
> > Thanks for the reply! Yes, I use Premiere CS6 and I can export the video
> to
> > folder of pictures. But if I have a 5 minute video (some are even longer)
> > that's 18,000 images!
> >
> > I can create a single .pto file but surely there must be a better way
> than
> > having to make 18,000 .pto files??
> >
> > What about making a dynamic .pto file using PHP or something? When I make
> > thumbnails on a website, I use PHP to make a list of all the images in a
> > folder, then create a thumbnail for each image in the list. Does your
> > script create 18,000 .pto files because Hugin needs all of them?
> >
> > thanks,
> >
> > Robert
>
> Sure, you can generate a .pto file using any scripting language, even
> PHP (though I would imagine python or even bash might be a bit simpler).
>
> Basically, you need a script that loops over every frame file, generates
> the pto, processes it, and saves the output file with the proper name.
> If you get clever with the script, it could scan a directory and process
> all files in it. That way, you just explode the video into a directory,
> then fire off the script.
>
> --Sean
>
> --
> A list of frequently asked questions is available at:
> http://wiki.panotools.org/Hugin_FAQ
> ---
> You received this message because you are subscribed to a topic in the
> Google Groups "hugin and other free panoramic software" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/hugin-ptx/m3Ow9lIEh_A/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> hugin-ptx+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/hugin-ptx/20160711011311.GA15129%40coach.home
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Design215 Inc.
Commercial Photography, Advertising and Media
www.Design215.com

Robert Giordano, President
+1 954 461 7340 mobile
+1 954 630 3695 office
+1 954 566 6155 fax

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/CAHSzGQvuBya3yaTVSFb_GR01hz-zchUoyx_NCL9sbnXr0kub_g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[hugin-ptx] Re: Can Hugin change the projection of a video?

[Robert Giordano]

Hi Zoilo,

Thanks for the reply! Yes, I use Premiere CS6 and I can export the video to 
folder of pictures. But if I have a 5 minute video (some are even longer) 
that's 18,000 images!

I can create a single .pto file but surely there must be a better way than 
having to make 18,000 .pto files??

What about making a dynamic .pto file using PHP or something? When I make 
thumbnails on a website, I use PHP to make a list of all the images in a 
folder, then create a thumbnail for each image in the list. Does your 
script create 18,000 .pto files because Hugin needs all of them?

thanks,

Robert


On Sunday, July 10, 2016 at 7:52:24 PM UTC-4, Zoilo ABAD wrote:
>
> Hi,
>
> the best solution I have found for the moment is to 
>  - slice the video on picture (I use premiere but you can have a lot of 
> method to do that)
>  - create one template .pto with all the modification you want to do
>  - copy the template the time you have of picture (3600 times for you...)
>  - change the name of the picture inside the pto
>  - use the batch tool on hugin to import all the pto and process them
>
> I have made a little tool with processing to copy the pto and change the 
> picture name inside
> you can take a look and modify the code to make what you want
>
> If you don't know how to play with processing let me know and if I have 
> time I do a special version for you
> https://fablabwgtn.github.io/Mobile-360/post/tutorial-stitch.html
>
> Zoilo
>
>

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/24c164e3-feb5-4d0a-b510-22c45eb113ea%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[hugin-ptx] Can Hugin change the projection of a video?

[Robert Giordano]

I want to change the projection of all frames in a video from Fisheye to 
Equirectangular Panini. I'm not trying to stitch any images. I'm not doing 
a 360 video. I'm just trying to do a lens correction. I've exported a 
single frame from my video and Hugin changes the image perfectly. Is it 
possible to use Hugin to change all of the frames in the video?

thanks,

Robert




-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/94dddf80-80ea-4787-830c-2fdbf21ef576%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[hugin-ptx] Compile problem w/current hg

[Robert Krawitz]

OpenSUSE 42.1 + all patches:

[ 45%] Building CXX object 
src/hugin1/base_wx/CMakeFiles/huginbasewx.dir/wxPanoCommand.cpp.o
/home/rlk/sandbox/hugin/src/hugin1/base_wx/wxPanoCommand.cpp: In member 
function ‘virtual bool 
PanoCommand::wxNewProjectCmd::processPanorama(HuginBase::Panorama&)’:
/home/rlk/sandbox/hugin/src/hugin1/base_wx/wxPanoCommand.cpp:834:26: error: 
invalid user-defined conversion from ‘wxString’ to ‘char’ [-fpermissive]
 opts.verdandiOptions = config->Read(wxT("/VerdandiDefaultArgs"), 
wxEmptyString);
  ^
In file included from /usr/include/wx-2.8/wx/memory.h:16:0,
 from /usr/include/wx-2.8/wx/object.h:20,
 from /usr/include/wx-2.8/wx/wx.h:16,
 from /home/rlk/sandbox/hugin/src/hugin1/panoinc_WX.h:40,
 from 
/home/rlk/sandbox/hugin/src/hugin1/base_wx/wxPanoCommand.cpp:29:
/usr/include/wx-2.8/wx/string.h:832:5: note: candidate is: wxString::operator 
const wxChar*() const 
 operator const wxChar*() const { return c_str(); }
 ^
/usr/include/wx-2.8/wx/string.h:832:5: note:   no known conversion for implicit 
‘this’ parameter from ‘const wxChar* {aka const wchar_t*}’ to ‘char’
src/hugin1/base_wx/CMakeFiles/huginbasewx.dir/build.make:350: recipe for target 
'src/hugin1/base_wx/CMakeFiles/huginbasewx.dir/wxPanoCommand.cpp.o' failed
make[2]: *** 
[src/hugin1/base_wx/CMakeFiles/huginbasewx.dir/wxPanoCommand.cpp.o] Error 1
make[2]: Target 'src/hugin1/base_wx/CMakeFiles/huginbasewx.dir/build' not 
remade because of errors.
CMakeFiles/Makefile2:1570: recipe for target 
'src/hugin1/base_wx/CMakeFiles/huginbasewx.dir/all' failed
make[1]: *** [src/hugin1/base_wx/CMakeFiles/huginbasewx.dir/all] Error 2


-- 
Robert Krawitz <r...@alum.mit.edu>

***  MIT Engineers   A Proud Tradition   http://mitathletics.com  ***
Member of the League for Programming Freedom  --  http://ProgFree.org
Project lead for Gutenprint   --http://gimp-print.sourceforge.net

"Linux doesn't dictate how I work, I dictate how Linux works."
--Eric Crampton

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/201603140107.u2E17jpg008426%40dsl092-065-009.bos1.dsl.speakeasy.net.
For more options, visit https://groups.google.com/d/optout.

Re: [hugin-ptx] Very weird runtime error

[Robert Krawitz]

On Sat, 6 Feb 2016 08:19:55 +0100, Jan Dubiec wrote:
> On 2016-02-06 02:13, Robert Krawitz wrote:
> [...]
>> ABI versions of what?
> Compilers ABI, i.e. C++ ABI version 1002 vs. 1009. I bet that you
> compile hugin with gcc 5.2/5.3 and have wxWidgets compiled with gcc 4.x.

I thought of that.  I *thought* that I recompiled it with 4.x, but
still see that problem.  I'll take another shot at it.

> http://stackoverflow.com/questions/23895081/can-you-mix-c-compiled-with-different-versions-of-the-same-compiler.


-- 
Robert Krawitz <r...@alum.mit.edu>

***  MIT Engineers   A Proud Tradition   http://mitathletics.com  ***
Member of the League for Programming Freedom  --  http://ProgFree.org
Project lead for Gutenprint   --http://gimp-print.sourceforge.net

"Linux doesn't dictate how I work, I dictate how Linux works."
--Eric Crampton

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/201602061644.u16GiqHW010585%40dsl092-065-009.bos1.dsl.speakeasy.net.
For more options, visit https://groups.google.com/d/optout.

Re: [hugin-ptx] Very weird runtime error

[Robert Krawitz]

On Sat, 6 Feb 2016 08:19:55 +0100, Jan Dubiec wrote:
> On 2016-02-06 02:13, Robert Krawitz wrote:
> [...]
>> ABI versions of what?
> Compilers ABI, i.e. C++ ABI version 1002 vs. 1009. I bet that you
> compile hugin with gcc 5.2/5.3 and have wxWidgets compiled with gcc 4.x.
>
> http://stackoverflow.com/questions/23895081/can-you-mix-c-compiled-with-different-versions-of-the-same-compiler.

That did turn out to be the issue.  I thought I had cleaned up my
build directory, but apparently not.  Blowing away my build directory
and recreating it solved it.  Sorry for the trouble.
-- 
Robert Krawitz <r...@alum.mit.edu>

***  MIT Engineers   A Proud Tradition   http://mitathletics.com  ***
Member of the League for Programming Freedom  --  http://ProgFree.org
Project lead for Gutenprint   --http://gimp-print.sourceforge.net

"Linux doesn't dictate how I work, I dictate how Linux works."
--Eric Crampton

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/201602070326.u173QwdG005863%40dsl092-065-009.bos1.dsl.speakeasy.net.
For more options, visit https://groups.google.com/d/optout.

[hugin-ptx] Very weird runtime error

[Robert Krawitz]

I'm getting a rather strange runtime error.  Running openSUSE Leap
42.1, building my own package from hg:

$ /usr/bin/hugin
Fatal Error: Mismatch between the program and library build versions detected.
The library used 2.8 (no debug,Unicode,compiler with C++ ABI 1002,STL 
containers,compatible with 2.6),
and your program used 2.8 (no debug,Unicode,compiler with C++ ABI 1009,STL 
containers,compatible with 2.6).
Aborted

-- 
Robert Krawitz <r...@alum.mit.edu>

***  MIT Engineers   A Proud Tradition   http://mitathletics.com  ***
Member of the League for Programming Freedom  --  http://ProgFree.org
Project lead for Gutenprint   --http://gimp-print.sourceforge.net

"Linux doesn't dictate how I work, I dictate how Linux works."
--Eric Crampton

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/201602060059.u160xjP9002932%40dsl092-065-009.bos1.dsl.speakeasy.net.
For more options, visit https://groups.google.com/d/optout.

Re: [hugin-ptx] Very weird runtime error

[Robert Krawitz]

On Sat, 6 Feb 2016 12:04:22 +1100, Greg 'groggy' Lehey wrote:
> On Friday,  5 February 2016 at 19:59:45 -0500, Robert Krawitz wrote:
>> I'm getting a rather strange runtime error.  Running openSUSE Leap
>> 42.1, building my own package from hg:
>>
>> $ /usr/bin/hugin
>> Fatal Error: Mismatch between the program and library build versions 
>> detected.
>> The library used 2.8 (no debug,Unicode,compiler with C++ ABI 1002,STL 
>> containers,compatible with 2.6),
>> and your program used 2.8 (no debug,Unicode,compiler with C++ ABI 1009,STL 
>> containers,compatible with 2.6).
>> Aborted
>
> I would have thought that that error message is particularly clear,
> modulo mentioning the name of the library.  Do you need help moving
> between ABI versions?

ABI versions of what?
-- 
Robert Krawitz <r...@alum.mit.edu>

***  MIT Engineers   A Proud Tradition   http://mitathletics.com  ***
Member of the League for Programming Freedom  --  http://ProgFree.org
Project lead for Gutenprint   --http://gimp-print.sourceforge.net

"Linux doesn't dictate how I work, I dictate how Linux works."
--Eric Crampton

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/201602060113.u161Dn41003142%40dsl092-065-009.bos1.dsl.speakeasy.net.
For more options, visit https://groups.google.com/d/optout.

[hugin-ptx] Makefile overwritten

[Robert Krawitz]

If you do an in-tree build (I know...not recommended),
src/hugin1/hugin/xrc/data/help_en_EN/Makefile gets overwritten in the
build process, leaving a modified file in the tree.

-- 
Robert Krawitz r...@alum.mit.edu

***  MIT Engineers   A Proud Tradition   http://mitathletics.com  ***
Member of the League for Programming Freedom  --  http://ProgFree.org
Project lead for Gutenprint   --http://gimp-print.sourceforge.net

Linux doesn't dictate how I work, I dictate how Linux works.
--Eric Crampton

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
hugin and other free panoramic software group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/201507031857.t63Iv08m031452%40dsl092-065-009.bos1.dsl.speakeasy.net.
For more options, visit https://groups.google.com/d/optout.

[hugin-ptx] Compile problem with current repository

[Robert Krawitz]

[  2%] Building C object src/foreign/levmar/CMakeFiles/huginlevmar.dir/lmlec.c.o
In file included from /home/rlk/sandbox/hugin/src/foreign/levmar/lmlec.c:72:0:
/home/rlk/sandbox/hugin/src/foreign/levmar/lmlec_core.c: In function 
‘dlevmar_lec_dif’:
/home/rlk/sandbox/hugin/src/foreign/levmar/lmlec_core.c:605:3: warning: passing 
argument 2 of ‘dlevmar_dif’ from incompatible pointer type [enabled by default]
   ret=LEVMAR_DIF(LMLEC_FUNC, pp, x, mm, n, itmax, opts, info, work, NULL, 
(void *)data);
   ^
In file included from /home/rlk/sandbox/hugin/src/foreign/levmar/lmlec.c:30:0:
/home/rlk/sandbox/hugin/src/foreign/levmar/levmar.h:113:12: note: expected ‘int 
(*)(double *, double *, int,  int,  int,  double,  void *)’ but argument is of 
type ‘double *’
 extern int dlevmar_dif(
^
In file included from /home/rlk/sandbox/hugin/src/foreign/levmar/lmlec.c:72:0:
/home/rlk/sandbox/hugin/src/foreign/levmar/lmlec_core.c:605:3: warning: passing 
argument 4 of ‘dlevmar_dif’ makes pointer from integer without a cast [enabled 
by default]
   ret=LEVMAR_DIF(LMLEC_FUNC, pp, x, mm, n, itmax, opts, info, work, NULL, 
(void *)data);
   ^
In file included from /home/rlk/sandbox/hugin/src/foreign/levmar/lmlec.c:30:0:
/home/rlk/sandbox/hugin/src/foreign/levmar/levmar.h:113:12: note: expected 
‘double *’ but argument is of type ‘int’
 extern int dlevmar_dif(
^
In file included from /home/rlk/sandbox/hugin/src/foreign/levmar/lmlec.c:72:0:
/home/rlk/sandbox/hugin/src/foreign/levmar/lmlec_core.c:605:3: warning: passing 
argument 7 of ‘dlevmar_dif’ makes integer from pointer without a cast [enabled 
by default]
   ret=LEVMAR_DIF(LMLEC_FUNC, pp, x, mm, n, itmax, opts, info, work, NULL, 
(void *)data);
   ^
In file included from /home/rlk/sandbox/hugin/src/foreign/levmar/lmlec.c:30:0:
/home/rlk/sandbox/hugin/src/foreign/levmar/levmar.h:113:12: note: expected 
‘int’ but argument is of type ‘double *’
 extern int dlevmar_dif(
^
In file included from /home/rlk/sandbox/hugin/src/foreign/levmar/lmlec.c:72:0:
/home/rlk/sandbox/hugin/src/foreign/levmar/lmlec_core.c:605:3: error: too few 
arguments to function ‘dlevmar_dif’
   ret=LEVMAR_DIF(LMLEC_FUNC, pp, x, mm, n, itmax, opts, info, work, NULL, 
(void *)data);
   ^
In file included from /home/rlk/sandbox/hugin/src/foreign/levmar/lmlec.c:30:0:
/home/rlk/sandbox/hugin/src/foreign/levmar/levmar.h:113:12: note: declared here
 extern int dlevmar_dif(
^
src/foreign/levmar/CMakeFiles/huginlevmar.dir/build.make:123: recipe for target 
'src/foreign/levmar/CMakeFiles/huginlevmar.dir/lmlec.c.o' failed
make[2]: *** [src/foreign/levmar/CMakeFiles/huginlevmar.dir/lmlec.c.o] Error 1
CMakeFiles/Makefile2:250: recipe for target 
'src/foreign/levmar/CMakeFiles/huginlevmar.dir/all' failed
make[1]: *** [src/foreign/levmar/CMakeFiles/huginlevmar.dir/all] Error 2
Makefile:137: recipe for target 'all' failed
make: *** [all] Error 2


$ gcc -v
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib64/gcc/x86_64-suse-linux/4.8/lto-wrapper
Target: x86_64-suse-linux
Configured with: ../configure --prefix=/usr --infodir=/usr/share/info 
--mandir=/usr/share/man --libdir=/usr/lib64 --libexecdir=/usr/lib64 
--enable-languages=c,c++,objc,fortran,obj-c++,java,ada 
--enable-checking=release --with-gxx-include-dir=/usr/include/c++/4.8 
--enable-ssp --disable-libssp --disable-plugin 
--with-bugurl=http://bugs.opensuse.org/ --with-pkgversion='SUSE Linux' 
--disable-libgcj --disable-libmudflap --with-slibdir=/lib64 --with-system-zlib 
--enable-__cxa_atexit --enable-libstdcxx-allocator=new --disable-libstdcxx-pch 
--enable-version-specific-runtime-libs --enable-linker-build-id 
--enable-linux-futex --program-suffix=-4.8 --without-system-libunwind 
--with-arch-32=i586 --with-tune=generic --build=x86_64-suse-linux 
--host=x86_64-suse-linux
Thread model: posix
gcc version 4.8.3 20140627 [gcc-4_8-branch revision 212064] (SUSE Linux)

-- 
Robert Krawitz r...@alum.mit.edu

***  MIT Engineers   A Proud Tradition   http://mitathletics.com  ***
Member of the League for Programming Freedom  --  http://ProgFree.org
Project lead for Gutenprint   --http://gimp-print.sourceforge.net

Linux doesn't dictate how I work, I dictate how Linux works.
--Eric Crampton

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
hugin and other free panoramic software group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/201506250001.t5P01Al1003821%40dsl092-065-009.bos1.dsl.speakeasy.net.
For more options, visit https://groups.google.com/d/optout.

Re: [hugin-ptx] Re: Final version Hugin 2014.0.0 released

[Robert Lesac]

On 18.12.2014. 0:42, Matthew Petroff wrote:

My recent builds have been dynamically linked, instead of statically
linked as outlined on the Panotools wiki, since it makes the download
considerably smaller. I have some scattered notes from when I set up the
build environment, but they're much less detailed than what is currently
on the Panotools wiki for static builds. I might try to pull together my
notes next month and post them somewhere on the wiki, but creating any
sort of detailed instructions would require rebuilding the build
environment from scratch, which is rather time consuming.


I know that's a lot of work, so would you consider cleaning personal 
stuff from the VM and post it so we have a starting point?



Robert


-Matthew

On Monday, December 15, 2014 3:24:20 AM UTC-5, dex Otaku wrote:

On Sunday, 14 December 2014 17:23:46 UTC-6, Matthew Petroff wrote:

If someone steps up to take over, I'd be happy to give him or
her pointers.



Hi Matthew,
If you can come up with build instructions that are clearer than the
current wiki, I'd give making builds a try.
That's assuming it doesn't require any commercial dev tools.
I'm not a dev but with clear enough instructions I can manage it.

--
A list of frequently asked questions is available at:
http://wiki.panotools.org/Hugin_FAQ
---
You received this message because you are subscribed to the Google
Groups hugin and other free panoramic software group.
To unsubscribe from this group and stop receiving emails from it, send
an email to hugin-ptx+unsubscr...@googlegroups.com
mailto:hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/hugin-ptx/f0fb71a2-f794-421f-9822-aee0b934f638%40googlegroups.com
https://groups.google.com/d/msgid/hugin-ptx/f0fb71a2-f794-421f-9822-aee0b934f638%40googlegroups.com?utm_medium=emailutm_source=footer.
For more options, visit https://groups.google.com/d/optout.



--

Pano/VR/Gigapixel photography: http://robertlesac.com

--
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups hugin and other free panoramic software group.

To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/5493650D.3040707%40robertlesac.com.
For more options, visit https://groups.google.com/d/optout.

Re: [hugin-ptx] Re: Final version Hugin 2014.0.0 released

[Robert Lesac]

On 19.12.2014. 1:04, Matthew Petroff wrote:

Along with the notes, I'll upload my SDK somewhere. Since Windows isn't
FOSS, I can't post the VM.


Ha, that part slipped my mind :)

Robert


-Matthew

On Thursday, December 18, 2014 6:36:55 PM UTC-5, Robert Lesac wrote:

On 18.12.2014. 0:42, Matthew Petroff wrote:
  My recent builds have been dynamically linked, instead of statically
  linked as outlined on the Panotools wiki, since it makes the
download
  considerably smaller. I have some scattered notes from when I set
up the
  build environment, but they're much less detailed than what is
currently
  on the Panotools wiki for static builds. I might try to pull
together my
  notes next month and post them somewhere on the wiki, but
creating any
  sort of detailed instructions would require rebuilding the build
  environment from scratch, which is rather time consuming.

I know that's a lot of work, so would you consider cleaning personal
stuff from the VM and post it so we have a starting point?


Robert

  -Matthew
 
  On Monday, December 15, 2014 3:24:20 AM UTC-5, dex Otaku wrote:
 
  On Sunday, 14 December 2014 17:23:46 UTC-6, Matthew Petroff
wrote:
 
  If someone steps up to take over, I'd be happy to give
him or
  her pointers.
 
 
 
  Hi Matthew,
  If you can come up with build instructions that are clearer
than the
  current wiki, I'd give making builds a try.
  That's assuming it doesn't require any commercial dev tools.
  I'm not a dev but with clear enough instructions I can manage
it.
 
  --
  A list of frequently asked questions is available at:
  http://wiki.panotools.org/Hugin_FAQ
http://wiki.panotools.org/Hugin_FAQ
  ---
  You received this message because you are subscribed to the Google
  Groups hugin and other free panoramic software group.
  To unsubscribe from this group and stop receiving emails from it,
send
  an email to hugin-ptx+...@googlegroups.com javascript:
  mailto:hugin-ptx+...@googlegroups.com javascript:.
  To view this discussion on the web visit
 

https://groups.google.com/d/msgid/hugin-ptx/f0fb71a2-f794-421f-9822-aee0b934f638%40googlegroups.com

https://groups.google.com/d/msgid/hugin-ptx/f0fb71a2-f794-421f-9822-aee0b934f638%40googlegroups.com

 

https://groups.google.com/d/msgid/hugin-ptx/f0fb71a2-f794-421f-9822-aee0b934f638%40googlegroups.com?utm_medium=emailutm_source=footer

https://groups.google.com/d/msgid/hugin-ptx/f0fb71a2-f794-421f-9822-aee0b934f638%40googlegroups.com?utm_medium=emailutm_source=footer.

  For more options, visit https://groups.google.com/d/optout
https://groups.google.com/d/optout.


--

Pano/VR/Gigapixel photography: http://robertlesac.com

--
A list of frequently asked questions is available at:
http://wiki.panotools.org/Hugin_FAQ
---
You received this message because you are subscribed to the Google
Groups hugin and other free panoramic software group.
To unsubscribe from this group and stop receiving emails from it, send
an email to hugin-ptx+unsubscr...@googlegroups.com
mailto:hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/hugin-ptx/55b99ecf-9b34-472b-a2cc-d791fbf88871%40googlegroups.com
https://groups.google.com/d/msgid/hugin-ptx/55b99ecf-9b34-472b-a2cc-d791fbf88871%40googlegroups.com?utm_medium=emailutm_source=footer.
For more options, visit https://groups.google.com/d/optout.



--

Pano/VR/Gigapixel photography: http://robertlesac.com

--
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups hugin and other free panoramic software group.

To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/54936C76.8080703%40robertlesac.com.
For more options, visit https://groups.google.com/d/optout.

Re: [hugin-ptx] Change fast preview resolution?

[Robert Lesac]

On 28.10.2014. 1:54, Terry Duell wrote:

Hello Robert,

On Tue, 28 Oct 2014 11:41:05 +1100, Robert Lesac
rob...@robertlesac.com wrote:


Hi!
Is there a way to change the fast preview resolution?
I find it too coarse for my taste and have plenty of ram (3gb vram,
32gb ram).



The hugin preview window provides a more accurate image, but is slower
to draw.
If you haven't tried that give it a go and see if it helps.


It is more precise, but lacks features compared to fast preview.
You can't check masks or use identify.

I did take a look a the registry, but only found preferences and widow 
positions there.


Is the fast preview resolution hard coded?

cheers

--

Pano/VR/Gigapixel photography: http://robertlesac.com

--
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups hugin and other free panoramic software group.

To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/544F5A2D.8000402%40robertlesac.com.
For more options, visit https://groups.google.com/d/optout.

[hugin-ptx] Change fast preview resolution?

[Robert Lesac]

Hi!
Is there a way to change the fast preview resolution?
I find it too coarse for my taste and have plenty of ram (3gb vram, 32gb 
ram).


It would be nice if it could be exposed through preferences but I'll 
settle for whatever, config files/registry.

Thanks

--

Pano/VR/Gigapixel photography: http://robertlesac.com

--
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups hugin and other free panoramic software group.

To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/544EE621.9030301%40robertlesac.com.
For more options, visit https://groups.google.com/d/optout.

Re: [hugin-ptx] Problem with GL preview

[Robert Krawitz]

On Wed, 10 Sep 2014 00:33:53 -0700 (PDT), Brandon wrote:
 Tonight this bug is really bothering me. I have hit my undo button
 often enough that I have noticed the change that is causing the
 problem tonight. On the stitching tab if I have the canvas set to
 the optimal size (23514) the bug is not there, but if I set it
 smaller than 11750 (about half) the problem starts
 happening. Conversely if I set the output any bigger than optimal
 size it shows up. The further I get from that general range the
 worse the blurring gets.

If this is the problem I was reporting (with corruption in the GL
preview, http://rlk.smugmug.com/Photography/Hugin-demo/n-NbPQS/), then
in my case it isn't affected by canvas size (I always set the canvas
size to optimal right away).
-- 
Robert Krawitz r...@alum.mit.edu

MIT VI-3 1987 - Congrats MIT Engineers 6 straight men's hoops tourney
Tall Clubs International  --  http://www.tall.org/ or 1-888-IM-TALL-2
Member of the League for Programming Freedom  --  http://ProgFree.org
Project lead for Gutenprint   --http://gimp-print.sourceforge.net

Linux doesn't dictate how I work, I dictate how Linux works.
--Eric Crampton

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
hugin and other free panoramic software group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/201409101233.s8ACXJSl014757%40dsl092-065-009.bos1.dsl.speakeasy.net.
For more options, visit https://groups.google.com/d/optout.

Re: [hugin-ptx] Problem with GL preview

[Robert Krawitz]

On Tue, 5 Aug 2014 08:16:06 -0700 (PDT), Brandon wrote:
 I get this problem from time to time. When it is messed up, if I go through 
 the preview one image at a time I generally find that it is caused by just a 
 few pictures and not all of them are a mess.

In this case, all (or perhaps all but one) are a mess.

 Near as I can tell it is caused when optimizing some of the lens parameters(I 
 have not narrowed it down to a single one yet, currently I am thinking that 
 any of the lens settings can mess it up). My work around has been to either 
 ingorne it as it does not show up in the final pano or use the other preview. 
 If I really want to use the GL preview I have found that reseting the lens 
 parameters and optimizing again will solve the problem almost every time.

I've already optimized the same set of parameters.  Resetting the lens
parameters temporarily cleared it; when I reoptimized, it came right
back.

 For debugging I find this in both the 2012 and 2013 versions. As far as lens 
 on the camera I have found it with every camera that I have used, a point and 
 shoot as well as a 30mm and 12 mm(after adjusting for sensor size) lens.

Both of those are wide angle.  I've done some panoramas with longer
lenses than that, and generally haven't see the problem.

 I am pretty sure the problem is that the GL preview has a problem with the 
 lens optimizations from time to time. At one point I went through and messed 
 up the settings one at a time to see what each does and it is easy to take a 
 normal good looking pano and make it look like modern art with the GL 
 preview. To do that take any good pano, go to the lens tab and change any of 
 the lens settings by 2 or more whole numbers and it will be way out of whack, 
 some times it takes a lot less.

Unfortunately, the regular preview lacks a lot of features that the
GL preview offers.  The ones that matter most to me are on the fly
cropping, positioning, and exposure adjustment.  Positioning and
exposure adjustment I can work around, because there's usually enough
usable imagge.  Cropping is another matter.

 Near as I can tell the other preview does not do it.

It doesn't.
-- 
Robert Krawitz r...@alum.mit.edu

MIT VI-3 1987 - Congrats MIT Engineers 6 straight men's hoops tourney
Tall Clubs International  --  http://www.tall.org/ or 1-888-IM-TALL-2
Member of the League for Programming Freedom  --  http://ProgFree.org
Project lead for Gutenprint   --http://gimp-print.sourceforge.net

Linux doesn't dictate how I work, I dictate how Linux works.
--Eric Crampton

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
hugin and other free panoramic software group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/201408051534.s75FYHqF001250%40dsl092-065-009.bos1.dsl.speakeasy.net.
For more options, visit https://groups.google.com/d/optout.

Re: [hugin-ptx] Problem with GL preview

[Robert Krawitz]

On Wed, 06 Aug 2014 08:24:25 +1000, Terry Duell wrote:
 Hello Robert,

 On Tue, 05 Aug 2014 22:07:49 +1000, Robert Krawitz r...@alum.mit.edu  
 wrote:

 On Tue, 05 Aug 2014 12:34:31 +1000, Terry Duell wrote:

 [snip]

 OK. Can you provide a .pto from a very early stage, i.e. prior to doing
 any refinement, say just after generating control points for all images
 and no optimisation steps performed?

 Here it is.  I presume that control point generation is deterministic.

 Using this .pto (almanor-16-bad-1.pto), if I deselect images  
 1,3,5,7,9,11,12 I can then optimise everything without all hell breaking  
 loose. I optimised in steps, positions, positions and view, positions and  
 barrel, positions view and barrel, then everything. Are you able to  
 reproduce this behaviour?

It still eventually happens, after enough iterations of removing bad
points, reoptimizing everything but translation, and fine tuning all
points.  In this case, when I got the max error under 2 (average .6,
max 1.7), the problem showed up again.  This is about when I'd
typically expect it to show.  I've attached it at the point it shows up.

 Whilst this might not be an acceptable workaround for you, the mean error  
 is 3.1 pix, max 12.4, it is still considered a good fit.
 It doesn't solve the basic problem, but maybe adds a bit more info to help  
 track down the cause.

It would be helpful if there were a way to trace every operation I
perform.  My description isn't very specific, but it's very hard to be
precise when there are thousands of control points and all that.

I don't consider max 12.4 to be a good fit at all.  At that level,
there's usually some visible discontinuities in the background, where
they're most objectionable (IMO).  Maybe I'm too finicky, but I like
to get it under 1.
-- 
Robert Krawitz r...@alum.mit.edu

MIT VI-3 1987 - Congrats MIT Engineers 6 straight men's hoops tourney
Tall Clubs International  --  http://www.tall.org/ or 1-888-IM-TALL-2
Member of the League for Programming Freedom  --  http://ProgFree.org
Project lead for Gutenprint   --http://gimp-print.sourceforge.net

Linux doesn't dictate how I work, I dictate how Linux works.
--Eric Crampton

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
hugin and other free panoramic software group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/201408052249.s75MngRt003128%40dsl092-065-009.bos1.dsl.speakeasy.net.
For more options, visit https://groups.google.com/d/optout.


almanor-16-bad-2.pto
Description: Binary data

[hugin-ptx] Problem with GL preview

[Robert Krawitz]

I've observed a problem with the GL preview that makes it very hard to
use for many of my panoramas.  Particularly when I use a wide angle
lens, I find that after I do enough optimization steps the preview
gets badly garbled such that it's essentially unusable.  If I use a
normal or short telephoto lens, this usually doesn't happen.

The sequence of steps I usually use is:

1) Create control points

2) Perform an initial optimization step, then do position/view/barrel
   distortion, then optimize everything except translation (lens
   distortion is significant with my 8-16).

3) Use the GL viewer to center and straighten the pano.

4) Calculate optimal size and FoV in the stitch panel (I hate that
   3000 pixel size that all panos start with; it's one extra step I
   have to do).

5) Crop out foreground and sky CP's (Celeste isn't perfect, and I
   usually don't use a tripod much less a pano head) and re-optimize.

6) Remove all control points except between adjacent images (I shoot
   panos with a lot of overlap, and I've found that control points
   between non-adjacent images lead to larger errors in the output).

7) Crop out any foreground points that made it through the original
   crop, and other control points with a lot of error (carefully -- I
   want to make sure that the points with large error are actual bad
   points; if there are a lot of foreground points, sometimes the good
   points are the ones with large residual error).  I run multiple
   passes, gradually bringing down the acceptable error.  At this
   stage I usually try to get it down to about 3 units.

8) Fine tune all points, remove all points with correlation
   coefficient less than 0.8, reoptimize, remove the points that the
   fine tune botched.

9) Continue with iterative optimization until I get worst case error
   under 1 unit.

10) Do photometric optimization.

Anyway, at some point during all of this the preview gets garbled.  I
found a particular case with a particular pano where the GL preview is
good, but the next optimization step results in a garbled preview.

The original images in question are all in
http://rlk.smugmug.com/Photography/Hugin-demo/n-NbPQS/ .  The good
preview is
http://rlk.smugmug.com/Photography/Hugin-demo/n-NbPQS/i-tmdKB7J; the
next optimization step results in
http://rlk.smugmug.com/Photography/Hugin-demo/n-NbPQS/i-vSbVSWP .
This is independent of projection (at least equirectangular and
Mercator).

The .pto file is attached.

In case it matters, I'm using the current repository (although this
problem has been around for at least a few years, I think) with a
Radeon HD5870 using the radeon driver with kernel 3.11.10 and the
following Mesa bits:

DirectFB-Mesa-1.6.3-4.1.3.x86_64
Mesa-10.2.4-381.1.x86_64
Mesa-32bit-10.2.4-381.1.x86_64
Mesa-demo-8.2.0-37.2.x86_64
Mesa-demo-x-8.2.0-37.2.x86_64
Mesa-devel-10.2.4-381.1.x86_64
Mesa-libEGL-devel-10.2.4-381.1.x86_64
Mesa-libEGL1-10.2.4-381.1.x86_64
Mesa-libEGL1-32bit-10.2.4-381.1.x86_64
Mesa-libGL-devel-10.2.4-381.1.x86_64
Mesa-libGL1-10.2.4-381.1.x86_64
Mesa-libGL1-32bit-10.2.4-381.1.x86_64
Mesa-libGLESv1_CM-devel-10.2.4-381.1.x86_64
Mesa-libGLESv1_CM1-10.2.4-381.1.x86_64
Mesa-libGLESv2-2-10.2.4-381.1.x86_64
Mesa-libGLESv2-devel-10.2.4-381.1.x86_64
Mesa-libglapi-devel-10.2.4-381.1.x86_64
Mesa-libglapi0-10.2.4-381.1.x86_64
Mesa-libglapi0-32bit-10.2.4-381.1.x86_64
libOSMesa-devel-10.2.4-381.1.x86_64
libOSMesa9-10.2.4-381.1.x86_64
libOSMesa9-32bit-10.2.4-381.1.x86_64

-- 
Robert Krawitz r...@alum.mit.edu

MIT VI-3 1987 - Congrats MIT Engineers 6 straight men's hoops tourney
Tall Clubs International  --  http://www.tall.org/ or 1-888-IM-TALL-2
Member of the League for Programming Freedom  --  http://ProgFree.org
Project lead for Gutenprint   --http://gimp-print.sourceforge.net

Linux doesn't dictate how I work, I dictate how Linux works.
--Eric Crampton

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
hugin and other free panoramic software group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/201408050153.s751rZq9027345%40dsl092-065-009.bos1.dsl.speakeasy.net.
For more options, visit https://groups.google.com/d/optout.


almanor-16-bad.pto
Description: Binary data

Re: [hugin-ptx] Problem with GL preview

[Robert Krawitz]

On Tue, 05 Aug 2014 12:22:26 +1000, Terry Duell wrote:
 Hello Robert,

 On Tue, 05 Aug 2014 11:53:35 +1000, Robert Krawitz r...@alum.mit.edu  
 wrote:

 I've observed a problem with the GL preview that makes it very hard to
 use for many of my panoramas.  Particularly when I use a wide angle
 lens, I find that after I do enough optimization steps the preview
 gets badly garbled such that it's essentially unusable.  If I use a
 normal or short telephoto lens, this usually doesn't happen.

 The sequence of steps I usually use is:


 [snip]

 6) Remove all control points except between adjacent images (I shoot
panos with a lot of overlap, and I've found that control points
between non-adjacent images lead to larger errors in the output).


 I see the problem here, I'm running Hugin-2014.1.0 (current development  
 source).
 When I first open your .pto all is OK, but it quickly goes haywire when  
 any refinement is done.

Correct, but at this point I've already performed quite a bit of
refinement without hitting the problem.

 I note your comment (6), above, but wonder if you still have the problem  
 is you try to stitch with less overlap, say leaving out every second image.
 I can't try that here as I only have dummy images and there aren't the  
 control points between the non adjacent images.

Even if I remove all but one image from the viewer, I have the same
problem.
-- 
Robert Krawitz r...@alum.mit.edu

MIT VI-3 1987 - Congrats MIT Engineers 6 straight men's hoops tourney
Tall Clubs International  --  http://www.tall.org/ or 1-888-IM-TALL-2
Member of the League for Programming Freedom  --  http://ProgFree.org
Project lead for Gutenprint   --http://gimp-print.sourceforge.net

Linux doesn't dictate how I work, I dictate how Linux works.
--Eric Crampton

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
hugin and other free panoramic software group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/201408050225.s752PvkM027482%40dsl092-065-009.bos1.dsl.speakeasy.net.
For more options, visit https://groups.google.com/d/optout.

Re: [hugin-ptx] Re: Hugin 2014 RC4 windows x64 build?

[Robert Lesac]

Hi,
There is only the 32bit version of RC4 there.

Robert

On 1.7.2014. 19:23, Harry van der Wolf wrote:

See http://sourceforge.net/projects/hugin/files/hugin/hugin-2014.0/

Harry


2014-07-01 13:00 GMT+02:00 Robert Lesac rob...@robertlesac.com
mailto:rob...@robertlesac.com:

I found a mention of the RC4 64bit windows build on Launchpad (butil
matthewpetroff), but can't find the file for download.
Any idea where I could find it?

Thanks!


On Monday, June 30, 2014 8:43:27 PM UTC+2, Robert Lesac wrote:

Hi!
Would someone be kind enough to build the x64 version?

Thanks!

--

Pano/VR/Gigapixel photography: http://robertlesac.com

--
A list of frequently asked questions is available at:
http://wiki.panotools.org/Hugin_FAQ
---
You received this message because you are subscribed to the Google
Groups hugin and other free panoramic software group.
To unsubscribe from this group and stop receiving emails from it,
send an email to hugin-ptx+unsubscr...@googlegroups.com
mailto:hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit

https://groups.google.com/d/msgid/hugin-ptx/ee878470-d5d8-4461-b48d-dd344302d8da%40googlegroups.com

https://groups.google.com/d/msgid/hugin-ptx/ee878470-d5d8-4461-b48d-dd344302d8da%40googlegroups.com?utm_medium=emailutm_source=footer.

For more options, visit https://groups.google.com/d/optout.


--
A list of frequently asked questions is available at:
http://wiki.panotools.org/Hugin_FAQ
---
You received this message because you are subscribed to the Google
Groups hugin and other free panoramic software group.
To unsubscribe from this group and stop receiving emails from it, send
an email to hugin-ptx+unsubscr...@googlegroups.com
mailto:hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/hugin-ptx/CAGARPptBHxBGutrmmevX8US1kWw8QVRHCrYnxV1CNhA_5eHW-Q%40mail.gmail.com
https://groups.google.com/d/msgid/hugin-ptx/CAGARPptBHxBGutrmmevX8US1kWw8QVRHCrYnxV1CNhA_5eHW-Q%40mail.gmail.com?utm_medium=emailutm_source=footer.
For more options, visit https://groups.google.com/d/optout.



--

Pano/VR/Gigapixel photography: http://robertlesac.com

--
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups hugin and other free panoramic software group.

To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/53B3C1C9.3000709%40robertlesac.com.
For more options, visit https://groups.google.com/d/optout.

Re: [hugin-ptx] Re: Hugin 2014 RC4 windows x64 build?

[Robert Lesac]

Hi,
I was referring to this launchpad bug: 
https://bugs.launchpad.net/hugin/+bug/1335231
There is a mention of 64bit debug build, but for the life of me I can't 
find where is it.


On Tuesday, July 1, 2014 7:23:03 PM UTC+2, Harry van der Wolf wrote:

 See http://sourceforge.net/projects/hugin/files/hugin/hugin-2014.0/

 Harry


 2014-07-01 13:00 GMT+02:00 Robert Lesac rob...@robertlesac.com 
 javascript::

 I found a mention of the RC4 64bit windows build on Launchpad (butil 
 matthewpetroff), but can't find the file for download.
 Any idea where I could find it?

 Thanks!


 On Monday, June 30, 2014 8:43:27 PM UTC+2, Robert Lesac wrote:

 Hi! 
 Would someone be kind enough to build the x64 version? 

 Thanks! 

 -- 

 Pano/VR/Gigapixel photography: http://robertlesac.com 

  -- 
 A list of frequently asked questions is available at: 
 http://wiki.panotools.org/Hugin_FAQ
 --- 
 You received this message because you are subscribed to the Google Groups 
 hugin and other free panoramic software group.
 To unsubscribe from this group and stop receiving emails from it, send an 
 email to hugin-ptx+...@googlegroups.com javascript:.
 To view this discussion on the web visit 
 https://groups.google.com/d/msgid/hugin-ptx/ee878470-d5d8-4461-b48d-dd344302d8da%40googlegroups.com
  
 https://groups.google.com/d/msgid/hugin-ptx/ee878470-d5d8-4461-b48d-dd344302d8da%40googlegroups.com?utm_medium=emailutm_source=footer
 .

 For more options, visit https://groups.google.com/d/optout.




-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
hugin and other free panoramic software group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/a0d30209-8531-4b76-a122-056433736487%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[hugin-ptx] Re: Hugin 2014 RC4 windows x64 build?

[Robert Lesac]

I found a mention of the RC4 64bit windows build on Launchpad (butil 
matthewpetroff), but can't find the file for download.
Any idea where I could find it?

Thanks!

On Monday, June 30, 2014 8:43:27 PM UTC+2, Robert Lesac wrote:

 Hi! 
 Would someone be kind enough to build the x64 version? 

 Thanks! 

 -- 

 Pano/VR/Gigapixel photography: http://robertlesac.com 


-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
hugin and other free panoramic software group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/ee878470-d5d8-4461-b48d-dd344302d8da%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[hugin-ptx] Hugin 2014 RC4 windows x64 build?

[Robert Lesac]

Hi!
Would someone be kind enough to build the x64 version?

Thanks!

--

Pano/VR/Gigapixel photography: http://robertlesac.com

--
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups hugin and other free panoramic software group.

To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/53B1AFC6.5050509%40robertlesac.com.
For more options, visit https://groups.google.com/d/optout.

Re: [hugin-ptx] Hugin 2014.0RC3 release

[Robert Lesac]

Hi,

any chance for a windows x64 build?

On 18.5.2014. 11:53, Harry van der Wolf wrote:

Hi all,

Unfortunately it was necessary to do an RC3 release as we had some
serious bugs in our RC series.

See below the release notes for the Hugin 2014 RC3 release.

The full ChangeLog can be found in the source tarball.




--

Pano/VR/Gigapixel photography: http://robertlesac.com

--
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups hugin and other free panoramic software group.

To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/537B9389.1060104%40robertlesac.com.
For more options, visit https://groups.google.com/d/optout.

[hugin-ptx] Problem w/latest repository and wxWidgets 2.8.12

[Robert Krawitz]

Looks like wxSpinCtrl in at least 2.8.12 doesn't have a SetMax member.

diff -r 365250f51eec src/hugin1/hugin/PanoOperation.cpp
--- a/src/hugin1/hugin/PanoOperation.cppSat May 17 09:56:14 2014 +0200
+++ b/src/hugin1/hugin/PanoOperation.cppSat May 17 11:58:01 2014 -0400
@@ -1204,7 +1204,7 @@
 wxDialog dlg;
 wxXmlResource::Get()-LoadDialog(dlg, parent, wxT(stack_size_dialog));
 wxSpinCtrl* stackSpin = XRCCTRL(dlg, stack_size_spinctrl, wxSpinCtrl);
-stackSpin-SetMax(pano.getNrOfImages());
+stackSpin-SetRange(stackSpin-GetMin(), pano.getNrOfImages());
 size_t oldStackSize = cfg-Read(wxT(/StackDialog/StackSize), 3);
 oldStackSize = std::min(oldStackSize, pano.getNrOfImages());
 stackSpin-SetValue(oldStackSize);


-- 
Robert Krawitz r...@alum.mit.edu

MIT VI-3 1987 - Congrats MIT Engineers 6 straight men's hoops tourney
Tall Clubs International  --  http://www.tall.org/ or 1-888-IM-TALL-2
Member of the League for Programming Freedom  --  http://ProgFree.org
Project lead for Gutenprint   --http://gimp-print.sourceforge.net

Linux doesn't dictate how I work, I dictate how Linux works.
--Eric Crampton

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
hugin and other free panoramic software group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/201405171600.s4HG05pl017839%40dsl092-065-009.bos1.dsl.speakeasy.net.
For more options, visit https://groups.google.com/d/optout.

Re: [hugin-ptx] Re: Problem w/latest repository and wxWidgets 2.8.12

[Robert Krawitz]

On Sat, 17 May 2014 10:14:45 -0700 (PDT), T. Modes wrote:
 Thanks, fixed in repository.

Looks like the fix is only on the 2014.0 branch, not the mainline?

 Am Samstag, 17. Mai 2014 18:00:05 UTC+2 schrieb rlk:

 Looks like wxSpinCtrl in at least 2.8.12 doesn't have a SetMax member. 

 diff -r 365250f51eec src/hugin1/hugin/PanoOperation.cpp 
 --- a/src/hugin1/hugin/PanoOperation.cppSat May 17 09:56:14 2014 
 +0200 
 +++ b/src/hugin1/hugin/PanoOperation.cppSat May 17 11:58:01 2014 
 -0400 
 @@ -1204,7 +1204,7 @@ 
  wxDialog dlg; 
  wxXmlResource::Get()-LoadDialog(dlg, parent, 
 wxT(stack_size_dialog)); 
  wxSpinCtrl* stackSpin = XRCCTRL(dlg, stack_size_spinctrl, 
 wxSpinCtrl); 
 -stackSpin-SetMax(pano.getNrOfImages()); 
 +stackSpin-SetRange(stackSpin-GetMin(), pano.getNrOfImages()); 
  size_t oldStackSize = cfg-Read(wxT(/StackDialog/StackSize), 3); 
  oldStackSize = std::min(oldStackSize, pano.getNrOfImages()); 
  stackSpin-SetValue(oldStackSize); 

-- 
Robert Krawitz r...@alum.mit.edu

MIT VI-3 1987 - Congrats MIT Engineers 6 straight men's hoops tourney
Tall Clubs International  --  http://www.tall.org/ or 1-888-IM-TALL-2
Member of the League for Programming Freedom  --  http://ProgFree.org
Project lead for Gutenprint   --http://gimp-print.sourceforge.net

Linux doesn't dictate how I work, I dictate how Linux works.
--Eric Crampton

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
hugin and other free panoramic software group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/201405172058.s4HKwNha019034%40dsl092-065-009.bos1.dsl.speakeasy.net.
For more options, visit https://groups.google.com/d/optout.

[hugin-ptx] Hugin 2014.rc1 and Python scripting, doesn't work

[Robert Lesac]

Hi,
I wanted to try out the new scripting interface, but for the life of me 
can't get it to work.
Setup: HuginSetup_2014.0.0-rc1_64bit_Windows_Python + Python 3.3.5 + Win7 
64x
From the Hugin interface all scripts return -1.

Manually running a script complains about HSI not being available, so I 
copied HSI.* to the scripts directory and the script will run from the 
command line.
From Hugin I still get the same error.

Trying 'import hsi' from the Python interpreter just gets me a complaint 
'ImportError: No module named 'hsi''.
Seems to me it might be a path mixup, any ideas how to fix it?


Thanks!

-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
hugin and other free panoramic software group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/b66baca8-aaac-4e53-b7fe-2c098f28ef7f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[hugin-ptx] Re: Hugin 2014.rc1 and Python scripting, doesn't work

[Robert Lesac]

Update:
Added PYTHONPATH (pointing to the hugin/bin) to my system variables, didn't 
help with Hugin, but Python now imports HSI successfully.

On Sunday, March 23, 2014 2:35:14 PM UTC+1, Robert Lesac wrote:

 Hi,
 I wanted to try out the new scripting interface, but for the life of me 
 can't get it to work.
 Setup: HuginSetup_2014.0.0-rc1_64bit_Windows_Python + Python 3.3.5 + Win7 
 64x
 From the Hugin interface all scripts return -1.

 Manually running a script complains about HSI not being available, so I 
 copied HSI.* to the scripts directory and the script will run from the 
 command line.
 From Hugin I still get the same error.

 Trying 'import hsi' from the Python interpreter just gets me a complaint 
 'ImportError: No module named 'hsi''.
 Seems to me it might be a path mixup, any ideas how to fix it?


 Thanks!



-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
hugin and other free panoramic software group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/74fac189-a2bb-49a0-a150-a322bc0f8f6f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [hugin-ptx] Re: Hugin 2014.rc1 and Python scripting, doesn't work

[Robert Lesac]

Hi,
There is no RC2 build for for Windows yet.
At least I can stop muck around trying to fix it.
Thanks!

On Sunday, March 23, 2014 5:43:16 PM UTC+1, Stefan Peter wrote:

 On 23.03.2014 15:41, Robert Lesac wrote: 
  Update: 
  Added PYTHONPATH (pointing to the hugin/bin) to my system variables, 
  didn't help with Hugin, but Python now imports HSI successfully. 

 Python scripting was broken with RC1, try RC2 (no idea if RC2 has been 
 packaged for Mac though). 


  
  On Sunday, March 23, 2014 2:35:14 PM UTC+1, Robert Lesac wrote: 
  
  Hi, 
  I wanted to try out the new scripting interface, but for the life of 
  me can't get it to work. 
  Setup: HuginSetup_2014.0.0-rc1_64bit_Windows_Python + Python 3.3.5 + 
  Win7 64x 
  From the Hugin interface all scripts return -1. 
  
  Manually running a script complains about HSI not being available, 
  so I copied HSI.* to the scripts directory and the script will run 
  from the command line. 
  From Hugin I still get the same error. 
  
  Trying 'import hsi' from the Python interpreter just gets me a 
  complaint 'ImportError: No module named 'hsi''. 
  Seems to me it might be a path mixup, any ideas how to fix it? 
  
  
  Thanks! 
  
  -- 
  A list of frequently asked questions is available at: 
  http://wiki.panotools.org/Hugin_FAQ 
  --- 
  You received this message because you are subscribed to the Google 
  Groups hugin and other free panoramic software group. 
  To unsubscribe from this group and stop receiving emails from it, send 
  an email to hugin-ptx+...@googlegroups.com javascript: 
  mailto:hugin-ptx+...@googlegroups.com javascript:. 
  To view this discussion on the web visit 
  
 https://groups.google.com/d/msgid/hugin-ptx/74fac189-a2bb-49a0-a150-a322bc0f8f6f%40googlegroups.com
  
  
 https://groups.google.com/d/msgid/hugin-ptx/74fac189-a2bb-49a0-a150-a322bc0f8f6f%40googlegroups.com?utm_medium=emailutm_source=footer.
  

  For more options, visit https://groups.google.com/d/optout. 


 -- 
 In summary, I think you are trying to solve a problem that may not 
 need to be solved, using a tool that is not meant to solve it, without 
 understanding what is causing your problems and without knowing how 
 the tool actually works in the first place :) 
 Jeffrey J. Kosowsky on the backuppc mailing list 



-- 
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- 
You received this message because you are subscribed to the Google Groups 
hugin and other free panoramic software group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/d39fbf5a-cacd-48b8-83e4-b30c962ab2d7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[hugin-ptx] Autocrop

[Robert Krawitz]

Autocrop is very useful, but there are several additional things in the
fast preview that I think would make it more useful based on building 25
panoramas over the past week:

1) Dynamically display (and allow values to be input) the width, height,
   and form factor of the result, not just the margins (and update them
   while the mouse is being dragged, not just at the end).

2) An interactive mode whereby when you drag an edge (or corner) of the
   crop frame, Hugin calculates the best crop region (optionally
   constrained by form factor) with that edge or corner constrained.
   The UI would not allow the edge or corner in question to be moved
   outside the image.  As an intermediate possibility, only update the
   other margins when the drag is complete.

3) Crop to the outer envelope of the panorama, so that the entire output
   is contained in the result.  Currently, autocrop attempts to find the
   greatest rectilinear area that is entirely enclosed within the image
   (an inner envelope, if you will).

These are ranked in order of importance (to me).
-- 
Robert Krawitz r...@alum.mit.edu

MIT VI-3 1987 - Congrats MIT Engineers 5 straight men's hoops tourney
Tall Clubs International  --  http://www.tall.org/ or 1-888-IM-TALL-2
Member of the League for Programming Freedom  --  http://ProgFree.org
Project lead for Gutenprint   --http://gimp-print.sourceforge.net

Linux doesn't dictate how I work, I dictate how Linux works.
--Eric Crampton

-- 
-- 
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 hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx

--- 
You received this message because you are subscribed to the Google Groups 
hugin and other free panoramic software group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [hugin-ptx] Re: Hugin 2013.0beta1 released

[Robert Alatalo]

No, I made sure not to download the python version.
I created a video of the problem, probably won't help fix the issue but
will explain what I am doing.  Unfortunately, it's .10 GB (1,189,510,144
bytes) AVI and I need to convert it to something smaller or free up a
little space on my google drive so I can upload it.  Running it though
Handbrake got it down to 5.00 MB (5,246,976 bytes)

Video can be seen:
https://docs.google.com/file/d/0B9czjrB4DYWoR2V6cU1FaUU4bzg/edit?usp=sharing

I don't expect it to provide a quick solution, but hopefully someone can
help me gather some additional data to improve things.

thanks,
Robert






On Fri, May 3, 2013 at 5:55 AM, dex Otaku dexot...@gmail.com wrote:

 On Monday, 29 April 2013 17:57:51 UTC-5, Robert Alatalo wrote:

 I wanted to try out the latest version ( 2013.0.beta1 ) but after it sets
 everything up, it crashes when I try to build the panoramic image.
 I uninstalled and installed latest 2012 windows 64 version and that
 worked, uninstalled that and retested the 2013.0.beta1 and it still failed.
 Reloaded the defaults from preferences, I am running on windows 7 x64,
 should be current with patches.

 Robert - are you trying to run the python-enabled version without having
 python installed?

 --
 --
 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 hugin-ptx@googlegroups.com
 To unsubscribe from this group, send email to
 hugin-ptx+unsubscr...@googlegroups.com
 For more options, visit this group at
 http://groups.google.com/group/hugin-ptx

 ---
 You received this message because you are subscribed to the Google Groups
 hugin and other free panoramic software group.
 To unsubscribe from this group and stop receiving emails from it, send an
 email to hugin-ptx+unsubscr...@googlegroups.com.
 For more options, visit https://groups.google.com/groups/opt_out.




-- 
-- 
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 hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx

--- 
You received this message because you are subscribed to the Google Groups 
hugin and other free panoramic software group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [hugin-ptx] Re: Hugin 2013.0beta1 released

[Robert Alatalo]

Wow... great... thanks, and good to know it's already been fixed.
-Robert


On Tue, May 7, 2013 at 4:04 PM, T. Modes thomas.mo...@gmx.de wrote:

 
  I don't expect it to provide a quick solution, but hopefully someone can
  help me gather some additional data to improve things.

 Okay, found the bug. It is fixed in the repository. Should be work in
 the next version (probably beta2).

 As a workaround: don't use create pano in the assistant tab. Instead
 open panorama editor (View-Panorama editor), then go to stitcher tab
 and press stitch there.

 --
 --
 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 hugin-ptx@googlegroups.com
 To unsubscribe from this group, send email to
 hugin-ptx+unsubscr...@googlegroups.com
 For more options, visit this group at
 http://groups.google.com/group/hugin-ptx

 ---
 You received this message because you are subscribed to the Google Groups
 hugin and other free panoramic software group.
 To unsubscribe from this group and stop receiving emails from it, send an
 email to hugin-ptx+unsubscr...@googlegroups.com.
 For more options, visit https://groups.google.com/groups/opt_out.




-- 
-- 
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 hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx

--- 
You received this message because you are subscribed to the Google Groups 
hugin and other free panoramic software group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [hugin-ptx] Re: Hugin 2013.0beta1 released

[Robert Alatalo]

Hello,

What log should I look for, and there was no error from the application
only the windows generated one about detecting a problem and looking for a
solution and killing the application.

Sorry for not being very helpful, please help me be more helpful.  If this
was Solaris I would truss the process and look for corefile and more, but
on windows I am at a loss.

C:\PROGRA~1\Hugindir /s *log
 Volume in drive C is Acer
 Volume Serial Number is 240B-EA36
File Not Found

Can I enable better logging or otherwise collect additional data to be
useful?

thanks,
Robert


On Thu, May 2, 2013 at 12:15 PM, T. Modes thomas.mo...@gmx.de wrote:

 Hi Robert,

 On 30 Apr., 00:57, Robert Alatalo wrote:
  Hello,
 
  I wanted to try out the latest version ( 2013.0.beta1 ) but after it sets
  everything up, it crashes when I try to build the panoramic image.
  I uninstalled and installed latest 2012 windows 64 version and that
 worked,
  uninstalled that and retested the 2013.0.beta1 and it still failed.
  Reloaded the defaults from preferences, I am running on windows 7 x64,
  should be current with patches.
 

 that's very unspecific. What are you doing exactly? And what is
 happening?
 Is there an error message? Or can be something seen in the log?

 Thomas

 --
 --
 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 hugin-ptx@googlegroups.com
 To unsubscribe from this group, send email to
 hugin-ptx+unsubscr...@googlegroups.com
 For more options, visit this group at
 http://groups.google.com/group/hugin-ptx

 ---
 You received this message because you are subscribed to the Google Groups
 hugin and other free panoramic software group.
 To unsubscribe from this group and stop receiving emails from it, send an
 email to hugin-ptx+unsubscr...@googlegroups.com.
 For more options, visit https://groups.google.com/groups/opt_out.




-- 
-- 
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 hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx

--- 
You received this message because you are subscribed to the Google Groups 
hugin and other free panoramic software group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [hugin-ptx] Re: Hugin 2013.0beta1 released

[Robert Alatalo]

More precisely as to what I was doing.
I had already:
1) imported the 4 jpg images. ( from Nikon D600, fine setting )
2) let the system pick control points and align the images
3) cropped and otherwise adjusted the view to what I wanted

I was pushing the button to create the final image, and there was no
further messages or indications of progress and then a couple (not very
long) time windows reported that the application had failed.

thanks,
Robert


On Fri, May 3, 2013 at 6:21 AM, Robert Alatalo ralat...@gmail.com wrote:

 Hello,

 What log should I look for, and there was no error from the application
 only the windows generated one about detecting a problem and looking for a
 solution and killing the application.

 Sorry for not being very helpful, please help me be more helpful.  If this
 was Solaris I would truss the process and look for corefile and more, but
 on windows I am at a loss.

 C:\PROGRA~1\Hugindir /s *log
  Volume in drive C is Acer
  Volume Serial Number is 240B-EA36
 File Not Found

 Can I enable better logging or otherwise collect additional data to be
 useful?

 thanks,
 Robert


 On Thu, May 2, 2013 at 12:15 PM, T. Modes thomas.mo...@gmx.de wrote:

 Hi Robert,

 On 30 Apr., 00:57, Robert Alatalo wrote:
  Hello,
 
  I wanted to try out the latest version ( 2013.0.beta1 ) but after it
 sets
  everything up, it crashes when I try to build the panoramic image.
  I uninstalled and installed latest 2012 windows 64 version and that
 worked,
  uninstalled that and retested the 2013.0.beta1 and it still failed.
  Reloaded the defaults from preferences, I am running on windows 7 x64,
  should be current with patches.
 

 that's very unspecific. What are you doing exactly? And what is
 happening?
 Is there an error message? Or can be something seen in the log?

 Thomas

 --
 --
 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 hugin-ptx@googlegroups.com
 To unsubscribe from this group, send email to
 hugin-ptx+unsubscr...@googlegroups.com
 For more options, visit this group at
 http://groups.google.com/group/hugin-ptx

 ---
 You received this message because you are subscribed to the Google Groups
 hugin and other free panoramic software group.
 To unsubscribe from this group and stop receiving emails from it, send an
 email to hugin-ptx+unsubscr...@googlegroups.com.
 For more options, visit https://groups.google.com/groups/opt_out.





-- 
-- 
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 hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx

--- 
You received this message because you are subscribed to the Google Groups 
hugin and other free panoramic software group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[hugin-ptx] Re: Hugin 2013.0beta1 released

[Robert Alatalo]

Hello,

I wanted to try out the latest version ( 2013.0.beta1 ) but after it sets 
everything up, it crashes when I try to build the panoramic image. 
I uninstalled and installed latest 2012 windows 64 version and that worked, 
uninstalled that and retested the 2013.0.beta1 and it still failed.
Reloaded the defaults from preferences, I am running on windows 7 x64, 
should be current with patches.

I can share the pictures or am willing to run any tests, etc..
I support Unix but not windows so I am not sure if there is a core file or 
not, I didn't see that it reported creating one, so I am not sure how best 
to assist.

thanks,
Robert


On Sunday, March 3, 2013 3:23:15 PM UTC-5, Harry van der Wolf wrote:

 Hugin-2013.0 RELEASE NOTES

 ABOUT

 Hugin is more than just a panorama stitcher. 

 Hugin can be found at
 * SourceForge:  http://hugin.sourceforge.net/
 * Launchpad:https://launchpad.net/hugin


 DOWNLOAD

 The 2013.0 source tarball can be downloaded

 * from SourceForge at

 http://sourceforge.net/projects/hugin/files/hugin/hugin-2013.0/hugin-2013.0.0_beta1.tar.bz2/download

 * from Launchpad at

 https://launchpad.net/hugin/2013.0/2013.0beta1/+download/hugin-2013.0.0_beta1.tar.bz2

 This is a source code release.  For executables see below.

 This tarball is equivalent to rev/changeset b7f603b17a69 in our Mercurial
 repository, where it is also tagged 2013.0.0beta1

 Verify its SHA1SUM
 8b13bd71eb9a7e318fb2fcb119803c44896c0143  hugin-2013.0.0beta1.tar.bz2

 EXECUTABLES

 Users communities produce executables for their respective platforms.

 These executables are then added to the download section on SourceForge at
 http://sourceforge.net/projects/hugin/files/hugin/

 A number of users have built recent snapshots and executables are likely 
 to be
 announced within a few days of this tarball release.

 Watch http://groups.google.com/group/hugin-ptx for the announcements of 
 binary
 releases.  If you don't see a binary for your platform it has most likely 
 not
 been produced yet.  Consider stepping up to the task.  Instructions at


 http://wiki.panotools.org/Development_of_Open_Source_tools#Supported_Platforms

 Announce your build on http://groups.google.com/group/hugin-ptx


 CHANGES SINCE 2012.0.0

 * The greatest change is the redesign of the (Graphical) User Interface 
 (GUI). The user interface now consists of three modes: Simple, Advanced and 
 Expert.
 The Simple interface is for the beginning panorama photographer and offers 
 all tools to create your panorama. You can also use this mode if you have a 
 simple, straightforward panorama. The Simple interface mode uses the Fast 
 Preview  window as its main workflow window.
 The Advanced interface mode offers you more options to improve your 
 panorama. It uses the Panorama Editor as its main window.
 The Expert mode gives you access to all options and functions that Hugin 
 has to offer. This is where you can optimize your complicated, multilayer, 
 mosaic, multi-stack, you name it, panorama. It also uses the Panorama 
 Editor as its main window.

 * The Hugin build for Mac OS X has switched from Carbon to Cocoa and is 
 now fully 64bit.

 New tools added:
 * pto_var ( change image variables inside pto files)
 * pto_lensstack (modify assigned lenses and stack in pto files)
 * geocpset  (set/add geometric constraints for multirow panorama with 
 featureless images)


 Other Improvements
 * Many more improvements and bug fixes.

 UPGRADING

 Upgrading from previous versions of Hugin should be seamless. If you do 
 have
 problems with old settings, these can be reset in the Preferences by 
 clicking
 'Load defaults'.

 It is strongly recommeded to set the default control point detector to
 Hugin's CPFind.  It is the only control point generator endorsed by Hugin.
 Third-party generators may be compatible with the plug-in architecture.


 COMPILING

 Users compiling from source refer to the dependencies listed at
 http://wiki.panotools.org/Development_of_Open_Source_tools#Dependencies

 and the build processes listed at

 http://wiki.panotools.org/Development_of_Open_Source_tools#Build_your_Own_Test_Builds

 More information in the README and INSTALL_cmake files in the tarball.


 KNOWN ISSUES AND WORKAROUNDS

 There is a known problem building Hugin with CMake 2.8.5rc2.
 Workaround: Upgrade to a newer CMake version.

 Mac OS X:
 - Mac OS X Tiger (10.4) is no longer supported.
 - The PPC platform is no longer supported.
 - The OpenMP enabled enblend is now compatible on Mac OS X Lion (10.7).
 - The cmake compilation of Hugin is currently broken due to the fact that
 the boost library on OS X is currently at version 1.50 and boost versions 
 = 1.48
 conflict with a number of Mac OS X macros (from AssertMacros.h). This can
 not be disabled as WxWindows for Mac (a.k.a. WxMac) needs these macros.
 An XCode build, where a specific boost (=1.46) can be specified, is
 possible. The 2013.0 OSX bundle will be based on an XCode build with boost

Re: [hugin-ptx] Google Summer of Code 2013

[Robert Campbell]

On Feb 21, 2013, at 7:09 PM, Jim Watters wrote:

 Hugin and Panotools community,
 What new ideas do you have that a student could implement?


I'm the type to make panos while holding my p-n-s Canon S95.  I've tried doing 
some bracketed shots and create HDR from that, but I've had limited success.  
Mainly due to hand movement and images in one stack overlapping another stack 
too much.  Understandable, really.  

But the thought occurred to me that maybe instead of control points, what we 
really need are control dowels - sort of like forensic police dowels used to 
plot the trajectory of a bullet**.  I would think it would allow connecting 
different exposure levels of the pano together easily, as well as through each 
stack? Maybe a little ambitious?  I don't know of any other software using that 
type of system, so it might be a good opportunity at breaking new ground for 
some aspiring student.


** - 
https://www.ridgidforum.com/forum/attachments/4791d1225679629-texas-traffic-stop-3.jpg

I freely admit that I'm not sure the ROI on this would justify the effort.  
Just throwing it out there.

Bob Campbell

-- 
-- 
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 hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx

--- 
You received this message because you are subscribed to the Google Groups 
hugin and other free panoramic software group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [hugin-ptx] Google Summer of Code 2013

[Robert Campbell]

Yes, this and what Gnome summarized are close to what I was thinking.  So, if 
you have two adjacent stacks of three exposures, presumably they would all 
overlap by at least 10% and all six images would share a particular control 
point - thus creating a single line down through both stacks.  Presumably, all 
the dowel lines would be radiating out from the camera (and probably mostly 
parallel by the time they intersect the images?).  

I may have been a little confusing by mentioning the exposure levels, but I was 
thinking this would allow exposure-level priority versus stack-priority?  So, 
if you wanted to make three panos, one of each exposure level, then merge as a 
single stack (maybe in another HDR program) you can do that.  The reason I 
can't (quite/easily) do that now is that I'm hand-holding the camera rather 
than using a tripod.  When you use a tripod, you know that each image of a 
stack of exposures has the same framing/rotation/etc, so you can create one 
pano makefile with all the control points, adjustments, etc, and just switch 
out the filenames.  I can't make those assumptions; creating a pano of each 
exposure level doesn't get the same rotational/spatial information for each 
frame, so I can't just swap things around, which causes each exposure level to 
be projected slightly differently, then the stacks don't line up quite right.

Again, the ROI might be a little low, but I have a hunch this might make Hugin 
a bit more versatile (esp. for semi-advanced users that don't what to lug 
around a tripod with a pano-head everywhere :D )


On Feb 27, 2013, at 10:19 PM, Tduell wrote:

 Hello Bob,
 It seems to me that you really only need two dowels, probably best not too 
 close to one another. The first dowel would align all of the first control 
 points, and the second align all the second control points thus ensuring all 
 images are rotated around the first dowel correctly. Probably some 
 corrections required. All the images could then be cropped to the minimum 
 rectangle and you should have a set of aligned images.
 
 On Thursday, February 28, 2013 2:48:52 PM UTC+11, Bob Campbell wrote:
 
 
 
 I'm the type to make panos while holding my p-n-s Canon S95.  I've tried 
 doing some bracketed shots and create HDR from that, but I've had limited 
 success.  Mainly due to hand movement and images in one stack overlapping 
 another stack too much.  Understandable, really.   
 
 But the thought occurred to me that maybe instead of control points, what we 
 really need are control dowels - sort of like forensic police dowels used 
 to plot the trajectory of a bullet**. 
 [snip]
 
 -- 
 -- 
 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 hugin-ptx@googlegroups.com
 To unsubscribe from this group, send email to 
 hugin-ptx+unsubscr...@googlegroups.com
 For more options, visit this group at http://groups.google.com/group/hugin-ptx
  
 --- 
 You received this message because you are subscribed to the Google Groups 
 hugin and other free panoramic software group.
 To unsubscribe from this group and stop receiving emails from it, send an 
 email to hugin-ptx+unsubscr...@googlegroups.com.
 For more options, visit https://groups.google.com/groups/opt_out.
  
  

-- 
-- 
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 hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx

--- 
You received this message because you are subscribed to the Google Groups 
hugin and other free panoramic software group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [hugin-ptx] Re: Build noise

[Robert Krawitz]

On Mon, 25 Feb 2013 09:52:50 -0800 (PST), T. Modes wrote:
 Hi Robert,

 On 24 Feb., 19:55, Robert Krawitz r...@alum.mit.edu wrote:
 Here's another warning fix.

 diff -r 074d34083817 src/hugin1/ptbatcher/PTBatcherGUI.cpp
 --- a/src/hugin1/ptbatcher/PTBatcherGUI.cpp     Sat Feb 23 10:15:41 2013 
 +0100

 This does not work. This fixes the warning, but breaks functionality.
 The interface of this function is defined by wxWidgets and only with
 this interface it is called correctly.

I see you found a correct fix.

 BTW, I notice that src/hugin1/hugin/xrc/data/help_en_EN/Makefile gets
 modified by cmake, resulting in my sandbox always having a big diff in
 that file.

 Don't build in the source tree. Use a separate build directory.

Ah.
-- 
Robert Krawitz r...@alum.mit.edu

MIT VI-3 1987  -  Congrats MIT Engineers in the D3 Hoops tourney 2013
Tall Clubs International  --  http://www.tall.org/ or 1-888-IM-TALL-2
Member of the League for Programming Freedom  --  http://ProgFree.org
Project lead for Gutenprint   --http://gimp-print.sourceforge.net

Linux doesn't dictate how I work, I dictate how Linux works.
--Eric Crampton

-- 
-- 
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 hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx

--- 
You received this message because you are subscribed to the Google Groups 
hugin and other free panoramic software group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [hugin-ptx] Re: Build noise

[Robert Krawitz]

On Sat, 23 Feb 2013 01:15:53 -0800 (PST), T. Modes wrote:
 Hi Robert,

 On 23 Feb., 03:00, Robert Krawitz r...@alum.mit.edu wrote:
 I've made a few more changes to suppress build noise, attached.  I've
 also attached a build log containing the remaining warnings.


 Thanks for the patch. I committed a slightly modified version.

 Thomas

Here's another warning fix.

diff -r 074d34083817 src/hugin1/ptbatcher/PTBatcherGUI.cpp
--- a/src/hugin1/ptbatcher/PTBatcherGUI.cpp Sat Feb 23 10:15:41 2013 +0100
+++ b/src/hugin1/ptbatcher/PTBatcherGUI.cpp Sun Feb 24 13:52:15 2013 -0500
@@ -467,7 +467,7 @@
 const void* BatchIPCConnection::OnRequest(const wxString topic, const 
wxString item, size_t* size, wxIPCFormat format)
 #else
 #define RETURNEMPTYSTRING return ((wxChar*) )
-wxChar* BatchIPCConnection::OnRequest(const wxString topic, const wxString 
item, int* size, wxIPCFormat format)
+wxChar* BatchIPCConnection::OnRequest(const wxString topic, const wxString 
item, size_t* size, wxIPCFormat format)
 #endif
 {
 *size=wxNO_LEN;
diff -r 074d34083817 src/hugin1/ptbatcher/PTBatcherGUI.h
--- a/src/hugin1/ptbatcher/PTBatcherGUI.h   Sat Feb 23 10:15:41 2013 +0100
+++ b/src/hugin1/ptbatcher/PTBatcherGUI.h   Sun Feb 24 13:52:15 2013 -0500
@@ -58,7 +58,7 @@
 #if wxCHECK_VERSION(2,9,0)
 virtual const void* OnRequest(const wxString topic, const wxString item, 
size_t* size = NULL, wxIPCFormat format = wxIPC_TEXT);
 #else
-virtual wxChar* OnRequest(const wxString topic, const wxString item, 
int* size = NULL, wxIPCFormat format = wxIPC_TEXT);
+virtual wxChar* OnRequest(const wxString topic, const wxString item, 
size_t* size = NULL, wxIPCFormat format = wxIPC_TEXT);
 #endif
 };


BTW, I notice that src/hugin1/hugin/xrc/data/help_en_EN/Makefile gets
modified by cmake, resulting in my sandbox always having a big diff in
that file.

-- 
Robert Krawitz r...@alum.mit.edu

MIT VI-3 1987 - Congratulations MIT Engineers men's hoops Final Four!
Tall Clubs International  --  http://www.tall.org/ or 1-888-IM-TALL-2
Member of the League for Programming Freedom  --  http://ProgFree.org
Project lead for Gutenprint   --http://gimp-print.sourceforge.net

Linux doesn't dictate how I work, I dictate how Linux works.
--Eric Crampton

-- 
-- 
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 hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx

--- 
You received this message because you are subscribed to the Google Groups 
hugin and other free panoramic software group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [hugin-ptx] Re: Build noise

[Robert Krawitz]

One more:

diff -r caed526eacc2 src/hugin_base/panotools/PanoToolsInterface.cpp
--- a/src/hugin_base/panotools/PanoToolsInterface.cpp   Sun Feb 24 13:44:59 
2013 +0100
+++ b/src/hugin_base/panotools/PanoToolsInterface.cpp   Sun Feb 24 14:28:04 
2013 -0500
@@ -569,7 +569,7 @@
 image.format = projd.internalFormat;
 } else {
 image.format = _equirectangular;
-PrintError(unsupported projection);
+PrintError((char *)unsupported projection);
 }
 image.formatParamCount = projd.numberOfParameters;
 assert(image.formatParamCount == (int) projParams.size());

Also, I'm seeing several warnings of this type:

[ 84%] Building CXX object 
src/hugin_cpfind/cpfind/CMakeFiles/cpfind.dir/main.cpp.o
In file included from 
/home/rlk/sandbox/hugin/src/hugin_cpfind/cpfind/PanoDetector.h:35:0,
 from 
/home/rlk/sandbox/hugin/src/hugin_cpfind/cpfind/main.cpp:31:
/home/rlk/sandbox/hugin/src/foreign/zthread/include/zthread/PoolExecutor.h:58:9:
 warning: ‘ZThread::PoolExecutor’ has a field ‘ZThread::PoolExecutor::_impl’ 
whose type uses the anonymous namespace [enabled by default]

-- 
Robert Krawitz r...@alum.mit.edu

MIT VI-3 1987 - Congratulations MIT Engineers men's hoops Final Four!
Tall Clubs International  --  http://www.tall.org/ or 1-888-IM-TALL-2
Member of the League for Programming Freedom  --  http://ProgFree.org
Project lead for Gutenprint   --http://gimp-print.sourceforge.net

Linux doesn't dictate how I work, I dictate how Linux works.
--Eric Crampton

-- 
-- 
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 hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx

--- 
You received this message because you are subscribed to the Google Groups 
hugin and other free panoramic software group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[hugin-ptx] Build noise

[Robert Krawitz]

Hugin throws off a tremendous amount of build noise of the form:

[ 84%] Building CXX object 
src/hugin_cpfind/cpfind/CMakeFiles/cpfind.dir/main.cpp.o
In file included from 
/home/rlk/sandbox/hugin/src/foreign/vigra/vigra/stdimage.hxx:42:0,
 from 
/home/rlk/sandbox/hugin/src/hugin_cpfind/./localfeatures/Image.h:25,
 from 
/home/rlk/sandbox/hugin/src/hugin_cpfind/cpfind/PanoDetector.h:31,
 from 
/home/rlk/sandbox/hugin/src/hugin_cpfind/cpfind/main.cpp:31:
/home/rlk/sandbox/hugin/src/foreign/vigra/vigra/sized_int.hxx: In instantiation 
of ‘struct 
vigra::detail::SelectBiggestIntegerTypevigra::detail::IntTypeListlong long 
int, vigra::Int_type_not_supported_on_this_platform ’:
/home/rlk/sandbox/hugin/src/foreign/vigra/vigra/sized_int.hxx:79:10:   
recursively required from ‘struct 
vigra::detail::SelectBiggestIntegerTypevigra::detail::IntTypeListshort int, 
vigra::detail::IntTypeListint, vigra::detail::IntTypeListlong int, 
vigra::detail::IntTypeListlong long int, 
vigra::Int_type_not_supported_on_this_platform’
/home/rlk/sandbox/hugin/src/foreign/vigra/vigra/sized_int.hxx:79:10:   required 
from ‘struct 
vigra::detail::SelectBiggestIntegerTypevigra::detail::IntTypeListsigned char, 
vigra::detail::IntTypeListshort int, vigra::detail::IntTypeListint, 
vigra::detail::IntTypeListlong int, vigra::detail::IntTypeListlong long int, 
vigra::Int_type_not_supported_on_this_platform ’
/home/rlk/sandbox/hugin/src/foreign/vigra/vigra/sized_int.hxx:141:65:   
required from here
/home/rlk/sandbox/hugin/src/foreign/vigra/vigra/sized_int.hxx:79:10: warning: 
comparison between ‘enum vigra::detail::IntTypeListlong long int, 
vigra::Int_type_not_supported_on_this_platform::anonymous’ and ‘enum 
vigra::detail::SelectBiggestIntegerTypevigra::Int_type_not_supported_on_this_platform::anonymous’
 [-Wenum-compare]
/home/rlk/sandbox/hugin/src/foreign/vigra/vigra/sized_int.hxx:79:10: warning: 
enumeral mismatch in conditional expression: 
‘vigra::detail::SelectBiggestIntegerTypevigra::Int_type_not_supported_on_this_platform::anonymous
 enum’ vs ‘vigra::detail::IntTypeListlong long int, 
vigra::Int_type_not_supported_on_this_platform::anonymous enum’ 
[-Wenum-compare]
/home/rlk/sandbox/hugin/src/foreign/vigra/vigra/sized_int.hxx: In instantiation 
of ‘struct 
vigra::detail::SelectBiggestIntegerTypevigra::detail::IntTypeListlong int, 
vigra::detail::IntTypeListlong long int, 
vigra::Int_type_not_supported_on_this_platform  ’:
/home/rlk/sandbox/hugin/src/foreign/vigra/vigra/sized_int.hxx:79:10:   
recursively required from ‘struct 
vigra::detail::SelectBiggestIntegerTypevigra::detail::IntTypeListshort int, 
vigra::detail::IntTypeListint, vigra::detail::IntTypeListlong int, 
vigra::detail::IntTypeListlong long int, 
vigra::Int_type_not_supported_on_this_platform’
/home/rlk/sandbox/hugin/src/foreign/vigra/vigra/sized_int.hxx:79:10:   required 
from ‘struct 
vigra::detail::SelectBiggestIntegerTypevigra::detail::IntTypeListsigned char, 
vigra::detail::IntTypeListshort int, vigra::detail::IntTypeListint, 
vigra::detail::IntTypeListlong int, vigra::detail::IntTypeListlong long int, 
vigra::Int_type_not_supported_on_this_platform ’
/home/rlk/sandbox/hugin/src/foreign/vigra/vigra/sized_int.hxx:141:65:   
required from here

This patch fixes it.

diff -r 816c5e57562e src/foreign/vigra/vigra/sized_int.hxx
--- a/src/foreign/vigra/vigra/sized_int.hxx Thu Feb 21 19:10:21 2013 +0100
+++ b/src/foreign/vigra/vigra/sized_int.hxx Fri Feb 22 10:00:40 2013 -0500
@@ -43,6 +43,14 @@
 
 namespace vigra {
 
+#ifdef __GNUC__
+# if __GNUC__ = 4
+#  if __GNUC_MINOR__ = 6
+#pragma GCC diagnostic ignored -Wenum-compare
+#  endif
+# endif
+#endif
+
 class Int_type_not_supported_on_this_platform {};
 
 #ifndef NO_PARTIAL_TEMPLATE_SPECIALIZATION
@@ -160,6 +168,14 @@
 
 #endif // NO_PARTIAL_TEMPLATE_SPECIALIZATION
 
+#ifdef __GNUC__
+# if __GNUC__ = 4
+#  if __GNUC_MINOR__ = 6
+#pragma GCC diagnostic warning -Wenum-compare
+#  endif
+# endif
+#endif
+
 } // namespace vigra
 
 #endif /* VIGRA_SIZED_INT_HXX */

-- 
Robert Krawitz r...@alum.mit.edu

MIT VI-3 1987 - Congratulations MIT Engineers men's hoops Final Four!
Tall Clubs International  --  http://www.tall.org/ or 1-888-IM-TALL-2
Member of the League for Programming Freedom  --  http://ProgFree.org
Project lead for Gutenprint   --http://gimp-print.sourceforge.net

Linux doesn't dictate how I work, I dictate how Linux works.
--Eric Crampton

-- 
-- 
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 hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx

--- 
You received

Re: [hugin-ptx] Build noise

[Robert Krawitz]

I've made a few more changes to suppress build noise, attached.  I've
also attached a build log containing the remaining warnings.

-- 
Robert Krawitz r...@alum.mit.edu

MIT VI-3 1987 - Congratulations MIT Engineers men's hoops Final Four!
Tall Clubs International  --  http://www.tall.org/ or 1-888-IM-TALL-2
Member of the League for Programming Freedom  --  http://ProgFree.org
Project lead for Gutenprint   --http://gimp-print.sourceforge.net

Linux doesn't dictate how I work, I dictate how Linux works.
--Eric Crampton

-- 
-- 
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 hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx

--- 
You received this message because you are subscribed to the Google Groups 
hugin and other free panoramic software group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to hugin-ptx+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.




hugin-warnings.patch
Description: Binary data


hugin-build-log.compact
Description: Binary data

Re: [hugin-ptx] CHDK

[Robert Campbell]

On Jan 12, 2013, at 3:56 PM, JohnPW wrote:

 Anybody use CHDK? How do you like it? What is your experience with it?

I'm using it on my S95 and a 1200 IS I picked up for $40.  Haven't shot much 
raw on the 1200, so I can't say if the raw format is missing the iptc data, but 
I recall it does output Canon's CR2 format.  I've been using it for time lapse 
(with an A/C adapter) and for motion sensing for lightning.  That's the primary 
reason to use CHDK (IMO) - the scripting.  Browse through some of the scripts 
and if there are any you'd really like to have.

One thing to note is that it makes the camera boot slower.  At least, when 
you've only got it loaded on the SD card*.  But you can have a CHDK card and a 
non-CHDK card and swap them out on the fly; only use the CHDK one when you know 
you want that functionality.

As for Frederic's tip about the slow file writes, I've found that's true of any 
PS compared to a DSLR.  JPGs might be fairly quick (until you try a continuous 
mode), but in the end, they're not going to put the same caliber processor in 
them as their DSLRs (and PS's are SD based, slower than CFs). Raw files, of 
course, exacerbate that slowness.


* - you can load CHDK into the camera's firmware so it's always there, or just 
have it bootstrap every time from the SD card.  They generally recommend the 
card method.



Bob

-- 
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 hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx

[hugin-ptx] Compiler warnings

[Robert Krawitz]

I'm getting a flood of compiler warnings.  They aren't new, but they're
annoying...

[ 84%] Building CXX object 
src/hugin_cpfind/cpfind/CMakeFiles/cpfind.dir/main.cpp.o
In file included from 
/home/rlk/sandbox/hugin/src/foreign/vigra/vigra/stdimage.hxx:42:0,
 from 
/home/rlk/sandbox/hugin/src/hugin_cpfind/./localfeatures/Image.h:25,
 from 
/home/rlk/sandbox/hugin/src/hugin_cpfind/cpfind/PanoDetector.h:31,
 from 
/home/rlk/sandbox/hugin/src/hugin_cpfind/cpfind/main.cpp:31:
/home/rlk/sandbox/hugin/src/foreign/vigra/vigra/sized_int.hxx: In instantiation 
of ‘struct 
vigra::detail::SelectBiggestIntegerTypevigra::detail::IntTypeListlong long 
int, vigra::Int_type_not_supported_on_this_platform ’:
/home/rlk/sandbox/hugin/src/foreign/vigra/vigra/sized_int.hxx:79:10:   
recursively required from ‘struct 
vigra::detail::SelectBiggestIntegerTypevigra::detail::IntTypeListshort int, 
vigra::detail::IntTypeListint, vigra::detail::IntTypeListlong int, 
vigra::detail::IntTypeListlong long int, 
vigra::Int_type_not_supported_on_this_platform’
/home/rlk/sandbox/hugin/src/foreign/vigra/vigra/sized_int.hxx:79:10:   required 
from ‘struct 
vigra::detail::SelectBiggestIntegerTypevigra::detail::IntTypeListsigned char, 
vigra::detail::IntTypeListshort int, vigra::detail::IntTypeListint, 
vigra::detail::IntTypeListlong int, vigra::detail::IntTypeListlong long int, 
vigra::Int_type_not_supported_on_this_platform ’
/home/rlk/sandbox/hugin/src/foreign/vigra/vigra/sized_int.hxx:141:65:   
required from here

-- 
Robert Krawitz r...@alum.mit.edu

MIT VI-3 1987 - Congratulations MIT Engineers men's hoops Final Four!
Tall Clubs International  --  http://www.tall.org/ or 1-888-IM-TALL-2
Member of the League for Programming Freedom  --  http://ProgFree.org
Project lead for Gutenprint   --http://gimp-print.sourceforge.net

Linux doesn't dictate how I work, I dictate how Linux works.
--Eric Crampton

-- 
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 hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx

Re: [hugin-ptx] OffTopic - Color Film Development

[Robert Campbell]

Check out Denver Pro Photo:
http://www.denverprophoto.com/services.html

And Boulder Pro Photo (not affiliated):
http://www.boulderprophoto.com/services/film_processing_proofing_scanning.html

Slightly cheaper, but more consumer-oriented is Mike's Camera (not sure I trust 
them with my film, so I pay the extra...):
http://mikescamera.com/FilmServices.html

Haven't used any of them by mail since they're local, though, but I would think 
they'd be fine with it. 

I still make my own BW contact sheets since most places charge about $7 for a 
scanned  printed contact sheet but my darkroom charges $8 and hour and I can 
do about 3 or 4 for the price of one...


Bob

On Oct 30, 2012, at 8:23 PM, Dale wrote:

 I am looking for film development in the US that allows color slide and black 
 and white film negative.  Many places are discontinuing the return of film 
 and converting everything to digital.  This is a problem for me.  Suggestions?
 
 Dale
 
 -- 
 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 hugin-ptx@googlegroups.com
 To unsubscribe from this group, send email to 
 hugin-ptx+unsubscr...@googlegroups.com
 For more options, visit this group at http://groups.google.com/group/hugin-ptx

-- 
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 hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx

[hugin-ptx] OK, so I got this far and managed to stitch 2 photos, but now how do I save it?! Please help. rj

[Robert A. Jones]

-- 
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 hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx

[hugin-ptx] Having trouble when stitching multi-row panoramas

[Robert Elliott]

I am trying to stitch together some multi-row panoramic shots I took.  I 
get an error that says warning 30 unconnected image groups found:and it 
lists the photos I am trying to stitch.

I tried stitching the three rows separately and they all work.  The problem 
comes up when I try to stitch two or more rows.

I used Microsoft Image Composite Editor and it stitched the images together 
without an error.  I really want to use Hugin because it is  much better 
program and I have more control to manipulate the image than with the 
Microsoft program.  Is there a way you can help me?

Bob Elliott

-- 
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 hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to 
hugin-ptx+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx