[hugin-ptx] Re: [BUG] Segfault with unset

Manuel Presnitz schrieb am Montag, 18. Juli 2022 um 21:45:18 UTC+2: > Hi, > > sorry for not reporting the bug via Launchpad, but after several attempts > to create an Ubuntu One > account I gave up. > > However, I get a seg fault when starting hugin on two different machines. > Should be f

[hugin-ptx] Re: [BUG] Segfault with unset

In case this wasn't obvious and implied by your post, the error in the code is exactly where the seg fault occurs: hugin/src/hugin-2021.0.0/src/hugin_base/hugin_utils/utils.cpp:475 475 if (strlen(xdgDataDir) == 0) Seg faults often indicate a bug in a distant place, that may be hard to identif

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

On 27.04.2015 17:16, tmodes wrote: >> The .py modules mentioned shold be changed to have >> # @api-max 2015.0 >> instead of >> # @api-max 2014.1 > > I know. But it would be nice if someone could test the scripts and > report back if there are still running. (I never used them so I can not > judge

Re: [hugin-ptx] Re: bug cpclean and line control points

On 2013-07-05 12:59 PM, T. Modes wrote: Am Dienstag, 2. Juli 2013 23:57:14 UTC+2 schrieb Jim Watters: I think the worst cp should always be removed. But would be happy with a flag to have this ability. In the default branch cpclean has now an option to include line cp for filtering.

Re: [hugin-ptx] Re: bug cpclean and line control points

Am Dienstag, 2. Juli 2013 23:57:14 UTC+2 schrieb Jim Watters: > > > I think the worst cp should always be removed. But would be happy with a > flag to have this ability. > > In the default branch cpclean has now an option to include line cp for filtering. Thomas -- A list of frequently as

Re: [hugin-ptx] Re: bug cpclean and line control points

On 2013-07-03 2:58 PM, T. Modes wrote: Am Dienstag, 2. Juli 2013 23:57:14 UTC+2 schrieb Jim Watters: The problem of line control points is exaggerated because the optimizer gives more weight to them. This is new to me. I thought the optimizer treats all cp the same. Can you give a sou

Re: [hugin-ptx] Re: bug cpclean and line control points

Am Dienstag, 2. Juli 2013 23:57:14 UTC+2 schrieb Jim Watters: > > The problem of line control points is exaggerated because the optimizer > gives more weight to them. > This is new to me. I thought the optimizer treats all cp the same. Can you give a source? Or give a hint, where in the source

Re: [hugin-ptx] Re: bug cpclean and line control points

