[hugin-ptx] Re: multiblend error
No, that didn't change everything. But it now works after recompiling without asan, it finished the blend as expected. One would need more time to investigate. Thank you very much for fixing the memset. > This one's not so obvious. Try changing line 531: > > int lp; > > to > > size_t lp; > > If that doesn't work, which I suspect it won't, you may just have to add > printfs to figure out exactly where it's breaking. > > >> -- 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 emails from it, send an email to hugin-ptx+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/5d09e692-09db-4a96-ab9a-85d796e08c6d%40googlegroups.com.
[hugin-ptx] Re: multiblend error
Your guess was right!! Now it goes further, but exists in collapse(), see below. = ==6086==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x7f766b376ec0 at pc 0x56341f8eadf3 bp 0x7ffd1ce25190 sp 0x7ffd1ce25180 READ of size 2 at 0x7f766b376ec0 thread T0 #0 0x56341f8eadf2 in collapse(struct_level*, struct_level*) (/usr/local/bin/multiblend+0x1bdf2) #1 0x56341f8ebe68 in blend() (/usr/local/bin/multiblend+0x1ce68) #2 0x56341f8ef7ec in go(char**, int) (/usr/local/bin/multiblend+0x207ec) #3 0x56341f8d60ff in main (/usr/local/bin/multiblend+0x70ff) #4 0x7f78e0235b96 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x21b96) #5 0x56341f8d6739 in _start (/usr/local/bin/multiblend+0x7739) 0x7f766b376ec0 is located 0 bytes to the right of 3926283968-byte region [0x7f7581311800,0x7f766b376ec0) allocated by thread T0 here: #0 0x7f78e0bba745 in memalign (/usr/lib/x86_64-linux-gnu/libasan.so.5+0x10c745) #1 0x56341f8ebadc in blend() (/usr/local/bin/multiblend+0x1cadc) #2 0x56341f8ef7ec in go(char**, int) (/usr/local/bin/multiblend+0x207ec) #3 0x56341f8d60ff in main (/usr/local/bin/multiblend+0x70ff) #4 0x7f78e0235b96 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x21b96) SUMMARY: AddressSanitizer: heap-buffer-overflow (/usr/local/bin/multiblend+0x1bdf2) in collapse(struct_level*, struct_level*) Shadow bytes around the buggy address: 0x0fef4d666d80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0fef4d666d90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0fef4d666da0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0fef4d666db0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0fef4d666dc0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 =>0x0fef4d666dd0: 00 00 00 00 00 00 00 00[fa]fa fa fa fa fa fa fa 0x0fef4d666de0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa 0x0fef4d666df0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa 0x0fef4d666e00: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa 0x0fef4d666e10: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa 0x0fef4d666e20: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa Shadow byte legend (one shadow byte represents 8 application bytes): Addressable: 00 Partially addressable: 01 02 03 04 05 06 07 Heap left redzone: fa Freed heap region: fd Stack left redzone: f1 Stack mid redzone: f2 Stack right redzone: f3 Stack after return: f5 Stack use after scope: f8 Global redzone: f9 Global init order: f6 Poisoned by user:f7 Container overflow: fc Array cookie:ac Intra object redzone:bb ASan internal: fe Left alloca redzone: ca Right alloca redzone:cb Shadow gap: cc ==6086==ABORTING Il giorno sabato 25 gennaio 2020 12:52:11 UTC+1, Monkey ha scritto: > > The likely suspect is the memset on line 449. > "(output->pitch*output->h)< casting those variables to size_t it should fix the problem. > > Replace: > > if (first) memset(output->data,0,(output->pitch*output->h)< > with: > > if (first) > memset(output->data,0,((size_t)output->pitch*(size_t)output->h)< > If it works, I'd love to know how much faster it is than Enblend, if > you've tried it. > > > > On Friday, 24 January 2020 21:27:22 UTC, Hans Bull wrote: >> >> After multiblend repeatedly aborted while trying to blend a 28611x51445, >> I recompiled it with -fsanitize=address and got the following. Any ideas >> where the problem might be? >> >> >> opening images (caching enabled)... >> processing 10.tif... >> processing 11.tif... >> 28611x51445, 8bpp, 13 levels >> seaming... >> masks... >> blending... >> = >> ==4832==ERROR: AddressSanitizer: negative-size-param: (size=-1350667056) >>#0 0x7fba7c09eecd (/usr/lib/x86_64-linux-gnu/libasan.so.5+0x66ecd) >> >>#1 0x55fe2de3ca07 in mask_into_output(struct_level*, float*, >> struct_level*, bool) (/usr/local/bin/ >> multiblend+0x19a07) >>#2 0x55fe2de3ee41 in blend() (/usr/local/bin/multiblend+0x1be41) >>#3 0x55fe2de42604 in go(char**, int) >> (/usr/local/bin/multiblend+0x1f604) >>#4 0x55fe2de2a0ff in main (/usr/local/bin/multiblend+0x70ff) >>#5 0x7fba7b7bfb96 in __libc_start_main >> (/lib/x86_64-linux-gnu/libc.so.6+0x21b96) >>#6 0x55fe2de2a739 in _start (/usr/local/bin/multiblend+0x7739) >> >> 0x7fb71c8b4800 is located 0 bytes inside of 3926283968-byte region >> [0x7fb71c8b4800,0x7fb806919ec0) >> allocated by thread T
[hugin-ptx] multiblend error
After multiblend repeatedly aborted while trying to blend a 28611x51445, I recompiled it with -fsanitize=address and got the following. Any ideas where the problem might be? opening images (caching enabled)... processing 10.tif... processing 11.tif... 28611x51445, 8bpp, 13 levels seaming... masks... blending... = ==4832==ERROR: AddressSanitizer: negative-size-param: (size=-1350667056) #0 0x7fba7c09eecd (/usr/lib/x86_64-linux-gnu/libasan.so.5+0x66ecd) #1 0x55fe2de3ca07 in mask_into_output(struct_level*, float*, struct_level*, bool) (/usr/local/bin/ multiblend+0x19a07) #2 0x55fe2de3ee41 in blend() (/usr/local/bin/multiblend+0x1be41) #3 0x55fe2de42604 in go(char**, int) (/usr/local/bin/multiblend+0x1f604) #4 0x55fe2de2a0ff in main (/usr/local/bin/multiblend+0x70ff) #5 0x7fba7b7bfb96 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x21b96) #6 0x55fe2de2a739 in _start (/usr/local/bin/multiblend+0x7739) 0x7fb71c8b4800 is located 0 bytes inside of 3926283968-byte region [0x7fb71c8b4800,0x7fb806919ec0) allocated by thread T0 here: #0 0x7fba7c144745 in memalign (/usr/lib/x86_64-linux-gnu/libasan.so.5+0x10c745) #1 0x55fe2de3eb17 in blend() (/usr/local/bin/multiblend+0x1bb17) #2 0x55fe2de42604 in go(char**, int) (/usr/local/bin/multiblend+0x1f604) #3 0x55fe2de2a0ff in main (/usr/local/bin/multiblend+0x70ff) #4 0x7fba7b7bfb96 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x21b96) SUMMARY: AddressSanitizer: negative-size-param (/usr/lib/x86_64-linux-gnu/libasan.so.5+0x66ecd) ==4832==ABORTING -- 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 emails from it, send an email to hugin-ptx+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/07c69f65-7693-48f6-a313-e5243a59e4a1%40googlegroups.com.
[hugin-ptx] cpfind, masks and memory
I have to deal with very large scanned input files and therefore tried to speed up cpfind by masking those parts without overlap. ncores is already at 1. It seems though that memory usage (and therefore swapping) is not reduced, and additionally, scaling down uses only one thread. Is there any possibility to reduce cpfind memory usage? Cheers HB -- 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 emails from it, send an email to hugin-ptx+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/18bbe19e-c584-4393-ace7-fad083ca1de6%40googlegroups.com.
[hugin-ptx] multiblend OpenMP
Would it be possible to make multiblend OpenMP enabled? Especially the image processing loop could benefit ... not too easy, after a glance at the source code. Cheers HB -- 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 emails from it, send an email to hugin-ptx+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/6310d9cd-5ea1-4eb1-80b7-680271ae8098%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[hugin-ptx] Re: Ubuntu ppa nightly
Thank you! That worked, after an hour or so. The dependencies are more or less still valid (libwxgtk3.0-gtk3-dev instead of libwxgtk2.8-dev, swig3.0 instead of swig2.0) -- 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 emails from it, send an email to hugin-ptx+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/0795ebb4-9148-450b-9612-c8060b946f7c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[hugin-ptx] Ubuntu ppa nightly
I noticed the nightly ppa (https://launchpad.net/~hugin/+archive/ubuntu/nightly ) is quite out of date (18 weeks ago). Are there any current builds available for Ubuntu? Or are there detailed build instructions? Cheers HB -- 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 emails from it, send an email to hugin-ptx+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/ac734113-b3ee-4a64-bad3-a3478230f51e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [hugin-ptx] hugin 2018.1.0.e7fabd53598b from nightly repo fails
I could not agree more...Nightly did its job. Works again. Thank you very much! Cheers, HB Il giorno martedì 24 luglio 2018 18:47:43 UTC+2, T. Modes ha scritto: > > > > Am Dienstag, 24. Juli 2018 16:11:56 UTC+2 schrieb Stefan Peter: >> >> > hugin: >> > >> /build/hugin-6ZZNNM/hugin-2018.1.0+hg7975+dfsg/src/hugin_base/panodata/ImageVariableGroup.cpp:111: >> >> >> > void >> > >> HuginBase::ImageVariableGroup::unlinkVariablePart(HuginBase::ConstImageVariableGroup::ImageVariableEnum, >> >> >> > unsigned int): Assertion »m_variables.find(variable) != >> > m_variables.end()« failed. >> > > This is only triggered by building the nightly with CMAKE_BUILD_TYPE=None. > When building with default settings the message there is no crash. The > build type None does activate the DEBUG_ASSERT statements (I have learned > by this report) and this triggers the message. > Strange that no Linux user has proposed to use the debugger to get a > meaningful backtrace. > > It should be fixed now in the repository. It will take some hours until > Stefan updates the nightly. Then it should work again. (I think the nightly > have fulfilled there purpose, so we catch at least bigger error during > development. There is always the possibility of breaking the nightly - but > this is the nature of them.) > > -- 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 emails from it, send an email to hugin-ptx+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/e29e7624-1e0d-4da3-af4a-228c877014db%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [hugin-ptx] hugin 2018.1.0.e7fabd53598b from nightly repo fails
Dear Stefan Peter, I just tried with 2018.1.0.e7fabd53598b and removed .hugin config file, but the problem remains. Cheers, HB Il giorno martedì 24 luglio 2018 16:11:56 UTC+2, Stefan Peter ha scritto: > > Dear Hans Bull > > On 23.07.2018 19:31, Hans Bull wrote: > > on Ubuntu 16.04. Cannot add more than one image, either with drag and > > drop or even with pto_gen, it quits with > > > > hugin: > > > /build/hugin-6ZZNNM/hugin-2018.1.0+hg7975+dfsg/src/hugin_base/panodata/ImageVariableGroup.cpp:111: > > > > void > > > HuginBase::ImageVariableGroup::unlinkVariablePart(HuginBase::ConstImageVariableGroup::ImageVariableEnum, > > > > unsigned int): Assertion »m_variables.find(variable) != > > m_variables.end()« failed. > > > > Can you try to rename the .hugin file in your user directory to, let's > say aaa.hugin and see if this helps? > This should reset all hugin settings to their default. > > With kind regards > > Stefan Peter > > -- 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 emails from it, send an email to hugin-ptx+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/7576b81b-ecb6-417a-8073-3c85f776022b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [hugin-ptx] hugin 2018.1.0.e7fabd53598b from nightly repo fails
Unfortunately no dialogue box appears, the only way I could get a error message at all was by running hugin from a terminal. The nightly versions worked until 5 days or so ago. Have to revert to 2017.0 for now, since I have some stuff to stitch. Cheers, HB Il giorno lunedì 23 luglio 2018 19:36:47 UTC+2, Gunter Königsmann ha scritto: > > Normally the dialogue that shows this error message offers to crash the > program in order to create a meaningful bug report with crash info. If you > press "abort" instead of "ok" in that occasion you might be lucky and hugin > might do what you want from it. > > Kind regards, > >Gunter. > > Hans Bull > schrieb am Mo., 23. Juli 2018, > 19:31: > >> on Ubuntu 16.04. Cannot add more than one image, either with drag and >> drop or even with pto_gen, it quits with >> >> hugin: >> /build/hugin-6ZZNNM/hugin-2018.1.0+hg7975+dfsg/src/hugin_base/panodata/ImageVariableGroup.cpp:111: >> >> void >> HuginBase::ImageVariableGroup::unlinkVariablePart(HuginBase::ConstImageVariableGroup::ImageVariableEnum, >> >> unsigned int): Assertion »m_variables.find(variable) != m_variables.end()« >> failed. >> >> -- >> 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 emails from it, send an >> email to hugin-ptx+...@googlegroups.com . >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/hugin-ptx/cf0defac-c793-41c5-af5e-bb4310394f78%40googlegroups.com >> >> <https://groups.google.com/d/msgid/hugin-ptx/cf0defac-c793-41c5-af5e-bb4310394f78%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> > -- 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 emails from it, send an email to hugin-ptx+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/ac9a2675-d8c7-4cb0-a890-5b2386fc80a5%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[hugin-ptx] hugin 2018.1.0.e7fabd53598b from nightly repo fails
on Ubuntu 16.04. Cannot add more than one image, either with drag and drop or even with pto_gen, it quits with hugin: /build/hugin-6ZZNNM/hugin-2018.1.0+hg7975+dfsg/src/hugin_base/panodata/ImageVariableGroup.cpp:111: void HuginBase::ImageVariableGroup::unlinkVariablePart(HuginBase::ConstImageVariableGroup::ImageVariableEnum, unsigned int): Assertion »m_variables.find(variable) != m_variables.end()« failed. -- 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 emails from it, send an email to hugin-ptx+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/cf0defac-c793-41c5-af5e-bb4310394f78%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[hugin-ptx] Re: Facebook cmp panorama metadata in hugin?
Gives me a double 403 error unfortunately Il giorno domenica 13 maggio 2018 12:35:27 UTC+2, Erik Krause ha scritto: > > Am 13.05.2018 um 09:47 schrieb Gunter Königsmann: > > is there a way to tell hugin to add panorama metadata to the > > produced jpeg > > Use Exif Fixer: > http://panoramaphotographer.com/software/exiffixer/ > > -- 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 emails from it, send an email to hugin-ptx+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/98841c19-ed1f-40d8-9a56-2ccec5c23b7b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[hugin-ptx] Re: Why is part of the stitched image black?
The --coarse-mask=12 thing does not really work for me It even seems that the enblend bug got worse in the recent daily builds. Anyone have the same impression? Il giorno venerdì 21 luglio 2017 05:30:43 UTC+2, Isaac Qiao ha scritto: > > check on this: > https://bugs.launchpad.net/enblend/+bug/721136/comments/19 > I solved the holes in my case by using > enblend --pre-assemble --fine-mask > --primary-seam-generator=nearest-feature-transform -o result.jpg *.tif > you could also use > enblend --pre-assemble --coarse-mask=12 -o result.jpg *.tif > or other number after coarse-mask larger than 8.(because by default, > enblend use 8 here. and by increasing it, enblend will look for a less > accurate seam between images) > > > -- 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 emails from it, send an email to hugin-ptx+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/5ba3a8e1-d404-43ca-aa6a-9245ec8e02ab%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[hugin-ptx] Re: exposure fused from any arrangement panorama bug
Indeed. Il giorno venerdì 24 febbraio 2017 18:00:18 UTC+1, Alex Romosan ha scritto: > > > that's not the problem. the blended panorama is just fine. the blended > and fused panorama is fine if i remove the position tag with gimp. this > is a bug that's been present for a while now. > > --alex-- > > > -- 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 emails from it, send an email to hugin-ptx+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/de3b13df-30ff-42cf-82e8-0dbc8b630bea%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [hugin-ptx] Why is part of the stitched image black?
The new default graph-cut algorithm in most cases seems to produce better seams, but sometimes has the black areas as a show stopper. In some cases it helped me splitting the panorama in two partial ones and doing a final enblend on the two intermediate files. But things should no be like this. HB Roger Broadie: > > That's helpful. I tried the option you recommended on several panoramas > that had the black area or areas showing in different places and it solved > them all. The > only comment I would make is that in the most difficult of those stitches, > on which I concentrated the most, it left a vestigial stitching flaw in a > straight line that did not > appear when I used the built-in stitcher. But that had its own similar > small flaw elsewhere, so you have to take your pick as to which you prefer. > > Roger Broadie > > > -- 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 emails from it, send an email to hugin-ptx+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/c2ae05e7-123e-46f7-be19-d16225fdf9a1%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [hugin-ptx] Why is part of the stitched image black?
Have you tried the enblend command line option --primary-seam-generator=nearest-feature-transform For me this normally solves the problem. Methinks the bug is sitting in the graph-cut (now default) seam finder algorithm. Cheers HB -- 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 emails from it, send an email to hugin-ptx+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/8a1a619a-bdc9-459f-80eb-e2101cee6832%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[hugin-ptx] Re: 2016.2 RC1 - error on TIFF control point generation: "caught exception: std::bad_alloc"
A "Warning: no TIFFTAG_SAMPLEFORMAT or TIFFTAG_DATATYPE, guessing pixeltype 'UINT16'." also occurs with 16bit TIFs generated by Nikon Capture NX-D. Nothing to worry about IMO. HB -- 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 emails from it, send an email to hugin-ptx+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/9b869ae3-0178-4312-9a20-8ad93299ba84%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [hugin-ptx] Re: Control points editor / Line detection / Projection of a single image
Thank you Stefan! I did not know the nighlty repository was still alive! Saves me much time. Cheers, HB Il giorno lunedì 16 maggio 2016 11:26:37 UTC+2, Stefan Peter ha scritto: > > > > How can I get a 64-bit Debian Linux version with this fix? Thanks. > > You can try the Hugin nightly builds for Ubuntu at > https://launchpad.net/~hugin/+archive/ubuntu/nightly > > > With kind regards > > Stefan Peter > > > -- > -- > A: Because it messes up the order in which people normally read text. > Q: Why is top-posting such a bad thing? > A: Top-posting. > Q: What is the most annoying thing in e-mail? > (See https://en.wikipedia.org/wiki/Posting_style for details) > -- 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 emails from it, send an email to hugin-ptx+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/4320fed2-054a-4317-b164-5b91fae40fa6%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[hugin-ptx] Re: newest hugin conflict with inkscape
Not only Inkscape, but also QGIS!! -- 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 emails from it, send an email to hugin-ptx+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/c57893b6-659a-43bc-b4c1-18931012f6fb%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [hugin-ptx] Exposure fused from any arrangement problem
Hello Terry, I thought I included the pto :( but I didn't. Sorry. Here it is: https://www.dropbox.com/s/dkw4jgioevv8o3c/_DSC7681-_DSC7689___x.pto?dl=0 And here the stiched image w/o problems: https://www.dropbox.com/s/1ha2vhsdjwjltmp/_DSC7681-_DSC7689___x.jpg?dl=0 The fused one should be included in the archive. Best, HB Il giorno domenica 31 agosto 2014 00:28:17 UTC+2, Tduell ha scritto: > > Hello Hans, > > > On Sat, 30 Aug 2014 21:31:50 +1000, Hans Bull > wrote: > > > Thank you so much, Terry! I uploaded everything here (using JPG instead > > > of the original 16bit TIF): > > > https://www.dropbox.com/s/mr2csuxuj5uyji9/_DSC7681-_DSC7689___x.tar.xz?dl=0 > > The archive includes the stitched files for immediate comparison. > Colours > > are not so important, since I use to convert the result to b/w, using > > darktable. > > OK, I have the files. > Let's also have your .pto file so I can see your control points and image > > EVs. > > Cheers, > -- > Regards, > Terry Duell > -- 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 emails from it, send an email to hugin-ptx+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/bac77242-5c66-4b1f-abc9-a5ca145bd103%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [hugin-ptx] Exposure fused from any arrangement problem
Thank you so much, Terry! I uploaded everything here (using JPG instead of the original 16bit TIF): https://www.dropbox.com/s/mr2csuxuj5uyji9/_DSC7681-_DSC7689___x.tar.xz?dl=0 The archive includes the stitched files for immediate comparison. Colours are not so important, since I use to convert the result to b/w, using darktable. Best, HB -- 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 emails from it, send an email to hugin-ptx+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/ea4efc57-3187-4701-959e-6409d08742dc%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [hugin-ptx] Exposure fused from any arrangement problem
Terry, optimizing only y,p,r,v unfortunately yields only marginally different results. --primary-seam-generator=graph-cut or --no-optimize does not help either. Photos are hand-held. In any case, a "exposure corrected, low dynamic range" stitch gives a perfectly aligned image (like the one on the right). That's what I do no understand. Best, HB -- 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 emails from it, send an email to hugin-ptx+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/27a5ff29-15d2-4049-9b0b-f888c28befb4%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[hugin-ptx] Re: Exposure fused from any arrangement problem
Finally found the old thread, referring to the 2013 version: https://groups.google.com/forum/?fromgroups#!topic/hugin-ptx/QZIRpWBotas --no-ciecam does not help, though. The problem persists in the ubuntu ppa:hugin/next (Raring, 64bit) I am using. -- 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 emails from it, send an email to hugin-ptx+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/99e37c8d-5d93-460e-b05b-55dfd29c93a8%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[hugin-ptx] Feature request: nona GPU fallback
Since some card drivers do not support the fantastic nona GPU feature, would it be possible to implement a (trivial) fallback to CPU calculation in the case of errors like the one below? CPU fallback is already used when the projection is not supported Cheers HB nona -g -z LZW -r ldr -m TIFF_m -o _DSC2464-_DSC2466 -i 0 /tmp/huginpto_4gGz3v nona: using graphics card: Intel Open Source Technology Center Mesa DRI Intel(R) Sandybridge Mobile nona: Unsupported framebuffer format in: /build/buildd/hugin-2014.0.0~rc4+dfsg/src/hugin_base/vigra_ext/ImageTransformsGPU.cpp:738 make: *** [_DSC2464-_DSC2466.tif] error 1 -- 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 emails from it, send an email to hugin-ptx+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/896f0eee-e283-4f1d-9f28-bb905238045f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[hugin-ptx] Re: error C7011: implicit cast from "int" to "float"
Here you are :-)
Il giorno giovedì 9 gennaio 2014 20:44:24 UTC+1, T. Modes ha scritto:
>
> It works here (Windows, ATI graphics card) without problems.
>
> Could you please post the output of
>
> nona -g -z LZW -r ldr -m TIFF_m -o test -i 1 -d 6_gennaio_2014_082-084.pto
>
> (the switch -d prints some more verbose output, it should print the code,
> which does not compile)
>
>
--
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 emails from it, send an email
to hugin-ptx+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/hugin-ptx/1cb6a527-9948-4f5a-ae48-825d59d7e610%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
nona: using graphics card: NVIDIA Corporation GeForce GT 540M/PCIe/SSE2
destStart=[6182, 376]
destEnd=[10742, 3469]
destSize=[(4560, 3093)]
srcSize=[(4896, 3672)]
srcBuffer=0x7f12db6cc010
srcAlphaBuffer=0
destBuffer=0x7f12d8e71010
destAlphaBuffer=0x7f12d80fd010
destGLInternalFormat=GL_RGBA8
destGLFormat=GL_RGB
destGLType=GL_UNSIGNED_BYTE
srcGLInternalFormat=GL_RGBA8
srcGLFormat=GL_RGB
srcGLType=GL_UNSIGNED_BYTE
srcAlphaGLType=GL_BYTE
destAlphaGLType=GL_UNSIGNED_BYTE
warparound=0
needsAtanWorkaround=0
maxTextureSize=16384
Source chunks:
[(0, 0) to (4896, 3672) = (4896x3672)]
Dest chunks:
[(0, 0) to (2280, 3093) = (2280x3093)]
[(2280, 0) to (4560, 3093) = (2280x3093)]
Total GPU memory used: 436136544
Interpolator chunks:
[(0, 0) to (4, 4) = (4x4)]
[(4, 0) to (8, 4) = (4x4)]
[(0, 4) to (4, 8) = (4x4)]
[(4, 4) to (8, 8) = (4x4)]
#version 110
#extension GL_ARB_texture_rectangle : enable
uniform sampler2DRect SrcTexture;
float sinh(in float x) { return (exp(x) - exp(-x)) / 2.0; }
float cosh(in float x) { return (exp(x) + exp(-x)) / 2.0; }
float atan2_xge0(const in float y, const in float x) {
return atan(y, x);
}
float atan2_safe(const in float y, const in float x) {
return atan(y, x);
}
float atan_safe(const in float yx) {
return atan(yx);
}
void main(void)
{
float discardA = 1.0;
float discardB = 0.0;
vec2 src = gl_TexCoord[0].st;
src -= vec2(5856.5000, 1910.);
// erect_pano(3749.1925443392915440)
src.t = 3749.1925443392915440 * atan_safe(src.t / 3749.1925443392915440);
// plane_transfer_to_camera
// distance : 3749.1925443392915440
// x : -0.019747837108399300676
// y : -0.00051089640700884301951
// z : -0.010687542017789300811
// plane yaw : 0.000
// plane pitch: 0.000
{
float phi = src.s / 3749.1925443392915440;
float theta = 1.5707963267948965580 - src.t / 3749.1925443392915440;
vec3 p = vec3(sin(theta)*sin(phi), cos(theta), sin(theta)*-cos(phi));
vec3 plane_coeff=vec3(0.000, 6.1230317691118862911e-17,
-1.000);
float den = -dot(plane_coeff, p);
if ( abs(den) < 1E-15 ) { discardA = 0.0; discardB = 1.0; }
float u = length(plane_coeff);
u = -u * u / den;
if ( u < 0 ) { discardA = 0.0; discardB = 1.0; }
p *= u;
p -=
vec3(-0.019747837108399300676,-0.00051089640700884301951,-0.010687542017789300811);
src = 3749.1925443392915440 * vec2( atan2_safe(p.s, -p.p),
asin(p.t/length(p)));
}
// rotate_erect(11778.435754189942600, -2591.5784907236384242)
{
src.s += -2591.5784907236384242;
float w = (abs(src.s) > 11778.435754189942600) ? 1.0 : 0.0;
float n = (src.s < 0.0) ? 0.5 : -0.5;
src.s += w * -23556.871508379885199 * ceil(src.s /
23556.871508379885199 + n);
}
// sphere_tp_erect(3749.1925443392915440)
{
float phi = src.s / 3749.1925443392915440;
float theta = -src.t / 3749.1925443392915440 + 1.5707963267948965580;
if (theta < 0.0) {
theta = -theta;
phi += 3.1415926535897931160;
}
if (theta > 3.1415926535897931160) {
theta = 3.1415926535897931160 - (theta - 3.1415926535897931160);
phi += 3.1415926535897931160;
}
float s = sin(theta);
vec2 v = vec2(s * sin(phi), cos(theta));
float r = length(v);
theta = 3749.1925443392915440 * atan2_safe(r, s * cos(phi));
src = v * (theta / r);
}
// persp_sphere(3749.1925443392915440)
{
mat3 m = mat3(0.6117730632294585, 0.0088114070154342478969,
5.4649435885076430553e-05,
-0.0088115764850840647138, 0.4194543892267468,
0.0062017635935263737759,
0.000, -0.0062020043720422933509,
0.8076738593788537);
float r = length(src);
float t
[hugin-ptx] Re: error C7011: implicit cast from "int" to "float"
Sure. Here is the entire project w/ files (I did not take the photos ;-) ): http://74.91.160.24/hugin_error_c7011.tar.gz Il giorno giovedì 9 gennaio 2014 20:12:05 UTC+1, T. Modes ha scritto: > > > ... > -- 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 emails from it, send an email to hugin-ptx+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/896ae87c-1948-4b40-99a6-e514542305b4%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[hugin-ptx] error C7011: implicit cast from "int" to "float"
Using Ubuntu 12.04 64 bit with the new Hugin 2014 beta and optimizing for yprxyzrvb I get the following error message: Checking nona...[OK] Checking enblend...[OK] Checking enfuse...[OK] Checking hugin_hdrmerge...[OK] Checking exiftool...[OK] === Stitching panorama === nona -g -z LZW -r ldr -m TIFF_m -o 6_gennaio_2014_082-084 -i 0 /tmp/huginpto_WtmXTH nona: using graphics card: NVIDIA Corporation GeForce GT 540M/PCIe/SSE2 nona -g -z LZW -r ldr -m TIFF_m -o 6_gennaio_2014_082-084 -i 1 /tmp/huginpto_WtmXTH nona: using graphics card: NVIDIA Corporation GeForce GT 540M/PCIe/SSE2 nona: GL info log: 0(41) : error C7011: implicit cast from "int" to "float" nona: coordinate transform shader program could not be compiled. make: *** [6_gennaio_2014_082-0840001.tif] Fehler 1 -- 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 emails from it, send an email to hugin-ptx+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/606d4f70-8d0d-4b0c-9fc1-737d87624cea%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [hugin-ptx] Hugin 2014.0beta1 released
> > Thank you so much, especially @Stefan Peter for the binaries! > -- 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 emails from it, send an email to hugin-ptx+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/5bdf663b-ad5e-4477-a5df-a6783bcc5953%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[hugin-ptx] Re: Poor stitching in 2013 release
This problem seems to appear only with panoramas with fused stacks or fused from any arrangement, according to what I observed. Do not know the reason, though. -- 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 emails from it, send an email to hugin-ptx+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/b43b5d2a-85c3-4bcb-a37b-133bb85883da%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [hugin-ptx] Correcting chromatic aberration with align_image_stack
Excuse me for reactivating this old thread. Would it be possible to make align_imge_stack look up the lens parameters in the lensfun database and do the correction together with the aligning? Would that make any sense? Should quality improve? > > -- 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 emails from it, send an email to hugin-ptx+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/18ad1911-4ff5-49e3-9445-ad17fa7f7099%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [hugin-ptx] Re: field of view must be positive
I experienced the same in the very same configuration as Thomas from the very same ppa. cpfind does not work any more, giving first "field of view must be positive" and then "bad params". Il giorno mercoledì 5 giugno 2013 13:47:36 UTC+2, Thomas Pryds ha scritto: > > 2013/5/24 T. Modes >: > > I can't reproduce the issue (Win 64 bit, Fedora 32 bit). Can somebody > > else reproduce this issue? If yes, what is the common point? > > I just experienced the same, on Ubuntu 12.10, 64 bit, in Hugin > 2013.0.0.70b10450ff94 (from the ppa) with libpano13 > 2.9.18+dfsg+2.9.19+hg783+1-0ubuntu5~quantal (also from the ppa). Also > two images. These have very large overlap; probably more than 80%, > JPEG files from a Canon EOS 500D. I have put the image files and pto > in a zip (app 14 MB) here if that's helpful: http://goo.gl/XVURG > > The messages appears when I click the "Calculate" button in the > "Photos" tab in the panorama editor (the one under "Optimise -> > Geometric"). When I click "ok" to the error message, Hugin either > closes abruptly, sometime after being unresponsive for some minutes. > > When I click the "Calculate" button, the following is output to the > console (the lines are mine): > -- > Optimizing Variables > Strategy 1 > Average (rms) distance between Controlpoints > after 0 iteration(s): 1189.61048121521 units > Strategy 1 > Average (rms) distance between Controlpoints > after 1 iteration(s): 111.313937620796 units > Strategy 1 > Average (rms) distance between Controlpoints > after 2 iteration(s): 34.195941354383 units > Strategy 1 > Average (rms) distance between Controlpoints > after 3 iteration(s): 13.1204719941758 units > Strategy 1 > Average (rms) distance between Controlpoints > after 4 iteration(s): 12.3721620730045 units > Strategy 1 > Average (rms) distance between Controlpoints > after 5 iteration(s): 3.93389385081116 units > Strategy 1 > Average (rms) distance between Controlpoints > after 6 iteration(s): 2.77917699920753 units > Strategy 1 > Average (rms) distance between Controlpoints > after 7 iteration(s): 2.68576195240624 units > Strategy 1 > Average (rms) distance between Controlpoints > after 8 iteration(s): 2.68576195240624 units > > Optimizing Variables > Strategy 2 > Average (rms) distance between Controlpoints > after 0 iteration(s): 2.43781390925982 units > Strategy 2 > Average (rms) distance between Controlpoints > after 1 iteration(s): 2.29918791227656 units > Strategy 2 > Average (rms) distance between Controlpoints > after 2 iteration(s): 2.29485798190338 units > Strategy 2 > Average (rms) distance between Controlpoints > after 3 iteration(s): 2.29484159105581 units > Strategy 2 > Average (rms) distance between Controlpoints > after 4 iteration(s): 2.29484153243107 units > --- > > Then the error message appears. When I click "ok", the following is > output: > > --- > Bad params > --- > > Then, after sometimes being unresponsive, the following is output: > > --- > Segmentation fault (core dumped) > --- > > > > Thomas > -- 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 emails from it, send an email to hugin-ptx+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/d508e6bd-a468-448a-b02f-d603b32f0497%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[hugin-ptx] Re: I need help calibrating my Sigma 8mm / 3.5f lens in Hugin and I am willing to pay. +Dustin Gelegonya
You should have a look here: http://www.darktable.org/2013/07/have-your-lens-calibrated/ -- 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 emails from it, send an email to hugin-ptx+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/aeafdb31-f331-46de-a37a-c6808fca1eee%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [hugin-ptx] Individiual nona command possibile in Hugin?
That's great news! So this means I use an outdated version of nona / libpano13 (using "next" repository, Ubuntu 12.04 64bit)? > The default branch has already the GLSL shader code for all input > projections, some more output projections and the translation parameters. > It was implemented some time ago, but there was no feedback. It works in > with my test projects, but there are more untested project variants. > > Thomas > -- 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 emails from it, send an email to hugin-ptx+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/5f0c6dc3-354e-45f1-809e-a9a033841c79%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [hugin-ptx] Individiual nona command possibile in Hugin?
> the most simple are always the bests > > Carlos E G Carvalho (Cartola) > > Exactly! . Another more or less related question: I'm getting the message on some images "Nona-GPU does not support the translation parameters. Switch to CPU calculation.". Is there any active development on this? It would be fantastic! -- 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 emails from it, send an email to hugin-ptx+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/cbe1600f-5c71-451d-80a1-39d1dd2f319b%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
