[Hugin-devs] [Bug 678649] Re: Crash if pics on network not available

2017-05-06 Thread tmodes
** Changed in: hugin
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Hugin.
https://bugs.launchpad.net/bugs/678649

Title:
  Crash if pics on network not available

Status in Hugin:
  Fix Released

Bug description:
  Hugin crashes if the pictures, used by hugin, are stored on a network
  drive and network connection is interrupted.

  Operating system: Windows XP Pro
  Path to pics: \\\foo\pic*.tif

  Exactly procedure that lead to crash:
  1. start hugin (at windows) and create project with pics on available network 
drive
  2. suspend windows to hard disk
  3. turn off router and dhcp server
  4. reactivate windows
  5. forget to turn router and dhcp server on
  6. click on panorama preview
  --> hugin crashes after some time

To manage notifications about this bug go to:
https://bugs.launchpad.net/hugin/+bug/678649/+subscriptions

___
Mailing list: https://launchpad.net/~hugin-devs
Post to : hugin-devs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~hugin-devs
More help   : https://help.launchpad.net/ListHelp


[Hugin-devs] [Bug 679177] Re: PTBatcherGUI: multiple selections

2017-05-06 Thread tmodes
** Changed in: hugin
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Hugin.
https://bugs.launchpad.net/bugs/679177

Title:
  PTBatcherGUI: multiple selections

Status in Hugin:
  Fix Released

