[Hugin-devs] [Bug 1851591] Re: Hugin fails to build with exiv2-0.27.99.0

It looks like exiv2-0.27.99.0 causes problems elsewhere as well. Digikam 6.2.0 won't run with this version, so have to revert to exiv2-0.27.2 Cheers, Terry -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin.

[Hugin-devs] [Bug 1851591] [NEW] Hugin fails to build with exiv2-0.27.99.0

Public bug reported: Attempting to build hugin (default branch snapshot e71bc5c2902d 8232) on Fedora 31 with exiv2-0.27.99.0 (the version required to build the current enblend source) results in errors as follows...

[Hugin-devs] [Bug 1849220] Re: current default fails to build in Fedora 30

Now builds OK with exiv2-0.27.99.0 Cheers, Terry -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Enblend. https://bugs.launchpad.net/bugs/1849220 Title: current default fails to build in Fedora 30 Status in Enblend: New Bug

[Hugin-devs] [Bug 1849220] Re: current default fails to build in Fedora 30

** Changed in: enblend Importance: Undecided => High -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Enblend. https://bugs.launchpad.net/bugs/1849220 Title: current default fails to build in Fedora 30 Status in Enblend: New Bug

[Hugin-devs] [Bug 1849220] [NEW] current default fails to build in Fedora 30

Public bug reported: Attempting to build current default (6b604e79e85b 1529 default) in Fedora 30, using rpmbuild fails with the following message... /home/terry/rpmbuild/BUILD/enblend-4.3.0-1529hg-Source/src/metadata.h:53:31: error: 'UniquePtr' in 'class Exiv2::Image' does not name a type

[Hugin-devs] [Bug 1829309] Re: Building current default in Fedora 30 fails due to Python plugins

Thanks Thomas. Cheers, Terry -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/1829309 Title: Building current default in Fedora 30 fails due to Python plugins Status in Hugin: Fix Committed

[Hugin-devs] [Bug 1829309] Re: Building current default in Fedora 30 fails due to Python plugins

I looked a bit more into this, and found that src/hugin_script_interface/hpi.py doesn't reference python3. I've just made a temporary local change to hpi.py (#!/usr/bin/python3), and hugin now builds here without error on Fedora 30. I've not tested whether the python scripting works. Cheers,

[Hugin-devs] [Bug 1829309] Re: Building current default in Fedora 30 fails due to Python plugins

Hello Thomas, Not sure if I have a local issue, but still not building in Fedora 30. here's the last of the output from rpmbuild which identifies the problem... Bytecompiling .py files below

[Hugin-devs] [Bug 1829309] Re: Building current default in Fedora 30 fails due to Python plugins

OK, thanks Thomas. Hopefully something our new Python interface maintainer will be able to sort out. Cheers, Terry -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/1829309 Title: Building

[Hugin-devs] [Bug 1829309] Re: Building current default in Fedora 30 fails due to Python plugins

Attempted a test build of the current default on Fedora 30 and ran into this python plugin build problem again! I made local changes which build OK, but failed in my attempt to push those changes to the repo. Not sure if that was due to a problem at the repo end or I no longer have push

[Hugin-devs] [Bug 1834767] Re: Current default fails to build

Thanks for that. It seems to have worked. Cheers, Terry -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Enblend. https://bugs.launchpad.net/bugs/1834767 Title: Current default fails to build Status in Enblend: New Bug

[Hugin-devs] [Bug 1834767] Re: Current default fails to build

Hello Bruno, I probably should push my fix to the repo, if you are happy with it. I don't think I have ever done that previously for Enblend, I can't find any reference in my notes to what the push command to enblend looks like, or find any reference anywhere. I assume I have push privilege ??

[Hugin-devs] [Bug 1834767] Re: Current default fails to build

OK, I've tried that fix and it does now build, but haven't used the build in anger. Doc build problems did occur...seems to be a regular issue with Fedora, so had to switch off building of any docs. I haven't looked at why the docs are an issue, beyond my ken. I have attached a patch for others

[Hugin-devs] [Bug 1834767] Re: Current default fails to build

Hello Bruno, Thanks for that thought. If I get time I'll have a look, but Thomas probably knows his way around the code much better than I do and may beat me to trying this fix. Cheers, Terry -- You received this bug notification because you are a member of Hugin Developers, which is

[Hugin-devs] [Bug 1834767] [NEW] Current default fails to build

Public bug reported: Attempting to build the current Enblend default source in Fedora 30, using rpmbuild. Build fails with the following message... In file included from /home/terry/rpmbuild/BUILD/enblend-4.3.0-1519hg-Source/src/enfuse.cc:188:

[Hugin-devs] [Bug 1829309] [NEW] Building current default in Fedora 30 fails due to Python plugins

Public bug reported: Building current hugin default 8203 01e87b730bb3 in Fedora 30, fails with the following message... Bytecompiling .py files below /home/terry/rpmbuild/BUILDROOT/hugin-2019.1.0-0.1.20190516hg.fc30.x86_64/usr/lib/debug/usr/lib64/python2.7 using /usr/bin/python2.7

[Hugin-devs] [Bug 1828925] Re: Hugin build fails in fedora 30

I'm pretty sure that the build now progresses past the reported fail point OK, but still fails to complete OK as a result of python plugin issues. AS this appears to be unrelated to this bug bug report, I'll raise a new one. Cheers, Terry -- You received this bug notification because you are a

Re: [Hugin-devs] [Bug 1828925] Re: Hugin build fails in fedora 30

Hello Bruno, On Wed, 15 May 2019 07:53:37 +1000, Bruno Postle wrote: > It appears to be because fedora exiv2 went from 0.27.0 to 0.27.1 a few > days ago. > > gcc went from 9.0.1 to 9.1.1 a few days before, and this was ok: > https://apps.fedoraproject.org/koschei/package/hugin?collection=f30

[Hugin-devs] [Bug 1828925] Re: Hugin build fails in fedora 30

I'm using exiv2 0.27.1, as provided by Fedora 30. -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/1828925 Title: Hugin build fails in fedora 30 Status in Hugin: New Bug description:

[Hugin-devs] [Bug 1828925] [NEW] Hugin build fails in fedora 30

Public bug reported: Building hugin snapshot 8199:62b0662d5bee in Fedora 30 produces the following error... "/home/terry/rpmbuild/BUILD/hugin-2019.1.0/src/hugin_base/panodata/SrcPanoImage.cpp:339:30: error: expected '{' before '&' token make[2]: ***

[Hugin-devs] [Bug 1708897] Re: Default branch fails to build on Fedora 26

Hello Thomas, It may have been the same issue, the latest default now builds without error on Fedora 26. Thanks for your prompt help. Cheers, Terry -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin.

[Hugin-devs] [Bug 1708897] [NEW] Default branch fails to build on Fedora 26

Public bug reported: Attempting to build latest default branch (a7af0338a2bd 7764 default), on Fedora 26. The build fails with the following message... /home/terry/rpmbuild/BUILD/hugin-2017.1.0/src/hugin_base/vigra_ext/Interpolators.h:50:15: warning: 'double vigra_ext::sinc(double)' defined

[Hugin-devs] [Bug 1647215] Re: Problems building current default

An update. Builds OK here now if only building PS docs. Cheers, Terry -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Enblend. https://bugs.launchpad.net/bugs/1647215 Title: Problems building current default Status in Enblend: New

[Hugin-devs] [Bug 1647215] Re: Problems building current default

Hello Chris, Maybe one of the tools has changed in Fedora 25. Whatever the cause it is beyond me, so I'll have to fall back to doing test builds without docs. Hopefully someone who builds for Fedora will have an insight. Cheers, Terry -- You received this bug notification because you are a

[Hugin-devs] [Bug 1647215] [NEW] Problems building current default

Public bug reported: Attempting to build the current default (1491:24c37812cde3) on Fedora 25 x86_64, using rpmbuild and cmake. Problems occur in the docs stage. The last part of the rpmbuild log, leading up to the first reported problem, is attached. I'll provide the full rpmbuild log if

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

Just tested with a build of default branch, and it all seems to be working OK. Thanks Thomas. Cheers, Terry -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/1645051 Title: Hugin help throws up

[Hugin-devs] [Bug 1645051] [NEW] Hugin help throws up warnings

Public bug reported: A build of current default (f556b5ff8d96 7578 default) on Fedora 25 x86_64. Selecting 'Help' shows help OK, but when selecting a help section (e.g. 1 About Hugin) a dialog box appears "Hugin Warning HTML anchor About_Hugin does not exist". This seems to be the behaviour

[Hugin-devs] [Bug 1617676] Re: hugin is crashing on start

Hugin keeps the path to the image files and .pto last used. I suspect this isn't related to your current problem, but you can easily rename your '.hugin' file to (say) '.hugin_old' and see what happens. If you get the same behaviour then your '.hugin' isn't the culprit and you can revert.

[Hugin-devs] [Bug 1611021] Re: Too much iterations and time to align

Hello Darko82, Not a normal situation, in my experience. It suggests there are some problems with the project, but impossible to say at this stage. Which version of Hugin, and what OS? With such a large project I am reluctant to suggest you make your images available so we can see what is

[Hugin-devs] [Bug 1597594] Re: Enblend-4.3-1472 fails to build in FC24

Hello Thomas, I had read the NEWS file and checked the link, but as it mentioned it was distributed under Boost licence I jumped to the conclusion that it was in fact identical to the optional header included in the Fedora 24 boost-devel. It doesn't appear in the list of songs provided by GCC

[Hugin-devs] [Bug 1597594] Re: Enblend-4.3-1472 fails to build in FC24

Thanks for the explanation Thomas. I can confirm that the default branch does now build OK on Fedora 24. Here, optional headers not found -- Could not find OPTIONAL package Optional -- No optional headers found, fall back to boost -- Boost version: 1.60.0 which is probably of little consequence

[Hugin-devs] [Bug 1597594] Re: Enblend-4.3-1472 fails to build in FC24

OK, I do have "boost/optional.hpp", it is in /usr/include, but FindOptional is not finding it. I tried a local change as follows... diff -r c8d6c0d1a6fe CMakeModules/FindOptional.cmake --- a/CMakeModules/FindOptional.cmake Sun Jul 03 18:11:07 2016 +0200 +++ b/CMakeModules/FindOptional.cmake

[Hugin-devs] [Bug 1597594] Re: Enblend-4.3-1472 fails to build in FC24

the latest default includes fixes to CMakelists.txt to correct FindOptional, which seems to be related to this problem. Attempting to build the current default (1473) cmake reports... -- Could not find OPTIONAL package Optional -- No optional headers found, fall back to boost Fedora 24 is using

[Hugin-devs] [Bug 1598005] Re: Default branch problems in Fedora 24

Hello Thomas, I have just tested a build of the default branch and all is OK except for the sizer issue. I assume you have tested these changes in Fedora 23, and if OK then would guess it is OK for the patch to go into the 2016.2 branch. Any builds of 2016.2 that use the later tools may still

[Hugin-devs] [Bug 1598005] Re: Default branch problems in Fedora 24

Hello Thomas, I've tied the workaround described in your post #11, and we get the icons back but still no menu names displayed. Cheers, Terry -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin.

[Hugin-devs] [Bug 1598005] Re: Default branch problems in Fedora 24

There was a bug reported here that had an issue with wxGTK3, and noted that the problem was fixed by building against wxGTK, but we have passed the point where I could try that. It may not be related. Cheers, Terry ** Bug watch added: Red

[Hugin-devs] [Bug 1598005] Re: Default branch problems in Fedora 24

Hello Thomas, It looks like runtime toolkit is now 3.20 and compile time is 3.20.2 but don't know if this brought any change that would cause what I'm seeing. Fedora 24 is also using gcc-6.1.1, could this have an influence? It would be good if someone who has Fedora 24 x86_64 could test build

[Hugin-devs] [Bug 1598005] Re: Default branch problems in Fedora 24

Hello Thomas, I also have no problem here with Fedora 23, the problem is with Fedora 24 and suspect the problem is the changes that it brings. Cheers, Terry -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin.

[Hugin-devs] [Bug 1598005] Re: Default branch problems in Fedora 24

Sorry, I should have zipped all the screenshots into a single file. -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/1598005 Title: Default branch problems in Fedora 24 Status in Hugin: New

[Hugin-devs] [Bug 1598005] [NEW] Default branch problems in Fedora 24

Public bug reported: The default branch (hugin-2016.3.0.1e53df29f670) builds without error in fedora 24 x86_64 but there are display problems. Image 'Selection_006.jpg' shows the window when it first opens. Image 'Selection_007.jpg' shows the window after a slight drag from bottom RH corner.

[Hugin-devs] [Bug 1597594] Re: Enblend-4.3-1472 fails to build in FC24

Trying to do a bit of sleuthing on this. I note that when I run cmake I get the message along the lines (I didn't get a copy) "optional not found falling back to Boost" If I look at file 'FindOptional.cmake', I see... IF (OPTONAL_INCLUDE_DIR) # Already in cache, be silent

[Hugin-devs] [Bug 1597594] [NEW] Enblend-4.3-1472 fails to build in FC24

Public bug reported: Attempting to build Enblend-4.3-1472 (current default branch) in Fedora 24, using rpmbuild. The build fails with the following message... In file included from /home/terry/rpmbuild/BUILD/enblend-4.3.0-1472hg-Source/src/enblend.cc:81:0:

[Hugin-devs] [Bug 1581889] Re: Current default branch fails to build

Yes, I always use cmake. Thanks. I will test build again when adjustments for cmake have been done. Cheers, Terry -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Enblend. https://bugs.launchpad.net/bugs/1581889 Title: Current default

[Hugin-devs] [Bug 1581889] [NEW] Current default branch fails to build

Public bug reported: Attempting to build the current default branch (1165d8692e19 1457 default) on Fedora 23 x86_64 using rpmbuild, the build exits with the following error message... In file included from /home/terry/rpmbuild/BUILD/enblend-4.3.0-1457hg-Source/src/enblend.cc:81:0:

[Hugin-devs] [Bug 1557749] Re: Latest default branch fails to build

Hello Thomas, It builds here OK now. Thanks for your help. Cheers, Terry -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/1557749 Title: Latest default branch fails to build Status in Hugin:

Re: [Hugin-devs] [Bug 1557749] Re: Latest default branch fails to build

On Thu, 17 Mar 2016 08:16:54 +1100, Stefan Peter <1557...@bugs.launchpad.net> wrote: > Hi Terry > > thank you very much for the fixes, the latest ( (2016.1.0+hg7307) build > succeeded. > Hello Stefan, Thank Thomas, not me. Cheers, Terry -- Regards, Terry Duell -- You received this bug

[Hugin-devs] [Bug 1557749] [NEW] Latest default branch fails to build

Public bug reported: Attempting to build the default branch (6944dd3eb874 7306 ) on Fedora 23 x86_64 using Fedora's rpmbuild, I get the following output from rpmbuild... /home/terry/rpmbuild/BUILD/hugin-2016.1.0/src/hugin1/hugin/PapywizardImport.cpp:100:83: required from here

[Hugin-devs] [Bug 1537368] Re: enblend 4.1.4 build-error with gcc-6

And he did...in his original report text. Just a another example of my 'domestic blindness'! Sorry, should have read more carefully. Cheers, Terry -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Enblend.

[Hugin-devs] [Bug 1537224] Re: Optimisation details not showing correctly in Assistant

Hello Thomas, The fix to the branch works OK here. Thanks for your help. Cheers, Terry -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/1537224 Title: Optimisation details not showing correctly

[Hugin-devs] [Bug 1537224] [NEW] Optimisation details not showing correctly in Assistant

Public bug reported: After optimisation, selecting 'Assistant' tab in Fast Preview window doesn't show the optimisation details. If I drag either of the FOV sliders the optimisation details flicker on and off, but don't remain displayed. System info, from Hugin, as follows... Operating

[Hugin-devs] [Bug 1529902] Re: tca_correct fails with "expecting exactly one alpha band"

I tried your file with hugin-7200:d185664c5ce1, and got this message... Warning: no TIFFTAG_SAMPLEFORMAT or TIFFTAG_DATATYPE, guessing pixeltype 'UINT16'. Warning: no TIFFTAG_SAMPLEFORMAT or TIFFTAG_DATATYPE, guessing pixeltype 'UINT16'. Warning: no TIFFTAG_SAMPLEFORMAT or TIFFTAG_DATATYPE,

Re: [Hugin-devs] [Hugin-bug-hunters] [Bug 1529272] Re: Stitching using PTBatcherGUI eats all memory, Hugin_stitch_project works

Hello fububtu, On Sun, 27 Dec 2015 02:11:10 +1100, fubuntu wrote: > Thank you for your answer, now this becomes clearer to me. And I realize > that there was an important information missing in my bug report: The > GUI actually never shows up, the process gets killed before that.

[Hugin-devs] [Bug 1529272] Re: Stitching using PTBatcherGUI eats all memory, Hugin_stitch_project works

Good that the problem is solved. Sorry I neglected to include the leading '.' in the filename, hope that didn't cause too much confusion. Cheers, Terry -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin.

[Hugin-devs] [Bug 1515504] Re: missing optmiser and exposure butons

Hello Mark, If I understand your problem correctly I don't think what you are seeing is a fault with hugin-2015.0.0. This version only shows the Optimiser and Exposure tabs when these optimisations have been set to use "Custom settings", which you should see in the Photos tab using the Advanced

[Hugin-devs] [Bug 1478174] Re: hugin_executor scripting fails to find remapped image

Hello Thomas, I think that is a good solution. Thanks. Cheers, Terry -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/1478174 Title: hugin_executor scripting fails to find remapped image Status

[Hugin-devs] [Bug 1478174] Re: hugin_executor scripting fails to find remapped image

OK, a bit of further testing illuminates the first issue (enblend: failed to open hgex.TIF: No such file or directory). Editing the supplied 'normal_enblend.executor' script to ... [General] Description=Normal panorama with enblend StepCount=3 IntermediateImageType=tif solves the problem,

[Hugin-devs] [Bug 1478174] [NEW] hugin_executor scripting fails to find remapped image

Public bug reported: Testing hugin-2015.1.0 hugin_executor scripting, using the supplied normal_enblend.executor script, which fails due to enblend looking for %prefix%.TIF, but %prefix%.tif has been generated, script output as follows... Stitching using Normal panorama with enblend

[Hugin-devs] [Bug 1476916] [NEW] hugin-2015.1.0, latest git repo fails to build

Public bug reported: Attempting to build hugin-2015.1.0 using git master (rev.txt is e90f79f9a147) on Fedora 22 x86_64 using rpmbuild. Build fails with the following error message... /home/terry/rpmbuild/BUILD/hugin-2015.1.0/src/celeste/Celeste.cpp: In function 'void

[Hugin-devs] [Bug 1469004] Re: Problems building 4.2 docs

OK, thanks Thomas. -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Enblend. https://bugs.launchpad.net/bugs/1469004 Title: Problems building 4.2 docs Status in Enblend: Fix Committed Bug description: Running into problems

[Hugin-devs] [Bug 1469004] Re: Problems building 4.2 docs

I have just run a few test local builds (not using rpmbuild), and everything builds and installs OK. Attempting to emulate this successful process in rpmbuild still results in the process halting few times and waiting on user input, which has usually just been a carriage return, with the

[Hugin-devs] [Bug 1469004] Re: Problems building 4.2 docs

Hello Thomas, I have just tried the latest changeset, built as per comment #5, but added -DENABLE_HTML_DOC=ON to test the full recipe. The build still halts a few times with 'fatal error' being emitted twice from enfuse doc build, but these aren't rpmbuild errors. As before, the process will

[Hugin-devs] [Bug 1469004] Re: Problems building 4.2 docs

Hello Thomas, I just tried that changeset, using the following in my rpmbuild .spec file, a bit of a guess that this is what you wanted me to try. %build %cmake . -DENABLE_OPENMP=ON -DDOC=ON -DINSTALL_PDF_DOC=ON make %{?_smp_mflags} make pdf The build process stopped numerous time, wanting

[Hugin-devs] [Bug 1469004] Re: Problems building 4.2 docs

A bit more grist t' mill on this, this morning I made another attempt to build, using rpmbuild on Fedora, a source archive generated (from enblend 69d6a6e14271 1183 source) via cmake and 'make package_source', and again using the build instruction in rpmbuild ... '%cmake . -DENABLE_OPENMP=ON

[Hugin-devs] [Bug 1469349] Re: Default branch fails to build

Thanks Thomas, it now builds without error. -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/1469349 Title: Default branch fails to build Status in Hugin - Panorama Tools GUI: Fix Committed

[Hugin-devs] [Bug 1469004] Re: Problems building 4.2 docs

Thanks Bruno. I thought I had all the dependencies... I believed configure, but I had missed a couple. Not a lot of joy though, it still fails to build pdf, this is the latest error report from rpmbuild, using '%cmake . -DENABLE_OPENMP=ON -DDOC=ON -DINSTALL_PDF_DOC=ON'. [ 50%] Error renaming

[Hugin-devs] [Bug 1469349] [NEW] Default branch fails to build

Public bug reported: Attempting to build hugin 570ece0052c0 7046 default, on Fedora 21, I get the following error... /home/terry/rpmbuild/BUILD/hugin-2015.1.0/src/hugin1/hugin/PreviewIdentifyTool.cpp: In member function 'virtual void PreviewIdentifyTool::AfterDrawImagesEvent()':

[Hugin-devs] [Bug 1469004] [NEW] Problems building 4.2 docs

Public bug reported: Running into problems generating the pdf docs, on Fedora 21 if I run ./configure, it reports can build all documentation: yes Building in rpmbuild using cmake, with -DDOC=ON, ps docs are generated OK. Building in rpmbuild using cmake, with -DDOC=ON -DINSTALL_HTML_DOC=ON, both

[Hugin-devs] [Bug 1460928] [NEW] Current repo src gives bad blend with masks

Public bug reported: A build of the current repository source (enblend-4.2.0-1165) gives a bad result when blending images with masks. The hugin builtin blender (verdandi) produces the expected result. Attached archive includes 4 project images, screenshot of stitches from enblend and verdandi,

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

** 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/1457165 Title: incorrect documentation for hugin_executor(1) Status in Hugin - Panorama

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

Hello Andreas, Here, with a ~/.hugin, and no prefix provided to hugin_executor, the default output prefix (%projectname), which is the input project filename, is used. Do you have suggested wording that we should use? Cheers, Terry -- You received this bug notification because you are a member

[Hugin-devs] [Bug 1448816] Re: hugin-2015.0.0_beta1 has no 'Actions' menu

I have run very minimal tests on crop_cp.py, top_five.py and woa.py on a Fedora 21 build of the current 2015.1.0 source (6907:b87b66fe6645). These scripts all run, no errors produced here. I have not tested shooting_pattern.py. Cheers, Terry -- You received this bug notification because you

[Hugin-devs] [Bug 1448816] Re: hugin-2015.0.0_beta1 has no 'Actions' menu

It is possible that this is a result of some change in my Fedora system, but not sure what, at this stage. A build of the current default (hugin-2015.1.0 6899:b30cc246eedc) shows the same behaviour and there are no changes in the default source, since a build of 6887:a8201bc48fa7, which shows

[Hugin-devs] [Bug 1448816] Re: hugin-2015.0.0_beta1 has no 'Actions' menu

Stefan, thanks for pointing out the problem at comment #2. I had been thinking that the Actions menu would still be added but the python scripts would return errors. Cheers, Terry -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin.

[Hugin-devs] [Bug 1448816] [NEW] hugin-2015.0.0_beta1 has no 'Actions' menu

Public bug reported: hugin-2015.0.0_beta1 builds here OK, but has no 'Actions' menu. I have built using rpmbuild on Fedora 21, using the same .spec file as for recent builds of the default branch and those builds provide the 'Actions' menu, although attempting to use WOA in a recent build of

[Hugin-devs] [Bug 1384283] Re: At Appstart: wxWidgets Debug Alert ...

One might expect a new binary release for a situation such as this, but the hugin project only makes source code releases, and relies on the user community to build the binary packages. Cheers, Terry -- You received this bug notification because you are a member of Hugin Developers, which is

Re: [Hugin-devs] [Hugin-bug-hunters] [Bug 1428864] Re: Align_image_stack doesn't include lens and exposure settings in output images

On Mon, 16 Mar 2015 02:15:09 +1100, tmodes 1428...@bugs.launchpad.net wrote: Currently none of our command line tools adds EXIF data to the output (The exception are hugin_executor and hugin_stitch_project/PTBatcherGUI which are using exiftool to copy EXIF data from the input image to the

[Hugin-devs] [Bug 1428864] [NEW] Align_image_stack doesn't include lens and exposure settings in output images

Public bug reported: Hand held exposure stacks are automatically detected by hugin (current repo source). If the hand held image stacks are pre-aligned by align_image_stack then passed to hugin, hugin then fails to detect the stacks and is also unable to detect HFOV. Is it possible for

Re: [Hugin-devs] [Hugin-bug-hunters] [Bug 1426814] [NEW] hugin_executor cannot handle .pto in parent dir

On Sun, 01 Mar 2015 16:08:32 +1100, Sean Greenslade s...@seangreenslade.com wrote: But now there is no makefile, and I am told that hugin_executor is to be used in its place. But when I try to run it from a dir that doesn't contain the .pto using a relative path, this happens: [snip]

Re: [Hugin-devs] [Hugin-bug-hunters] [Bug 1384283] Re: At Appstart: wxWidgets Debug Alert ...

On Sat, 14 Feb 2015 09:12:46 +1100, Robin Canfield 1384...@bugs.launchpad.net wrote: Pretty sure that previous email meant someone was finally working on the problem, not that it has been fixed already. It means an attempt to fix the problem has been committed to the source code in the

Re: [Hugin-devs] [Hugin-bug-hunters] [Bug 1384283] Re: At Appstart: wxWidgets Debug Alert ...

On Sat, 14 Feb 2015 13:22:50 +1100, Robin Canfield 1384...@bugs.launchpad.net wrote: Yeah, what a Google search brings up isn't great. At least not last time I checked. Don't really know how to work with it with scripts. Maybe I'll try loading HugIn on some more computers (I do a lot

[Hugin-devs] [Bug 1411005] Re: hugin_executor branch (6815:06f25da1a783) fails to build

problem solved, my vigra was not up to date. I updated to vigra-1.10.0-1.fc20 and the latest source now builds OK. Marked as invalid. Cheers, Terry ** Changed in: hugin Status: New = Invalid -- You received this bug notification because you are a member of Hugin Developers, which is

[Hugin-devs] [Bug 1411005] [NEW] hugin_executor branch (6815:06f25da1a783) fails to build

Public bug reported: Trying to build current hugin_executor branch 6815:06f25da1a783 on Fedora 20 x86_64. I am getting a number of errors when linking CXX executables related to libhuginbase.so.0.0, an example below. Linking CXX executable fulla cd

[Hugin-devs] [Bug 1389952] Re: Fast Panorama preview doesn't honour 'overview' setting

Hello Thomas, I have built the latest source, and will see how it goes. Cheers, Terry -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/1389952 Title: Fast Panorama preview doesn't honour

[Hugin-devs] [Bug 1349758] Re: resulting image broken halfway

Whoops, forgot that the script generates a whole bunch of .pto files, so probably best to provide just the one output by pano_modify...the last prior to calling pto2mk. Cheers, Terry -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to

[Hugin-devs] [Bug 1349758] Re: resulting image broken halfway

Hello Nigel, Can you provide an archive (zip or bz2 or ...) with the project images and your .pto file? It would be preferable if the project images were downsized to keep the archive small, if that's possible. Cheers, Terry -- You received this bug notification because you are a member of

[Hugin-devs] [Bug 1406171] Re: New builtin blender doesn't fallback to 8 bit for jpeg

Fails to build here... /home/terry/rpmbuild/BUILD/hugin-2014.1.0/src/hugin_base/vigra_ext/utils.h:655:35: error: 'TypeAsString' is not a member of 'vigra' const std::string pixelType = vigra::TypeAsStringtypename DestTraits::ValueType::result(); -- You received this bug notification

[Hugin-devs] [Bug 1406171] [NEW] New builtin blender doesn't fallback to 8 bit for jpeg

Public bug reported: Testing hugin-executor branch (6781:b0daf9c2446e) built on Fedora 20 x86_64. Using two input 16 bit tiff images, builtin blender, and attempting to stitch exposure corrected ldr with output to jpeg. Stitch fails, JPEH does not support requested pixel type UINT16. When using

[Hugin-devs] [Bug 1405025] Re: Saved TIFFs have transparent alpha layer

Just bad luck, I guess, that nobody picked this before now. I can confirm that fix works OK here. Thanks Thomas. Cheers, Terry -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/1405025 Title:

[Hugin-devs] [Bug 1405025] Re: Saved TIFFs have transparent alpha layer

Same behaviour using multiblend, so it may vigra or libtiff causing this. -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/1405025 Title: Saved TIFFs have transparent alpha layer Status in Hugin

[Hugin-devs] [Bug 1405025] Re: Saved TIFFs have transparent alpha layer

Just ran my test project with a build of default branch 6694:a152bfe9c418 (using the bundles vigra) using enblend and the resulting tiff is good...no obscuring transparency layer. So it looks like this problem is due to changes in vigra. -- You received this bug notification because you are a

[Hugin-devs] [Bug 1405035] Re: Saved TIFF contains only one of the source images

I have a project here which is showing this behaviour. I am using hugin_executor branch (6771:7a2a12e71e67) built on Fedora 20 x86_64. The source images are two uncompressed tiff (~70MB each) and attempts to downsize them to provide an acceptable attachment size and still exhibit the problem

[Hugin-devs] [Bug 1405035] Re: Saved TIFF contains only one of the source images

Attachment (archive.zip) has input images, output stitch and .pto which exhibits this problem. Cheers, Terry ** Attachment added: newtest.zip https://bugs.launchpad.net/hugin/+bug/1405035/+attachment/4286849/+files/newtest.zip -- You received this bug notification because you are a

[Hugin-devs] [Bug 1405025] Re: Saved TIFFs have transparent alpha layer

I can reproduce this behaviour with the default branch (6775) and hugin_executor branch (6771) built on Fedora 20 x86_64. -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/1405025 Title: Saved

[Hugin-devs] [Bug 1405038] Re: Should be possible to render without having to save pto project

I don't have any problem saving panos without first saving the .pto. What OS are you using and which processor (Hugin_stitch_project or PTBatcherH GUI)? -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin.

[Hugin-devs] [Bug 1405038] Re: Should be possible to render without having to save pto project

I meant PTBatcherGUI, sorry. -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/1405038 Title: Should be possible to render without having to save pto project Status in Hugin - Panorama Tools GUI:

[Hugin-devs] [Bug 1405025] Re: Saved TIFFs have transparent alpha layer

save as png is showing the same behaviour here. -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/1405025 Title: Saved TIFFs have transparent alpha layer Status in Hugin - Panorama Tools GUI:

[Hugin-devs] [Bug 1402347] Re: Segmentation autooptimiser

I tried your .pto with hugin-2014.1.0 (Fedora 20 x86_64) and also suffered seg fault. Abridged output below. [terry@localhost Ben-hill]$ autooptimiser -a -s -o unopt2.pto unopt.pto *** Adaptive geometric optimisation Optimizing Variables Strategy 1 Average (rms) distance between Controlpoints

[Hugin-devs] [Bug 1397168] Re: CPFind gets bad control points for stacks

The problem hasn't arisen again in the testing I've done thus far. Thanks Thomas, you're worth your weight in cocky's feathers :-) Cheers, Terry -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin.

[Hugin-devs] [Bug 1396940] [NEW] Stack detection - odd behaviour

Public bug reported: I'm working with hugin_executor branch (6769:aed7abb78308) built on Fedora 20 x86_64. I have a set of bracketed shots (0,-1EV, +1EV), When loaded into hugin, hugin detects that there is varying exposure but can't find any stacks. If a subset of these images are downscaled

[Hugin-devs] [Bug 1397168] Re: CPFind gets bad control points for stacks

Here is the .pto file ** Attachment added: the project file https://bugs.launchpad.net/hugin/+bug/1397168/+attachment/4269972/+files/IMGP1825%20-%20IMGP1833.pto -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin.

  1   2   3   >