[Hugin-devs] [Bug 1751343] Re: Hotkey zoom controls for mask tab
** 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/1751343 Title: Hotkey zoom controls for mask tab Status in Hugin: Fix Released Bug description: It is possible to use hotkeys 0, 1 and 2 to zoom in on the image in control points tab. Similar hotkeys would be very useful in mask tab too. Maybe additional hotkeys for 50% and 25% zooms too? To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/1751343/+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 1750398] Re: align_image_stack fails to open EXR files
** 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/1750398 Title: align_image_stack fails to open EXR files Status in Hugin: Fix Released Bug description: align_image_stack fails to open EXR files generated with darktable, the output is as follow: $ align_image_stack DSCF4117.exr DSCF4118.exr -p OUT.exr /build/hugin/src/hugin-2018.0.0/src/hugin_base/panodata/SrcPanoImage.cpp 346 Error opening file /build/hugin/src/hugin-2018.0.0/src/hugin_base/panodata/SrcPanoImage.cpp 346 Error opening file Written project file OUT.exr (an output file is generated, but it is only 12.9KB) I have tried every compression method (off, RLE, ZIP, ZIPS, PIZ, PXR24, B44, B44A) and the result is consistent. I'm using Arch Linux with hugin 2018 and openexr 2.2.0. To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/1750398/+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 1811441] Re: media-gfx/hugin-2018.0.0 with media-gfx/exiv2-0.27.0: Exiv2Helper.cpp:566:23: error: missing binary operator before token "("
This was already fixed in changeset
c7fe8d5afb5f667892f088dc656169e5e8ddf11e 8 weeks ago.
** Changed in: hugin
Status: New => Fix Committed
** Changed in: hugin
Milestone: None => 2019.0beta1
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Hugin.
https://bugs.launchpad.net/bugs/1811441
Title:
media-gfx/hugin-2018.0.0 with media-gfx/exiv2-0.27.0:
Exiv2Helper.cpp:566:23: error: missing binary operator before token
"("
Status in Hugin:
Fix Committed
Bug description:
cf. https://bugs.gentoo.org/673730
In src/hugin_base/panodata/Exiv2Helper.cpp, it is sufficient to
replace
#include "exiv2/easyaccess.hpp"
by
#include
To manage notifications about this bug go to:
https://bugs.launchpad.net/hugin/+bug/1811441/+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 1810594] Re: nona option to set range compression
Good catch. That was an oversight from an earlier development version. I fixed this to atof. -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/1810594 Title: nona option to set range compression Status in Hugin: Fix Committed Bug description: Probably could be helpful to have ability to override range compression in the nona command line. This patch adds "--range- compression" option. To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/1810594/+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 1810594] Re: nona option to set range compression
Thanks for the patch. I committed a slightly modified version. (I prefer the precedence of the exposure switches over the range compression switch.) Also the range check was wrong. Additionally I added the same switch to pano_modify. ** Changed in: hugin Status: New => Fix Committed ** Changed in: hugin Milestone: None => 2019.0beta1 -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/1810594 Title: nona option to set range compression Status in Hugin: Fix Committed Bug description: Probably could be helpful to have ability to override range compression in the nona command line. This patch adds "--range- compression" option. To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/1810594/+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 1809782] Re: Hugin icons blurred in Gnome
Changeset ff4d3dc8c63d install now also bigger versions of the icon files. ** Changed in: hugin Status: New => Fix Committed ** Changed in: hugin Milestone: None => 2019.0beta1 -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/1809782 Title: Hugin icons blurred in Gnome Status in Hugin: Fix Committed Bug description: In gnome, hugin related icons are blurred. Maybe they need to be in a higher resolution or svg files need to be used? I'm using hugin compiled from default under Ubuntu 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/1809782/+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 1810110] Re: Request flat or panned image stitching mode
First, this request would needed to rewrite big parts of the program new. Second, this is already possible and documented here http://hugin.sourceforge.net/tutorials/scans/en.shtml Derived for this tutorial there is also an user-defined assistant available (Edit>user defined assistant>scanned images). ** Changed in: hugin Status: New => 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/1810110 Title: Request flat or panned image stitching mode Status in Hugin: Fix Released Bug description: Sometimes in video documentaries or animation an image is too large to fit all at once, so the view is panned across. It's not a perspective move, everything is flat. The frames can be stitched manually using GIMP, but often there are slight defects, because pixels don't always match up to the panning speed 1:1. I tried to use Hugin to stitch, but it seems to be very camera- centric. I could not figure out how to disable the perspective transformations or the exposure changes. I also had to manually play around in the crop window, because the auto-centering stuff just didn't work right. Finally, it failed, telling me that a seam would be visible, and I couldn't figure out how to override and force the output. I request a wizard for stitching flat images, where all it does is figure out the sub-pixel position of each image and then outputs the entire uncropped image (no cropping, rotation, exposure, etc). I could also see this wizard being useful if I wanted to scan in something larger than my flatbed scanner and stitch it together into a single image. If all of this is already possible, I request documentation on how to do it. To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/1810110/+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 1809782] Re: Hugin icons blurred in Gnome
The icon is specified in the hugin.desktop file. There is some documentation about this file format, but I found only spare documentation about how to specify different icon size. https://specifications.freedesktop.org/icon-theme-spec/latest/ar01s07.html https://developer.gnome.org/desktop-entry-spec/ If you found a better spec, post the link. Or you could check what size the other programs install. Check paths /usr/share/pixmaps /usr/share/icons/hicolor/scalable/apps /usr/share/icons -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/1809782 Title: Hugin icons blurred in Gnome Status in Hugin: New Bug description: In gnome, hugin related icons are blurred. Maybe they need to be in a higher resolution or svg files need to be used? I'm using hugin compiled from default under Ubuntu 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/1809782/+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 1809782] Re: Hugin icons blurred in Gnome
I have currently no access to a GNOME desktop and can't test for myself. Currently there is only a 48x48 icon. In the attached patch I added 2 svg variants for the icons and install them additionally. But I don't know if GNOME picks up the correct one or still fall back to the 48x48 png icon. Could you please test the attached patch? Thanks ** Patch added: "Install svg icons" https://bugs.launchpad.net/hugin/+bug/1809782/+attachment/5225115/+files/install_svg_icons.patch -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/1809782 Title: Hugin icons blurred in Gnome Status in Hugin: New Bug description: In gnome, hugin related icons are blurred. Maybe they need to be in a higher resolution or svg files need to be used? I'm using hugin compiled from default under Ubuntu 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/1809782/+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 1808996] Re: updated pt_BR translation
Thanks. I committed your changes. Concerning the issue with push: maybe you have used an older (now non-working) or the read-only address. For me pushing worked with ssh://yoursfusern...@hg.code.sf.net/p/hugin/hugin. ** Changed in: hugin Status: New => Fix Committed ** Changed in: hugin Milestone: None => 2019.0beta1 -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/1808996 Title: updated pt_BR translation Status in Hugin: Fix Committed Bug description: Here's the last updated translation. I was unable to update it via "hg push" this time, I got a HTTP Error 403: Forbidden error. To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/1808996/+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 678925] Re: Column header in cp window wrong after fine tune all points
Fixed in changeset b2a28e4f548f. ** Changed in: hugin Status: Confirmed => Fix Committed ** Changed in: hugin Milestone: None => 2019.0beta1 -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/678925 Title: Column header in cp window wrong after fine tune all points Status in Hugin: Fix Committed Bug description: From Alex Clarks Post on hugin-ptx: > After "fine-tune all points", the distance column does > not contain distances but the correlation value. [...] > It goes back to displaying distances after an > optimisation. The header always reads "Distance", so this is confusing to the user, it should either change according to the content or another column should be added that always displays correlation values. To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/678925/+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 1460042] Re: option to remove contrast enhanced square in CP editor
The changes were committed yesterday in changeset 61ee38d778bf. Additionally I set the milestone for this bug report to 2019.0 beta1. So it won't be in older versions. -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/1460042 Title: option to remove contrast enhanced square in CP editor Status in Hugin: Fix Committed Bug description: When reviewing (and deleting) auto generated control points, I would very much like to be able to set the "view" to 200% and NOT to have the little contrast-enhanced accuracy-aid appear. The enhanced window obscures the *context* of the control point, which is crucial during this process. Feature request: option to turn OFF the contrast enhanced, zoomed, square. BugBear To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/1460042/+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 1460042] Re: option to remove contrast enhanced square in CP editor
In the default branch the contrast enhanced zoom square is automatically deactivated when the zoom is 200 % or above. I decided against a new option. For 200 % zoom it is always off. For the smaller zoom it is always on. ** Changed in: hugin Status: New => Fix Committed ** Changed in: hugin Milestone: None => 2018.2beta1 -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/1460042 Title: option to remove contrast enhanced square in CP editor Status in Hugin: Fix Committed Bug description: When reviewing (and deleting) auto generated control points, I would very much like to be able to set the "view" to 200% and NOT to have the little contrast-enhanced accuracy-aid appear. The enhanced window obscures the *context* of the control point, which is crucial during this process. Feature request: option to turn OFF the contrast enhanced, zoomed, square. BugBear To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/1460042/+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 1054617] Re: Columns of tables should be sortable
In default branch the table on the cp tab is now sortable. ** Changed in: hugin Status: Triaged => Fix Committed ** Changed in: hugin Milestone: None => 2018.2beta1 -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/1054617 Title: Columns of tables should be sortable Status in Hugin: Fix Committed Bug description: Within hugin there are many tables, e.g. for the control points. When searching fo a particularly bad fitting control point pair it would be great if the table columns would be sortable. Of course scenarios are thinkable for all tables in hugin, so all tables should offer the possibility to sort for a specific column. To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/1054617/+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 1801512] Re: Import Raw Files raw filter is broken
** Changed in: hugin Milestone: None => 2018.2beta1 -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/1801512 Title: Import Raw Files raw filter is broken Status in Hugin: Fix Committed Bug description: I tried Edit > Import raw files. The Import Raw Files window opens. I'm in a test-folder with raw files from many camera makes and models, many raw formats, including DNG. The filter is set to "RAW files" (incorrect capitalization), but no raw files are shown. When I change the filter to "All files (*)" then it shows them. In fact, when the filter is set to raw files, the only things visible in the window are folders. I couldn't get a single file to appear. To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/1801512/+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 1785555] Re: Remember state of Overview and Grid between sessions in OpenGL preview
** Changed in: hugin Milestone: None => 2018.2beta1 -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/178 Title: Remember state of Overview and Grid between sessions in OpenGL preview Status in Hugin: Fix Committed Bug description: Hello Hugin does not remember the state of "View > Overview" and "View > Grid" between sessions in the OpenGL editor, so every time I run Hugin I have to hide those. Would be nice if it remembered the setting. Operating System: Linux 4.17.0-sabayon x86_64 Architecture: 64 bit Free memory: 2187192 kiB Hugin Version: 2018.0.0.5abfb4de7961 Path to resources: /usr/share/hugin/xrc/ Path to data: /usr/share/hugin/data/ Hugins camera and lens database: /home/morgan/.hugindata/camlens.db Multi-threading using C++11 std::thread and OpenMP Monitor profile: B133HAN02.1 #1 2016-10-19 21-46 D6500 2.2 F-S XYZLUT+MTX Libraries wxWidgets: wxWidgets 3.0.4 wxWidgets Library (wxGTK port) Version 3.0.4 (Unicode: wchar_t, debug level: 1), compiled at Jun 14 2018 19:21:01 Runtime version of toolkit used is 2.24. Compile-time GTK+ version is 2.24.31. libpano13: 2.9.19 Boost: 1.65.0 Exiv2: 0.26 SQLite3: 3.23.1 Vigra: 1.11.0 LittleCMS2: 2.9 To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/178/+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 1785562] Re: Photos tab has distracting grid color
** Changed in: hugin Milestone: None => 2018.2beta1 -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/1785562 Title: Photos tab has distracting grid color Status in Hugin: Fix Committed Bug description: When run using a dark theme (Breeze Dark, standard KDE theme), the Photos tab has a white grid. It contrasts too much with the background and is distracting. https://i.imgur.com/SjIzQwF.png Please reduce the contrast or remove it altogether. The user can after all just click a row to have a selection-highlight appear to help see which values belong to which row. https://i.imgur.com/Abdzz9q.png System settings: https://i.imgur.com/ttAwqiP.png Operating System: Linux 4.17.0-sabayon x86_64 Architecture: 64 bit Free memory: 1389288 kiB Hugin Version: 2018.0.0.5abfb4de7961 Path to resources: /usr/share/hugin/xrc/ Path to data: /usr/share/hugin/data/ Hugins camera and lens database: /home/morgan/.hugindata/camlens.db Multi-threading using C++11 std::thread and OpenMP Monitor profile: B133HAN02.1 #1 2016-10-19 21-46 D6500 2.2 F-S XYZLUT+MTX Libraries wxWidgets: wxWidgets 3.0.4 wxWidgets Library (wxGTK port) Version 3.0.4 (Unicode: wchar_t, debug level: 1), compiled at Jun 14 2018 19:21:01 Runtime version of toolkit used is 2.24. Compile-time GTK+ version is 2.24.31. libpano13: 2.9.19 Boost: 1.65.0 Exiv2: 0.26 SQLite3: 3.23.1 Vigra: 1.11.0 LittleCMS2: 2.9 To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/1785562/+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 1802790] Re: [PATCH] proper check for sys/sysctl.h at build time
Thanks for the patch. But the code in the mentioned file was not used anymore. So I removed the whole file without the need to change the build system. ** Changed in: hugin Status: New => Fix Committed ** Changed in: hugin Milestone: None => 2018.2beta1 -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/1802790 Title: [PATCH] proper check for sys/sysctl.h at build time Status in Hugin: Fix Committed Bug description: The "platform" part of "hugin_utils" has an hardcoded list of platforms where sys/sysctl.h is not present (basically Windows, and Solaris). This is because sys/sysctl.h is not a standard POSIX header. OTOH, there are more platforms without that header, for example GNU/Hurd. A better way is to check whether sys/sysctl.h exists, and include it only in that case. Attached there is a hg commit that does this. To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/1802790/+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 1801519] Re: Importing DNG files using RawTherapee fails
** Changed in: hugin
Status: Incomplete => Fix Committed
** Changed in: hugin
Milestone: None => 2018.2beta1
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Hugin.
https://bugs.launchpad.net/bugs/1801519
Title:
Importing DNG files using RawTherapee fails
Status in Hugin:
Fix Committed
Bug description:
I clicked on Edit > Import Raw Files, changed the filter to "All files
(*)" (see bug 1801512), selected some DNG files (from Adobe DNG
Converter 11.0), clicked "Import", and it failed with:
Executing: /home/morgan/programs/rawtherapee/rawtherapee-cli -O
/home/morgan/photos/2018-10-17/2018-10-17\ 1\ 03.tif -p /tmp/rt.pp3 -s -p
/tmp/.mount_Hugin_obDWOJ/usr/share/hugin/datahugin_rt.pp3 -tz -Y -c
/home/morgan/photos/2018-10-17/2018-10-17\ 1\ 03.dng
RawTherapee, version 5.4-1075-gd75741a99, command line.
Error: "/tmp/.mount_Hugin_obDWOJ/usr/share/hugin/datahugin_rt.pp3" not found.
What is datahugin_rt.pp3?
Recommendations:
1. Hugin should allow the user to specify a custom processing profile, or use
the one alongside the file if one exists. And it does - good! It does so thanks
to specifying a custom -p before -s.
2. Use uncompressed 16-bit TIFF files as intermediate files, because they are
fast to write and the user loses no image quality along the way. Hugin does not
handle 32-bit files correctly yet.
Changing the above command as needed, the final command should look as
follows:
"${HOME}/programs/rawtherapee/rawtherapee-cli" -O "/tmp/2018-10-17 1
03.tif" -p /tmp/rt.pp3 -s -b16 -t -Y -c
"/home/morgan/photos/2018-10-17/2018-10-17 1 03.dng"
To manage notifications about this bug go to:
https://bugs.launchpad.net/hugin/+bug/1801519/+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 1801519] Re: Importing DNG files using RawTherapee fails
Done. I added the -b16 switch for the RT processing.
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Hugin.
https://bugs.launchpad.net/bugs/1801519
Title:
Importing DNG files using RawTherapee fails
Status in Hugin:
Incomplete
Bug description:
I clicked on Edit > Import Raw Files, changed the filter to "All files
(*)" (see bug 1801512), selected some DNG files (from Adobe DNG
Converter 11.0), clicked "Import", and it failed with:
Executing: /home/morgan/programs/rawtherapee/rawtherapee-cli -O
/home/morgan/photos/2018-10-17/2018-10-17\ 1\ 03.tif -p /tmp/rt.pp3 -s -p
/tmp/.mount_Hugin_obDWOJ/usr/share/hugin/datahugin_rt.pp3 -tz -Y -c
/home/morgan/photos/2018-10-17/2018-10-17\ 1\ 03.dng
RawTherapee, version 5.4-1075-gd75741a99, command line.
Error: "/tmp/.mount_Hugin_obDWOJ/usr/share/hugin/datahugin_rt.pp3" not found.
What is datahugin_rt.pp3?
Recommendations:
1. Hugin should allow the user to specify a custom processing profile, or use
the one alongside the file if one exists. And it does - good! It does so thanks
to specifying a custom -p before -s.
2. Use uncompressed 16-bit TIFF files as intermediate files, because they are
fast to write and the user loses no image quality along the way. Hugin does not
handle 32-bit files correctly yet.
Changing the above command as needed, the final command should look as
follows:
"${HOME}/programs/rawtherapee/rawtherapee-cli" -O "/tmp/2018-10-17 1
03.tif" -p /tmp/rt.pp3 -s -b16 -t -Y -c
"/home/morgan/photos/2018-10-17/2018-10-17 1 03.dng"
To manage notifications about this bug go to:
https://bugs.launchpad.net/hugin/+bug/1801519/+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 1801543] Re: Distracting white background in OpenGL viewer
Hugin was using wxSYS_COLOUR_APPWORKSPACE. This seems to be unsuited on GTK. Fixed in repository. ** Changed in: hugin Status: Opinion => Fix Committed ** Changed in: hugin Milestone: None => 2018.2beta1 -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/1801543 Title: Distracting white background in OpenGL viewer Status in Hugin: Fix Committed Bug description: In 2018.0.0.5abfb4de7961 in the OpenGL viewer the area immediately around the images is black, good, but the area on both sides of that area is a very distracting white. Would be better if it was black. To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/1801543/+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 1801543] Re: Distracting white background in OpenGL viewer
The color of the control is not changed by Hugin. It takes the color from the theme. Also a different color is helpful to see the size of the full canvas and so facilitate setting the crop. ** Changed in: hugin Status: New => Opinion -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/1801543 Title: Distracting white background in OpenGL viewer Status in Hugin: Opinion Bug description: In 2018.0.0.5abfb4de7961 in the OpenGL viewer the area immediately around the images is black, good, but the area on both sides of that area is a very distracting white. Would be better if it was black. To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/1801543/+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 1785563] Re: OpenGL preview grid very distracting
This can't be changed easily and would require a complete rewrite of the grid code. But you can disable the grid. Background: The grid is OpenGL texture with a fixed size which is remapped to the corresponding projection. If we reduce the line thickness in the texture the grid will be not visible for a wide fov (e.g. 360 deg HFOV). So the thickness was optimized for wider fov which is more often used then very small fov as your screenshot. -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/1785563 Title: OpenGL preview grid very distracting Status in Hugin: New Bug description: Hello The cyan grid in the OpenGL preview is very fat and very distracting. How can I change the color to something less distracting, and change the line thickness to 1px? To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/1785563/+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 1801512] Re: Import Raw Files raw filter is broken
Fixed in repository. ** Changed in: hugin Status: Incomplete => Fix Committed -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/1801512 Title: Import Raw Files raw filter is broken Status in Hugin: Fix Committed Bug description: I tried Edit > Import raw files. The Import Raw Files window opens. I'm in a test-folder with raw files from many camera makes and models, many raw formats, including DNG. The filter is set to "RAW files" (incorrect capitalization), but no raw files are shown. When I change the filter to "All files (*)" then it shows them. In fact, when the filter is set to raw files, the only things visible in the window are folders. I couldn't get a single file to appear. To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/1801512/+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 1801509] Re: Don't accept DNG or any raw files using Add Images window
By default with Add images only image files are shown. Only when you select All files you will see the raw files. Here we are using vigra identification of image file. Some raw file are here rejected, but some will accepted, because technical these files are TIFF files. I struggling to remove the all file filter. Then somebody will complain why can you not select e.g. a file with mixed capitalization in the extension. ** Changed in: hugin Status: New => Opinion -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/1801509 Title: Don't accept DNG or any raw files using Add Images window Status in Hugin: Opinion Bug description: Hello, I'm Morgan from RawTherapee. Testing Hugin_Panorama_Creator-git-20181103-x86_64.AppImage for its integration with RawTherapee. I'll open separate issues for things I notice. Edit > Add Images, Hugin accepted raw files as input. Some raw file formats such as Canon's CR2 crash Hugin, some formats such as Fujifilm's RAF are rejected, while other formats such as NEF and DNG are opened and their embedded thumbnails are used. This is wrong, and there are two possible solutions: 1. Do not accept any raw files in the Edit > Add Images dialog. 2. Do accept raw images in the Edit > Add Images dialog, but when the user clicks "Open" then automatically switch over to the "Import raw files" window. To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/1801509/+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 1801519] Re: Importing DNG files using RawTherapee fails
> What is datahugin_rt.pp3?
I should be data/hugin_rt.pp3. In this I reset all crop because the optical
model assume that the optical center and the image center are identical.
>2. Use uncompressed 16-bit TIFF files as intermediate files,
Hugins default for the remapped files is LZW compressed TIFF files. So I used
the same format also for the developed raw files.
> Changing the above command as needed, the final command should look as
> follows:
According to https://rawpedia.rawtherapee.com/Command-Line_Options -b16 is the
default:
-b<8|16>
Specify bit depth per channel (16 by default).
Only applies to TIFF and PNG output, JPEG is always 8.
-t[z]
Specify output to be TIFF (16-bit if -b8 is not set).
Is the documentation wrong? Or is -b16 really the default?
** Changed in: hugin
Status: New => Incomplete
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Hugin.
https://bugs.launchpad.net/bugs/1801519
Title:
Importing DNG files using RawTherapee fails
Status in Hugin:
Incomplete
Bug description:
I clicked on Edit > Import Raw Files, changed the filter to "All files
(*)" (see bug 1801512), selected some DNG files (from Adobe DNG
Converter 11.0), clicked "Import", and it failed with:
Executing: /home/morgan/programs/rawtherapee/rawtherapee-cli -O
/home/morgan/photos/2018-10-17/2018-10-17\ 1\ 03.tif -p /tmp/rt.pp3 -s -p
/tmp/.mount_Hugin_obDWOJ/usr/share/hugin/datahugin_rt.pp3 -tz -Y -c
/home/morgan/photos/2018-10-17/2018-10-17\ 1\ 03.dng
RawTherapee, version 5.4-1075-gd75741a99, command line.
Error: "/tmp/.mount_Hugin_obDWOJ/usr/share/hugin/datahugin_rt.pp3" not found.
What is datahugin_rt.pp3?
Recommendations:
1. Hugin should allow the user to specify a custom processing profile, or use
the one alongside the file if one exists. And it does - good! It does so thanks
to specifying a custom -p before -s.
2. Use uncompressed 16-bit TIFF files as intermediate files, because they are
fast to write and the user loses no image quality along the way. Hugin does not
handle 32-bit files correctly yet.
Changing the above command as needed, the final command should look as
follows:
"${HOME}/programs/rawtherapee/rawtherapee-cli" -O "/tmp/2018-10-17 1
03.tif" -p /tmp/rt.pp3 -s -b16 -t -Y -c
"/home/morgan/photos/2018-10-17/2018-10-17 1 03.dng"
To manage notifications about this bug go to:
https://bugs.launchpad.net/hugin/+bug/1801519/+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 1801512] Re: Import Raw Files raw filter is broken
The file filter is currently set to uppercase extensions. The following filter is in this dialog active: *.DNG;*.CRW;*.CR2;*.CR3;*.RAW;*.ERF;*.RAF;*.MRW;*.NEF;*.ORF;*.RW2;*.PEF;*.SRW;*.ARW Have you lower case extensions? ** Changed in: hugin Status: New => Incomplete -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/1801512 Title: Import Raw Files raw filter is broken Status in Hugin: Incomplete Bug description: I tried Edit > Import raw files. The Import Raw Files window opens. I'm in a test-folder with raw files from many camera makes and models, many raw formats, including DNG. The filter is set to "RAW files" (incorrect capitalization), but no raw files are shown. When I change the filter to "All files (*)" then it shows them. In fact, when the filter is set to raw files, the only things visible in the window are folders. I couldn't get a single file to appear. To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/1801512/+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 1801510] Re: Fix capitalization of the word "raw"
Fixed in repository. ** Changed in: hugin Status: New => Fix Committed ** Changed in: hugin Milestone: None => 2018.2beta1 -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/1801510 Title: Fix capitalization of the word "raw" Status in Hugin: Fix Committed Bug description: The word "raw" is an ordinary noun/adjective, as in "a raw carrot", "a raw image", and as such it should be capitalized "raw", not "RAW" as it is not an acronym nor an abbreviation. When used in sentence case: "Open raw photo" When used in title case: "Open Raw Photo" Places I noticed where it's incorrectly capitalized: 1. "Edit > Import RAW File(s)..." 2. The window which pops up when you click "Edit > Import RAW File(s)..." has incorrect capitalization in the title. Since it's a title it should use title case, so it should be "Import Raw Files". To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/1801510/+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 1801511] Re: Fix capitalization of "dcraw" and "darktable"
Fixed in repository. ** Changed in: hugin Status: New => Fix Committed ** Changed in: hugin Milestone: None => 2018.2beta1 -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/1801511 Title: Fix capitalization of "dcraw" and "darktable" Status in Hugin: Fix Committed Bug description: Both dcraw and darktable are stylized in lowercase. They are incorrectly capitalized in the "Import Raw Files" window. To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/1801511/+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 1801513] Re: RawTherapee - specify processing profile
Fixed in repository. ** Changed in: hugin Status: New => Fix Committed ** Changed in: hugin Milestone: None => 2018.2beta1 -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/1801513 Title: RawTherapee - specify processing profile Status in Hugin: Fix Committed Bug description: The Import Raw Images window has a RawTherapee tab with a textbox called "Default history stack". We don't use the term "history stack", and in fact RawTherapee has a history panel which is never saved, so this term would confuse users. I would suggest renaming "Default history stack" to "Processing profile". http://rawpedia.rawtherapee.com/Main_Page#Processing_Profiles To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/1801513/+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 1798874] Re: Debug Report appears when opening hugin
This sounds like a problem with your graphic driver. Could you check if OpenGL works in other application? Maybe updating the graphic driver can help. Otherwise you can start Hugin with pressed control key and disable the fast preview window. But then some functionality is limited. -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/1798874 Title: Debug Report appears when opening hugin Status in Hugin: Incomplete Bug description: Unable to open the software on my computer. I am running windows 7. A debug report appears with hugin.xml and hugin.dmp listed as files in the report. If I unchecked them and click ok nothing happens. If I click cancel nothing happens. I've uninstalled and reinstall and restarted nothing works. Please help. To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/1798874/+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 1798874] Re: Debug Report appears when opening hugin
Which Hugin version? Does this happens also with latest version 2018.0? If this also happens with the latest version 2018.0 please attach the file hugin.xml which the debug report can generate. ** Changed in: hugin Status: New => Incomplete -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/1798874 Title: Debug Report appears when opening hugin Status in Hugin: Incomplete Bug description: Unable to open the software on my computer. I am running windows 7. A debug report appears with hugin.xml and hugin.dmp listed as files in the report. If I unchecked them and click ok nothing happens. If I click cancel nothing happens. I've uninstalled and reinstall and restarted nothing works. Please help. To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/1798874/+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 898553] Re: Problems with right-to-left languages
We have currently no developer on a RTL system, so this is difficult to fix. Have you tried to set the language in the preferences to English explicit and then restart Hugin? -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/898553 Title: Problems with right-to-left languages Status in Hugin: New Bug description: I have tried 2011.4 and 2011.2 versions both 32 and 64bit on WinXP and Win7, and on all the versions its happaned. my computers are right-to-left (Hebrew language). all the fields are aligned to the right, you can see it here: http://www.flickr.com/photos/46856481@N00/6435536139. the control points appear in the reverse order on the image. after trying to align the images, its seems that the process going right, but after it opens the fast panorama preview window and nothing is displayed, you can see it here: http://www.flickr.com/photos/46856481@N00/6435536279. another issue that related is, when I load images and go to control points to add them manually, on the small square zoom that shown display the image from the opposite side of the image, like image is mirrored. in my opinion it all related to the right-to-left problem. To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/898553/+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 1796131] Re: Hugin no start
Please update to latest version 2018.0. I hope that this error was fixed in the last version. If the bug appears also in this version, please provide the backtrace (see the button labeled backtrace in your screenshot). ** Changed in: hugin Status: New => Incomplete -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/1796131 Title: Hugin no start Status in Hugin: Incomplete Bug description: problem when starting Hugin To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/1796131/+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 1795269] Re: black parts inside blend depending on final size
*** This bug is a duplicate of bug 721136 *** https://bugs.launchpad.net/bugs/721136 This is a known bug in enblend. It is difficult to track down. see https://bugs.launchpad.net/enblend/+bug/721136 Workaround is to add switch --primary-seam-generator=nft to enblend options. Or using the internal blender. ** Project changed: hugin => enblend ** This bug has been marked a duplicate of bug 721136 enblend creates an unexplainable black area. -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Enblend. https://bugs.launchpad.net/bugs/1795269 Title: black parts inside blend depending on final size Status in Enblend: New Bug description: Hugin "2018.0.0.5abfb4de7961 built by Thomas" on Windows 10. I'm blending/fusing 21 images covering most of a scene at least twice, with exclusion masks on most of the images where another image covers the same part in a more desirable way. The resulting blended and blended_fused images looked OK (no black "holes" inside the final image) when I had the canvas width equal to 4000 px, but when I increased the canvas width to 8000 px (which automatically scaled the width of the final image as well) then two parts of the new blended_fused image corresponding to exclusion masks turned black, and one of those parts turned black in the new blended image as well. I tried several other canvas widths as well (5000 px, 7000 px, 7500 px, 7732 px, 7738 px, 7740 px, 7742 px) and all but one of those blended and blended_fused images show black parts corresponding to some exclusion masks, but not always the same ones. Three of the blended_fused images show a black area corresponding to one of the original images, with a very sharp left edge but with the right edge gradually fading to black. There is no obvious pattern to which parts turn black for which canvas width. I have occasionally seen such unexpected black parts in blended and blended_fused images before, also with previous versions of hugin. I would then try using an older version of hugin (lately mostly the 2014 version) to stitch the project (without changing any parameters) and that often but not always produced good results. I hadn't before noticed that the canvas width had such influence. I expected that the appearance of the final images with a smaller canvas width would be similar to the appearance of the final images with a larger canvas width, except for the reduction in resolution. I did not expect that there would be interior black parts for some canvas widths but not for others, even nearby others. I attach the blended and blended_fused images at considerably reduced size, but still large enough that you can see where the unexpected black parts are. I also attach the project file, and the logs from two of the stitch operations. The file names begin with a number that is the canvas width. Here is the system information: Operating System: Windows 10 (build 17134), 64-bit edition Architecture: 64 bit Free memory: 3649692 kiB Active Codepage: 1252 (Western European Windows) Hugin Version: 2018.0.0.5abfb4de7961 built by Thomas Path to resources: C:\Program Files\Hugin\share\hugin\xrc\ Path to data: C:\Program Files\Hugin\share\hugin\data\ Hugins camera and lens database: C:\Users\Louis\AppData\Roaming\hugin\camlens.db Multi-threading using C++11 std::thread and OpenMP Monitor profile: C:\WINDOWS\system32\spool\drivers\color\sRGB Color Space Profile.icm Libraries wxWidgets: wxWidgets 3.1.1 wxWidgets Library (wxMSW port) Version 3.1.1 (Unicode: wchar_t, debug level: 1), compiled at Nov 18 2017 10:28:15 Runtime version of toolkit used is 10.0. libpano13: 2.9.19 Exiv2: 0.26 SQLite3: 3.18.0 Vigra: 1.11.0 LittleCMS2: 2.9 To manage notifications about this bug go to: https://bugs.launchpad.net/enblend/+bug/1795269/+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 1789054] Re: Strange red color tint appears when blending images.
The photometric optimizer has probably some problems with the color. Reset the white balance settings (context menu on photos tab, or set Er + Eb for all images to 1) ** Changed in: hugin Status: New => Incomplete -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/1789054 Title: Strange red color tint appears when blending images. Status in Hugin: Incomplete Bug description: Hey, When tring to stitch some spherical panoramas, (mainly with blue sky mid day), after photo align in hugin, I can see both on preview and on the stitch panorama jpeg, a red color tint on some parts of the image, that isn't there on the original photo. for some reason, Hugin adds a red color cast when blending the photos. The red color cast CAN NOT be seen on the original files, it's become visible only after the photo alignment. Can't figure where it's coming from or why Hugin addes it. I can send the original photos and the stitched panorama. Operating System: Windows 7 (build 7601, Service Pack 1), 64-bit edition Architecture: 64 bit Free memory: 11795404 kiB Hugin ver. 2018.0.0 To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/1789054/+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 1787042] Re: Allow rendering to specific size
*** This bug is a duplicate of bug 679878 *** https://bugs.launchpad.net/bugs/679878 ** This bug has been marked a duplicate of bug 679878 stitcher tab FoV/Size relation -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/1787042 Title: Allow rendering to specific size Status in Hugin: New Bug description: Not sure if this is a bug or a missing feature... seams like the latter. I have a pano with a FOV of 150°x70°, and an optimal size of 12341px x 6776px. I would like to render to a height of 4000px and have the width adapt while maintaining the proportion. When I change the height (Stitcher tab), instead of changing the width, the FOV changes. To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/1787042/+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 1787045] Re: TIFF compression setting is being ignored
*** This bug is a duplicate of bug 1761277 *** https://bugs.launchpad.net/bugs/1761277 ** This bug has been marked a duplicate of bug 1761277 "no compression" outputs LZW compressed TIFF -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/1787045 Title: TIFF compression setting is being ignored Status in Hugin: New Bug description: The TIFF compression setting is being ignored. File > Preferences > Stitching > Output format: Default format: TIFF, TIFF compression: LZW. In the Stitcher tab: [x] Exposure corrected, low dynamic range Format: TIFF, Compression: None. Stitch! The saved image uses LZW compression. Version: 2018.0.0.5abfb4de7961 To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/1787045/+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 1785555] Re: Remember state of Overview and Grid between sessions in OpenGL preview
I don't know which one is better, or if both are more or less equal. It is just that beside the main operating system there are now behavior differences between different Linux flavors. This makes testing more complicate. -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/178 Title: Remember state of Overview and Grid between sessions in OpenGL preview Status in Hugin: Fix Committed Bug description: Hello Hugin does not remember the state of "View > Overview" and "View > Grid" between sessions in the OpenGL editor, so every time I run Hugin I have to hide those. Would be nice if it remembered the setting. Operating System: Linux 4.17.0-sabayon x86_64 Architecture: 64 bit Free memory: 2187192 kiB Hugin Version: 2018.0.0.5abfb4de7961 Path to resources: /usr/share/hugin/xrc/ Path to data: /usr/share/hugin/data/ Hugins camera and lens database: /home/morgan/.hugindata/camlens.db Multi-threading using C++11 std::thread and OpenMP Monitor profile: B133HAN02.1 #1 2016-10-19 21-46 D6500 2.2 F-S XYZLUT+MTX Libraries wxWidgets: wxWidgets 3.0.4 wxWidgets Library (wxGTK port) Version 3.0.4 (Unicode: wchar_t, debug level: 1), compiled at Jun 14 2018 19:21:01 Runtime version of toolkit used is 2.24. Compile-time GTK+ version is 2.24.31. libpano13: 2.9.19 Boost: 1.65.0 Exiv2: 0.26 SQLite3: 3.23.1 Vigra: 1.11.0 LittleCMS2: 2.9 To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/178/+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 1785553] Re: Wrong gamma of 32-bit float images in Control Points editor
For float/double images there is the setting in the preferences. So this is not a bug. ** Changed in: hugin Status: New => Won't Fix -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/1785553 Title: Wrong gamma of 32-bit float images in Control Points editor Status in Hugin: Won't Fix Bug description: Hello 32-bit floating-point images (from RawTherapee) are overexposed in the Control Points editor. Maybe they have the wrong gamma applied, or the embedded ICC profile is not used? If you open the source images in GIMP-2.10.4 you will see them correctly with the correct gamma. They are of course very dark, so maybe the CP Editor is trying to make them easier to view for the user through dynamic range compression and increasing exposure. If that's the case, then nice, but the large CP editor magnification box, the one that magnifies the few pixels you are hovering over when placing new CPs, still shows a completely black preview, as you can see in screenshot screenshot_20180806_081643.png. Sample images and screenshots: https://filebin.net/3cp8rzg4e1t84vk2 Please download these, as the link will expire 2 months from now. Operating System: Linux 4.17.0-sabayon x86_64 Architecture: 64 bit Free memory: 2246320 kiB Hugin Version: 2018.0.0.5abfb4de7961 Path to resources: /usr/share/hugin/xrc/ Path to data: /usr/share/hugin/data/ Hugins camera and lens database: /home/morgan/.hugindata/camlens.db Multi-threading using C++11 std::thread and OpenMP Monitor profile: B133HAN02.1 #1 2016-10-19 21-46 D6500 2.2 F-S XYZLUT+MTX Libraries wxWidgets: wxWidgets 3.0.4 wxWidgets Library (wxGTK port) Version 3.0.4 (Unicode: wchar_t, debug level: 1), compiled at Jun 14 2018 19:21:01 Runtime version of toolkit used is 2.24. Compile-time GTK+ version is 2.24.31. libpano13: 2.9.19 Boost: 1.65.0 Exiv2: 0.26 SQLite3: 3.23.1 Vigra: 1.11.0 LittleCMS2: 2.9 To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/1785553/+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 1785555] Re: Remember state of Overview and Grid between sessions in OpenGL preview
There was and is code to save these settings. It seems to work on Windows, Mac and GTK3, but not with GTK2, seufz. Trying to fix in repository. ** Changed in: hugin Status: New => Fix Committed -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/178 Title: Remember state of Overview and Grid between sessions in OpenGL preview Status in Hugin: Fix Committed Bug description: Hello Hugin does not remember the state of "View > Overview" and "View > Grid" between sessions in the OpenGL editor, so every time I run Hugin I have to hide those. Would be nice if it remembered the setting. Operating System: Linux 4.17.0-sabayon x86_64 Architecture: 64 bit Free memory: 2187192 kiB Hugin Version: 2018.0.0.5abfb4de7961 Path to resources: /usr/share/hugin/xrc/ Path to data: /usr/share/hugin/data/ Hugins camera and lens database: /home/morgan/.hugindata/camlens.db Multi-threading using C++11 std::thread and OpenMP Monitor profile: B133HAN02.1 #1 2016-10-19 21-46 D6500 2.2 F-S XYZLUT+MTX Libraries wxWidgets: wxWidgets 3.0.4 wxWidgets Library (wxGTK port) Version 3.0.4 (Unicode: wchar_t, debug level: 1), compiled at Jun 14 2018 19:21:01 Runtime version of toolkit used is 2.24. Compile-time GTK+ version is 2.24.31. libpano13: 2.9.19 Boost: 1.65.0 Exiv2: 0.26 SQLite3: 3.23.1 Vigra: 1.11.0 LittleCMS2: 2.9 To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/178/+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 1785552] Re: 32-bit float image preview broken in OpenGL
*** This bug is a duplicate of bug 696660 *** https://bugs.launchpad.net/bugs/696660 ** This bug has been marked a duplicate of bug 696660 Old preview needs to be merged into Fast Preview window -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/1785552 Title: 32-bit float image preview broken in OpenGL Status in Hugin: New Bug description: Hello 32-bit floating-point images (from RawTherapee) load and are previewed correctly using the "Preview panorama" button, but the preview is broken using "OpenGL Fast panorama preview" - some images are completely black, others completely overexposed. Sample files and screenshots: https://filebin.net/3cp8rzg4e1t84vk2 Please download these, as the link will expire 2 months from now. Operating System: Linux 4.17.0-sabayon x86_64 Architecture: 64 bit Free memory: 2246320 kiB Hugin Version: 2018.0.0.5abfb4de7961 Path to resources: /usr/share/hugin/xrc/ Path to data: /usr/share/hugin/data/ Hugins camera and lens database: /home/morgan/.hugindata/camlens.db Multi-threading using C++11 std::thread and OpenMP Monitor profile: B133HAN02.1 #1 2016-10-19 21-46 D6500 2.2 F-S XYZLUT+MTX Libraries wxWidgets: wxWidgets 3.0.4 wxWidgets Library (wxGTK port) Version 3.0.4 (Unicode: wchar_t, debug level: 1), compiled at Jun 14 2018 19:21:01 Runtime version of toolkit used is 2.24. Compile-time GTK+ version is 2.24.31. libpano13: 2.9.19 Boost: 1.65.0 Exiv2: 0.26 SQLite3: 3.23.1 Vigra: 1.11.0 LittleCMS2: 2.9 To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/1785552/+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 1785562] Re: Photos tab has distracting grid color
This was a bug in the underlying control. Should be fixed in repository now. ** Changed in: hugin Status: New => Fix Committed -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/1785562 Title: Photos tab has distracting grid color Status in Hugin: Fix Committed Bug description: When run using a dark theme (Breeze Dark, standard KDE theme), the Photos tab has a white grid. It contrasts too much with the background and is distracting. https://i.imgur.com/SjIzQwF.png Please reduce the contrast or remove it altogether. The user can after all just click a row to have a selection-highlight appear to help see which values belong to which row. https://i.imgur.com/Abdzz9q.png System settings: https://i.imgur.com/ttAwqiP.png Operating System: Linux 4.17.0-sabayon x86_64 Architecture: 64 bit Free memory: 1389288 kiB Hugin Version: 2018.0.0.5abfb4de7961 Path to resources: /usr/share/hugin/xrc/ Path to data: /usr/share/hugin/data/ Hugins camera and lens database: /home/morgan/.hugindata/camlens.db Multi-threading using C++11 std::thread and OpenMP Monitor profile: B133HAN02.1 #1 2016-10-19 21-46 D6500 2.2 F-S XYZLUT+MTX Libraries wxWidgets: wxWidgets 3.0.4 wxWidgets Library (wxGTK port) Version 3.0.4 (Unicode: wchar_t, debug level: 1), compiled at Jun 14 2018 19:21:01 Runtime version of toolkit used is 2.24. Compile-time GTK+ version is 2.24.31. libpano13: 2.9.19 Boost: 1.65.0 Exiv2: 0.26 SQLite3: 3.23.1 Vigra: 1.11.0 LittleCMS2: 2.9 To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/1785562/+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 1785463] Re: align_stack_images error 1
I don't see the error message which causes the error code. How do you run align_image_stack? From Hugin itself? Or from another program? When running from Hugin, go the preferences, tab general and select "copy log message to clipboard". When you now run align_image_stack the clipboard should contain a more meaningful log. Please post the log from the clipboard here. If this does not work or you are running align_image_stack from another program, run align_image_stack with the given command from the terminal/shell and post the output from the terminal. ** Changed in: hugin Status: New => Incomplete -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/1785463 Title: align_stack_images error 1 Status in Hugin: Incomplete Bug description: Hello while using align_image_stack I got the following message Command: align_image_stack -f 22.616454 -v -p /tmp/ap_res5lUldB "/home/yanez/Pictures/2018_07_22/DSC05084.JPG" "/home/yanez/Pictures/2018_07_22/DSC05088.JPG" failed with error code: 1 I am using an update version of your code. It appear in Ubuntu 16.04 LTS. Operating System: Linux 4.4.0-127-generic x86_64 Architecture: 64 bit Free memory: 1253012 kiB Hugin Version: 2018.0.0.5abfb4de7961 Path to resources: /usr/share/hugin/xrc/ Path to data: /usr/share/hugin/data/ Hugins camera and lens database: /home/yanez/.hugindata/camlens.db Multi-threading using C++11 std::thread and OpenMP Monitor profile: HP 15 Notebook PC 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.58.0 Exiv2: 0.25 SQLite3: 3.11.0 Vigra: 1.10.0 LittleCMS2: 2.6 I found a similar bug in an old version of the code. It was related to unecual size of tiff files. Those are jpg and same size. Regards and thanks in advance. Jorge To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/1785463/+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 1782532] Re: 'new lens' incorrectly sets exposure
Fixed in repository. But keep in mind that when in a stack the position is linked the lens parameters should also be linked - so there shouldn't be different lenses in the same stack. This is not enforced. ** Changed in: hugin Status: New => Fix Committed ** Changed in: hugin Milestone: None => 2018.2beta1 -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/1782532 Title: 'new lens' incorrectly sets exposure Status in Hugin: Fix Committed Bug description: Using Hugin 2018.0.0.5abfb4de7961 on Kubuntu Linux. In short: selecting a stack of exposure-bracketed images, then choosing 'New Lens' causes the photometric parameters of the first image to be used by all the images of the entire stack. To reproduce: - Load an exposure-bracketed stack of images, say with exposures EV=10, 11, 12, 13, 14. - Switch to the Photos tab if not there already, and choose 'Photometric parameters' in the right-hand box of radio buttons. - Check that the photos have different exposures, as expected. - Select all the photos. - Right-click and choose Lens → New Lens. - See that the photos now all have the same exposure. System info: Operating System: Linux 4.15.0-23-generic x86_64 Architecture: 64 bit Free memory: 276816 kiB Hugin Version: 2018.0.0.5abfb4de7961 Path to resources: /usr/share/hugin/xrc/ Path to data: /usr/share/hugin/data/ Hugins camera and lens database: /home/sybren/.hugindata/camlens.db Multi-threading using C++11 std::thread and OpenMP Libraries wxWidgets: wxWidgets 3.0.4 wxWidgets Library (wxGTK port) Version 3.0.4 (Unicode: wchar_t, debug level: 1), Runtime version of toolkit used is 2.24. Compile-time GTK+ version is 2.24.32. libpano13: 2.9.19 Boost: 1.65.1 Exiv2: 0.25 SQLite3: 3.22.0 Vigra: 1.11.0 LittleCMS2: 2.9 To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/1782532/+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 679984] Re: Add support for images in a RAW format
Implemented RAW import function in default branch. ** Changed in: hugin Status: Triaged => Fix Committed ** Changed in: hugin Milestone: None => 2018.2beta1 -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/679984 Title: Add support for images in a RAW format Status in Hugin: Fix Committed Bug description: Instead of using already compressed JPG files, hugin should be able to work with uncompressed RAW image files, such as the NEF format created by Nikon cameras. A possibility to implement this is to use dcraw. See also http://www.cybercom.net/~dcoffin/dcraw/ To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/679984/+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 1778802] Re: PATCH: speed improvements
Thanks again. I committed most patches to repository (some were slightly modified). For ImageVariableGroup.patch: I made Panorama::getImage inline. GetImage should only return the address of the SrcPanoImage class, nothing more is happen in this function. I don't know why this should be so expensive (or is the lookup in the std::vector so expensive?) ** Changed in: hugin Status: New => Fix Committed ** Changed in: hugin Milestone: None => 2018.2beta1 -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/1778802 Title: PATCH: speed improvements Status in Hugin: Fix Committed Bug description: I tried to profile hugin on a large project with 500 images and 10 control points. I identified and fixed some bottlenecks: ImageVariable.patch - reimplemented ImageVariable with shared_ptr - reduces complexity from O(n) to O(1) ImageVariableGroup.patch - move some method calls out of a loop GreatCircles.patch - reduce number of segments for short lines GreatCircles-image.patch - HuginBase::SrcPanoImage is expensive, initialize equirectangularImage only once To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/1778802/+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 1778802] Re: PATCH: speed improvements
Thanks you for your work. Some comments: ImageVariable.patch: This I need to check. This is a big change and I want to understand it before committing it. ImageVariableGroup.patch: This code and similar one is used at several places. Would it also help to inline the getimage function to achieve the same/similar speed improvement? GreatCircles.patch: Already pushed to repository. GreatCircles-image.patch: Instead of the workaround (and the same or similar code is used at several places through the whole repository) we should fix the initialization of the SrcPanoImage class. I tried to rewrite the initialization of this class with modern C++. Could you please try if the attached patch brings the same effect? -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/1778802 Title: PATCH: speed improvements Status in Hugin: New Bug description: I tried to profile hugin on a large project with 500 images and 10 control points. I identified and fixed some bottlenecks: ImageVariable.patch - reimplemented ImageVariable with shared_ptr - reduces complexity from O(n) to O(1) ImageVariableGroup.patch - move some method calls out of a loop GreatCircles.patch - reduce number of segments for short lines GreatCircles-image.patch - HuginBase::SrcPanoImage is expensive, initialize equirectangularImage only once To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/1778802/+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 1778802] Re: PATCH: speed improvements
** Patch added: "New initialization of members of SrcPanoImage class" https://bugs.launchpad.net/hugin/+bug/1778802/+attachment/5157128/+files/SrcPanoImage_init.patch -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/1778802 Title: PATCH: speed improvements Status in Hugin: New Bug description: I tried to profile hugin on a large project with 500 images and 10 control points. I identified and fixed some bottlenecks: ImageVariable.patch - reimplemented ImageVariable with shared_ptr - reduces complexity from O(n) to O(1) ImageVariableGroup.patch - move some method calls out of a loop GreatCircles.patch - reduce number of segments for short lines GreatCircles-image.patch - HuginBase::SrcPanoImage is expensive, initialize equirectangularImage only once To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/1778802/+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 1774036] Re: 2018.0.0 crashes on "load images"
*** This bug is a duplicate of bug 679049 *** https://bugs.launchpad.net/bugs/679049 Sorry, but I can't reproduce the crash. (It does not crash, but shows strange images - because this raw files as internal TIFF images, so it is not easy to distinguish them from TIFF files ) But the main issue with the file is that Hugin does not work with raw files. You need to convert the file to e.g. TIFF with your raw converter before feeding to Hugin. ** Changed in: hugin Status: New => Invalid ** This bug has been marked a duplicate of bug 679049 Crashes when importing RAW files -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/1774036 Title: 2018.0.0 crashes on "load images" Status in Hugin: Invalid Bug description: I've tried downloading Hugin from https://sourceforge.net/projects/hugin/files/hugin/hugin-2018.0/ and via `brew install homebrew/cask/hugin` (which is just a script pointer to the DMG) and the app has the same crashing issue. I've tested this with 2017.0.0 and 2016.2.0 as well (the only other versions with .DMG files on SourceForge). Steps to reproduce: - (install, go through security & privacy process just to open the app) - click "1. Load images..." - load 6 images listed below (or any images at all) - app crashes, error report listed below 6 files used: https://www.dropbox.com/s/nw7b9j3tqpudluh/_MG_9269.CR2?dl=0 https://www.dropbox.com/s/vczmrga36sl7p8o/_MG_9270.CR2?dl=0 https://www.dropbox.com/s/703hqj21wgkw9n1/_MG_9271.CR2?dl=0 https://www.dropbox.com/s/67ht4qusf7weyrq/_MG_9272.CR2?dl=0 https://www.dropbox.com/s/8b6jyl04masbft8/_MG_9273.CR2?dl=0 https://www.dropbox.com/s/7r4w9uloo443jzz/_MG_9274.CR2?dl=0 (I've tried other Canon 5D Mark III files and they crash too) Error log being reported to Apple (see attached) To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/1774036/+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 1758503] Re: Fw: hugin: fails to find control-points, defective
If you set the lens projection to cylindrical when it is a rectilinear
lens it can't work.
** Changed in: hugin
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Hugin.
https://bugs.launchpad.net/bugs/1758503
Title:
Fw: hugin: fails to find control-points, defective
Status in Hugin:
Invalid
Bug description:
Begin forwarded message:
Date: Fri, 23 Mar 2018 08:38:52 +0100
From: andrew glaeser
To: sub...@bugs.debian.org
Subject: hugin: fails to find control-points, defective
- -BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: hugin
Version: 2018.0.0+dfsg-1+b1
Severity: important
Dear Maintainer,
the problem exists since the the stretch-release, in fact the tendency to
defectiveness of the GUI showed already with Jessie+backports, it wasn't
possible to stitch the panoramic views there using the GUI, but one had to do
it on the terminal using this instead:
> hugin_stitch_project (1) - Stitch a hugin project
With the stretch-release the situation worsened, now GUI is not workable at
all anymore, because either the order of images is wrong, so there can be no
control-points found, or otherwise cpoints are found for two images out of
three only.
I used to start off with the Assistant, then switched to the advanced view,
sharing of data between the two now also seems to be broken.
Now it is basically the same story both in the simple view, using the
Assistant or with the advanced view, that hugin is _not_workable_.
I upgraded to the version in Testing (buster):
> andrew@a68n:~$ sat install -t testing hugin
> [sudo] password for andrew:
> The following NEW packages will be installed:
> libilmbase23{a} libopenexr23{a}
> The following packages will be upgraded:
> hugin hugin-data hugin-tools libc-bin libc-l10n libc6 libwxbase3.0-0v5
> libwxgtk3.0-0v5 locales 9 packages upgraded, 2 newly installed, 0 to remove
> and 2131 not upgraded. Need to get 26.4 MB of archives. After unpacking
> 7,211 kB will be used. The following packages have unmet dependencies:
> libc6-dev : Depends: libc6 (= 2.24-11+deb9u3) but 2.27-2 is to be installed
> libc6-i386 : Depends: libc6 (= 2.24-11+deb9u3) but 2.27-2 is to be
> installed libc-dev-bin : Depends: libc6 (< 2.25) but 2.27-2 is to be
> installed open: 20; closed: 36; defer: 4; conflict:
> 4
.Internal
> error: found 2 (choice -> promotion) mappings for a single choice. Internal
> error: found 2 (choice -> promotion) mappings for a single choice. The
> following actions will resolve these dependencies:
>
> Upgrade the following packages:
> 1) libc-dev-bin [2.24-11+deb9u3 (now, stable) -> 2.27-2 (testing)]
> 2) libc6-dev [2.24-11+deb9u3 (now, stable) -> 2.27-2 (testing)]
> 3) libc6-i386 [2.24-11+deb9u3 (now, stable) -> 2.27-2 (testing)]
>
>
>
> Accept this solution? [Y/n/q/?]
> The following NEW packages will be installed:
> libilmbase23{a} libopenexr23{a}
> The following packages will be upgraded:
> hugin hugin-data hugin-tools libc-bin libc-dev-bin libc-l10n libc6
> libc6-dev libc6-i386 libwxbase3.0-0v5 libwxgtk3.0-0v5 locales
> 12 packages upgraded, 2 newly installed, 0 to remove and 2128 not upgraded.
> Need to get 32.2 MB of archives. After unpacking 10.8 MB will be used.
> Do you want to continue? [Y/n/?]
> Get: 1 http://ftp2.de.debian.org/debian buster/main amd64 libc-l10n all
> 2.27-2 [859 kB] Get: 2 http://ftp2.de.debian.org/debian buster/main amd64
> libc6-i386 amd64 2.27-2 [2,852 kB] Get: 3 http://ftp2.de.debian.org/debian
> buster/main amd64 libc-dev-bin amd64 2.27-2 [270 kB] Get: 4
> http://ftp2.de.debian.org/debian buster/main amd64 libc6-dev amd64 2.27-2
> [2,670 kB] Get: 5 http://ftp2.de.debian.org/debian buster/main amd64
> locales all 2.27-2 [3,804 kB] Get: 6 http://ftp2.de.debian.org/debian
> buster/main amd64 libc6 amd64 2.27-2 [2,904 kB] Get: 7
> http://ftp2.de.debian.org/debian buster/main amd64 libc-bin amd64 2.27-2
> [786 kB] Get: 8 http://ftp2.de.debian.org/debian buster/main amd64 hugin
> amd64 2018.0.0+dfsg-1+b1 [1,250 kB] Get: 9 http://ftp2.de.debian.org/debian
> buster/main amd64 hugin-tools amd64 2018.0.0+dfsg-1+b1 [3,141 kB] Get: 10
> http://ftp2.de.debian.org/debian buster/main amd64 hugin-data all
> 2018.0.0+dfsg-1 [7,625 kB] Get: 11 http://ftp2.de.debian.org/debian
> buster/main amd64 libilmbase23 amd64 2.2.1-2 [85.6 kB] Get: 12
> http://ftp2.de.debian.org/debian buster/main amd64 libopenexr23 amd64
> 2.2.1-4 [579 kB] Get: 13 http://ftp2.de.debian.org/debian buster/main amd64
> libwxbase3.0-0v5 amd64 3.0.3.1+dfsg2-1 [1,063 kB] Get: 14
> http://ftp2.de.debian.org/debian buster/main amd64 libwxgtk3.0-0v5 amd64
> 3.0.3.1+dfsg2-1 [4
[Hugin-devs] [Bug 1770946] Re: Package Hugin as flatpak
I cited from out download page: The Hugin project makes reasonable efforts to ensure that the released source code builds on a wide variety of platforms. We also provide information how to build the source code (links below). We don't have the resources to go beyond that. Sometimes we also don't have access to specific platforms and can't guarantee that the code builds either. Please don't ask us for binaries / pre-compiled versions. We believe that if a group of users of a specific platform feels the need, they will eventually produce them. We don't have the resources to host a flatpak repository. If some user wants to do this (e.g. push it to another flatpak hoster), he/she should go ahead. We will happily accept patches needed to implement this. But we will don't it on our own. Sorry. ** Changed in: hugin Status: New => Incomplete -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/1770946 Title: Package Hugin as flatpak Status in Hugin: Incomplete Bug description: Hi, I would like to ask to package Hugin as a flatpak, which is a Linux distribution agnostic way of delivering software. The documentation about it can be found here: http://docs.flatpak.org/en/latest/ That would bring several advantages for Linux users and developers, such as being able to use the latest version of the application on several distributions and different versions (old LTS or a just released one), it avoids dependency problems, it allows application sandboxing, and more: http://docs.flatpak.org/en/latest/introduction.html#target-audience Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/1770946/+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 1763929] Re: hugin_stacker doesn't stack floating point files
Implemented support for UINT32, float and double pixel types in hugin_stacker in default branch. ** Summary changed: - hugin_stack doesn't stack floating point files + hugin_stacker doesn't stack floating point files ** Changed in: hugin Status: New => Fix Committed ** Changed in: hugin Milestone: None => 2018.2beta1 -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/1763929 Title: hugin_stacker doesn't stack floating point files Status in Hugin: Fix Committed Bug description: Would be nice if it did. I tried stacking with Raw Therapee's 32bit floating point files, remapping went smoothly but hugin_stack ended up throwing this error "unsupported pixel type: FLOAT". To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/1763929/+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 679912] Re: add ability to change location of .hugin
** Changed in: hugin Milestone: None => 2018.2beta1 -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/679912 Title: add ability to change location of .hugin Status in Hugin: Fix Committed Bug description: Add an possibility to change location or file name of the ini-file ~/.hugin (on Linux), for ex. using a command line option. The reason is that there is another program called Hugin (www.hugin.com), which actually pre-dates your Hugin, and it uses the same ini-file - so they mess it up for each other. I have asked them and the path ~/.hugin is hard-coded there, so my only hope for using both is to change it in your Hugin. Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/679912/+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 1754126] Re: Low resolution blurred GUI on macOS High Sierra with retina screen, solution provided
** Changed in: hugin Milestone: None => 2018.2beta1 -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/1754126 Title: Low resolution blurred GUI on macOS High Sierra with retina screen, solution provided Status in Hugin: Fix Committed Bug description: I have attached a screenshot with the two versions of Hugin, with and without the fix. The differences are not well pronounced on the image, so please zoom in if you cannot see the differences clearly. If you open the GUI for the fist time even without starting a project you immediately see the low resolution of the GUI on a retina screen. I have worked out a solution for the problem, add NSHighResolutionCapable to the „Info.plist“ file. To do so, view the Hugin.app package and open „Hugin.app/Contents/Info.plist“ in your favorite text editor. At the end of the file you will see something like this: CFBundleDocumentTypes … Then add this almost at the end of the file BEFORE and : NSHighResolutionCapable True So that the end looks like this: CFBundleDocumentTypes … NSHighResolutionCapable True With this fix the app is high resolution capable and looks like any other app on macOS. So far I tested this works without problems, if I notice some problems with this fix I’ll notify you. I would be glad if you would apply the fix for the macOS version. But nether the less thank you for the great panorama stitching tool 👍. Here are some information: Link to Apple Developer site: https://developer.apple.com/library/content/documentation/GraphicsAnimation/Conceptual/HighResolutionOSX/Explained/Explained.html macOS Version: High Sierra 10.13.3 Here is a dump of the System window: Operating System: Mac OS X (Darwin 17.4.0 x86_64) Architecture: 64 bit Free memory: 0 kiB Hugin Version: 2018.0.0.5abfb4de7961 built by Niklas Mischkulnig Path to resources: /private/var/folders/l3/.../T/AppTranslocation/.../d/Hugin.app/Contents/Resources/xrc/ Path to data: /private/var/folders/l3/.../T/AppTranslocation/.../d/Hugin.app/Contents/Resources/xrc/ Hugins camera and lens database: /Users/***/.hugindata/camlens.db Multi-threading using C++11 std::thread and OpenMP Monitor profile: /Library/ColorSync/Profiles/Displays/Color LCD-----.icc Libraries wxWidgets: wxWidgets 3.0.3 wxWidgets Library (wxMac port) Version 3.0.3 (Unicode: wchar_t, debug level: 0), compiled at Jan 19 2018 22:52:55 Runtime version of toolkit used is 10.13. libpano13: 2.9.19 Boost: 1.64.0 Exiv2: 0.25 SQLite3: 3.19.3 Vigra: 1.11.0 LittleCMS2: 2.8 To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/1754126/+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 1758503] Re: Fw: hugin: fails to find control-points, defective
What the heck?
Your examples does not belong to a single panorama. They are shot from several
places. And there is a totally unconnected image mixed in. The assistant will
not work for this complete image set.
When I take only a subset, e.g. images DSC01056 - DSC01059.JPG, the assistant
works fine.
When I load your example image Hugin ask me for the crop factor/field of
view. (Hugin does not ask you because you already stitched images from
this camera on you camera. And this information is used when you add a
new image.) But probably the information stored in your lens database is
wrong (each user has it's own database). This is FAQ
https://wiki.panotools.org/Hugin_FAQ#After_adding_an_image_the_focal_length_is_another_value_than_the_EXIF_value
as already written, even if you don't believe it.
** Changed in: hugin
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Hugin.
https://bugs.launchpad.net/bugs/1758503
Title:
Fw: hugin: fails to find control-points, defective
Status in Hugin:
Invalid
Bug description:
Begin forwarded message:
Date: Fri, 23 Mar 2018 08:38:52 +0100
From: andrew glaeser
To: sub...@bugs.debian.org
Subject: hugin: fails to find control-points, defective
- -BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: hugin
Version: 2018.0.0+dfsg-1+b1
Severity: important
Dear Maintainer,
the problem exists since the the stretch-release, in fact the tendency to
defectiveness of the GUI showed already with Jessie+backports, it wasn't
possible to stitch the panoramic views there using the GUI, but one had to do
it on the terminal using this instead:
> hugin_stitch_project (1) - Stitch a hugin project
With the stretch-release the situation worsened, now GUI is not workable at
all anymore, because either the order of images is wrong, so there can be no
control-points found, or otherwise cpoints are found for two images out of
three only.
I used to start off with the Assistant, then switched to the advanced view,
sharing of data between the two now also seems to be broken.
Now it is basically the same story both in the simple view, using the
Assistant or with the advanced view, that hugin is _not_workable_.
I upgraded to the version in Testing (buster):
> andrew@a68n:~$ sat install -t testing hugin
> [sudo] password for andrew:
> The following NEW packages will be installed:
> libilmbase23{a} libopenexr23{a}
> The following packages will be upgraded:
> hugin hugin-data hugin-tools libc-bin libc-l10n libc6 libwxbase3.0-0v5
> libwxgtk3.0-0v5 locales 9 packages upgraded, 2 newly installed, 0 to remove
> and 2131 not upgraded. Need to get 26.4 MB of archives. After unpacking
> 7,211 kB will be used. The following packages have unmet dependencies:
> libc6-dev : Depends: libc6 (= 2.24-11+deb9u3) but 2.27-2 is to be installed
> libc6-i386 : Depends: libc6 (= 2.24-11+deb9u3) but 2.27-2 is to be
> installed libc-dev-bin : Depends: libc6 (< 2.25) but 2.27-2 is to be
> installed open: 20; closed: 36; defer: 4; conflict:
> 4
.Internal
> error: found 2 (choice -> promotion) mappings for a single choice. Internal
> error: found 2 (choice -> promotion) mappings for a single choice. The
> following actions will resolve these dependencies:
>
> Upgrade the following packages:
> 1) libc-dev-bin [2.24-11+deb9u3 (now, stable) -> 2.27-2 (testing)]
> 2) libc6-dev [2.24-11+deb9u3 (now, stable) -> 2.27-2 (testing)]
> 3) libc6-i386 [2.24-11+deb9u3 (now, stable) -> 2.27-2 (testing)]
>
>
>
> Accept this solution? [Y/n/q/?]
> The following NEW packages will be installed:
> libilmbase23{a} libopenexr23{a}
> The following packages will be upgraded:
> hugin hugin-data hugin-tools libc-bin libc-dev-bin libc-l10n libc6
> libc6-dev libc6-i386 libwxbase3.0-0v5 libwxgtk3.0-0v5 locales
> 12 packages upgraded, 2 newly installed, 0 to remove and 2128 not upgraded.
> Need to get 32.2 MB of archives. After unpacking 10.8 MB will be used.
> Do you want to continue? [Y/n/?]
> Get: 1 http://ftp2.de.debian.org/debian buster/main amd64 libc-l10n all
> 2.27-2 [859 kB] Get: 2 http://ftp2.de.debian.org/debian buster/main amd64
> libc6-i386 amd64 2.27-2 [2,852 kB] Get: 3 http://ftp2.de.debian.org/debian
> buster/main amd64 libc-dev-bin amd64 2.27-2 [270 kB] Get: 4
> http://ftp2.de.debian.org/debian buster/main amd64 libc6-dev amd64 2.27-2
> [2,670 kB] Get: 5 http://ftp2.de.debian.org/debian buster/main amd64
> locales all 2.27-2 [3,804 kB] Get: 6 http://ftp2.de.debian.org/debian
> buster/main amd64 libc6 amd64 2.27-2 [2,904 kB] Get: 7
> http://ftp2.de.debian.org/debian buster/main amd64 libc-bin amd64 2.27-2
> [786 kB] Get: 8 http://ftp2.de.debian
[Hugin-devs] [Bug 1761280] Re: sort some items in Hugin Prefs in a different way
I thought about this. But I think the current placement makes more sense: 1.) When disabling the "choose alternative program" only the program text field is disabled. The argument text field remains enabled. This should provide a feedback that the checkbox affects only the first text field. 2.) Normally you give first the program name and then the arguments. Reverse the order would contradict this "normal" order. 3.) When you give first the arguments and then the program name then somebody could also think that the argument does not belong to the given program name below (and he/she would put the arguments for the alternative program in the program text field, where there are wrong.) ** Changed in: hugin Status: New => Opinion -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/1761280 Title: sort some items in Hugin Prefs in a different way Status in Hugin: Opinion Bug description: Not a real bug but just to make sure that less advanced users are not puzzled. In Preferences "Programs" the two topics Enblend and Enfuse each show one selection [ ] choose alternative program followed by two input fields: the first for an alternative path and a second for default arguments. This way of sorting items could be read as if the "default arguments" are only valid for alternative executables. I propose resorting items like this: Default Arguments: All arguments set here are defaults for new projects (...) they are set by hugin -> (last sentence should also end with a full stop) [ ] Use alternative (...) program: [Choose executable...] This way it is made clear that "default arguments" are valid for both an alternative program as well as for the built in version. To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/1761280/+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 1761277] Re: "no compression" outputs LZW compressed TIFF
The problem is enblend. The bug has already fixed in changeset 882d3ccba621, but is not yet included in a released version. ** Project changed: hugin => enblend ** Changed in: enblend Status: New => Fix Committed -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Enblend. https://bugs.launchpad.net/bugs/1761277 Title: "no compression" outputs LZW compressed TIFF Status in Enblend: Fix Committed Bug description: I want to stitch 16 bit Tiffs and set Hugin to output a panorama without compression. For some unknown reason this is ignored and the 16 bit panorama is larger than expected. exiftool reports Compression: LZW Hugin 2018.0.0 on Mac OS X 10.11 This happens with scans as well as with Tiffs from RAW files. To manage notifications about this bug go to: https://bugs.launchpad.net/enblend/+bug/1761277/+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 679912] Re: add ability to change location of .hugin
The default branch is now using the XDG specification to store the settings (when compiled with wxWidgets 3.1.1 or later). With this it is possible to change the location of the setting file by setting environment variable XDG_CONFIG_HOME. ** Changed in: hugin Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/679912 Title: add ability to change location of .hugin Status in Hugin: Fix Committed Bug description: Add an possibility to change location or file name of the ini-file ~/.hugin (on Linux), for ex. using a command line option. The reason is that there is another program called Hugin (www.hugin.com), which actually pre-dates your Hugin, and it uses the same ini-file - so they mess it up for each other. I have asked them and the path ~/.hugin is hard-coded there, so my only hope for using both is to change it in your Hugin. Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/679912/+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 1758503] Re: Fw: hugin: fails to find control-points, defective
"Assistant is not workable" is not sufficient to debug the issue.
Provide a small test project for testing (images + pto file).
** Changed in: hugin
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Hugin.
https://bugs.launchpad.net/bugs/1758503
Title:
Fw: hugin: fails to find control-points, defective
Status in Hugin:
Incomplete
Bug description:
Begin forwarded message:
Date: Fri, 23 Mar 2018 08:38:52 +0100
From: andrew glaeser
To: sub...@bugs.debian.org
Subject: hugin: fails to find control-points, defective
- -BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: hugin
Version: 2018.0.0+dfsg-1+b1
Severity: important
Dear Maintainer,
the problem exists since the the stretch-release, in fact the tendency to
defectiveness of the GUI showed already with Jessie+backports, it wasn't
possible to stitch the panoramic views there using the GUI, but one had to do
it on the terminal using this instead:
> hugin_stitch_project (1) - Stitch a hugin project
With the stretch-release the situation worsened, now GUI is not workable at
all anymore, because either the order of images is wrong, so there can be no
control-points found, or otherwise cpoints are found for two images out of
three only.
I used to start off with the Assistant, then switched to the advanced view,
sharing of data between the two now also seems to be broken.
Now it is basically the same story both in the simple view, using the
Assistant or with the advanced view, that hugin is _not_workable_.
I upgraded to the version in Testing (buster):
> andrew@a68n:~$ sat install -t testing hugin
> [sudo] password for andrew:
> The following NEW packages will be installed:
> libilmbase23{a} libopenexr23{a}
> The following packages will be upgraded:
> hugin hugin-data hugin-tools libc-bin libc-l10n libc6 libwxbase3.0-0v5
> libwxgtk3.0-0v5 locales 9 packages upgraded, 2 newly installed, 0 to remove
> and 2131 not upgraded. Need to get 26.4 MB of archives. After unpacking
> 7,211 kB will be used. The following packages have unmet dependencies:
> libc6-dev : Depends: libc6 (= 2.24-11+deb9u3) but 2.27-2 is to be installed
> libc6-i386 : Depends: libc6 (= 2.24-11+deb9u3) but 2.27-2 is to be
> installed libc-dev-bin : Depends: libc6 (< 2.25) but 2.27-2 is to be
> installed open: 20; closed: 36; defer: 4; conflict:
> 4
.Internal
> error: found 2 (choice -> promotion) mappings for a single choice. Internal
> error: found 2 (choice -> promotion) mappings for a single choice. The
> following actions will resolve these dependencies:
>
> Upgrade the following packages:
> 1) libc-dev-bin [2.24-11+deb9u3 (now, stable) -> 2.27-2 (testing)]
> 2) libc6-dev [2.24-11+deb9u3 (now, stable) -> 2.27-2 (testing)]
> 3) libc6-i386 [2.24-11+deb9u3 (now, stable) -> 2.27-2 (testing)]
>
>
>
> Accept this solution? [Y/n/q/?]
> The following NEW packages will be installed:
> libilmbase23{a} libopenexr23{a}
> The following packages will be upgraded:
> hugin hugin-data hugin-tools libc-bin libc-dev-bin libc-l10n libc6
> libc6-dev libc6-i386 libwxbase3.0-0v5 libwxgtk3.0-0v5 locales
> 12 packages upgraded, 2 newly installed, 0 to remove and 2128 not upgraded.
> Need to get 32.2 MB of archives. After unpacking 10.8 MB will be used.
> Do you want to continue? [Y/n/?]
> Get: 1 http://ftp2.de.debian.org/debian buster/main amd64 libc-l10n all
> 2.27-2 [859 kB] Get: 2 http://ftp2.de.debian.org/debian buster/main amd64
> libc6-i386 amd64 2.27-2 [2,852 kB] Get: 3 http://ftp2.de.debian.org/debian
> buster/main amd64 libc-dev-bin amd64 2.27-2 [270 kB] Get: 4
> http://ftp2.de.debian.org/debian buster/main amd64 libc6-dev amd64 2.27-2
> [2,670 kB] Get: 5 http://ftp2.de.debian.org/debian buster/main amd64
> locales all 2.27-2 [3,804 kB] Get: 6 http://ftp2.de.debian.org/debian
> buster/main amd64 libc6 amd64 2.27-2 [2,904 kB] Get: 7
> http://ftp2.de.debian.org/debian buster/main amd64 libc-bin amd64 2.27-2
> [786 kB] Get: 8 http://ftp2.de.debian.org/debian buster/main amd64 hugin
> amd64 2018.0.0+dfsg-1+b1 [1,250 kB] Get: 9 http://ftp2.de.debian.org/debian
> buster/main amd64 hugin-tools amd64 2018.0.0+dfsg-1+b1 [3,141 kB] Get: 10
> http://ftp2.de.debian.org/debian buster/main amd64 hugin-data all
> 2018.0.0+dfsg-1 [7,625 kB] Get: 11 http://ftp2.de.debian.org/debian
> buster/main amd64 libilmbase23 amd64 2.2.1-2 [85.6 kB] Get: 12
> http://ftp2.de.debian.org/debian buster/main amd64 libopenexr23 amd64
> 2.2.1-4 [579 kB] Get: 13 http://ftp2.de.debian.org/debian buster/main amd64
> libwxbase3.0-0v5 amd64 3.0.3.1+dfsg2-1 [1,063 kB] Get: 14
> http://ftp2.de.debian.org/debian buster/main amd64 l
[Hugin-devs] [Bug 1758503] Re: Fw: hugin: fails to find control-points, defective
Sorry, but I don't understand fully what you want to say.
Issue 1:
> it wasn't possible to stitch the panoramic views there using the GUI, but one
> had to do
> it on the terminal using this instead:
> hugin_stitch_project (1) - Stitch a hugin project
This is probably a messed up batch queue. Read the FAQ how to fix this:
https://wiki.panotools.org/Hugin_FAQ#PTBatcherGUI_does_not_stitch
https://wiki.panotools.org/Hugin_FAQ#How_do_I_clean_up_the_batch_queue
Issue 2:
> With the stretch-release the situation worsened, now GUI is not workable at
>all anymore, because either the order of images is wrong, so there can be no
>control-points found, or otherwise cpoints are found for two images out of
>three only.
The images are shown in the order you added them to the project. So I don't
understand what you mean with "order is wrong".
Otherwise you can simply change the order by drag and drop in the photos tab in
the panorama editor.
One cause for non-finding of control points are wrong lens data. So check the
lens projection and the hfov after adding the image to the project. If they are
messed up, this is FAQ
https://wiki.panotools.org/Hugin_FAQ#After_adding_an_image_the_focal_length_is_another_value_than_the_EXIF_value
** Changed in: hugin
Status: New => Incomplete
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Hugin.
https://bugs.launchpad.net/bugs/1758503
Title:
Fw: hugin: fails to find control-points, defective
Status in Hugin:
Incomplete
Bug description:
Begin forwarded message:
Date: Fri, 23 Mar 2018 08:38:52 +0100
From: andrew glaeser
To: sub...@bugs.debian.org
Subject: hugin: fails to find control-points, defective
- -BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: hugin
Version: 2018.0.0+dfsg-1+b1
Severity: important
Dear Maintainer,
the problem exists since the the stretch-release, in fact the tendency to
defectiveness of the GUI showed already with Jessie+backports, it wasn't
possible to stitch the panoramic views there using the GUI, but one had to do
it on the terminal using this instead:
> hugin_stitch_project (1) - Stitch a hugin project
With the stretch-release the situation worsened, now GUI is not workable at
all anymore, because either the order of images is wrong, so there can be no
control-points found, or otherwise cpoints are found for two images out of
three only.
I used to start off with the Assistant, then switched to the advanced view,
sharing of data between the two now also seems to be broken.
Now it is basically the same story both in the simple view, using the
Assistant or with the advanced view, that hugin is _not_workable_.
I upgraded to the version in Testing (buster):
> andrew@a68n:~$ sat install -t testing hugin
> [sudo] password for andrew:
> The following NEW packages will be installed:
> libilmbase23{a} libopenexr23{a}
> The following packages will be upgraded:
> hugin hugin-data hugin-tools libc-bin libc-l10n libc6 libwxbase3.0-0v5
> libwxgtk3.0-0v5 locales 9 packages upgraded, 2 newly installed, 0 to remove
> and 2131 not upgraded. Need to get 26.4 MB of archives. After unpacking
> 7,211 kB will be used. The following packages have unmet dependencies:
> libc6-dev : Depends: libc6 (= 2.24-11+deb9u3) but 2.27-2 is to be installed
> libc6-i386 : Depends: libc6 (= 2.24-11+deb9u3) but 2.27-2 is to be
> installed libc-dev-bin : Depends: libc6 (< 2.25) but 2.27-2 is to be
> installed open: 20; closed: 36; defer: 4; conflict:
> 4
.Internal
> error: found 2 (choice -> promotion) mappings for a single choice. Internal
> error: found 2 (choice -> promotion) mappings for a single choice. The
> following actions will resolve these dependencies:
>
> Upgrade the following packages:
> 1) libc-dev-bin [2.24-11+deb9u3 (now, stable) -> 2.27-2 (testing)]
> 2) libc6-dev [2.24-11+deb9u3 (now, stable) -> 2.27-2 (testing)]
> 3) libc6-i386 [2.24-11+deb9u3 (now, stable) -> 2.27-2 (testing)]
>
>
>
> Accept this solution? [Y/n/q/?]
> The following NEW packages will be installed:
> libilmbase23{a} libopenexr23{a}
> The following packages will be upgraded:
> hugin hugin-data hugin-tools libc-bin libc-dev-bin libc-l10n libc6
> libc6-dev libc6-i386 libwxbase3.0-0v5 libwxgtk3.0-0v5 locales
> 12 packages upgraded, 2 newly installed, 0 to remove and 2128 not upgraded.
> Need to get 32.2 MB of archives. After unpacking 10.8 MB will be used.
> Do you want to continue? [Y/n/?]
> Get: 1 http://ftp2.de.debian.org/debian buster/main amd64 libc-l10n all
> 2.27-2 [859 kB] Get: 2 http://ftp2.de.debian.org/debian buster/main amd64
> libc6-i386 amd64 2.27-2 [2,852 kB] Get: 3 http://ftp2.de.debian.org/debian
> buster/main amd64 libc-dev-b
[Hugin-devs] [Bug 1678624] Re: keyboard shortcuts for Masks tab
*** This bug is a duplicate of bug 1751343 ***
https://bugs.launchpad.net/bugs/1751343
** This bug has been marked a duplicate of bug 1751343
Hotkey zoom controls for mask tab
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Hugin.
https://bugs.launchpad.net/bugs/1678624
Title:
keyboard shortcuts for Masks tab
Status in Hugin:
Triaged
Bug description:
The Control Points tab has keyboard shortcuts to zoom in and out
("100%" and "fit to window"). I'd like to have the same for the Masks
tab.
Also when zooming in to 100% (or other zoom levels via drop down menu)
the view should focus on the region of the selected masks (if one is
selected). This feature (focus on selected item while zooming) is
already implemented in the Control Points tab.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hugin/+bug/1678624/+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 1752749] Re: Panini projection ignores corner handling (Tops and Bots)
*** This bug is a duplicate of bug 696091 *** https://bugs.launchpad.net/bugs/696091 I have to correct me. The fast preview is correct. The remapped output was wrong. This has been fixed in libpano13. -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/1752749 Title: Panini projection ignores corner handling (Tops and Bots) Status in Hugin: New Bug description: I’m trying to change the projection of a wide shot (18mm in 35mm terms) from Rectilinear to Panini (General) and I don’t manage to get the corners correctly - it looks like Hugin ignores the values that I set at the Tops and Bots fields. My steps are to add the image to the image list, open the Fast Panorama Preview screen, go to the Projection tab and set the compression value to 73, and the Top and Bots to 32 each one. Then I enlarge the field of view slightly to fit the image and I close the Panorama preview screen. I go to the stitcher tab, select Calculate optimal size, and press “Stitch!”. The output looks as if the Tops and Bots were left at 0. Note that if I go to the Crop tab in the preview screen and press Auto Crop, it crops a bar from the top and a bar from the bottom - again, as if the Tops and Bots are at 0. The file is relatively big so here is a link to download: https://www.dropbox.com/s/mh84bytkbiw8dld/P7230709.zip?dl=0 Version: 2018.0.0.5abfb4de7961 Reproduced also on version from mid/end of 2017. Thank you. To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/1752749/+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 1754963] Re: Trying to fine-tune position of one end of line in Control Points grabs the wrong end of the line
I reverted the changes concerning disable of fine-tune. Instead I modified the fine-tune code to better cope with line control points. -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/1754963 Title: Trying to fine-tune position of one end of line in Control Points grabs the wrong end of the line Status in Hugin: Fix Committed Bug description: When trying to straighten the image, both panes in the "Control Points" tab in main Hugin window, one needs to provide horizontal and vertical lines. To do that, one needs to select the beginning point of line in one pane, and the end point of line in the other pane of "Control Points" tab. Usually Hugin fine-tunes the endpoints correctly, but sometimes one needs to fine-tune the position (e.g. if Hugin moved point to parallel line with more contrast). But when I try to grab endpoint that I have created in right pane, Hugin catches the other endpoint instead. I have to switch panes, that is use left pane for end of line, right pane for beginning of the line. Steps: -- 1. Switch to "Control Points" tab 2. Ensure that both panes display the same image; zoom is set to "fit to window", all three checkboxes (auto fine-tune, auto add, auto estimate) are checked - this is the default setting 3. Select left endpoint of horizontal line on left pane (start of line) 4. Select right endpoint of horizontal line on right pane (end of line) 5. Switch to 100% zoom or more for fine-tuning; usually whole image does not fit into pane 6. Try to grab right endpoint on right pane (the one that was just added) Expected: - 1. You grab visible endpoint under cursor, and are able to fine-tune its position Actual result: -- 1. You grab the endpoint that was last manipulated previously (was added in the left pane, and/or manipulated there). 2. If you hold mouse button longer, it would move starting endpoint to unexpected position Workaround: --- 1. Switch panes: use left pane to fine-tune end of line, and right pane to fine-tune beginning of line. System and version: --- Operating System: Windows 10 (build 16299), 64-bit edition Architecture: 64 bit Free memory: 1685604 kiB Active Codepage: 1250 (Central European Windows) Hugin Version: 2018.0.0.5abfb4de7961 built by Thomas Path to resources: C:\Program Files\Hugin\share\hugin\xrc\ Path to data: C:\Program Files\Hugin\share\hugin\data\ Hugins camera and lens database: C:\Users\jnare\AppData\Roaming\hugin\camlens.db Multi-threading using C++11 std::thread and OpenMP Monitor profile: C:\WINDOWS\system32\spool\drivers\color\sRGB Color Space Profile.icm Libraries wxWidgets: wxWidgets 3.1.1 wxWidgets Library (wxMSW port) Version 3.1.1 (Unicode: wchar_t, debug level: 1), compiled at Nov 18 2017 10:28:15 Runtime version of toolkit used is 10.0. libpano13: 2.9.19 Exiv2: 0.26 SQLite3: 3.18.0 Vigra: 1.11.0 LittleCMS2: 2.9 To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/1754963/+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 1088142] Re: Support XDG basedir specification
Implemented in repository. But needs wxWidgets 3.1.1, otherwise the old location is used. ** Changed in: hugin Status: Triaged => Fix Committed ** Changed in: hugin Milestone: None => 2018.2beta1 -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/1088142 Title: Support XDG basedir specification Status in Hugin: Fix Committed Bug description: Please support FreeDesktop.org XDG basedir specification for Hugin? http://ploum.net/post/207-modify-your-application-to-use-xdg-folders https://live.gnome.org/GnomeGoals/XDGConfigFolders http://standards.freedesktop.org/basedir-spec/latest/ To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/1088142/+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 1754963] Re: Trying to fine-tune position of one end of line in Control Points grabs the wrong end of the line
The fine-tune function does only work with normal control points (because it is using auto-correlation). I disabled therefore the fine-tune button for line control points. ** Changed in: hugin Status: New => Fix Committed ** Changed in: hugin Milestone: None => 2018.2beta1 -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/1754963 Title: Trying to fine-tune position of one end of line in Control Points grabs the wrong end of the line Status in Hugin: Fix Committed Bug description: When trying to straighten the image, both panes in the "Control Points" tab in main Hugin window, one needs to provide horizontal and vertical lines. To do that, one needs to select the beginning point of line in one pane, and the end point of line in the other pane of "Control Points" tab. Usually Hugin fine-tunes the endpoints correctly, but sometimes one needs to fine-tune the position (e.g. if Hugin moved point to parallel line with more contrast). But when I try to grab endpoint that I have created in right pane, Hugin catches the other endpoint instead. I have to switch panes, that is use left pane for end of line, right pane for beginning of the line. Steps: -- 1. Switch to "Control Points" tab 2. Ensure that both panes display the same image; zoom is set to "fit to window", all three checkboxes (auto fine-tune, auto add, auto estimate) are checked - this is the default setting 3. Select left endpoint of horizontal line on left pane (start of line) 4. Select right endpoint of horizontal line on right pane (end of line) 5. Switch to 100% zoom or more for fine-tuning; usually whole image does not fit into pane 6. Try to grab right endpoint on right pane (the one that was just added) Expected: - 1. You grab visible endpoint under cursor, and are able to fine-tune its position Actual result: -- 1. You grab the endpoint that was last manipulated previously (was added in the left pane, and/or manipulated there). 2. If you hold mouse button longer, it would move starting endpoint to unexpected position Workaround: --- 1. Switch panes: use left pane to fine-tune end of line, and right pane to fine-tune beginning of line. System and version: --- Operating System: Windows 10 (build 16299), 64-bit edition Architecture: 64 bit Free memory: 1685604 kiB Active Codepage: 1250 (Central European Windows) Hugin Version: 2018.0.0.5abfb4de7961 built by Thomas Path to resources: C:\Program Files\Hugin\share\hugin\xrc\ Path to data: C:\Program Files\Hugin\share\hugin\data\ Hugins camera and lens database: C:\Users\jnare\AppData\Roaming\hugin\camlens.db Multi-threading using C++11 std::thread and OpenMP Monitor profile: C:\WINDOWS\system32\spool\drivers\color\sRGB Color Space Profile.icm Libraries wxWidgets: wxWidgets 3.1.1 wxWidgets Library (wxMSW port) Version 3.1.1 (Unicode: wchar_t, debug level: 1), compiled at Nov 18 2017 10:28:15 Runtime version of toolkit used is 10.0. libpano13: 2.9.19 Exiv2: 0.26 SQLite3: 3.18.0 Vigra: 1.11.0 LittleCMS2: 2.9 To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/1754963/+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 684826] Re: icpfind reports progress every 250 cross matches.
Closing here: icpfind has no access to internal of other cp generators. And cpfind is multi-threading. Implementing the proposed algorithm would require a lot of synchronization/blocking of different threads. This is wasting more cycles than it improves the behavior. ** Changed in: hugin Status: Triaged => Won't Fix -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/684826 Title: icpfind reports progress every 250 cross matches. Status in Hugin: Won't Fix Bug description: This is just fine for my current projects. For small projects it might update slightly too fast (too much useless overhead in painting the screen) while for a large project it goes a bit slowly. This means that it depends on the size of the project how fast the updates come. But most of all the updates depend on how fast my CPU is. To make the software future proof, we should make it for example: - set a timer to go off twice a second. - in the timer set a flag. - in the mainloop (e.g. every 1, 10 or 50 matches) check for the flag and print the progress if set. Reset flag. (this is the most sure-fire way to prevent IO concurrency problems. ). To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/684826/+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 679879] Re: Remember previous usage
The lens settings are stored now in the lens database and applied when adding images automatically. So closing here. ** Changed in: hugin Status: Triaged => 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/679879 Title: Remember previous usage Status in Hugin: Fix Released Bug description: I'd like to reduce the amount of detail that need to be added into hugin every time it is run on a new panorama project. I can see two non-exclusinve ways of improving user experience in this regard. The example in my mind here is the selection of lens parameters. 1. Allow command line options to select the lens ini file. E.g.: hugin -lens ~/lenses/panasonicfz5-default-36.ini a.pto 2. Allow hugin to rememeber previous settings. For example, it could keep last five lens parameters in its cache (~/.hugin file ?) for easy selection from a pop-up menu. Remembering previous settings would be especially useful in the selections in the Stitcher tab. To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/679879/+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 692404] Re: Architectural proj goes haywire
Not reproducible with 2018.0. Closing here. Reopen if you can reproduce it and provide new information. ** Changed in: hugin Status: Confirmed => 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/692404 Title: Architectural proj goes haywire Status in Hugin: Fix Released Bug description: Running current default branch (hgd042bd4094ee). After alignment, view in FPW is in equirectangular proj. with FOV 175x124. Switching proj to Architectural, FPW goes white, choosing another proj. and hugin disappears in a puff of smoke! Run project again, this time when switching proj. to Architectural, FPW goes white, see that FOV is 175x495. A click on vertical slider and FOV snaps to 175x178.5 and image reappears. I have had some trouble reproducing the crash. It does seem that there is some instability here. Yet to test if 2004.4.0 beta-2 behaves the same way, but am guessing that it probably does. Project .pto file attached, it may help. To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/692404/+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 790437] Re: Hugin crashes on equi to Architectural projection
The crash is not reproducible with 2018.0. I committed a further fix with improves the calculation of vfov. ** Changed in: hugin Status: Confirmed => Fix Committed ** Changed in: hugin Milestone: None => 2018.2beta1 -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/790437 Title: Hugin crashes on equi to Architectural projection Status in Hugin: Fix Committed Bug description: Hugin 2011.1.0.13dd690b1ce1 Ubuntu 10.4 I am loading an equirectangular image of 6.5 MB. Set HVOF to 360 and projection to equirectangular. When changing the projection to Architectural in Fast Panorama preview Huign disappears. To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/790437/+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 1505149] Re: Hugin don't start
Closing here because the initial bug is related to a bug in the graphic driver - not in Hugin. ** Changed in: hugin Status: Incomplete => Won't Fix -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/1505149 Title: Hugin don't start Status in Hugin: Won't Fix Status in hugin package in Ubuntu: New Bug description: Hugin crsh at start from terminal: :~$ hugin 11:19:14: Debug: Failed to connect to session manager: SESSION_MANAGER environment variable not defined (hugin:10254): Gtk-CRITICAL **: IA__gtk_widget_set_size_request: assertion 'height >= -1' failed (hugin:10254): GdkPixbuf-CRITICAL **: gdk_pixbuf_new: assertion 'width > 0' failed (hugin:10254): Gtk-CRITICAL **: IA__gtk_widget_set_size_request: assertion 'height >= -1' failed (hugin:10254): GdkPixbuf-CRITICAL **: gdk_pixbuf_new: assertion 'width > 0' failed (hugin:10254): Gtk-CRITICAL **: IA__gtk_widget_set_size_request: assertion 'height >= -1' failed (hugin:10254): Gtk-CRITICAL **: IA__gtk_widget_set_size_request: assertion 'height >= -1' failed (hugin:10254): Gtk-CRITICAL **: IA__gtk_widget_set_size_request: assertion 'height >= -1' failed (hugin:10254): Gtk-CRITICAL **: IA__gtk_widget_set_size_request: assertion 'height >= -1' failed (hugin:10254): Gtk-CRITICAL **: IA__gtk_widget_set_size_request: assertion 'height >= -1' failed (hugin:10254): Gtk-CRITICAL **: IA__gtk_widget_set_size_request: assertion 'height >= -1' failed (hugin:10254): Gtk-CRITICAL **: IA__gtk_widget_set_size_request: assertion 'height >= -1' failed (hugin:10254): Gtk-CRITICAL **: IA__gtk_widget_set_size_request: assertion 'height >= -1' failed (hugin:10254): Gtk-CRITICAL **: IA__gtk_widget_set_size_request: assertion 'height >= -1' failed (hugin:10254): Gtk-CRITICAL **: IA__gtk_widget_set_size_request: assertion 'height >= -1' failed /usr/share/hugin/data/plugins/top_five.py CAT:Control Points NAM:keep 5 CPs per image pair /usr/share/hugin/data/plugins/woa.py CAT:Control Points NAM:Warped Overlap Analysis /usr/share/hugin/data/plugins/crop_cp.py CAT:Control Points NAM:Crop Control Points /usr/share/hugin/data/plugins/shooting_pattern.py CAT:initial distribution NAM:6-1-1 Shooting Pattern intel_do_flush_locked failed: Input/output error ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: hugin 2015.0.0~rc3+dfsg-1build1 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic i686 ApportVersion: 2.19.1-0ubuntu2 Architecture: i386 CurrentDesktop: LXDE Date: Mon Oct 12 11:15:35 2015 InstallationDate: Installed on 2013-03-16 (940 days ago) InstallationMedia: Lubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.1) SourcePackage: hugin UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/1505149/+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 1301922] Re: Fast panorama editor very cumbersome to use
Set to incomplete because there is no feedback from the initial reporter for a long time. Set the status to open if you have more information. ** Changed in: hugin Status: New => Incomplete -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/1301922 Title: Fast panorama editor very cumbersome to use Status in Hugin: Incomplete Bug description: I want to suggest a few changes to the Fast Panorama Editor's interface which will vastly improve usability and shorten time spent working in it. Some parts of Hugin today in 2014 look like they've been designed either many years ago and bits and pieces were kept being added on without much concern for the overall appearance, or like it was designed to run on a small-screen phone. Luckily this can all be quickly fixed without much coding, just rearranging existing things. Currently there are six tabs in the Fast Panorama Editor, and clicking through them is a waste of time. Let's fix this: Assistant: input image control (projection, focal, sensor scale multiplier) Preview: a bunch of preview settings. Layout: it's a whole tab when in fact it is exactly one slider. A whole tab for a slider! Projection: output image control (projection, FOV, guides). Move/Drag: synonyms in the tab's name, y/p/r, again guides, center/fit/straighten. Crop: manual, auto, again guides. AT THE VERY LEAST let us move the images from the same tab we can change projection and crop from! To properly fix this, delete the tabs, they're a bad idea, they waste screen space like crazy, and merge things. Unified Fast Panorama Editor (UFPE). Consists of three main elements: the image control panels (two of them, one for input, one for output), the preview, and the preview controls. The first element, input/output image controls. Two panels (frames? not sure of the nomenclature in QT) at the top or on the left of the UFPE (depends on your screen aspect ratio, let them float so the user can choose), keep things small, don't waste space. First panel is your source image panel: [+] to load images (no need for a 100 pixel long button!), [-] to remove currently selected image (click on it on the preview to select it). Source image projection selector combobox. Source image focal inputbox. Source image sensor size multiplier inputbox. Second panel is your output image panel: Projection selector combobox. Projection parameters if any are needed (sliders for e.g. Panini) [Straighten] button. Yaw/pitch/roll numerical inputboxes of currently selected image or whole pano if none selected. Crop sub-panel [Fit inside] auto-crop button (i.e. no black edges). [Fit outside] auto-crop button (i.e. with black edges). Crop numerical inputboxes. Second element, the main panorama preview. Click on an image to select it. Click+drag to... drag it. Right-click for a context menu if needed. ZOOM IN/OUT USING THE MOUSE; using the sliders as is currently needed is highly inefficient :] Add [+][-] buttons Third element, at the bottom of the window, is the preview control: Exposure, photometrics, show CPs, identify, blabla, guides, grid, scale. Everything on one screen, everything fits even on 1024x768, panels can be detached and floated. Less than a day's work for someone familiar with that window, because there is not much code to be written, just a bunch of things to be moved and a whole bunch of code to delete. To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/1301922/+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 1635992] Re: Null count for "Tag 50341" (type 7, writecount -3, passcount 1) (in module "_TIFFVsetField")
Closing here because it can't be reproduced (and all TIFF warnings are deactivated). Reopening it when you have more information. ** Changed in: hugin Status: New => Won't Fix -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/1635992 Title: Null count for "Tag 50341" (type 7, writecount -3, passcount 1) (in module "_TIFFVsetField") Status in Hugin: Won't Fix Bug description: Hugin 2016.2.0.be8da0221960 from PPA on Xubuntu 16.04 Trying to stitch a couple of TIFFs created with Darktable The following error keeps popping up: Null count for "Tag 50341" (type 7, writecount -3, passcount 1) (in module "_TIFFVsetField") Hugin does its work, but clicking away the multiple error message (for each image, and it seems to come up every time the image is displayed) is a painful papercut To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/1635992/+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 1737654] Re: Hugin unable to stitch
No new information, setting to incomplete. Set back to open if you have more information. ** Changed in: hugin Status: New => Incomplete -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/1737654 Title: Hugin unable to stitch Status in Hugin: Incomplete Bug description: Unable to stitch, error as below, tried with JPG, TIFF input and using both GUI and hugin stitch Stitching panorama… Platform: Mac OS X (Darwin 14.5.0 x86_64) Version: 2017.0.0.eac5e8cc546e built by Niklas Mischkulnig Working directory: /Users/Yang/Pictures/Lightroom export/Glacier Point Output prefix: IMG_5813 - IMG_5828 Blender: enblend 4.2.1-f0304648cc0f ExifTool version: 10.50 Number of active images: 16 Output exposure value: 10.3 Canvas size: 12029x7061 ROI: (264, 328) - (11938, 5843) FOV: 115x61 Projection: Cylindrical(1) Using GPU for remapping: false Panorama Outputs: * Exposure corrected, low dynamic range First input image Number: 0 Filename: /Users/Yang/Pictures/Lightroom export/Glacier Point/IMG_5813.tif Size: 3648x5472 Projection: Normal (rectilinear) Response type: custom (EMoR) HFOV: 24 Exposure value: 10.3 Remapping LDR images… Multiple images output Warning: TIFFDecoder: no TIFFTAG_SAMPLEFORMAT or TIFFTAG_DATATYPE, guessing pixeltype ‘UINT16’. Warning: TIFFDecoder: no TIFFTAG_SAMPLEFORMAT or TIFFTAG_DATATYPE, guessing pixeltype ‘UINT16’. Warning: TIFFDecoder: no TIFFTAG_SAMPLEFORMAT or TIFFTAG_DATATYPE, guessing pixeltype ‘UINT16’. Warning: TIFFDecoder: no TIFFTAG_SAMPLEFORMAT or TIFFTAG_DATATYPE, guessing pixeltype ‘UINT16’. Warning: TIFFDecoder: no TIFFTAG_SAMPLEFORMAT or TIFFTAG_DATATYPE, guessing pixeltype ‘UINT16’. Warning: TIFFDecoder: no TIFFTAG_SAMPLEFORMAT or TIFFTAG_DATATYPE, guessing pixeltype ‘UINT16’. Warning: TIFFDecoder: no TIFFTAG_SAMPLEFORMAT or TIFFTAG_DATATYPE, guessing pixeltype ‘UINT16’. Warning: TIFFDecoder: no TIFFTAG_SAMPLEFORMAT or TIFFTAG_DATATYPE, guessing pixeltype ‘UINT16’. Warning: TIFFDecoder: no TIFFTAG_SAMPLEFORMAT or TIFFTAG_DATATYPE, guessing pixeltype ‘UINT16’. Warning: TIFFDecoder: no TIFFTAG_SAMPLEFORMAT or TIFFTAG_DATATYPE, guessing pixeltype ‘UINT16’. Warning: TIFFDecoder: no TIFFTAG_SAMPLEFORMAT or TIFFTAG_DATATYPE, guessing pixeltype ‘UINT16’. Warning: TIFFDecoder: no TIFFTAG_SAMPLEFORMAT or TIFFTAG_DATATYPE, guessing pixeltype ‘UINT16’. Warning: TIFFDecoder: no TIFFTAG_SAMPLEFORMAT or TIFFTAG_DATATYPE, guessing pixeltype ‘UINT16’. Warning: TIFFDecoder: no TIFFTAG_SAMPLEFORMAT or TIFFTAG_DATATYPE, guessing pixeltype ‘UINT16’. Warning: TIFFDecoder: no TIFFTAG_SAMPLEFORMAT or TIFFTAG_DATATYPE, guessing pixeltype ‘UINT16’. Warning: TIFFDecoder: no TIFFTAG_SAMPLEFORMAT or TIFFTAG_DATATYPE, guessing pixeltype ‘UINT16’. Warning: TIFFDecoder: no TIFFTAG_SAMPLEFORMAT or TIFFTAG_DATATYPE, guessing pixeltype ‘UINT16’. Warning: TIFFDecoder: no TIFFTAG_SAMPLEFORMAT or TIFFTAG_DATATYPE, guessing pixeltype ‘UINT16’. loading IMG_5813.tif remapping IMG_5813.tif Warning: TIFFDecoder: no TIFFTAG_SAMPLEFORMAT or TIFFTAG_DATATYPE, guessing pixeltype ‘UINT16’. saving IMG_5813 - IMG_5828.tif loading IMG_5814.tif Warning: TIFFDecoder: no TIFFTAG_SAMPLEFORMAT or TIFFTAG_DATATYPE, guessing pixeltype ‘UINT16’. Warning: TIFFDecoder: no TIFFTAG_SAMPLEFORMAT or TIFFTAG_DATATYPE, guessing pixeltype ‘UINT16’. remapping IMG_5814.tif saving IMG_5813 - IMG_58280001.tif loading IMG_5815.tif remapping IMG_5815.tif Warning: TIFFDecoder: no TIFFTAG_SAMPLEFORMAT or TIFFTAG_DATATYPE, guessing pixeltype ‘UINT16’. Warning: TIFFDecoder: no TIFFTAG_SAMPLEFORMAT or TIFFTAG_DATATYPE, guessing pixeltype ‘UINT16’. saving IMG_5813 - IMG_58280002.tif loading IMG_5816.tif Warning: TIFFDecoder: no TIFFTAG_SAMPLEFORMAT or TIFFTAG_DATATYPE, guessing pixeltype ‘UINT16’. Warning: TIFFDecoder: no TIFFTAG_SAMPLEFORMAT or TIFFTAG_DATATYPE, guessing pixeltype ‘UINT16’. remapping IMG_5816.tif saving IMG_5813 - IMG_58280003.tif loading IMG_5817.tif remapping IMG_5817.tif Warning: TIFFDecoder: no TIFFTAG_SAMPLEFORMAT or TIFFTAG_DATATYPE, guessing pixeltype ‘UINT16’. Warning: TIFFDecoder: no TIFFTAG_SAMPLEFORMAT or TIFFTAG_DATATYPE, guessing pixeltype ‘UINT16’. saving IMG_5813 - IMG_58280004.tif loading IMG_5818.tif Warning: TIFFDecoder: no TIFFTAG_SAMPLEFORMAT or TIFFTAG_DATATYPE, guessing pixeltype ‘UINT16’. Warning: TIFFDecoder: no TIFFTAG_SAMPLEFORMAT or TIFFTAG_DATATYPE, guessing pixeltype ‘UINT16’. remapping IMG_5818.tif saving IMG_5813 - IMG_58280005.tif Warning: TIFFDecoder: no TIFFTAG_SAMPLEFORMAT or TIFFTAG_DATATYPE, guessing pixeltype ‘UINT16’. Warning: TIFFDecoder: no TIFFTAG_SAMPLEFORMAT or TIFFTAG_DATATYPE, guessing pixeltype ‘UINT1
[Hugin-devs] [Bug 696091] Re: Panini general, Tops and Bots parameters in Quick Preview
This is an issue in libpano. Forward and backward transformation of General Panini are not reversible with hard squeeze (top/bottom>0). ** Project changed: hugin => panotools -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/696091 Title: Panini general,Tops and Bots parameters in Quick Preview Status in Panotools: Confirmed Bug description: The effect of Tops and Bots parameters of Panini General projection is over amplified in the quick preview compared to the final output. Things are OK in the normal preview window. Système d'exploitation : Windows XP (build 2600, Service Pack 3) Architecture : 32 bits Mémoire libre : 156592 kio Page de code active : 1252 (Western European Windows) Hugin Version : 2010.4.0.854952d82c8f built by Matthew Petroff Chemin vers les ressources : C:\Program Files\Hugin/share/hugin/xrc/ Chemin vers les données : C:\Program Files\Hugin/share/hugin/data/ To manage notifications about this bug go to: https://bugs.launchpad.net/panotools/+bug/696091/+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 1752749] Re: Panini projection ignores corner handling (Tops and Bots)
*** This bug is a duplicate of bug 696091 *** https://bugs.launchpad.net/bugs/696091 It is vice versa: the output is correct, the fast preview is wrong. This is a known bug. ** This bug has been marked a duplicate of bug 696091 Panini general,Tops and Bots parameters in Quick Preview -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/1752749 Title: Panini projection ignores corner handling (Tops and Bots) Status in Hugin: New Bug description: I’m trying to change the projection of a wide shot (18mm in 35mm terms) from Rectilinear to Panini (General) and I don’t manage to get the corners correctly - it looks like Hugin ignores the values that I set at the Tops and Bots fields. My steps are to add the image to the image list, open the Fast Panorama Preview screen, go to the Projection tab and set the compression value to 73, and the Top and Bots to 32 each one. Then I enlarge the field of view slightly to fit the image and I close the Panorama preview screen. I go to the stitcher tab, select Calculate optimal size, and press “Stitch!”. The output looks as if the Tops and Bots were left at 0. Note that if I go to the Crop tab in the preview screen and press Auto Crop, it crops a bar from the top and a bar from the bottom - again, as if the Tops and Bots are at 0. The file is relatively big so here is a link to download: https://www.dropbox.com/s/mh84bytkbiw8dld/P7230709.zip?dl=0 Version: 2018.0.0.5abfb4de7961 Reproduced also on version from mid/end of 2017. Thank you. To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/1752749/+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 1752135] Re: HDR tiff and EXR files lack color space from input files
For LDR images the icc profile is copied in depended of this argfile. But for HDR images I'm not sure, if the icc profile is the correct way. There are contrary opinions about this. So, currently I don't make this the default. -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/1752135 Title: HDR tiff and EXR files lack color space from input files Status in Hugin: Fix Committed Bug description: I am regularly creating HDR files (EXR and TIFF) from 16 bit source files using the ProPhoto RGB color space. The resulting HDR outputs generated by Hugin render with shifted colors. For EXR, sRGB is wrongly assigned to the file. 32 bit TIFFs are instead untagged and do not carry a color profile at all. As soon as I manually assign a profile, colors are back to normal. Hugin (or whatever process is used in the background), needs to assign the input color space also to the generated output HDR files. All of this happens with Hugin 2017.0.0.eac5e8cc546e on Windows 10, using the standard built-in tools. Btw, I have been searching for ages how to assign a color space manually to a file. I ended up using: magick "DSC_7847 - DSC_7856_hdr.tif" -profile proto.icc out.tiff To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/1752135/+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 1752135] Re: HDR tiff and EXR files lack color space from input files
The main problem is that OpenEXR does not support icc profiles, and Hugin is using the exr format as intermediate format for HDR output. But I implemented a workaround: The metadata transfer is now also called for HDR output (this was currently missing). Beside this new version you need to add "-icc_profile" to the final argfile for exiftool in preferences, stitching (2). (You can copy the icc profile also with exiftool -tagsfromfile input.tif -icc_profile out.tif.) ** Changed in: hugin Status: Incomplete => Fix Committed ** Changed in: hugin Milestone: None => 2018.2beta1 -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/1752135 Title: HDR tiff and EXR files lack color space from input files Status in Hugin: Fix Committed Bug description: I am regularly creating HDR files (EXR and TIFF) from 16 bit source files using the ProPhoto RGB color space. The resulting HDR outputs generated by Hugin render with shifted colors. For EXR, sRGB is wrongly assigned to the file. 32 bit TIFFs are instead untagged and do not carry a color profile at all. As soon as I manually assign a profile, colors are back to normal. Hugin (or whatever process is used in the background), needs to assign the input color space also to the generated output HDR files. All of this happens with Hugin 2017.0.0.eac5e8cc546e on Windows 10, using the standard built-in tools. Btw, I have been searching for ages how to assign a color space manually to a file. I ended up using: magick "DSC_7847 - DSC_7856_hdr.tif" -profile proto.icc out.tiff To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/1752135/+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 1752135] Re: HDR tiff and EXR files lack color space from input files
The source contains code to copy the icc profile. Can you provide a source image and the corresponding pto file for testing? The OpenEXR format does not officially support icc profile. (Some programs seems to use a private extension, but no officially.) So I fear there is currently no (official) way to copy the icc profile to exr file. I can therefore test only the tiff file. ** Changed in: hugin Status: New => Incomplete -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/1752135 Title: HDR tiff and EXR files lack color space from input files Status in Hugin: Incomplete Bug description: I am regularly creating HDR files (EXR and TIFF) from 16 bit source files using the ProPhoto RGB color space. The resulting HDR outputs generated by Hugin render with shifted colors. For EXR, sRGB is wrongly assigned to the file. 32 bit TIFFs are instead untagged and do not carry a color profile at all. As soon as I manually assign a profile, colors are back to normal. Hugin (or whatever process is used in the background), needs to assign the input color space also to the generated output HDR files. All of this happens with Hugin 2017.0.0.eac5e8cc546e on Windows 10, using the standard built-in tools. Btw, I have been searching for ages how to assign a color space manually to a file. I ended up using: magick "DSC_7847 - DSC_7856_hdr.tif" -profile proto.icc out.tiff To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/1752135/+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 1750398] Re: align_image_stack fails to open EXR files
** Changed in: hugin Milestone: None => 2018.2beta1 -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/1750398 Title: align_image_stack fails to open EXR files Status in Hugin: Fix Committed Bug description: align_image_stack fails to open EXR files generated with darktable, the output is as follow: $ align_image_stack DSCF4117.exr DSCF4118.exr -p OUT.exr /build/hugin/src/hugin-2018.0.0/src/hugin_base/panodata/SrcPanoImage.cpp 346 Error opening file /build/hugin/src/hugin-2018.0.0/src/hugin_base/panodata/SrcPanoImage.cpp 346 Error opening file Written project file OUT.exr (an output file is generated, but it is only 12.9KB) I have tried every compression method (off, RLE, ZIP, ZIPS, PIZ, PXR24, B44, B44A) and the result is consistent. I'm using Arch Linux with hugin 2018 and openexr 2.2.0. To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/1750398/+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 1751342] Re: Copy and paste image position to another
The function would be very special or would need a lot of configuration options to adapt to different use cases. Currently you can also select several images and modify the position of all selected images at once. And then there is the expression parser where you can modify the image positions (manipulate image variables in context menu or pto_var). I extended the parser to allow access to other image variables. So this should be easily possible to modify image positions. ** Changed in: hugin Status: New => Opinion -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/1751342 Title: Copy and paste image position to another Status in Hugin: Opinion Bug description: Not a bug report per se but a small feature request. The possibility to copy and paste image position from image to another would be nice feature to have in Hugin. Now transferring image position from image to image is a steb-by-step process involving lots of repetition repetition. To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/1751342/+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 1751343] Re: Hotkey zoom controls for mask tab
Fixed in repository. The same hotkeys work now also in mask editor. ** Changed in: hugin Status: New => Fix Committed ** Changed in: hugin Milestone: None => 2018.2beta1 -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/1751343 Title: Hotkey zoom controls for mask tab Status in Hugin: Fix Committed Bug description: It is possible to use hotkeys 0, 1 and 2 to zoom in on the image in control points tab. Similar hotkeys would be very useful in mask tab too. Maybe additional hotkeys for 50% and 25% zooms too? To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/1751343/+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 1750398] Re: align_image_stack fails to open EXR files
That are good news. Thanks for feedback. -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/1750398 Title: align_image_stack fails to open EXR files Status in Hugin: Fix Committed Bug description: align_image_stack fails to open EXR files generated with darktable, the output is as follow: $ align_image_stack DSCF4117.exr DSCF4118.exr -p OUT.exr /build/hugin/src/hugin-2018.0.0/src/hugin_base/panodata/SrcPanoImage.cpp 346 Error opening file /build/hugin/src/hugin-2018.0.0/src/hugin_base/panodata/SrcPanoImage.cpp 346 Error opening file Written project file OUT.exr (an output file is generated, but it is only 12.9KB) I have tried every compression method (off, RLE, ZIP, ZIPS, PIZ, PXR24, B44, B44A) and the result is consistent. I'm using Arch Linux with hugin 2018 and openexr 2.2.0. To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/1750398/+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 1750398] Re: align_image_stack fails to open EXR files
I added some more error checking to fine tune code. Maybe this fixes the issues with exr files. Please report back. ** Changed in: hugin Status: New => Fix Committed -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/1750398 Title: align_image_stack fails to open EXR files Status in Hugin: Fix Committed Bug description: align_image_stack fails to open EXR files generated with darktable, the output is as follow: $ align_image_stack DSCF4117.exr DSCF4118.exr -p OUT.exr /build/hugin/src/hugin-2018.0.0/src/hugin_base/panodata/SrcPanoImage.cpp 346 Error opening file /build/hugin/src/hugin-2018.0.0/src/hugin_base/panodata/SrcPanoImage.cpp 346 Error opening file Written project file OUT.exr (an output file is generated, but it is only 12.9KB) I have tried every compression method (off, RLE, ZIP, ZIPS, PIZ, PXR24, B44, B44A) and the result is consistent. I'm using Arch Linux with hugin 2018 and openexr 2.2.0. To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/1750398/+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 1750398] Re: align_image_stack fails to open EXR files
I fixed the error message in default branch. You now get a more verbose warning instead. align_image_stack was written for alignment of images directly from camera. So no testing for exr was done. I've not found the bug until now. PS: In Hugins preferences there is an option to copy log messages to clipboard > then all messages (even when the text if fast) are copied to the clipboard and can be inspected afterwards. -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/1750398 Title: align_image_stack fails to open EXR files Status in Hugin: New Bug description: align_image_stack fails to open EXR files generated with darktable, the output is as follow: $ align_image_stack DSCF4117.exr DSCF4118.exr -p OUT.exr /build/hugin/src/hugin-2018.0.0/src/hugin_base/panodata/SrcPanoImage.cpp 346 Error opening file /build/hugin/src/hugin-2018.0.0/src/hugin_base/panodata/SrcPanoImage.cpp 346 Error opening file Written project file OUT.exr (an output file is generated, but it is only 12.9KB) I have tried every compression method (off, RLE, ZIP, ZIPS, PIZ, PXR24, B44, B44A) and the result is consistent. I'm using Arch Linux with hugin 2018 and openexr 2.2.0. To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/1750398/+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 1750398] Re: align_image_stack fails to open EXR files
Can you load the exr file in Hugin? Or is there also an error or crash? -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/1750398 Title: align_image_stack fails to open EXR files Status in Hugin: New Bug description: align_image_stack fails to open EXR files generated with darktable, the output is as follow: $ align_image_stack DSCF4117.exr DSCF4118.exr -p OUT.exr /build/hugin/src/hugin-2018.0.0/src/hugin_base/panodata/SrcPanoImage.cpp 346 Error opening file /build/hugin/src/hugin-2018.0.0/src/hugin_base/panodata/SrcPanoImage.cpp 346 Error opening file Written project file OUT.exr (an output file is generated, but it is only 12.9KB) I have tried every compression method (off, RLE, ZIP, ZIPS, PIZ, PXR24, B44, B44A) and the result is consistent. I'm using Arch Linux with hugin 2018 and openexr 2.2.0. To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/1750398/+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 1747352] Re: 2018 version for Mac - Sends Windows Version
Sourceforge is not able to reproduce the issue. They requested some more information. Can you add them to the SF ticket https://sourceforge.net/p/forge/site-support/16341/ ? TIA -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/1747352 Title: 2018 version for Mac - Sends Windows Version Status in Hugin: Invalid Bug description: When I just tried to get the latest 2018 version of Hugin using Safari browser it auto commenced sending me the Windows version. I had no opportunity to select my operating system. I use Apple Mac latest OS update. To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/1747352/+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 1747352] Re: 2018 version for Mac - Sends Windows Version
This link can't be influenced by the Hugin project. It is handled by sourceforge itself. I opened already a ticket there: https://sourceforge.net/p/forge/site-support/16341/ But until now no comment. So I'm closing here. Please add further finding/comments in the above sourceforge ticket. ** Changed in: hugin Status: New => Invalid -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/1747352 Title: 2018 version for Mac - Sends Windows Version Status in Hugin: Invalid Bug description: When I just tried to get the latest 2018 version of Hugin using Safari browser it auto commenced sending me the Windows version. I had no opportunity to select my operating system. I use Apple Mac latest OS update. To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/1747352/+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 1747352] Re: 2018 version for Mac - Sends Windows Version
Either go directly to download folder: https://sourceforge.net/projects/hugin/files/hugin/hugin-2018.0/ or go above Hugin homepage>downloads: http://hugin.sourceforge.net/download/ (scroll down) -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/1747352 Title: 2018 version for Mac - Sends Windows Version Status in Hugin: New Bug description: When I just tried to get the latest 2018 version of Hugin using Safari browser it auto commenced sending me the Windows version. I had no opportunity to select my operating system. I use Apple Mac latest OS update. To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/1747352/+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 1747352] Re: 2018 version for Mac - Sends Windows Version
In the Web interface the dmg is marked as default for Mac OS. Can somebody on Mac OS test this? In the mean time you can download the dmg directly from the download page. Scroll down, there is a direct link to the Mac OS dmg. -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/1747352 Title: 2018 version for Mac - Sends Windows Version Status in Hugin: New Bug description: When I just tried to get the latest 2018 version of Hugin using Safari browser it auto commenced sending me the Windows version. I had no opportunity to select my operating system. I use Apple Mac latest OS update. To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/1747352/+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 1747135] Re: Wrong text in about screen
I uploaded an updated version. (But this is purely cosmetic.) ** Changed in: hugin Status: New => 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/1747135 Title: Wrong text in about screen Status in Hugin: Fix Released Bug description: The final version Hugin 2018.0 has a wrong naming in the about window. It mentions Pre-release Hugin 2018.0 instead of Hugin 2018.0. To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/1747135/+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 1744316] Re: Help window opens outside of the screen area
** 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/1744316 Title: Help window opens outside of the screen area Status in Hugin: Fix Released Bug description: tested on OS X 10.11 / Hugin 2018.0.0 rc1 The Help window opens outside of the screen area both when opening the help window from the menu and also when clicking on the question mark button inside the enblend options dialog. Opening Help from the menu shows the window with the title bar at a position with negative y coordinates, thus the standard close button of OS X can't be reached with the mouse. Mac OS X 10.11 doesn't allow such a window to be dragged to another position other than using the upper title bar of the window. So it should be tested that a new window opens with the upper left corner inside the screens field of view. As a test I have created a shortcut (using a third party macro editor) to manually reposition the front most window's top left corner to x=50 / y = 50. That actually works and now I tested if I had accidentally dragged one such window to this wrong coordinates and that position was later stored by my system prefs. So I closed the correctly repositioned window and tried opening it again: it still opens at a too high position. Also the help window can't be closed using the standard shortcut on Mac OS X: Cmd+W BTW the 'about' window is opened in the center of the screen. Now when the help window is front most and I try to quit Hugin (Cmd+Q) Hugin will crash this way: A dialog opens "atos needs to take control of another process for debugging to continue. Type the name and password of a user in the 'Developer Tools' group to allow this." username: password: [Cancel] [Continue] There is no such group defined on my system and no matter what user/pw I try or click 'Cancel' the program will crash. To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/1744316/+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 1744317] Re: copyright info in about window is outdated
** 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/1744317 Title: copyright info in about window is outdated Status in Hugin: Fix Released Bug description: OS X 10.11 / Hugin 2018.0.0 rc1 The copyright information in the "about" window (intro.htm) is still 2004-2017 but should be pushed to cover also 2018. To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/1744317/+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 1744316] Re: Help window opens outside of the screen area
I added an additional check for the windows position of the help window in changeset 5abfb4de7961. ** Changed in: hugin Status: New => Fix Committed ** Changed in: hugin Milestone: None => 2018.0rc2 -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/1744316 Title: Help window opens outside of the screen area Status in Hugin: Fix Committed Bug description: tested on OS X 10.11 / Hugin 2018.0.0 rc1 The Help window opens outside of the screen area both when opening the help window from the menu and also when clicking on the question mark button inside the enblend options dialog. Opening Help from the menu shows the window with the title bar at a position with negative y coordinates, thus the standard close button of OS X can't be reached with the mouse. Mac OS X 10.11 doesn't allow such a window to be dragged to another position other than using the upper title bar of the window. So it should be tested that a new window opens with the upper left corner inside the screens field of view. As a test I have created a shortcut (using a third party macro editor) to manually reposition the front most window's top left corner to x=50 / y = 50. That actually works and now I tested if I had accidentally dragged one such window to this wrong coordinates and that position was later stored by my system prefs. So I closed the correctly repositioned window and tried opening it again: it still opens at a too high position. Also the help window can't be closed using the standard shortcut on Mac OS X: Cmd+W BTW the 'about' window is opened in the center of the screen. Now when the help window is front most and I try to quit Hugin (Cmd+Q) Hugin will crash this way: A dialog opens "atos needs to take control of another process for debugging to continue. Type the name and password of a user in the 'Developer Tools' group to allow this." username: password: [Cancel] [Continue] There is no such group defined on my system and no matter what user/pw I try or click 'Cancel' the program will crash. To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/1744316/+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 1744317] Re: copyright info in about window is outdated
Because of other changes a RC2 is needed. Therefore update also to 2018.0 branch. ** Changed in: hugin Milestone: None => 2018.0rc2 -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/1744317 Title: copyright info in about window is outdated Status in Hugin: Fix Committed Bug description: OS X 10.11 / Hugin 2018.0.0 rc1 The copyright information in the "about" window (intro.htm) is still 2004-2017 but should be pushed to cover also 2018. To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/1744317/+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 1744316] Re: Help window opens outside of the screen area
The help system for Mac OS was updated already in 2017.0 (no changes in 2018.0). The help is displayed by wxWidgets (Hugin has currently no access to the internal of this window.) - so it can behave a little bit different for the initial position than other Hugin windows. So can somebody reproduce the issue? -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/1744316 Title: Help window opens outside of the screen area Status in Hugin: New Bug description: tested on OS X 10.11 / Hugin 2018.0.0 rc1 The Help window opens outside of the screen area both when opening the help window from the menu and also when clicking on the question mark button inside the enblend options dialog. Opening Help from the menu shows the window with the title bar at a position with negative y coordinates, thus the standard close button of OS X can't be reached with the mouse. Mac OS X 10.11 doesn't allow such a window to be dragged to another position other than using the upper title bar of the window. So it should be tested that a new window opens with the upper left corner inside the screens field of view. As a test I have created a shortcut (using a third party macro editor) to manually reposition the front most window's top left corner to x=50 / y = 50. That actually works and now I tested if I had accidentally dragged one such window to this wrong coordinates and that position was later stored by my system prefs. So I closed the correctly repositioned window and tried opening it again: it still opens at a too high position. Also the help window can't be closed using the standard shortcut on Mac OS X: Cmd+W BTW the 'about' window is opened in the center of the screen. Now when the help window is front most and I try to quit Hugin (Cmd+Q) Hugin will crash this way: A dialog opens "atos needs to take control of another process for debugging to continue. Type the name and password of a user in the 'Developer Tools' group to allow this." username: password: [Cancel] [Continue] There is no such group defined on my system and no matter what user/pw I try or click 'Cancel' the program will crash. To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/1744316/+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 1744317] Re: copyright info in about window is outdated
The code in 2018.0 was written in 2017. So I think for 2018.0 it is okay. Updated the year in default branch. ** Changed in: hugin Status: New => Fix Committed -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/1744317 Title: copyright info in about window is outdated Status in Hugin: Fix Committed Bug description: OS X 10.11 / Hugin 2018.0.0 rc1 The copyright information in the "about" window (intro.htm) is still 2004-2017 but should be pushed to cover also 2018. To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/1744317/+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 1740701] Re: Updated Hungarian translations
** 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/1740701 Title: Updated Hungarian translations Status in Hugin: Fix Released Bug description: Updated Hungarian translations for Hugin 2018.0.0 To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/1740701/+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 1628548] Re: hugin wont open
** 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/1628548 Title: hugin wont open Status in Hugin: Fix Released Bug description: I used the program once, and it was fine. Then the next time it opened, I got the message attached below. When I click on any of the buttons, the application closes. To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/1628548/+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 1740585] Re: Updated French translation
** 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/1740585 Title: Updated French translation Status in Hugin: Fix Released Bug description: Please find attached the updated French translation Best regards Jean-Luc To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/1740585/+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