Bug description:
  Could you enable multiple selections in the list? To apply one command
  to several list items.
  (I consider this a bug because multiple selections enabled is OS default.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/hugin/+bug/679177/+subscriptions

___
Mailing list: https://launchpad.net/~hugin-devs
Post to : hugin-devs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~hugin-devs
More help   : https://help.launchpad.net/ListHelp


[Hugin-devs] [Bug 679294] Re: does not flush cache when images are removed

2017-05-06 Thread tmodes
** Changed in: hugin
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Hugin.
https://bugs.launchpad.net/bugs/679294

Title:
  does not flush cache when images are removed

Status in Hugin:
  Fix Released

Bug description:
  Hello,
  this is http://bugs.debian.org/521589 (reported by Jens Kilian). I have 
doublechecked that it still applies to 2009.2.0 beta3:

  ---
  Steps to reproduce:
  - Create a small image /tmp/foo.tif (e.g., with gimp).
  - Start hugin and load /tmp/foo.tif.
  - Open the preview window.
  - Close preview and remove image ('Remove selected image(s))'.
  - Without leaving hugin, modify /tmp/foo.tif (e.g., with gimp).
  - In hugin, load /tmp/foo.tif again.
  - Select 'foo.tif' in the Images tab.  The old version is displayed.
  - Open preview and click 'Update'.  The old version is displayed.

  --

   I have doublechecked how 2009.2.0 beta3 behaves:
  Both old preview and preview on the Images tag exhibit this bug. The fast 
preview window does not. The bug really seems to be related to the filename, it 
does not matter if the inode changes as long as the filename is unchanged.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hugin/+bug/679294/+subscriptions

___
Mailing list: https://launchpad.net/~hugin-devs
Post to : hugin-devs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~hugin-devs
More help   : https://help.launchpad.net/ListHelp


[Hugin-devs] [Bug 679605] Re: Invalid PNGs crash Hugin

2017-05-06 Thread tmodes
** Changed in: hugin
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Hugin.
https://bugs.launchpad.net/bugs/679605

Title:
  Invalid PNGs crash Hugin

Status in Hugin:
  Fix Released

Bug description:
  I came across some PNG images which would always crash hugin as soon
  as they are loaded.

  Digging a little deeper I discovered that the PNG file had been
  truncated (specifically... the last PNG IDAT chunk wasn\'t the number
  of bytes it should have been).

  Most image viewers I tried opened this file without a problem. Hugin
  should either load the image or (better still) give an error saying
  the image is invalid.

  This was only tested on windows. I have attached an example truncated
  PNG file.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hugin/+bug/679605/+subscriptions

___
Mailing list: https://launchpad.net/~hugin-devs
Post to : hugin-devs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~hugin-devs
More help   : https://help.launchpad.net/ListHelp


[Hugin-devs] [Bug 679194] Re: Feature Request: Make the Manual CP Generation Process Interruptable

2017-05-06 Thread tmodes
** Changed in: hugin
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Hugin.
https://bugs.launchpad.net/bugs/679194

Title:
  Feature Request: Make the Manual CP Generation Process Interruptable

Status in Hugin:
  Fix Released

Bug description:
  Sometimes auto fine tune doesn't find matching control point with good
  correlation. User would than possibly like to abort the process of
  adding control point. It is somewhat unintuitive and uneconomical that
  he must first click  "add control point", only then can he press the
  "delete" button.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hugin/+bug/679194/+subscriptions

___
Mailing list: https://launchpad.net/~hugin-devs
Post to : hugin-devs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~hugin-devs
More help   : https://help.launchpad.net/ListHelp


[Hugin-devs] [Bug 682891] Re: "stitch now" aborts with error.

2017-05-06 Thread tmodes
** Changed in: hugin
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Hugin.
https://bugs.launchpad.net/bugs/682891

Title:
  "stitch now" aborts with error.

Status in Hugin:
  Fix Released

Bug description:
  I got this error:

  
  Stitching panorama
  ===
  nona  -z LZW -r ldr -m TIFF_m -o contour_pano1 -i 0 /tmp/huginpto_X1Gret
  ContractViolation: 
  Precondition violation!
  RemappedPanoImage::remapImage(): image sizes not 
consistent
  
(/home/wolff/hugin/wiki/hugin/hugin.hg/src/hugin_base/nona/RemappedPanoImage.h:450)

  caught exception: 
  Precondition violation!
  RemappedPanoImage::remapImage(): image sizes not 
consistent
  
(/home/wolff/hugin/wiki/hugin/hugin.hg/src/hugin_base/nona/RemappedPanoImage.h:450)

  make: *** [contour_pano1.tif] Error 1
  -

  and then a question to submit the full bugreport. So here I am..

  Turns out that when re-creating the source images (they were converted
  to JPG with a really low quality setting), I had forgotten to rotate
  them by 90 degrees. So all this blabla (and hugin claiming I found a
  bug), is caused by an image-size mismatch

  The error message should reflect this: "Image unexpectedly changed
  dimensions. "

To manage notifications about this bug go to:
https://bugs.launchpad.net/hugin/+bug/682891/+subscriptions

___
Mailing list: https://launchpad.net/~hugin-devs
Post to : hugin-devs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~hugin-devs
More help   : https://help.launchpad.net/ListHelp


[Hugin-devs] [Bug 1383226] Re: Hassle in Changing Projection

2017-05-06 Thread tmodes
** Changed in: hugin
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Hugin.
https://bugs.launchpad.net/bugs/1383226

Title:
  Hassle in Changing Projection

Status in Hugin:
  Fix Released

Bug description:
  Selection of "Rectilinear" in Fast Panorama Preview:Projection is impossible 
without first deselecting a Field of View box
  similarly
  Selection of "Rectilinear" in Panorama Editor:Stitcher is impossible without 
first deselecting a Field of View box

  
  Hugin RC 14.0.0_RC4
  OSX 10.7.5

To manage notifications about this bug go to:
https://bugs.launchpad.net/hugin/+bug/1383226/+subscriptions

___
Mailing list: https://launchpad.net/~hugin-devs
Post to : hugin-devs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~hugin-devs
More help   : https://help.launchpad.net/ListHelp


[Hugin-devs] [Bug 847433] Re: 'Create panorama' is disabled in single photo projects

2017-05-06 Thread tmodes
** Changed in: hugin
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Hugin.
https://bugs.launchpad.net/bugs/847433

Title:
  'Create panorama' is disabled in single photo projects

Status in Hugin:
  Fix Released

Bug description:
  When starting a project, both 2. Align... and 3. Create panorama are
  greyed out which makes sense.

  However if I load a single photo into Hugin, they are still greyed.
  This is a problem as a common use of Hugin for me is to load a single
  image and remap it to a different projection.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hugin/+bug/847433/+subscriptions

___
Mailing list: https://launchpad.net/~hugin-devs
Post to : hugin-devs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~hugin-devs
More help   : https://help.launchpad.net/ListHelp


[Hugin-devs] [Bug 1209447] Re: Hugin 2013rc1 crashes on libtiff assertion trying to load .CR2 files

2017-05-06 Thread tmodes
** Changed in: hugin
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Hugin.
https://bugs.launchpad.net/bugs/1209447

Title:
  Hugin 2013rc1 crashes on libtiff assertion trying to load .CR2 files

Status in Hugin:
  Fix Released

Bug description:
  Trying out 2013.0.0-rc1, I was excited to see that .CR2 files were
  included in the open image dialog, so I tried to load some. Hugin
  crashed on a failed assertion in libtiff:

  0   libsystem_kernel.dylib0x7fff88195212 __pthread_kill + 10
  1   libsystem_c.dylib 0x7fff85562b54 pthread_kill + 90
  2   libsystem_c.dylib 0x7fff855a6dce abort + 143
  3   libsystem_c.dylib 0x7fff855a7e2a __assert_rtn + 146
  4   libtiff.3.dylib   0x0001012f13b1 OJPEGPostDecode + 129
  5   libtiff.3.dylib   0x0001012fbc39 TIFFReadScanline + 
521
  6   libhugin_vigra_impex-2013.0.dylib 0x000100e84a3a 
vigra::TIFFDecoderImpl::nextScanline() + 148
  7   libhugin_base-2013.0.dylib0x0001006b2f49 void 
vigra::read_bands, 
vigra::RGBAccessor, unsigned 
char>(vigra::Decoder*, vigra::BasicImageIterator, 
vigra::RGBAccessor, unsigned char) 
+ 105
  8   libhugin_base-2013.0.dylib0x0001006b3965 void 
vigra::importVectorImage, 
vigra::RGBAccessor 
>(vigra::ImageImportInfo const&, 
vigra::BasicImageIterator, 
vigra::RGBAccessor) + 101
  9   libhugin_base-2013.0.dylib0x000100882760 
HuginBase::ImageCache::loadImageSafely(std::string const&) + 5314
  10  libhugin_base-2013.0.dylib0x00010087fa87 
HuginBase::ImageCache::loadSafely(boost::shared_ptr,
 boost::shared_ptr) + 245

  This is on Mac OS X 10.8.4; system information from the About dialog
  is the following:

  Operating System: Mac OS X (Darwin 12.4.0 x86_64)
  Architecture: 64 bit
  Free memory: 0 kiB

  Hugin
  Version: 2013.0.0-rc1 built by Matthieu DESILE
  Path to resources: /Applications/Hugin/Hugin.app/Contents/Resources/xrc/
  Path to data: /Applications/Hugin/Hugin.app/Contents/Resources/xrc/
  Path to public lensfun database: 
/Applications/Hugin/Hugin.app/Contents/Resources/lensfun
  Path to user lensfun database: /Users/gthb/.local/share/lensfun

  Libraries
  wxWidgets: 2.9.3.1
  libpano13: 2.9.19 
  Boost: 1.46.1
  Exiv2: 0.23.0
  Lensfun: 0.2.7.0

  Full  crash report from the Apple "Problem Reporter" dialog is
  attached.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hugin/+bug/1209447/+subscriptions

___
Mailing list: https://launchpad.net/~hugin-devs
Post to : hugin-devs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~hugin-devs
More help   : https://help.launchpad.net/ListHelp


[Hugin-devs] [Bug 1031914] Re: No SkyBox projection

2017-05-06 Thread tmodes
** Changed in: hugin
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Hugin.
https://bugs.launchpad.net/bugs/1031914

Title:
  No SkyBox projection

Status in Hugin:
  Fix Released

Bug description:
  3D SkyBox (cubic) projection should be offered as one of the
  projection options in Hugin.

  It is a commonly required 3D background format for 3D rendering.

  According to 
http://www.ptgrey.com/support/downloads/documents/ladybugSDK/ProjectionTypes.html
  the formulas needed are: U=X/Z,  V=Y/Z

  It seems this may be similar like a set of six square rectilinear
  projections (Front, Right, Top, Left, Bottom, Back) designed to fit
  together to make a cube.

  (platform independent feature request)

To manage notifications about this bug go to:
https://bugs.launchpad.net/hugin/+bug/1031914/+subscriptions

___
Mailing list: https://launchpad.net/~hugin-devs
Post to : hugin-devs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~hugin-devs
More help   : https://help.launchpad.net/ListHelp


[Hugin-devs] [Bug 1392670] Re: Dynamic display of final image dimensions in stitcher tab?

2017-05-06 Thread tmodes
** Changed in: hugin
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Hugin.
https://bugs.launchpad.net/bugs/1392670

Title:
  Dynamic display of final image dimensions in stitcher tab?

Status in Hugin:
  Fix Released

Bug description:
  I appreciate the 6 controls (canvas size*2 and crop*4) on the stitcher page, 
and primarily use the canvas size width to determine the output image size, but 
the two things I want to know are missing
  1) the final image dimensions
  2) the final image's aspect-ratio

  When you've used the fast panorama preview window to draw a crop area
  by hand, possibly with quite sizeable margins, it's useful to know
  that the finished thing is going to be 40 megapixels at 16:9 or
  whatever. Currently that requires a calculator - (right-left)*(bottom-
  top); seeing the numbers directly would be much easier.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hugin/+bug/1392670/+subscriptions