On 07/02/2013 06:35 AM, T. Modes wrote: Am Montag, 1. Juli 2013 19:40:20 UTC+2 schrieb Jim Watters: cpclean will not remove bad line control points. This is intentional. Cpclean will currently only remove "normal" cp. All line control points are ignored (also for calculation of errors/l

Re: [hugin-ptx] Re: bug cpclean and line control points

On 2013-07-02 1:35 PM, T. Modes wrote: Am Montag, 1. Juli 2013 19:40:20 UTC+2 schrieb Jim Watters: cpclean will not remove bad line control points. This is intentional. Cpclean will currently only remove "normal" cp. All line control points are ignored (also for calculation of errors/lim

[hugin-ptx] Re: bug linefind and edge of image

Am Montag, 1. Juli 2013 19:39:20 UTC+2 schrieb Jim Watters: > > linefind will find vertical lines that are the edge of the image. When the > camera has a tilt this is really bad. > > I have not seen such effects during testing. > I don't have permission to submit the images yet. > Without

[hugin-ptx] Re: bug cpclean and line control points

Am Montag, 1. Juli 2013 19:40:20 UTC+2 schrieb Jim Watters: > > cpclean will not remove bad line control points. > This is intentional. Cpclean will currently only remove "normal" cp. All line control points are ignored (also for calculation of errors/limits). The background was, that line co

Re: [hugin-ptx] Re: bug pto_var unlink link

On 2013-06-18 1:44 PM, T. Modes wrote: Hi Jim, On 18 Jun., 05:14, Jim Watters wrote: pto_var version 2013.0.0.70b10450ff94 built by Matthew Petroff, tested on Windows. The pto_var with unlink changes all images not just the one being unlinked. That's not a bug. You are thinking in the pano

[hugin-ptx] Re: bug pto_var unlink link

Hi Jim, On 18 Jun., 05:14, Jim Watters wrote: > pto_var version 2013.0.0.70b10450ff94 built by Matthew Petroff, tested on > Windows. > > The pto_var with unlink changes all images not just the one being unlinked. > That's not a bug. You are thinking in the panotools format, where you can link e

Re: [hugin-ptx] Re: Bug Tracker: proposal for migration

On October 29, 2010 06:27:36 pm Bruno Postle wrote: > I agree that the sourceforge tracker is failing us and that almost > anything must be better. Whatever it is if it has some integration > with the HG repository this would be very useful. * Launchpad has integration with bzr. I am waiting for

Re: [hugin-ptx] Re: Bug Tracker: proposal for migration

On Thu 28-Oct-2010 at 07:53 -0400, Yuval Levy wrote: I have not looked into repository integration. The quantity of bugs we are dealing with at the moment does not yet justify a custom solution IMO. If it comes along as a free bonus, great. Else, it won't happen any time soon. Maybe in 2011?

Re: [hugin-ptx] Re: Bug Tracker: proposal for migration

Hi Thomas, thank you for another good set of thoughts. On October 27, 2010 12:09:15 pm T. Modes wrote: > Actually it would be a fourth home (you forgot the manual on the > wiki). Yes, right. distribution is good. never put all of your eggs in a single basket. That was one of the major advan

[hugin-ptx] Re: Bug fixes in Enfuse 4.0 over 3.2

On Sep 7, 12:12 pm, "foot m. (mf4v07)" wrote: > When changing from version 3.2 to 4.0 I've noticed some changes in the default > selection process, and I would assume it is due to the fix in the release > notes > described as: > > > - Make Enblend and Enfuse aware of the input images' resolution.

[hugin-ptx] Re: Bug: parameters of the pannini are not exported, and future request

> I found that the export to PTmender script does not include the > parameters of the projection. This bug should be fixed in rev 4956 Thomas -- You received this message because you are subscribed to the Google Groups "hugin and other free panoramic software" group. A list of frequently aske

[hugin-ptx] Re: bug: crop circle not visible on 2009.4 OS X

circular fisheye On Jan 5, 10:14 pm, Bruno Postle wrote: > On Tue 05-Jan-2010 at 08:42 -0800, Jeffrey Martin wrote: > > >I cannot see the cropping circle on version 2009.4 on os X. I can see > >the rectangle that contains the circle, but not the circle. > > Are your input photos set to 'fisheye'

[hugin-ptx] Re: Bug in the camera response model?

On Tue, Oct 13, 2009 at 06:46, Seb Perez-D wrote: > On Tue, Oct 13, 2009 at 00:53, Bruno Postle wrote: >>> >>>Can anyone reproduce? (the steps to reproduce are in the bug report). >> >> I haven't tried to reproduce, but all this stuff has been heavily >> refactored in the layout branch, maybe it

[hugin-ptx] Re: Bug in the camera response model?

On Tue, Oct 13, 2009 at 00:53, Bruno Postle wrote: >> >>Can anyone reproduce? (the steps to reproduce are in the bug report). > > I haven't tried to reproduce, but all this stuff has been heavily > refactored in the layout branch, maybe it is already fixed there. OK, checking out & compiling. B

[hugin-ptx] Re: Bug in the camera response model?

On Tue 13-Oct-2009 at 00:42 +0200, Seb Perez-D wrote: > >I just got bitten by a strange bug, which I described here: >https://sourceforge.net/tracker/?func=detail&aid=2877384&group_id=77506&atid=550441 > >Basically, with two lenses and different camera response models, the >output depends on which

[hugin-ptx] Re: Bug Tracker Policy

On Fri 09-Oct-2009 at 02:14 -0400, Yuval Levy wrote: > >unless there are strong objections I intend to change the tracker policy >to accept only bug reports from identified users. This is fine by me, most reports initially raise questions rather than provide a reproducible bug description straig

[hugin-ptx] Re: Bug Tracker Policy

I don't think hugin will lose much by doing so. Most active contributors are already registered. On Fri, Oct 9, 2009 at 8:14 AM, Yuval Levy wrote: > > Hi all, > > unless there are strong objections I intend to change the tracker policy > to accept only bug reports from identified users. > > bug

[hugin-ptx] Re: bug: obscure compile failure if libpano12 is installed

James Legg wrote: > I don't remember directly changing anything in the non libpano13 > sections, but it does remove chunks from files that are changed in the > gsoc2009_layout branch. > > I think svn merge should be able to find its way around the patch > without to much hassle. thanks, James. I

[hugin-ptx] Re: bug: obscure compile failure if libpano12 is installed

On Sep 7, 5:59 pm, Yuval Levy wrote: > Yuval Levy wrote: > > yes, libpano12 is unmaintained legacy. > > I've cleaned up a lot of cruft. the patch is at > https://sourceforge.net/tracker/download.php?group_id=77506&atid=5504... Thanks Yuv! :) Reid --~--~-~--~~~---~--

[hugin-ptx] Re: bug: obscure compile failure if libpano12 is installed

On Mon, 2009-09-07 at 18:59 -0400, Yuval Levy wrote: > Yuval Levy wrote: > > yes, libpano12 is unmaintained legacy. > > I've cleaned up a lot of cruft. the patch is at > https://sourceforge.net/tracker/download.php?group_id=77506&atid=550441&file_id=342125&aid=2853853 > > needs to be tested. al

[hugin-ptx] Re: bug: obscure compile failure if libpano12 is installed

Yuval Levy wrote: > yes, libpano12 is unmaintained legacy. I've cleaned up a lot of cruft. the patch is at https://sourceforge.net/tracker/download.php?group_id=77506&atid=550441&file_id=342125&aid=2853853 needs to be tested. also if it affects a GSoC project pending integration (James?), it n

[hugin-ptx] Re: bug: obscure compile failure if libpano12 is installed

Reid Priedhorsky wrote: > Removing libpano12-dev and friends and replacing with libpano13-dev > and friends resulted in a successful build and working software. > > The docs indicate libpano13 is required, but the cmake step did not > complain that I had the wrong libpano version. yes, libpano12

[hugin-ptx] Re: bug in shear parameter handling: READ IT if you use them!

Hi dmg, I often correct for shear: all my scans from my Nikon Super Coolscan 4000 (aka LS-4000) suffer from shear while my other film scanner (Hasselblad Flextight 646) needs no correction. The biggest problem with the Nikon scanner (and should be true for most film scanners) is that the frame n

[hugin-ptx] Re: Bug Triage: priorities?

On 2009.06.25. 16:27, Yuval Levy wrote: > Hi Oskar, > > Oskar Sander wrote: >> Is there a one-pager in the wiki on what info and fields that should be >> entered? > > I just put up an initial draft at while sf tracker is quite limited when comparing to

[hugin-ptx] Re: Bug Triage: priorities?

Bruno Postle wrote: > On Wed 24-Jun-2009 at 10:30 +0200, Yuval Levy wrote: >> Can we agree that priority 5 bugs are "untriaged bugs" and whoever does >> the triage sets the priority to something else? > > Yes that seems quite logical for new bugs, I'm not sure what to do > about the old reports.

[hugin-ptx] Re: Bug Triage: priorities?

Hi Oskar, Oskar Sander wrote: > Is there a one-pager in the wiki on what info and fields that should be > entered? I just put up an initial draft at comments welcome. the page on the wiki is editable, feel free to improve or as questions. Yuv --~--~

[hugin-ptx] Re: Bug Triage: priorities?

On Wed 24-Jun-2009 at 10:30 +0200, Yuval Levy wrote: > >Can we agree that priority 5 bugs are "untriaged bugs" and whoever does >the triage sets the priority to something else? Yes that seems quite logical for new bugs, I'm not sure what to do about the old reports. -- Bruno --~--~-~-

[hugin-ptx] Re: Bug Triage: priorities?

Excuse my ignorance, but out of interest as a bug-reporter: Is there a one-pager in the wiki on what info and fields that should be entered? Cheers /O 2009/6/24 Yuval Levy > > hi all, > > weather is bad here. son and wife are sleeping. I work on codifying bug > triaging. > > One key issue to

[hugin-ptx] Re: bug

Thanks, now it works good. I just need to read the tutos! Thanks for all ivanchti On Nov 3, 7:44 pm, Andreas Metzler <[EMAIL PROTECTED]> wrote: > ivanchti <[EMAIL PROTECTED]> wrote: > > I tried the debian packages of enfuse  bt ther were no packages > > avalaible for my architecure. I try the co

[hugin-ptx] Re: bug

ivanchti <[EMAIL PROTECTED]> wrote: > I tried the debian packages of enfuse bt ther were no packages > avalaible for my architecure. I try the compilation. [...] Which arch is that? i386 was missing but is available now. cu andreas --~--~-~--~~~---~--~~ You rece

[hugin-ptx] Re: bug

Thanks a lot! I tried the debian packages of enfuse bt ther were no packages avalaible for my architecure. I try the compilation. Thank Ivanchti On Nov 2, 11:57 pm, Bruno Postle <[EMAIL PROTECTED]> wrote: > On Sun 02-Nov-2008 at 12:33 -0800, ivanchti wrote: > > > > >thank you, i downloaded. C

[hugin-ptx] Re: bug

On Sun 02-Nov-2008 at 12:33 -0800, ivanchti wrote: > >thank you, i downloaded. Can yo tell me the command lines to compil? >I'm not very used with console mode! usually something like this: tar zxf enblend-enfuse-3.2.tar.gz cd enblend-enfuse-3.2 ./configure make sudo make install

[hugin-ptx] Re: bug

thank you, i downloaded. Can yo tell me the command lines to compil? I'm not very used with console mode! Thanks On Nov 2, 2:17 am, Bruno Postle <[EMAIL PROTECTED]> wrote: > On Sat 01-Nov-2008 at 14:05 -0700, ivanchti wrote: > > > > >I had a bug message from my hugin : > >make: enfuse : commande

[hugin-ptx] Re: bug

Bruno Postle <[EMAIL PROTECTED]> wrote: > On Sat 01-Nov-2008 at 14:05 -0700, ivanchti wrote: >>I had a bug message from my hugin : >>make: enfuse : commande introuvable > You need to install the current version of enblend, this contains > the enfuse tool: > http://enblend.sourceforge.net/ Pa

[hugin-ptx] Re: bug

On Sat 01-Nov-2008 at 14:05 -0700, ivanchti wrote: > >I had a bug message from my hugin : >make: enfuse : commande introuvable You need to install the current version of enblend, this contains the enfuse tool: http://enblend.sourceforge.net/ -- Bruno --~--~-~--~~~---