[Hugin-bug-hunters] [Bug 1467731] [NEW] Bright pixels near bottom edge of output image

2015-06-22 Thread Dllu
Public bug reported:

In many panoramas, I noticed an erroneously bright bottom edge.

I am using Hugin version 2014.0.0.5da69bc383dd

The bug is often accompanied by strange black horizontal dotted lines.

Example 1:

https://upload.wikimedia.org/wikipedia/commons/archive/2/29/20150609065757!Capitolhill_panorama_1.jpg

The original seven images used to stitch the panorama are available at:
https://commons.wikimedia.org/wiki/File:Capitolhill_panorama_1_frame_0.JPG

Example 2:

https://upload.wikimedia.org/wikipedia/commons/archive/4/4e/20150623025822!Hurricane_ridge_panorama_5.jpg

My workflow is:

1) Add images
2) click "Align" in the simple UI
3) straighten and center the panorama in the simple UI
4) click "Calculate Field of View" and "Calculate Optimal Size" and "Fit Crop 
to Images", in that order, in the Stitcher tab of the advanced view.
5) click Stitch!

This is an exceptionally annoying bug because the defects are so subtle,
and yet they ruin the image when it is inspected carefully or printed.

** Affects: hugin
 Importance: Undecided
 Status: New

** Attachment added: "PTO file for first example"
   
https://bugs.launchpad.net/bugs/1467731/+attachment/4418999/+files/DSC00286%20-%20DSC00292.pto

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

Title:
  Bright pixels near bottom edge of output image

Status in Hugin - Panorama Tools GUI:
  New

Bug description:
  In many panoramas, I noticed an erroneously bright bottom edge.

  I am using Hugin version 2014.0.0.5da69bc383dd

  The bug is often accompanied by strange black horizontal dotted lines.

  Example 1:

  
https://upload.wikimedia.org/wikipedia/commons/archive/2/29/20150609065757!Capitolhill_panorama_1.jpg

  The original seven images used to stitch the panorama are available
  at:
  https://commons.wikimedia.org/wiki/File:Capitolhill_panorama_1_frame_0.JPG

  Example 2:

  
https://upload.wikimedia.org/wikipedia/commons/archive/4/4e/20150623025822!Hurricane_ridge_panorama_5.jpg

  My workflow is:

  1) Add images
  2) click "Align" in the simple UI
  3) straighten and center the panorama in the simple UI
  4) click "Calculate Field of View" and "Calculate Optimal Size" and "Fit Crop 
to Images", in that order, in the Stitcher tab of the advanced view.
  5) click Stitch!

  This is an exceptionally annoying bug because the defects are so
  subtle, and yet they ruin the image when it is inspected carefully or
  printed.

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

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


[Hugin-bug-hunters] [Bug 1467678] Re: nona segfaults with PNG and TIFF output

2015-06-22 Thread Bruno Postle
Here's a better stacktrace:

Core was generated by `nona -i 0 -m TIFF -o junk DSC_0251 - DSC_0254.pto'.
Program terminated with signal SIGSEGV, Segmentation fault.

Thread 1 (Thread 0x7ff2da3e5900 (LWP 11921)):
#0  operator() (v=@0x0: , this=) at 
/usr/include/vigra/inspectimage.hxx:1043
No locals.
#1  
inspectLine
 >, 
vigra::VectorElementAccessor, vigra::RGBValue**>, 
vigra::RGBAccessor >, 
vigra::ConstBasicImageIterator, 
vigra::StandardConstValueAccessor > >, 
vigra::FindMinMax > (f=, send=..., s=..., 
src=...) at /usr/include/vigra/inspectimage.hxx:71
No locals.
#2  operator() > (f=, 
this=) at /usr/include/vigra/inspectimage.hxx:225
t = {x = , y = 0}
w = 8536
#3  extra_passes_select, vigra::RGBValue**>, 
vigra::RGBAccessor >, 
vigra::ConstBasicImageIterator, 
vigra::StandardConstValueAccessor > > >, 
vigra::FindMinMax > (f=, g=...) at 
/usr/include/vigra/inspector_passes.hxx:71
No locals.
#4  inspectImage, vigra::RGBValue**>, 
vigra::RGBAccessor >, 
vigra::ConstBasicImageIterator, 
vigra::StandardConstValueAccessor > >, 
vigra::FindMinMax > (
f=, a=..., lowerright=..., upperleft=...) at 
/usr/include/vigra/inspectimage.hxx:236
No locals.
#5  find_value_range, vigra::RGBValue**>, 
vigra::RGBAccessor >, 
vigra::ConstBasicImageIterator, 
vigra::StandardConstValueAccessor > > (lower_right=..., 
upper_left=..., accessor=...)
at /usr/include/vigra/impexbase.hxx:164
i = 0
extrema = {min = 255 '\377', max = 0 '\000', count = 0}
#6  find_source_value_range, vigra::RGBValue**>, 
vigra::RGBAccessor >, 
vigra::ConstBasicImageIterator, 
vigra::StandardConstValueAccessor > > (lower_right=..., 
upper_left=..., export_info=..., accessor=...)
at /usr/include/vigra/impexbase.hxx:185
range = 
#7  vigra::detail::exportImage, vigra::RGBValue**>, 
vigra::RGBAccessor >, 
vigra::ConstBasicImageIterator, 
vigra::StandardConstValueAccessor > > (image_upper_left=..., 
image_lower_right=..., image_accessor=..., export_info=...) at 
/usr/include/vigra/impex.hxx:550
encoder = std::unique_ptr containing 0x22f6330
pixel_type = "UINT8"
downcast = false
type = vigra::UNSIGNED_INT_8
image_source_range = 
destination_range = 
#8  0x7ff2d9d675da in exportImage, vigra::RGBValue**>, 
vigra::RGBAccessor >, 
vigra::ConstBasicImageIterator, 
vigra::StandardConstValueAccessor > > (export_info=..., 
image_accessor=..., image_lower_right=..., 
image_upper_left=...) at /usr/include/vigra/impex.hxx:972
No locals.
#9  
vigra::exportImageAlpha, vigra::RGBValue**>, 
vigra::RGBAccessor >, 
vigra::ConstBasicImageIterator, 
vigra::StandardConstValueAccessor > (info=..., image=..., 
alpha=...)
at /usr/src/debug/hugin-2015.0.0/src/hugin_base/vigra_ext/impexalpha.hxx:394
No locals.
#10 0x7ff2d9d8e122 in 
exportImageAlpha, 
vigra::RGBValue**>, vigra::RGBAccessor >, vigra::ConstBasicImageIterator, 
vigra::StandardConstValueAccessor > (info=..., image=..., 
alpha=...) at 
/usr/src/debug/hugin-2015.0.0/src/hugin_base/vigra_ext/impexalpha.hxx:417
No locals.
#11 
HuginBase::Nona::WeightedStitcher, std::allocator > 
>, vigra::BasicImage > >::stitch 
(this=this@entry=0x7ffe0380e770, 
Python Exception  Cannot find type const 
HuginBase::Nona::AdvancedOptions::_Rep_type: 
opts=..., imgSet=std::set with 1 elements = {...}, filename="junk", 
remapper=..., advOptions=std::map with 0 elements)
at /usr/src/debug/hugin-2015.0.0/src/hugin_base/nona/Stitcher.h:614
basename = "junk"
pano = {data_ = 0x7ff2c9f04010, lines_ = 0x22e0f20, width_ = 8536, 
height_ = 4268, 
  allocator_ = {<__gnu_cxx::new_allocator >> = {}, }, 
  pallocator_ = {<__gnu_cxx::new_allocator*>> = {}, }}
panoMask = {data_ = 0x7ff2c7c45010 '\377' ..., 
lines_ = 0x22f73c0, width_ = 8536, height_ = 4268, 
  allocator_ = {<__gnu_cxx::new_allocator> = {}, }, 
  pallocator_ = {<__gnu_cxx::new_allocator> = {}, }}
ext = "tif"
cext = ""
outputfile = "junk.tif"
exinfo = {m_filename = "junk.tif", m_filetype = "", m_pixeltype = 
"UINT8", m_comp = "NONE", m_mode = "w", m_x_res = 150, 
  m_y_res = 150, m_pos = {x = 0, y = 0}, m_icc_profile = 
{> = {size_ = 0, 
  data_ = 0x22ef160 ""}, capacity_ = 2, 
alloc_ = {<__gnu_cxx::new_allocator> = {}, }}, 
  m_canvas_size = { = {x = 8536, y = 4268}, }, fromMin_ = 0, fromMax_ = 0, toMin_ = 0, toMax_ = 0}
#12 0x7ff2d9d681b9 in 
stitchPanoIntern >, 
vigra::BasicImage > (
Python Exception  Cannot find type const 
HuginBase::Nona::AdvancedOptions::_Rep_type: 
advOptions=std::map with 0 elements, 
imgs=std::set with 140728957200240 elements, basename="junk", 
progress=0x7ff2d8869d50, opts=..., pano=...) at 
/usr/src/debug/hugin-2015.0.0/src/hugin_base/nona/Stitcher.h:1030
stitcher = 
{, std::allocator > >, 
vigra::BasicImage > >> = {
_vptr.Stitcher = 0x7ff2da1c6598 , std::allocator > 
>, vigra::B

[Hugin-bug-hunters] [Bug 1467678] [NEW] nona segfaults with PNG and TIFF output

2015-06-22 Thread Bruno Postle
Public bug reported:

System: fedora f22 x86_64
hugin 2015.0.0 rc1 c48252eb571f
libtiff-4.0.3
libpng-1.6.16
libjpeg-turbo-1.4.0
vigra-1.10.0

I'm getting a segfault from nona with PNG and TIFF output, JPEG is fine.

This is a simple single image project with JPEG input:

  nona -i 0 -m TIFF  -o junk project.pto
  Segmentation fault (core dumped)

Result is the same with or without -m parameter and with multiple photo 
projects.
OMP_NUM_THREADS=1 doesn't help. I don't have a suitable GPU so I can't test 
that.

Thread 1 (Thread 0x7f100c213900 (LWP 3761)):
#0  0x7f100bbabbc8 in void vigra::detail::exportImage, vigra::RGBValue**>, 
vigra::RGBAccessor >, 
vigra::ConstBasicImageIterator, 
vigra::StandardConstValueAccessor > >(vigra::Diff2D, 
vigra::Diff2D, 
vigra::MultiImageVectorMaskAccessor4, vigra::RGBValue**>, 
vigra::RGBAccessor >, 
vigra::ConstBasicImageIterator, 
vigra::StandardConstValueAccessor >, vigra::ImageExportInfo 
const&, vigra::VigraFalseType)
() from /usr/lib64/hugin/libhuginbase.so.0.0
No symbol table info available.
#1  0x7f100bb9760a in void 
vigra::exportImageAlpha, vigra::RGBValue**>, 
vigra::RGBAccessor >, 
vigra::ConstBasicImageIterator, 
vigra::StandardConstValueAccessor 
>(vigra::triple, vigra::RGBValue**>, 
vigra::ConstBasicImageIterator, 
vigra::RGBValue**>, 
vigra::RGBAccessor > >, 
std::pair, 
vigra::StandardConstValueAccessor >, vigra::ImageExportInfo 
const&, vigra::VigraFalseType) [clone .isra.915] [clone .constprop.1312] () 
from /usr/lib64/hugin/libhuginbase.so.0.0
No symbol table info available.
#2  0x7f100bbbe152 in 
HuginBase::Nona::WeightedStitcher, std::allocator > 
>, vigra::BasicImage > 
>::stitch(HuginBase::PanoramaOptions const&, std::set, std::allocator >&, std::string const&, 
HuginBase::Nona::SingleImageRemapper, std::allocator > 
>, vigra::BasicImage > >&, 
std::map, 
std::allocator > > const&) () from 
/usr/lib64/hugin/libhuginbase.so.0.0
No symbol table info available.
#3  0x7f100bb981e9 in 
HuginBase::Nona::stitchPanoRGB_8_16(HuginBase::PanoramaData const&, 
HuginBase::PanoramaOptions const&, AppBase::ProgressDisplay*, std::string 
const&, std::set, std::allocator > const&, char const*, std::map, std::allocator > > const&) ()
   from /usr/lib64/hugin/libhuginbase.so.0.0
No symbol table info available.
#4  0x7f100bcd2c9a in 
HuginBase::Nona::stitchPanorama(HuginBase::PanoramaData const&, 
HuginBase::PanoramaOptions const&, AppBase::ProgressDisplay*, std::string 
const&, std::set, std::allocator > const&, std::map, 
std::allocator > > const&) ()
   from /usr/lib64/hugin/libhuginbase.so.0.0
No symbol table info available.
#5  0x7f100b967c0e in HuginBase::NonaFileOutputStitcher::runStitcher() () 
from /usr/lib64/hugin/libhuginbase.so.0.0
No symbol table info available.
#6  0x00404d27 in main ()
No symbol table info available.

I'll rebuild and try again with unstripped binaries.

** Affects: hugin
 Importance: Undecided
 Status: New

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

Title:
  nona segfaults with PNG and TIFF output

Status in Hugin - Panorama Tools GUI:
  New

Bug description:
  System: fedora f22 x86_64
  hugin 2015.0.0 rc1 c48252eb571f
  libtiff-4.0.3
  libpng-1.6.16
  libjpeg-turbo-1.4.0
  vigra-1.10.0

  I'm getting a segfault from nona with PNG and TIFF output, JPEG is
  fine.

  This is a simple single image project with JPEG input:

nona -i 0 -m TIFF  -o junk project.pto
Segmentation fault (core dumped)

  Result is the same with or without -m parameter and with multiple photo 
projects.
  OMP_NUM_THREADS=1 doesn't help. I don't have a suitable GPU so I can't test 
that.

  Thread 1 (Thread 0x7f100c213900 (LWP 3761)):
  #0  0x7f100bbabbc8 in void vigra::detail::exportImage, vigra::RGBValue**>, 
vigra::RGBAccessor >, 
vigra::ConstBasicImageIterator, 
vigra::StandardConstValueAccessor > >(vigra::Diff2D, 
vigra::Diff2D, 
vigra::MultiImageVectorMaskAccessor4, vigra::RGBValue**>, 
vigra::RGBAccessor >, 
vigra::ConstBasicImageIterator, 
vigra::StandardConstValueAccessor >, vigra::ImageExportInfo 
const&, vigra::VigraFalseType)
  () from /usr/lib64/hugin/libhuginbase.so.0.0
  No symbol table info available.
  #1  0x7f100bb9760a in void 
vigra::exportImageAlpha, vigra::RGBValue**>, 
vigra::RGBAccessor >, 
vigra::ConstBasicImageIterator, 
vigra::StandardConstValueAccessor 
>(vigra::triple, vigra::RGBValue**>, 
vigra::ConstBasicImageIterator, 
vigra::RGBValue**>, 
vigra::RGBAccessor > >, 
std::pair, 
vigra::StandardConstValueAccessor >, vigra::ImageExportInfo 
const&, vigra::VigraFalseType) [clone .isra.915] [clone .constprop.1312] () 
from /usr/lib64/hugin/libhuginbase.so.0.0
  No symbol table info available.
  #2  0x7f100bbbe152 in 
HuginBase::Nona::WeightedStitcher, std::allocator > 
>, vigra::BasicImage > 
>::stitch(HuginBase::PanoramaOptions const&, std::set, std::alloca

[Hugin-bug-hunters] [Bug 679654] Re: updated levmar library

2015-06-22 Thread tmodes
Updated internal levmar library to 2.6 in default branch.

** Changed in: hugin
   Status: Confirmed => Fix Committed

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

Title:
  updated levmar library

Status in Hugin - Panorama Tools GUI:
  Fix Committed

Bug description:
  Last December, an updated levmar was released (2.2), with change that
  could be very interesting for hugin:

   - Fixed an error in the computation of the damping factor of
  levmar_dif()  in lm_core.c. Thanks to John Ervin for reporting.

  This change is interesting, because levmar_dif is used for photometric
  optimisation by hugin.

  I took the liberty to try hugin with this newer version of the levmar
  library, and on my test panorama it took slightly longer but reached
  the same end result.

  This is of course not 0.7 material, but perhaps something for early
  0.7.1.

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

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


[Hugin-bug-hunters] [Bug 695420] Re: Add Color Management to Hugin

2015-06-22 Thread tmodes
The default branch contains now code for a color managed display of the
images in the GUI.

** Changed in: hugin
   Status: Triaged => Fix Committed

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

Title:
  Add Color Management to Hugin

Status in Hugin - Panorama Tools GUI:
  Fix Committed

Bug description:
  (Note: I'm also posting this to the Hugin gmail group)

  I've been playing with RPP (http://www.raw-photo-
  processor.com/RPP/Overview.html) for RAW conversion preliminary to
  generating panoramas with Hugin (most recently Harry van der Wolf's
  OSX build of 2010.4.0-beta2); and running into problems with the color
  space.

  RPP generates TIFF files in the BetaRGB color space; and using these
  files directly in Hugin I find two problems:

  1) The panomatic control point generator barfs on these - Exception
  Type:  EXC_CRASH (SIGABRT) in the crash logs ( I can provide details
  if you like).  I can generate control points manually, or with
  autopano-sift; and the alignment and distortion optimization runs as
  expected.

  2) The expoure optimization generally leads to absurd results; usually
  a strong horizontal exposure gradient, and if I try white balance
  optimization then the  resulting panorama reminds my of my experiments
  in recreational pharmacology many decades ago.

  I can work around this by converting the files from BetaRGB to
  ProPhoto (e.g. in Photoshop, that being what I'm most familiar with),
  after which Hugin handles them with no problems.  But this is a pain
  when I have hundreds of images to deal with.

  It's not clear if these are bugs or just a case of input that Hugin
  (or its components) weren't designed to handle; outside of RPP I
  haven't run across BetaRGB anywhere else.  And I don't know the
  underlying math well enough to know whether adding support for this is
  a trivial fix or a major overhaul.

  If this is a bug, I can provide lots of detail; if it's a missing
  feature, please consider this a feature request.

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

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


[Hugin-bug-hunters] [Bug 1465698] Re: Fast panorama preview: show/hide first photo of stack

2015-06-22 Thread Sybren Stüvel
Sounds good, thanks!

Do you know when we'll see this in an official build? It'll be a shame
to have to wait for another year before there is another Hugin
release

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

Title:
  Fast panorama preview: show/hide first photo of stack

Status in Hugin - Panorama Tools GUI:
  Fix Committed

Bug description:
  I have a suggestion for a usability improvement. Many of my projects
  involve HDR spherical panoramas. Usually I only enable the first photo
  of each HDR stack in the preview. However, sometimes I want to hide
  some photos, do some editing, then show all first-of-stack photos
  again.

  My issue is that it's hard to select each Nth photo of each stack.
  There is no visual indication of which photos belong to which stack,
  so I have to remember the stack size (I work with 3, 5 and 7 photos
  per stack, depending on the project), then do the math myself, then
  manually select 38 photos. It would seem that a computer is more
  suitable for this task. It would be sweet to be able to do this with a
  single click.

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

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


[Hugin-bug-hunters] [Bug 1362170] Re: nona GPU for remapping : seg fault

2015-06-22 Thread tmodes
Hugin does not use freeglut any more (only default branch). This
hopefully fixes also this segfault.

** Changed in: hugin
   Status: Confirmed => Fix Committed

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

Title:
  nona GPU for remapping : seg fault

Status in Hugin - Panorama Tools GUI:
  Fix Committed

Bug description:
  If i activate the  GPU for remapping, it's always crash :

  
  ===
  ***  Panorama makefile generated by Hugin   ***
  ===
  System information
  ===
  Operating system: GNU/Linux
  Release: 3.14.14-gentoo
  Kernel version: #1 SMP Thu Aug 14 21:23:51 CEST 2014
  Machine: x86_64
  Disc usage
  Sys. de fichiers Taille Utilisé Dispo Uti% Monté sur
  /dev/sda2   23G 19G  3,1G  86% /
  devtmpfs   3,9G   0  3,9G   0% /dev
  tmpfs  3,9G320K  3,9G   1% /dev/shm
  tmpfs  3,9G1,1M  3,9G   1% /run
  tmpfs  3,9G   0  3,9G   0% /sys/fs/cgroup
  tmpfs  3,9G2,1M  3,9G   1% /tmp
  /dev/sda3  212G173G   28G  87% /home
  /dev/sdb2  816G677G   98G  88% /Backup
  /dev/sdc2  241G136G   93G  60% /home/roumano/Musique
  /dev/sdc3  1,3T1,2T   17G  99% /home/roumano/Vidéos
  tmpfs  796M 52K  796M   1% /run/user/500
  Memory usage
   total   used   free sharedbuffers cached
  Mem:  7956   5647   2308 28117820
  -/+ buffers/cache:   4710   3245
  Swap: 3906   1775   2130
  ===
  Output options
  ===
  Hugin Version: 2014.0.0.51ff237f209e
  Project file: /tmp/huginpto_L9TZUg
  Output prefix: test
  Projection: Cylindrical (1)
  Field of view: 124 x 57
  Canvas dimensions: 6491 x 3246
  Crop area: (235,872) - (6306,3122)
  Output exposure value: 13.82
  Output stacks minimum overlap: 0.700
  Output layers maximum Ev difference: 0.50
  Selected outputs
  Normal panorama
  * Blended panorama
  Using GPU for remapping
  ===
  Input images
  ===
  Number of images in project file: 3
  Number of active images: 3
  Image 0: /home/roumano/raw/pano/2014-08-06--17.48.49.CR2.tif
  Image 0: Size 5196x3462, Exposure: 13.95
  Image 1: /home/roumano/raw/pano/2014-08-06--17.48.51.CR2.tif
  Image 1: Size 5196x3462, Exposure: 13.80
  Image 2: /home/roumano/raw/pano/2014-08-06--17.48.53.CR2.tif
  Image 2: Size 5196x3462, Exposure: 13.72
  ===
  Testing programs
  ===
  Checking nona...[OK]
  Checking enblend...[OK]
  Checking enfuse...[OK]
  Checking hugin_hdrmerge...[OK]
  Checking exiftool...[OK]
  ===
  Stitching panorama
  ===
  nona -g  -z LZW -r ldr -m TIFF_m -o test -i 0 /tmp/huginpto_L9TZUg
  nona: using graphics card: ATI Technologies Inc. AMD Radeon HD 7900 Series  
  make: *** [test.tif] Erreur de segmentation
  make: *** Suppression du fichier « test.tif »

  
  My card it's a ATI 7950 ( lspci : AMD/ATI] Tahiti PRO [Radeon HD 7950/8950 
OEM / R9 280] )
  Driver used : ati-drivers-14.6_beta1
  on another exemple, OpenCL on my computer is working great (much faster than 
via the pcu ) via darktable
  Debug information from darktable :  ( if it's can help ) 
  [opencl_init] device 0 `Tahiti' supports image sizes of 16384 x 16384
  [opencl_init] device 0 `Tahiti' allows GPU memory allocations of up to 1024MB
  [opencl_init] device 0: Tahiti 
   GLOBAL_MEM_SIZE:  2392MB
   MAX_WORK_GROUP_SIZE:  256
   MAX_WORK_ITEM_DIMENSIONS: 3
   MAX_WORK_ITEM_SIZES:  [ 256 256 256 ]
   DRIVER_VERSION:   1526.3 (VM)
   DEVICE_VERSION:   OpenCL 1.2 AMD-APP (1526.3)

  Don't known how to provide more information :
  - I have recompiled higin with debug information (no more information in the 
GUI)
  - don't known how to test nona from the commande line

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

___
Mailing list: https://launchpad.net/~hugin-bug-hunters
Post to : hugin-bug-hunters@lists.launchpad.net
Unsubs

[Hugin-bug-hunters] [Bug 1457165] Re: incorrect documentation for hugin_executor(1)

2015-06-22 Thread tmodes
** Changed in: hugin
   Status: Fix Committed => Fix Released

** Changed in: hugin
Milestone: None => 2015.0rc1

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

Title:
  incorrect documentation for hugin_executor(1)

Status in Hugin - Panorama Tools GUI:
  Fix Released

Bug description:
  Hello,

  hugin_executor(1) says:
 -p, --prefix=str
 Prefix used for stitching. If not provided the stitched image will
 have the name of the input project file.
   
  However if ~/.hugin does not exist then '%firstimage - %lastimage' will be 
used and otherwise the behavior is controlled by the value of OutputFilename in 
~/.hugin.

  cu Andreas

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

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


[Hugin-bug-hunters] [Bug 1465823] Re: hugin batch processor stops after making pto

2015-06-22 Thread tmodes
Thanks.
Should be now fixed in repository and will be in release candidate 2, which 
will be released next weekend.

** Changed in: hugin
   Status: New => Fix Committed

** Changed in: hugin
Milestone: None => 2015.0rc2

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

Title:
  hugin batch processor stops after making pto

Status in Hugin - Panorama Tools GUI:
  Fix Committed

Bug description:
  Hi,

  I am working with the current  RC1 (2015.0.0.d497c7fc1866) on Ubuntu
  14.04.

  My normal work flow is as follows:

  - put all single images in folder
  - start batch processer - look for pictures -start - select

  In between there is the message: Assertion failed! ... 
/usr/include/wx-3.0/wx/strvararg.h(451): 
  Ok, I can click away that.

  - I start the batch.
  - First window opens: .processing of pto file (pto file is saved)
  - Second progress window opens (which should make the actual stiched 
panorama).

  Nothing further happens, I cannot close or make any changes have to
  xkill everything.

  Upon restarting the batcher withthe  pto file. Image is made.

  
  Greetings,

  Georg

  
  PS: The image preview after looking for single pictures in the folder is 
great !

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

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


[Hugin-bug-hunters] [Bug 1465698] Re: Fast panorama preview: show/hide first photo of stack

2015-06-22 Thread tmodes
I implemented something similar in default branch (it will not be in version 
2015.0 because we are in a string freeze and this feature adds new strings.)
The "show all" button in the fast preview window got a context menu. In the 
context menu you can select which images the "show all" button should select.

** Changed in: hugin
   Importance: Undecided => Wishlist

** Changed in: hugin
   Status: New => Fix Committed

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

Title:
  Fast panorama preview: show/hide first photo of stack

Status in Hugin - Panorama Tools GUI:
  Fix Committed

Bug description:
  I have a suggestion for a usability improvement. Many of my projects
  involve HDR spherical panoramas. Usually I only enable the first photo
  of each HDR stack in the preview. However, sometimes I want to hide
  some photos, do some editing, then show all first-of-stack photos
  again.

  My issue is that it's hard to select each Nth photo of each stack.
  There is no visual indication of which photos belong to which stack,
  so I have to remember the stack size (I work with 3, 5 and 7 photos
  per stack, depending on the project), then do the math myself, then
  manually select 38 photos. It would seem that a computer is more
  suitable for this task. It would be sweet to be able to do this with a
  single click.

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

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