___
Mailing list: https://launchpad.net/~hugin-devs
Post to : hugin-devs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~hugin-devs
More help   : https://help.launchpad.net/ListHelp


[Hugin-devs] [Bug 1637847] Re: failed in wxArgNormalizer(): format specifier doesn't match argument type

2017-05-06 Thread tmodes
** Changed in: hugin
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Hugin.
https://bugs.launchpad.net/bugs/1637847

Title:
  failed in wxArgNormalizer(): format specifier doesn't match argument
  type

Status in Hugin:
  Fix Released

Bug description:
  Hugin 2016.2.0.be8da0221960 from PPA on Xubuntu 16.04
  * Interface Mode: Expert
  * Assistant Tab
  * Load two pictures (I reproduce this consistently with the test case for bug 
#1635992)
  * Press on 2. Align...

  Expected behaviour: generation of control points and optimization

  Observed behaviour: crash

  Backtrace:

  [1] MainFrame::RunAssistant(wxWindow*)
  [2] GLPreviewFrame::OnAlign(wxCommandEvent&)
  [3] wxAppConsoleBase::CallEventHandler(wxEvtHandler*, wxEventFunctor&, 
wxEvent&) const
  [4] wxEvtHandler::ProcessEventIfMatchesId(wxEventTableEntryBase const&, 
wxEvtHandler*, wxEvent&)
  [5] wxEventHashTable::HandleEvent(wxEvent&, wxEvtHandler*)
  [6] wxEvtHandler::TryHereOnly(wxEvent&)
  [7] wxEvtHandler::ProcessEventLocally(wxEvent&)
  [8] wxEvtHandler::ProcessEvent(wxEvent&)
  [9] wxWindowBase::TryAfter(wxEvent&)
  [10] wxWindowBase::TryAfter(wxEvent&)
  [11] wxWindowBase::TryAfter(wxEvent&)
  [12] wxWindowBase::TryAfter(wxEvent&)
  [13] wxEvtHandler::SafelyProcessEvent(wxEvent&)
  [14] g_signal_emit_valist
  [15] g_signal_emit
  [16] g_signal_emit_valist
  [17] g_signal_emit
  [18] g_closure_invoke
  [19] g_signal_emit_valist
  [20] g_signal_emit
  [21] gtk_propagate_event
  [22] gtk_main_do_event
  [23] g_main_context_dispatch
  [24] g_main_loop_run
  [25] gtk_main
  [26] wxGUIEventLoop::DoRun()
  [27] wxEventLoopBase::Run()
  [28] wxAppConsoleBase::MainLoop()
  [29] wxEntry(int&, wchar_t**)
  [30] main
  [31] __libc_start_main
  [32] _start

To manage notifications about this bug go to:
https://bugs.launchpad.net/hugin/+bug/1637847/+subscriptions

___
Mailing list: https://launchpad.net/~hugin-devs
Post to : hugin-devs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~hugin-devs
More help   : https://help.launchpad.net/ListHelp


[Hugin-devs] [Bug 1633076] Re: vig_optimize is not working on HDR images

2017-05-06 Thread tmodes
** Changed in: hugin
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Hugin.
https://bugs.launchpad.net/bugs/1633076

Title:
  vig_optimize is not working on HDR images

Status in Hugin:
  Fix Released

Bug description:
  PTO project before running vig_optimize:

  https://fliker09.tk/sharedstuff/launchpad/panorama_9_ptovariable.pto

  
  PTO file after running vig_optimize:

  https://fliker09.tk/sharedstuff/launchpad/vig_optimize.pto

  
  Source files:

  https://fliker09.tk/sharedstuff/launchpad/1.hdr
  https://fliker09.tk/sharedstuff/launchpad/2.hdr
  https://fliker09.tk/sharedstuff/launchpad/3.hdr
  https://fliker09.tk/sharedstuff/launchpad/4.hdr

  
  vig_optimize output:

  loading: 3.hdr
  downscaling: 3662x5488  1831x2744  916x1372  
  loading: 4.hdr
  downscaling: 3662x5488  1831x2744  916x1372  
  loading: 1.hdr
  downscaling: 3662x5488  1831x2744  916x1372  
  loading: 2.hdr
  downscaling: 3662x5488  1831x2744  916x1372  
  Sampling points
  sampling points
  extracting good points
  Selected 12 points
  Vignetting Optimization

  
  Nothing suspicious, but I don't get any optimization. For comparison, 
autooptimiser succeeds (but I am not quite satisfied with it, but that's for 
another discussion).

To manage notifications about this bug go to:
https://bugs.launchpad.net/hugin/+bug/1633076/+subscriptions

___
Mailing list: https://launchpad.net/~hugin-devs
Post to : hugin-devs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~hugin-devs
More help   : https://help.launchpad.net/ListHelp


[Hugin-devs] [Bug 1686608] Re: %projectionNumber works as %projection + "Number"

2017-05-06 Thread tmodes
** Changed in: hugin
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Hugin.
https://bugs.launchpad.net/bugs/1686608

Title:
  %projectionNumber works as %projection + "Number"

Status in Hugin:
  Fix Released

Bug description:
  hugin-hg, Arch Linux

  In Stitching (2) preferences, the user can define the arg file for
  ExifTool using placeholders.

  However, the placeholder %projectionNumber does not work.

  Expected result: 2
  Actual result: EquirectangularNumber

To manage notifications about this bug go to:
https://bugs.launchpad.net/hugin/+bug/1686608/+subscriptions

___
Mailing list: https://launchpad.net/~hugin-devs
Post to : hugin-devs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~hugin-devs
More help   : https://help.launchpad.net/ListHelp


[Hugin-devs] [Bug 1682974] Re: hugin won't start: "invalid window dc"

2017-05-06 Thread tmodes
** Changed in: hugin
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Hugin.
https://bugs.launchpad.net/bugs/1682974

Title:
  hugin won't start: "invalid window dc"

Status in Hugin:
  Fix Released

Bug description:
  Hi -- Kubuntu 16.10, added the nightly repo which appears to have last
  been updated 2017-04-10 (2016.3.0.84a397fa5e9a).

  Running hugin, I see a splash screen and an immediate failed
  assertion:

  ASSERT INFO:
  ../src/gtk/dcclient.cpp(1520): assert "IsOk()" failed in Clear(): invalid 
window dc

  BACKTRACE:
  [1] wxWindowDCImpl::Clear()
  [2] ImagesTreeCtrl::SetOptimizerMode()
  [3] OptimizePanel::Init(HuginBase::Panorama*)
  [4] MainFrame::MainFrame(wxWindow*, HuginBase::Panorama&)
  [5] huginApp::OnInit()
  [6] wxEntry(int&, wchar_t**)
  [7] main
  [8] __libc_start_main
  [9] _start

  If I click "Continue" many times, the program appears to start and
  work (though I haven't fully tested.)

  System info:

  Operating System: Linux 4.8.0-46-generic x86_64
  Architecture: 64 bit
  Free memory: 5107772 kiB

  Hugin
  Version: 2016.3.0.84a397fa5e9a
  Path to resources: /usr/share/hugin/xrc/
  Path to data: /usr/share/hugin/data/
  Hugins camera and lens database: /home/casey/.hugindata/camlens.db
  Multi-threading using C++11 std::thread and OpenMP

  Libraries
  wxWidgets: wxWidgets 3.0.2
  wxWidgets Library (wxGTK port)
  Version 3.0.2 (Unicode: wchar_t, debug level: 1),
  Runtime version of toolkit used is 2.24.
  Compile-time GTK+ version is 2.24.30.

  libpano13: 2.9.19 
  Boost: 1.61.0
  Exiv2: 0.25
  SQLite3: 3.14.1
  Vigra: 1.11.0
  LittleCMS2: 2.7

To manage notifications about this bug go to:
https://bugs.launchpad.net/hugin/+bug/1682974/+subscriptions

___
Mailing list: https://launchpad.net/~hugin-devs
Post to : hugin-devs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~hugin-devs
More help   : https://help.launchpad.net/ListHelp


[Hugin-devs] [Bug 1677992] Re: Latest versions of Hugin developpement fail to build

2017-05-06 Thread tmodes
** Changed in: hugin
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Hugin.
https://bugs.launchpad.net/bugs/1677992

Title:
  Latest versions of Hugin developpement fail to build

Status in Hugin:
  Fix Released

Bug description:
  Hi,
  I failed to build latest hg versions. 
  I get the following:

  [ 40%] Building CXX object 
src/hugin_base/CMakeFiles/huginbase.dir/vigra_ext/ImageTransformsGPU.cpp.o
  
/usr/local/src/hugin/hugin-2016.3.0/src/hugin_base/vigra_ext/ImageTransformsGPU.cpp:
 In function ‘bool vigra_ext::transformImageGPUIntern(const string&, const 
string&, int, const string&, const std::vector&, const 
std::vector&, vigra::Diff2D, const void*, int, int, int, int, const 
void*, int, vigra::Diff2D, vigra::Diff2D, void*, int, int, int, int, void*, 
int, bool)’:
  
/usr/local/src/hugin/hugin-2016.3.0/src/hugin_base/vigra_ext/ImageTransformsGPU.cpp:369:19:
 error: ‘GL_MAX_RECTANGLE_TEXTURE_SIZE’ was not declared in this scope
   glGetIntegerv(GL_MAX_RECTANGLE_TEXTURE_SIZE, );
 ^
  src/hugin_base/CMakeFiles/huginbase.dir/build.make:1358 : la recette pour la 
cible « 
src/hugin_base/CMakeFiles/huginbase.dir/vigra_ext/ImageTransformsGPU.cpp.o » a 
échouée
  make[2]: *** 
[src/hugin_base/CMakeFiles/huginbase.dir/vigra_ext/ImageTransformsGPU.cpp.o] 
Erreur 1

  
  The lastest version I managed to build was on march, 14th.

  Regards

  Jean-Luc

To manage notifications about this bug go to:
https://bugs.launchpad.net/hugin/+bug/1677992/+subscriptions

___
Mailing list: https://launchpad.net/~hugin-devs
Post to : hugin-devs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~hugin-devs
More help   : https://help.launchpad.net/ListHelp


[Hugin-devs] [Bug 1649883] Re: HDR and EXR files in PTO yields different results

2017-05-06 Thread tmodes
** Changed in: hugin
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Hugin.
https://bugs.launchpad.net/bugs/1649883

Title:
  HDR and EXR files in PTO yields different results

Status in Hugin:
  Fix Released

Bug description:
  Hugin: "Version: 2016.2.0"

  Here are the EXR files (they were obtained with luminance-hdr):

  http://www.mediafire.com/file/nhc2alxnza35tvo/1.exr
  http://www.mediafire.com/file/8jj6n6763xbdecz/2.exr
  http://www.mediafire.com/file/t9iuvwtev4lgvd9/3.exr
  http://www.mediafire.com/file/w8m8e7egatbb4ts/4.exr

  Here are the HDR files (they were obtained by converting EXR files,
  with the help of pfstools):

  http://www.mediafire.com/file/0v60kaygnb1wdtv/1.hdr
  http://www.mediafire.com/file/lk95b85gz3qd37s/2.hdr
  http://www.mediafire.com/file/qgtj18dgnd9ih6c/3.hdr
  http://www.mediafire.com/file/b5v9afass4c39re/4.hdr

  Here is the project file with EXR files:

  http://www.mediafire.com/file/u9u0waxwz7q6fgf/project_exr.pto

  Here is the project file with HDR files:

  http://www.mediafire.com/file/bex6eyrw16bxxfs/project_hdr.pto

  A note here - optimizations were made using the project with EXR
  files.

  Then I do:

  nona -m EXR_m -o panorama project_exr.pto
  nona -m EXR_m -o panorama project_hdr.pto

  The results:

  http://www.mediafire.com/file/08ngxjgl7dxrz8p/panorama0002_exr.exr
  http://www.mediafire.com/file/3wpy2ye2w2sazg4/panorama0002_hdr.exr

  Look at the window - in the case with EXR files project it is just
  "burned out". Looks like a bug. If any more info is required just ask!

To manage notifications about this bug go to:
https://bugs.launchpad.net/hugin/+bug/1649883/+subscriptions

___
Mailing list: https://launchpad.net/~hugin-devs
Post to : hugin-devs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~hugin-devs
More help   : https://help.launchpad.net/ListHelp


[Hugin-devs] [Bug 1678621] Re: Add Help button in enblend options dialog

2017-05-06 Thread tmodes
** Changed in: hugin
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Hugin.
https://bugs.launchpad.net/bugs/1678621

Title:
  Add Help button in enblend options dialog

Status in Hugin:
  Fix Released

Bug description:
  The dialog can be found in 
  editor window >> Stitcher tab > Processing: Blender: enblend: [Options]

  It would be nice to have a help button just like the one available in
  the preferences dialog (grouped with the Cancel and OK buttons). In
  this case it should probably link to /help/Enblend.html of Hugin's
  built in help pages. That way users can quickly look up command line
  arguments available for the current version of enblend without
  cluttering up the UI with a list of available options. (note to self:
  panotools wiki pages need an update to reflect the new command line
  arguments of enblend and how to combine them, also with a comparison
  to the behaviour of earlier versions of enblend prior to version 4.2)

To manage notifications about this bug go to:
https://bugs.launchpad.net/hugin/+bug/1678621/+subscriptions

___
Mailing list: https://launchpad.net/~hugin-devs
Post to : hugin-devs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~hugin-devs
More help   : https://help.launchpad.net/ListHelp


[Hugin-devs] [Bug 1645051] Re: Hugin help throws up warnings

2017-05-06 Thread tmodes
** Changed in: hugin
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Hugin.
https://bugs.launchpad.net/bugs/1645051

Title:
  Hugin help throws up warnings

Status in Hugin:
  Fix Released

Bug description:
  A build of current default (f556b5ff8d96 7578 default) on Fedora 25 x86_64.
  Selecting 'Help' shows help OK, but when selecting a help section (e.g. 1 
About Hugin) a dialog box appears "Hugin Warning HTML anchor About_Hugin does 
not exist".
  This seems to be the behaviour when selecting any highlighted text.
  Have I missed a dependency for this new help? 

  Cheers,
  Terry

To manage notifications about this bug go to:
https://bugs.launchpad.net/hugin/+bug/1645051/+subscriptions

___
Mailing list: https://launchpad.net/~hugin-devs
Post to : hugin-devs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~hugin-devs
More help   : https://help.launchpad.net/ListHelp


[Hugin-devs] [Bug 1678611] Re: "Most recently used projects" doesn't prompt the "Save changes...?" dialog

2017-05-06 Thread tmodes
** Changed in: hugin
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Hugin.
https://bugs.launchpad.net/bugs/1678611

Title:
  "Most recently used projects" doesn't prompt the "Save changes...?"
  dialog

Status in Hugin:
  Fix Released

Bug description:
  Choosing a .pto file from menu File -> "Most recently used projects"
  doesn't prompt the "Save changes to the panorama before closing?"
  dialog even if a currently open project was altered.

  Current situation: the selected older project will be opened while
  changes to the open project are lost. Compare with correct behaviour
  of menu File "New" and "Open".

  Tested on OS X 10.11 / Hugin 2016.2.0

To manage notifications about this bug go to:
https://bugs.launchpad.net/hugin/+bug/1678611/+subscriptions

___
Mailing list: https://launchpad.net/~hugin-devs
Post to : hugin-devs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~hugin-devs
More help   : https://help.launchpad.net/ListHelp


[Hugin-devs] [Bug 1629923] Re: Latest "hg" version failed to build

2017-05-06 Thread tmodes
** Changed in: hugin
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Hugin.
https://bugs.launchpad.net/bugs/1629923

Title:
  Latest "hg" version failed to build

Status in Hugin:
  Fix Released

Bug description:
  Hi,

  I tried today to build the latest hg version.

  I got the following error:

  [ 82%] Building CXX object 
src/hugin1/hugin/CMakeFiles/hugin.dir/PanoPanel.cpp.o
  [ 83%] Building CXX object 
src/hugin1/hugin/CMakeFiles/hugin.dir/GLViewer.cpp.o
  /usr/local/src/hugin/hugin-2016.3.0/src/hugin1/hugin/MainFrame.cpp: In member 
function 'void MainFrame::OnLoadingFailed(wxCommandEvent&)':
  /usr/local/src/hugin/hugin-2016.3.0/src/hugin1/hugin/MainFrame.cpp:1165:48: 
error: conversion from 'const wxScopedCharBuffer {aka const 
wxScopedCharTypeBuffer}' to non-scalar type 'std::__cxx11::string {aka 
std::__cxx11::basic_string}' requested
   std::string filename = e.GetString().mb_str(HUGIN_CONV_FILENAME);
  ^
  src/hugin1/hugin/CMakeFiles/hugin.dir/build.make:110: recipe for target 
'src/hugin1/hugin/CMakeFiles/hugin.dir/MainFrame.cpp.o' failed
  make[2]: *** [src/hugin1/hugin/CMakeFiles/hugin.dir/MainFrame.cpp.o] Error 1
  make[2]: *** Waiting for unfinished jobs
  CMakeFiles/Makefile2:2038: recipe for target 
'src/hugin1/hugin/CMakeFiles/hugin.dir/all' failed
  make[1]: *** [src/hugin1/hugin/CMakeFiles/hugin.dir/all] Error 2
  Makefile:149: recipe for target 'all' failed
  make: *** [all] Error 2

  I run debian sid

  Regards

  Jean-Luc

To manage notifications about this bug go to:
https://bugs.launchpad.net/hugin/+bug/1629923/+subscriptions

___
Mailing list: https://launchpad.net/~hugin-devs
Post to : hugin-devs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~hugin-devs
More help   : https://help.launchpad.net/ListHelp


[Hugin-devs] [Bug 1659528] Re: align_image_stack fails to process PNGs: Assertion failed

2017-05-06 Thread tmodes
** Changed in: hugin
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Hugin.
https://bugs.launchpad.net/bugs/1659528

Title:
  align_image_stack fails to process PNGs: Assertion failed

Status in Hugin:
  Fix Released

Bug description:
  align_image_stack fails for certian PNG files that were created by
  ImageMagick convert from a CorelDRAW-created PDF file.

  Here's the commandline output:

  Unable to read EXIF data from opened file:C47C_ref.png
  Unable to read EXIF data from opened file:C47C_src.png
  Creating control points between C47C_ref.png and C47C_src.png
  align_image_stack: 
/build/hugin-xzKV1g/hugin-2015.0.0+dfsg/src/tools/align_image_stack.cpp:740: 
int main2(std::vector, Parameters) [with 
PixelType = vigra::RGBValue]: Assertion `nextImgInfo.size() == 
firstImgInfo.size()' failed.

  Sometimes it works, sometimes it doesn't. I tried converting the files
  back and forth to different formats to drop any strange data that
  could confuse align_image_stack, but it kept failing to process the
  files.

  Is this a bug?

To manage notifications about this bug go to:
https://bugs.launchpad.net/hugin/+bug/1659528/+subscriptions

___
Mailing list: https://launchpad.net/~hugin-devs
Post to : hugin-devs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~hugin-devs
More help   : https://help.launchpad.net/ListHelp


[Hugin-devs] [Bug 1666030] Re: assistant fails to run if custom temporary directory is set

2017-05-06 Thread tmodes
** Changed in: hugin
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Hugin.
https://bugs.launchpad.net/bugs/1666030

Title:
  assistant fails to run if custom temporary directory is set

Status in Hugin:
  Fix Released

Bug description:
  If preferences->file name->Temporary dir is set to an non-empty value,
  running from cpfind from the Assistant ([2. Align]-button]) fails. The
  cpfind window pops up and closes immediately, an error message about
  unconnected images is shown.

  Running cpfind from the main window ([Photos]->[Create control
  points]) still works.

  Googling finds a thread on hugin-ptx but no solution:
  https://www.mail-archive.com/hugin-ptx@googlegroups.com/msg24909.html
  https://groups.google.com/forum/#!msg/hugin-ptx/w_oeNy9rqDE/8qRP5UJzAgAJ
  | Greg 'groggy' Lehey Fri, 16 Sep 2016 18:00:47 -0700
  | [...]
  | For the record: setting that variable (which ends up in ~/.hugin as
  | tmpDir=/var/tmp, for example) appears to cause hugin pass an empty
  | PATH environment variable to icpfind, which then fails.  It's not the
  | problem of icpfind, which works fine if started directly.  But I
  | haven't had time to track it down yet.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hugin/+bug/1666030/+subscriptions

___
Mailing list: https://launchpad.net/~hugin-devs
Post to : hugin-devs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~hugin-devs
More help   : https://help.launchpad.net/ListHelp


[Hugin-devs] [Bug 1643283] Re: Export with layers aligned

2017-05-06 Thread tmodes
** Changed in: hugin
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Hugin.
https://bugs.launchpad.net/bugs/1643283

Title:
  Export with layers aligned

Status in Hugin:
  Fix Released

Bug description:
  It would be great to be able to export panoramas with layers aligned.
  In some cases panorama images might require manual stitching. This is 
especially important when images are of different focus, shot with idea to do 
focus-stacking later.
  PTGui allows to export to PDF with layers aligned.
  While PDF is not a requirement, TIFF should suffice because layers are also 
supported by TIFF

To manage notifications about this bug go to:
https://bugs.launchpad.net/hugin/+bug/1643283/+subscriptions

___
Mailing list: https://launchpad.net/~hugin-devs
Post to : hugin-devs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~hugin-devs
More help   : https://help.launchpad.net/ListHelp


[Hugin-devs] [Bug 1652170] Re: UI: assistant leaves user confused about step to perform after loading images

2017-05-06 Thread tmodes
** Changed in: hugin
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Hugin.
https://bugs.launchpad.net/bugs/1652170

Title:
  UI: assistant leaves user confused about step to perform after loading
  images

Status in Hugin:
  Fix Released

Bug description:
  When using the assistant, the user begins loading the images with the
  proper button, the first.

  The second button is Align, the third Create panorama

  However, it seems that when images are loaded, they are aligned too.

  So, when the user has loaded the images, he/she gets them aligned, and
  he is confused whether he/she should press the align button or go
  straightforward with the Create panorama one.

  I think that the right thing is - provided that the preview is
  satisfactory - to create the panorama. However, if the user has
  changed something (projection, move, drag, etc), he/she should realign
  the images before creating the panorama.

  All this stuff isn't clear in the ui. I thing it would be better that
  after loading the photos with first button the second button remained
  grayed and unusable until something that requieres realigning is
  performed.

  Something even better would be to have a fool-proof assistant which
  directly creates the panorama without changing anything. This could be
  the most user-friendly use level, and it would gain hugin much more
  users

To manage notifications about this bug go to:
https://bugs.launchpad.net/hugin/+bug/1652170/+subscriptions

___
Mailing list: https://launchpad.net/~hugin-devs
Post to : hugin-devs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~hugin-devs
More help   : https://help.launchpad.net/ListHelp


[Hugin-devs] [Bug 1635362] Re: HDR display not working

2017-05-06 Thread tmodes
** Changed in: hugin
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Hugin.
https://bugs.launchpad.net/bugs/1635362

Title:
  HDR display not working

Status in Hugin:
  Fix Released

Bug description:
  I'm working on a personal hobby project and possibly I make all the errors 
you can make.
  I have made a series of pictures with my phone camera, a Sony Z2 with a cheap 
fish eye clip on it.
  This to evaluate if you are able to make a HDR sphere from them.  Only that 
is crazy but please stay with me. 
  I use a app, FV-5, that claims it can make bracked pictures.
  My Settings in the app is 0,7 in exposure size steps and 5 pictures. 
  The output is in PNG format. 
  I have had some success to make a sphere with a low dynamic range output but 
never a hdr directly from the staked pictures in Hugin. 
  I've tried third party program, NIK Collection inside GIPMP 2.9.4 to make 
pre-composed HDR:s.
  But when take them in Hugin in exr format they are all washed out and hard to 
see and put manual control points.
  In Hugin help you can read 

  "Hugin supports both HDR and 16bit imaging. These image formats
  contain a lot more brightness and colour information than can be
  displayed on a standard computer monitor, so Hugin only shows a rough
  representation of these pictures.

  16bit data can have linear or corrected gamma. Linear images appear
  very dark on many monitors, so set the Curve to gamma 2.2.

  For HDR data, try setting the Curve to logarithmic.

  Changes to the HDR and 16bit display mode require restarting Hugin to
  take effect."

  I've have put the settings to logarithmic but still the exr picture look 
washed out.
  Actually no diffrence what ever settings I choose, yes I restart Hugin after 
every change.
  Maybe my exr pictures is not made correctly?
  Therefor I was searching the web for a real .exr picture and found some 
here...

  https://github.com/openexr/openexr-
  images/blob/master/ScanLines/CandleGlass.exr

  When I try them I cant see any difference either, the picture in Hugin
  is black. It's working fine in a viewer like Luminance HDR.

  So I have many problems here but for a starter. Is the curve settings
  in preference  for display  correction with  HDR working at all in...

  2016.2.0.be8da0221960 built by Thomas

  OS Windows 10

  ???

To manage notifications about this bug go to:
https://bugs.launchpad.net/hugin/+bug/1635362/+subscriptions

___
Mailing list: https://launchpad.net/~hugin-devs
Post to : hugin-devs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~hugin-devs
More help   : https://help.launchpad.net/ListHelp


[Hugin-devs] [Bug 1678613] Re: "displayed images" section not updated correctly when changing order of images in Photos tab

2017-05-06 Thread tmodes
** Changed in: hugin
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Hugin.
https://bugs.launchpad.net/bugs/1678613

Title:
  "displayed images" section not updated correctly when changing order
  of images in Photos tab

Status in Hugin:
  Fix Released

Bug description:
  The Move/Drag tab in Fast Panorama preview window offers different
  drag modes. If set to one of the two available "individual" modes a
  second row of checkboxes appears in the "displayed images" section.

  Now when the image order is changed in Photos tab (e.g. drag one image
  up or down) the lower row of checkboxes isn't updated correctly. The
  "drag" checkbox seems to internally not point to the image file (e.g.
  "img_1234.jpg") but instead only marks the image number (e.g. #5).

  The correct behaviour is shown in both "standard" drag modes (normal and 
mosaic): 
  - Show only one image in the Fast Preview window (i.e. only one checkbox 
marked in "displayed images" section). Memorize image number.
  - Now switch to main editor window -> Photos tab: drag that image up or down 
in the list so the image number of the image file changes. The new position in 
fast preview window is updated: the marked checkbox has changed to the right 
new image number.

  The bug can be reproduced this way:
  Change drag mode to "single" and select both checkboxes of only one image. 
switch to main editor window > Images tab and drag that image up or down. Now 
in Fast Preview window only the "display" checkbox is updated while the "drag" 
checkbox still marks the old image number.

  Tested on OS X 10.11 / Hugin 2016.2.0

To manage notifications about this bug go to:
https://bugs.launchpad.net/hugin/+bug/1678613/+subscriptions

___
Mailing list: https://launchpad.net/~hugin-devs
Post to : hugin-devs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~hugin-devs
More help   : https://help.launchpad.net/ListHelp


[Hugin-devs] [Bug 1686172] Re: UX of ExifTool options in Hugin Preferences

2017-05-06 Thread tmodes
** Changed in: hugin
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Hugin.
https://bugs.launchpad.net/bugs/1686172

Title:
  UX of ExifTool options in Hugin Preferences

Status in Hugin:
  Fix Released

Bug description:
  While I encountered the bug reported here
  https://bugs.launchpad.net/hugin/+bug/1685928, I have spent some time
  trying to understand what is expected from the user in Hugin /
  Preference / Stitching (2).

  "Choosing" an arg file was not the obvious choice, since I have not create 
any yet.
  So I started reading the documentation of ExifTool and searching the web for 
some examples. Then I tried to look for specific hugin's user guide / wiki on 
how to define variables in the file. I did not find any.
  (The syntax should be like "-Model=some text", but how to make the use of 
variables when the text in the prefs reads "Placeholders will not be replaced" 
and I even do not know what the placeholders are?)

  So, "editing" the arg file looked like a way to go - I filled in an
  arg file name in to the field ("test") and clicked "Edit". Now, it
  became obvious what the template looks like ("Model=", etc.)

  Unfortunately, I did not enter the /absolute/path/name/to/test and as
  a result, the file disappeared the next day. The culprit was that my
  temporary directory is /tmp and the "test" file was created right
  there in /tmp/test... And my /tmp gets wiped every reboot.

  P.S. My journey was even a bit more miserable, because of the bug
  reported above - no matter what, no EXIF was copied to my output
  panorama. So I thought the errror had been on my side due to wrong
  syntax in arg file. Having looked at Hugin's source code I found that
  "Edit" can also create the file. Call me stupid, but this really took
  me quite lot of time...

  My proposal is to:

  * add the text "argfile may be left empty for the default settings";
  * add the text "argfile name must be an absolute path name" (or changing the 
code to place the file in some directory, like $HOME/.hugindata folder);
  * the "Edit" button should change its description to "Create / Edit". (Edit 
is for _existing_ file and as such provides no hint that it can also create the 
file.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/hugin/+bug/1686172/+subscriptions

___
Mailing list: https://launchpad.net/~hugin-devs
Post to : hugin-devs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~hugin-devs
More help   : https://help.launchpad.net/ListHelp