hugin-devs team mailing list archive
Mailing list archive
[Bug 808271] Re: Hugin on macosx doesn't parse extra cpfind parameters correctly
Sorry, you are completely correct. Using both works fine.
** Changed in: hugin
Status: New => Invalid
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Hugin.
Hugin on macosx doesn't parse extra cpfind parameters correctly
Status in Hugin - Panorama Tools GUI:
I have a long "line" of scanned images. These images have only one "neighbour" with repetitive data, hence I want to use the "--linearmatch 1" argument. The first run without it resulted in a lot of CPs found due to repetitions in the background. When cpfind is called from hugin with "--linearmatch 1" it gives an error:
Parse error: Argument: 1
Couldn't find match for argument
It does continue though.
The weird thing is that "--ncores 1" is accepted which I also need on my dual core system as the images are very big and I otherwise get a memory error (https://bugs.launchpad.net/hugin/+bug/717944).
I then tried "--ncores 1 --linearmatch 1", but that didn't help either. not in any order of specifying. When running from the commandline it works fine (which I finally did).
To manage notifications about this bug go to: