Re: [hugin-ptx] Problems stitching with newer versions of Hugin

Hi Greg, [I'm switching back to the main list as it might be relevant for other folks.] On 22/06/2024 08:55, Greg 'groggy' Lehey wrote: On Friday, 21 June 2024 at 22:56:06 +, wirz wrote: Hi Greg, So: I've tried things out, specifically enblend 4.3-e87da60fab22. It's better

Re: [hugin-ptx] keyboard shortcuts for new points in cp editor panel

to spend a rainy Sunday on that some time. cheers, lukas wirz -- A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ --- You received this message because you are subscribed to the Google Groups "hugin and other free panoramic software" group. To unsubs

Re: [hugin-ptx] keyboard shortcuts for new points in cp editor panel

I quickly had a look what is going on: Commit 8697 introduces the described behaviour, and more specifically, SetFocus() needs to be called on mouseEnter. I do, however, not know how to fix this appropriately. (There is also one superfluous semicolon.) cheers, lukas wirz On 16/06/2024 22

[hugin-ptx] keyboard shortcuts for new points in cp editor panel

this behaviour comes from or shall I have a go at bisecting it (it must be very recent)? cheers, lukas wirz -- A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ --- You received this message because you are subscribed to the Google Groups "

Re: [hugin-ptx] Problems stitching with newer versions of Hugin

On 07/05/2024 21:59, 'T. Modes' via hugin and other free panoramic software wrote: lukas wirz schrieb am Dienstag, 7. Mai 2024 um 18:20:03 UTC+2: That's slightly old, the version has been 4.3 for a bit. Just to make it more clear. The last released version is 4.2. The current development

Re: [hugin-ptx] Problems stitching with newer versions of Hugin

On 07/05/2024 10:19, Greg 'groggy' Lehey wrote: On Monday, 6 May 2024 at 15:58:31 +, wirz wrote: On 06/05/2024 06:05, Greg 'groggy' Lehey wrote: I've been making documentary panoramas of my house every week for the past 10 years, and for a long time I was using version 2018.0.0 of hugin

Re: [hugin-ptx] -v argument for cpfind in assistant files : mistake or missing documentation?

Hello chameleonscales@protonmail, cpfind -h tells me that '-v' stands for 'verbose', so it is completely expected that only the amount of printed output and not the result will be affected. cheers, lukas On 12/03/2024 23:45, 'ChameleonScales' via hugin and other free panoramic software

Re: [hugin-ptx] Re: How to get updated hugin-tools package for Hugin 2023.1

haven't looked at luminance-hdr, but for example in hugin these dependencies can be found in CMakeLists.txt (search for CPACK_DEBIAN_PACKAGE_DEPENDS or CPACK_DEBIAN_PACKAGE_SHLIBDEPS). cheers, Lukas Wirz -- A list of frequently asked questions is available at: http://wiki.panotools.org

Re: [hugin-ptx] Hugin computing power

significant if you do a lot of stitching. i might be able to catch some screen prints if you like. Ah, as Lukas Wirz wrote, it appears openCL...got those mixed up, but the point stands. a gpu that does openCL well is what you want, that ain't nvidea, this is intel and amd. No no, what I wrote

Re: [hugin-ptx] Hugin computing power

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

Re: [hugin-ptx] Combining small X-rays of circuit boards to make one complete image

, this is well within scope and 45 is not a very large number. cheers, lukas wirz On 21/12/2023 17:11, James C. Williams wrote: My current project is learning to use Hugin to create complete pictures of circuit boards from x-rays to be used for troubleshooting/repairs. I have obstacles. The first

Re: [hugin-ptx] Re: enblend / black corners and fringes

Hi Thomas and Chris, Thank you for your suggestions! I'm not sure when I'll have time for that, but starting with improved error detection should certainly be doable for some time soon. It's not important but I actually have an example where NFT+coarse+nopt leads to small but well visible black

Re: [hugin-ptx] Re: hugin/cmake patch

Hi Thomas, That's fine by me. I still think that what I typed was close to the correct (TM) solution but we can agree that it's not important enough to justify the additional cmake code. Thank you for merging the enblend patch! cheers, lukas On 19/10/2019 10:12, T. Modes wrote: > Hi Lukas,

Re: [hugin-ptx] Re: hugin/cmake patch

Hi, >> The cmake command to find python executables and libraries has changed >> in cmake 3.12. As a results hugin doesn't build for example in the >> current debian/testing. > [...] > > Hello, > > I have no opinion on the patch, it might be the correct thing to do. > I had successful builds

[hugin-ptx] hugin/cmake patch

Hi, The cmake command to find python executables and libraries has changed in cmake 3.12. As a results hugin doesn't build for example in the current debian/testing. Attached is a patch to fix this problem. It's tested against linux/cmake 3.13.4. I have not changed the WIN32 branches because

Re: [hugin-ptx] Re: enblend / black corners and fringes

Hi! On 26/09/2019 20:27, Monkey wrote: > I think all three should be fixed. #3 was one motivation for writing > Multiblend, because it can cause problems even when seams don't stray > (particularly when image edges make a corner). Multiblend assumes any > out-of-bounds pixel (per image) is the

[hugin-ptx] enblend / black corners and fringes

Hi, I have a been looking at the enblend problem that is described here (https://bugs.launchpad.net/enblend/+bug/721136) a bit more. In all examples that I know of, the problem is that the seamline(s) run(s) slightly outside of the overlap area. As a result, pixels are included from one image

Re: [hugin-ptx] Re: enblend patch

Hi Thomas, Sure, there is no hurry. I might also send another patch soon, I finally understood what causes the black corners/fringes but don't know how to fix it yet. cheers, lukas On 24/09/2019 20:43, T. Modes wrote: > Am Dienstag, 24. September 2019 16:37:44 UTC+2 schrieb lukas: >> >> I

[hugin-ptx] Fwd: enblend patch

I initially sent this mail 24 hours ago but it seems to have vanished. Again, with an updated patch. lukas Forwarded Message Subject: enblend patch Date: Sun, 22 Sep 2019 23:27:03 +0300 From: Wirz To: hugin and other free panoramic software Hi, attached is a patch that I

[hugin-ptx] enblend patch

Hi, attached is a patch that I would suggest to be applied to enblend. It does not solve any problem (with respect to the result image) that I am aware of. The problem that I'm fixing is in graphcut.h, in the function A_star: There was first an object of type CostComparer created, then this

[hugin-ptx] enblend patch 2

Hi, attached is a second patch for enblend. It fixes a memory leak which would occur whenever more than one seam is generated. cheers, lukas -- A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ --- You received this message because you are subscribed

Re: [hugin-ptx] Stiching aerial photos

Hi, I think there is nothing wrong with your pictures. I gave the first first two a try and they stitch fine (http://78.46.190.157:8080/first-two.jpg). Mostly that is, because there is a conceptual problem with aerial pictures: You can either stitch photos of any scene (with all the photos

Re: [hugin-ptx] Hugin: blending problem

Yes, I get that on a regular basis and have been for years. See https://bugs.launchpad.net/enblend/+bug/721136 cheers, lukas On 29/03/2019 15:55, lu...@usal.es wrote: > Hello everyone¡ > > Anyone get this error (see image in attachment) when he tries to make a > bracketing panorama > >

Re: [hugin-ptx] undefined reference to `wxTCPServer::Create(wxString const&)'

Hi, same problem here ... patch is attached. cheers, lukas On 18/01/2019 10:58, Jean-Luc Coulon (f5ibh) wrote: > Hi, > On Debian sid, I've the following error trying to build latest hg version > of hugin: > [ 81%] Linking CXX executable PTBatcherGUI > [ 81%] Built target icpfind > [ 82%]

[hugin-ptx] enblend compilation on debian testing

Hi, I'm currently failing to compile enblend (1516) on debian testing (with g++ 7.3). As far as I can say the actual problem is in the vigra header files which use some deprecated features (vigra itself warns about that but does not fail): [ 26%] Building CXX object

Re: [hugin-ptx] Hugin 2017.0 beta 1 release

I'm also getting a segfault when I add pictures (since two or three weeks ago). My machine runs debian/testing (kernel 4.4), the used libraries are 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.

Re: [hugin-ptx] Why is part of the stitched image black?

Maybe this old bug is resurfacing? https://bugs.launchpad.net/enblend/+bug/721136 I also still get that once in a while, but haven't mentioned it recently because I haven't learned anything new in the last three years. cheers, lukas On 22/12/16 18:41, Peter Cooper wrote: > The input files, and

Re: [hugin-ptx] Re: Hugin 2016.0 beta 1 released

On 17/02/16 17:29, T. Modes wrote: > > > Am Dienstag, 16. Februar 2016 22:08:45 UTC+1 schrieb Tduell: >> >> No sign of any mark on the "All" identify button in the Fast Panorama >> preview. >> Hope this helps. >> >> > Yes. The show all button is different in wxWidgets 2.8 and 3.0. And I >

Re: [hugin-ptx] Re: Hugin 2016.0 beta 1 released

Hi Thomas, On 16/02/16 22:08, Terry Duell wrote: > Hello Thomas, > > On Wed, 17 Feb 2016 05:46:38 +1100, T. Modes wrote: > >> >> >> Am Dienstag, 16. Februar 2016 02:49:47 UTC+1 schrieb Martin Pecka: >>> >>> Though I think the context menus in 3 are that unusual, that no

Re: [hugin-ptx] enblend / cmake

Hi Kornel, On 19/11/15 01:00, Kornel Benko wrote: > Am Mittwoch, 18. November 2015 um 23:44:24, schrieb Wirz <s...@lukas-wirz.de> >> Hi, >> >> I'm currently having trouble to build the 'package' target of enblend >> when I use cmake (files enblend.1 and

[hugin-ptx] enblend / cmake

Hi, I'm currently having trouble to build the 'package' target of enblend when I use cmake (files enblend.1 and enfuse.1 not found). (My system is Debian 8 with CMake 3.0.2.) For me the attached patch solves the problem. However, I don't know enough CMake to say for sure that this isn't my

Re: [hugin-ptx] focal length for Dodecahedron (12 images)?

pictured would be landscape. If you do portrait you'd need f=15.7mm or less. The single down facing pic needs to be parallel to one of the pics in the lower ring. The analogue holds for the up facing photo. (All of that is untested.) cheers, lukas On 09/10/15 23:23, Wirz wrote: > Hi Jan, > &

Re: [hugin-ptx] focal length for Dodecahedron (12 images)?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Jan, Based on what wikipedia says about regular dodecahedra and pentagons and after some scribling: Seen from the centre of a regular dodecahedron the height of one of the faces has an angle of 1.24 or 70.8 degrees. The diagonal of a pentagon

Re: [hugin-ptx] Re: clang compile errors

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Thomas, On 17/03/15 07:21, T. Modes wrote: Hi Lukas, Am Montag, 16. März 2015 04:13:06 UTC+1 schrieb lukas: Could I ask for the following patch to be applied to the hugin code? When compiling under the current Debian with clang++ 3.5, I

[hugin-ptx] clang compile errors

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi guys, Could I ask for the following patch to be applied to the hugin code? When compiling under the current Debian with clang++ 3.5, I get a number of compile errors which the patch fixes. cheers, lukas - -- Do not believe the naysayers who

Re: [hugin-ptx] unblended triangle in fused version?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Brandan, Is it just with the fused versions or will the low dynamic range do it as well? The bug I'm talking about is an enblend bug, so the fusing itself is irrelevant and your ldr version can be affected as well. It doesn't have to ...

Re: [hugin-ptx] unblended triangle in fused version?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 14/07/14 22:13, Bruno Postle twisted the bytes to say: On 14 July 2014 10:21, Wirz s...@lukas-wirz.de wrote: The bug I'm talking about is an enblend bug, so the fusing itself is irrelevant and your ldr version can be affected as well

Re: [hugin-ptx] unblended triangle in fused version?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Brandan, I think you are experiencing this bug https://bugs.launchpad.net/enblend/+bug/721136 For me, changing the output resolution, choosing a fine mask, switching off mask optimization and combinations of these sometimes helps. cheers, lukas

Re: [hugin-ptx] Enblend

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Kornel, In general I hope we can keep the number of packages that are newer than what comes with the normal distros at a minimum (currently I compile vigra, lcms and libpano13 myself every now and then in order to get the latest enblend and

Re: [hugin-ptx] Enblend

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Kornel, I ran into the same problem (Debian 7.3). 2.) I could not find appropriate debian package to replace it. That's what surprised me most: stable, unstable and testing have the same version that is behind the lcms-git by more than a year.

Re: [hugin-ptx] libpano13, cmake error

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Fixed, thank you! cheers, lukas Sorry, my cmake is too new. (It works here) Will correct. Kornel - -- Do not believe the naysayers who say it cannot be done. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment:

[hugin-ptx] enblend patch

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, [I'm not sure if this is the right place to post. Please direct my to a different place if appropriate.] I was trying to trace down a bug in enblend. I didn't find the one I was looking for but another one. Not sure if it causes anyone grief

[hugin-ptx] enblend / c++11

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, Currently I can compile enblend only after applying the following patch. I'm on Debian 7.2 and g++ 4.7. cheers, lukas diff -r 1d9b6aaf284e CMakeLists.txt - --- a/CMakeLists.txt Mon Oct 21 09:30:22 2013 +0200 +++ b/CMakeLists.txtWed Oct

Re: [hugin-ptx] Re: Possible Hugin bug in control points tab

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Thomas, Thanks for that hint! The reason for my problem was, that I used to pull from http://hugin.hg.sourceforge.net:8000/hgroot/hugin/hugin rather than http://hg.code.sf.net/p/hugin/hugin. Interestingly that doesn't produce any errors,

Re: [hugin-ptx] Re: Possible Hugin bug in control points tab

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Thomas, Is that problem really fixed for you? I'm currently running 2013.1.0.59f631f16431 which should be the latest version of the default branch and I'm observing exactly what can be seen on your screen shots: That is not the latest

Re: [hugin-ptx] Re: Possible Hugin bug in control points tab

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Christian, Thomas, This is fixed in the default branch. I confirm it's fixed after recompiling Hugin. Thank you very much, that was really fast! Is that problem really fixed for you? I'm currently running 2013.1.0.59f631f16431 which

Re: [hugin-ptx] CRITICAL: join us to nuke the pesky bug that is plaguing the fast preview

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Moin, Hmm, why is a graphics app trying to use PulseAudio? I don't even have it installed on any of my computers here! Exactly what I thought. Can you issue a ldd binary, like ldd /usr/local/bin/Hugin to display all linked libraries for hugin

Re: [hugin-ptx] long view of street?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Paul, that sound pretty much like what I tried a few month ago: http://tilia.dyndns.org:8000/img_3029-img_3071_fused.jpg My result is far from perfect of course, but it should do as a proof of concept. I took one photo of each house (to

[hugin-ptx] x-y-ratio in mosaic-mode

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, I have a question and---depending on the answer---a feature request/wish. I take photos of graffities a lot: [1] Is there any way to make sure the x-y-ratio of the object and the photo are the same? I have the impression that it differs a

Re: [hugin-ptx] Hugin file reduction

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Mike Earussi twisted the bytes to say: Does anyone know why Hugin is reducing my original files to 70% of their original size. Is this normal or is there some setting that needs to be changed so I can get the maximum resolution possible from my

Re: (I think it's a control point issue) Re: [hugin-ptx] Slowness fix?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Kornel Benko twisted the bytes to say: Am Dienstag 13 Juli 2010 schrieb Bruno Postle: On Wed 30-Jun-2010 at 01:08 +0100, James Legg wrote: The makefile export is 93% of the instruction fetches during saving. Improving these algorithms would be

Re: [hugin-ptx] Can this be stitched at all?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, Another problem: I recorded a 360 degree video, and got the frames stitched by Ryubin and Luca Vascon, using PTgui. However I fail to do so using hugin. As a beginner it would be extremely helpful to me, if someone could record his screen

Re: [hugin-ptx] Help with stitching - bad control points via Autopano-SIFT

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello Don, I'm running Hugin (2010.1.0.5161 by zoran zorkic) on Windows, but I've also tried many other versions (even a standalone Autopano-SIFT) and I just can't get a decent output. I shot an 8 photos panorama with 5DMK2 @ 12 mm (6 pan

Re: [hugin-ptx] Problems with photometric optimisation and the final output when translation is nonzero

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, The photometric optimiser claims there are no overlapping points. After a little bit more testing I can refine my initial description: If the translation parameters are large the optimizer claims there were no overlapping points -- in case of

Re: [hugin-ptx] Problems with photometric optimisation and the final output when translation is nonzero

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello Bruno, Bruno Postle twisted the bytes to say: On Sat 12-Jun-2010 at 01:05 +0200, Wirz wrote: I'm having some issues with the translation parameters (Tx, Ty, Tz). As soon as I start optimizing these parameters (and they get nonzero values

[hugin-ptx] Problems with photometric optimisation and the final output when translation is nonzero

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, I'm having some issues with the translation parameters (Tx, Ty, Tz). As soon as I start optimizing these parameters (and they get nonzero values) the photometric optimisation is not possible any more (Error: no overlapping points found,

[hugin-ptx] Re: Compiling Enblend (fails on my Debian machine)

Hi Seb, I followed exactly the instructions in the wiki, starting from scratch. Only texinfo was missing on my system. But the compilation still fails at the end: Updating ./versenblend.texi make[2]: *** No rule to make target `/../src/enblend.cc', needed by `varsenblend.texi'. Stop.

[hugin-ptx] svn 4393

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hey, Actually I don't have a question; I just want to report that I compiled the current version (4393) on a debian-lenny/t42-thinkpad with an ati graphic-chip yesterday and did a little bit of testing. Show control points works great. Would it be