Re: "linefind.exe has stopped working"

220 views
Skip to first unread message

alouest

unread,
Nov 12, 2012, 3:24:11 PM11/12/12
to hugi...@googlegroups.com
Well I had the same problem on 16 bits tiff, I ended up using cpfind in command line and the problem is solve give it a try!

Le lundi 12 novembre 2012 07:47:26 UTC-9, agb a écrit :
Hi!

I'm using Hugin.2012.0.0 on Windows 7 64bits to stich a long panorama of 33 16bit tifs.
I'm using the fix at https://groups.google.com/forum/?fromgroups#!msg/hugin-ptx/tf6Qiz7F7tI/nXtRSv_jUZ4J and control points are found.
I get the error "linefind.exe has stopped working" and so far I did not manage to find a fix for it on the Internet.
Any clue what I should do?

Gnome Nomad

unread,
Nov 12, 2012, 7:09:12 PM11/12/12
to hugi...@googlegroups.com
My experience is that linefind doesn't work on 16-bit images.

On 11/12/2012 10:24 AM, alouest wrote:
> Well I had the same problem on 16 bits tiff, I ended up using cpfind in
> command line and the problem is solve give it a try!
>
> Le lundi 12 novembre 2012 07:47:26 UTC-9, agb a �crit :
>
> Hi!
>
> I'm using Hugin.2012.0.0 on Windows 7 64bits to stich a long
> panorama of 33 16bit tifs.
> I'm using the fix at
> https://groups.google.com/forum/?fromgroups#!msg/hugin-ptx/tf6Qiz7F7tI/nXtRSv_jUZ4J
> <https://groups.google.com/forum/?fromgroups#%21msg/hugin-ptx/tf6Qiz7F7tI/nXtRSv_jUZ4J>
> and control points are found.
> I get the error "linefind.exe has stopped working" and so far I did
> not manage to find a fix for it on the Internet.
> Any clue what I should do?


--
Gnome Nomad
gnome...@gmail.com
wandering the landscape of god
http://www.clanjones.org/david/
http://dancing-treefrog.deviantart.com/
http://www.cafepress.com/otherend/

agb

unread,
Nov 13, 2012, 12:10:29 PM11/13/12
to hugi...@googlegroups.com
Hi!
I did manage to stich a number of other panoramas with 16bit tifs. Isn't Hugin always using linefind then?


On Tuesday, November 13, 2012 1:09:21 AM UTC+1, GnomeNomad wrote:
My experience is that linefind doesn't work on 16-bit images.

On 11/12/2012 10:24 AM, alouest wrote:
> Well I had the same problem on 16 bits tiff, I ended up using cpfind in
> command line and the problem is solve give it a try!
>
> Le lundi 12 novembre 2012 07:47:26 UTC-9, agb a �crit :

Gnome Nomad

unread,
Nov 13, 2012, 2:35:50 PM11/13/12
to hugi...@googlegroups.com
What happens with linefind and 16-bit tiffs is linefind finds no
vertical lines. If you convert the 16-bit tiffs to 8-bit, linefind finds
vertical lines in them.

What I do is make a set of 8- and 16-bit tiffs (with identical filenames
in separate folders), do my control point finding on the 8-bit tiffs,
then copy the resulting PTO file into the folder with the 16-bit tiffs.

I thought linefind silently failing on 16-bit tiffs had been fixed?

On 11/13/2012 07:10 AM, agb wrote:
> Hi!
> I did manage to stich a number of other panoramas with 16bit tifs. Isn't
> Hugin always using linefind then?
>
> On Tuesday, November 13, 2012 1:09:21 AM UTC+1, GnomeNomad wrote:
>
> My experience is that linefind doesn't work on 16-bit images.
>
> On 11/12/2012 10:24 AM, alouest wrote:
> > Well I had the same problem on 16 bits tiff, I ended up using
> cpfind in
> > command line and the problem is solve give it a try!
> >
> > Le lundi 12 novembre 2012 07:47:26 UTC-9, agb a �crit :
> >
> > Hi!
> >
> > I'm using Hugin.2012.0.0 on Windows 7 64bits to stich a long
> > panorama of 33 16bit tifs.
> > I'm using the fix at
> >
> https://groups.google.com/forum/?fromgroups#!msg/hugin-ptx/tf6Qiz7F7tI/nXtRSv_jUZ4J
> <https://groups.google.com/forum/?fromgroups#%21msg/hugin-ptx/tf6Qiz7F7tI/nXtRSv_jUZ4J>
>
> >
> <https://groups.google.com/forum/?fromgroups#%21msg/hugin-ptx/tf6Qiz7F7tI/nXtRSv_jUZ4J

T. Modes

unread,
Nov 13, 2012, 4:24:03 PM11/13/12
to hugin and other free panoramic software
>
> I thought linefind silently failing on 16-bit tiffs had been fixed?
>

After the fix the example you provided at groups.google.com/group/
hugin-ptx/browse_thread/thread/65b9f0b4b3f24cd0 did work for me. There
was no feedback, so the issue was solved for me. But instead of
testing, you did nagging with the issue in nearly all threads of the
last days. This is the first feedback after more than a half year to
the fix.
So please test again and provide more and new details (maybe with a
further example, because the example you provided works for me)

Gnome Nomad

unread,
Nov 14, 2012, 3:59:04 AM11/14/12
to hugi...@googlegroups.com
I'm using the version that Debian Sid offers: 2011.4.0.cf9be9344356. It
doesn't have the fix. Was the fixed version ever packaged for Debian? Or
was everything kind of on hold because the 2012 release was coming?

Stefan Peter

unread,
Nov 14, 2012, 12:05:07 PM11/14/12
to hugi...@googlegroups.com
On 14.11.2012 09:59, Gnome Nomad wrote:
> I'm using the version that Debian Sid offers: 2011.4.0.cf9be9344356. It
> doesn't have the fix. Was the fixed version ever packaged for Debian? Or
> was everything kind of on hold because the 2012 release was coming?
>

If you want to have a go at the fix mentined, you either have to use
2012.0.0+dfsg-1 from Debian/experimental or to have to roll your own
2012.0 version. Because Debian is in a freeze in preparation for the
wheezy release, 2012.0 won't probably get into sid anymore.


Regards

Stefan Peter


--
"In summary, I think you are trying to solve a problem that may not
need to be solved, using a tool that is not meant to solve it, without
understanding what is causing your problems and without knowing how
the tool actually works in the first place :)"
Jeffrey J. Kosowsky on the backuppc mailing list

Gnome Nomad

unread,
Nov 15, 2012, 5:29:01 PM11/15/12
to hugi...@googlegroups.com
On 11/14/2012 07:05 AM, Stefan Peter wrote:
> On 14.11.2012 09:59, Gnome Nomad wrote:
>> I'm using the version that Debian Sid offers: 2011.4.0.cf9be9344356. It
>> doesn't have the fix. Was the fixed version ever packaged for Debian? Or
>> was everything kind of on hold because the 2012 release was coming?
>>
>
> If you want to have a go at the fix mentined, you either have to use
> 2012.0.0+dfsg-1 from Debian/experimental

Just enabled experimental repository. When I force version Hugin to the
one from experimental, Synaptic tells me that hugin will be removed.
Let's try it and see what happens .. yup, Hugin's removed. Disabled
experimental repository, reinstalled Hugin from Sid, and it's back with
the 2011 version ... so doing it via Debian experimental repository
doesn't work.

> or to have to roll your own
> 2012.0 version. Because Debian is in a freeze in preparation for the
> wheezy release, 2012.0 won't probably get into sid anymore.

Guess I'll wait. My workaround takes extra time but it works.

Andreas Metzler

unread,
Nov 16, 2012, 1:40:04 PM11/16/12
to hugi...@googlegroups.com
Gnome Nomad <gnome...@gmail.com> wrote:
[...]
>> If you want to have a go at the fix mentined, you either have to use
>> 2012.0.0+dfsg-1 from Debian/experimental

> Just enabled experimental repository. When I force version Hugin to the
> one from experimental, Synaptic tells me that hugin will be removed.
> Let's try it and see what happens .. yup, Hugin's removed. Disabled
> experimental repository, reinstalled Hugin from Sid, and it's back with
> the 2011 version ... so doing it via Debian experimental repository
> doesn't work.
[...]

something like

apt-get install hugin=2012.0.0+dfsg-1 hugin-data=2012.0.0+dfsg-1 hugin-tools=2012.0.0+dfsg-1

should work.

cu andreas

--
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

Gnome Nomad

unread,
Nov 16, 2012, 6:41:57 PM11/16/12
to hugi...@googlegroups.com
On 11/16/2012 08:40 AM, Andreas Metzler wrote:
> Gnome Nomad wrote:
> [...]
>>> If you want to have a go at the fix mentined, you either have to use
>>> 2012.0.0+dfsg-1 from Debian/experimental
>
>> Just enabled experimental repository. When I force version Hugin to the
>> one from experimental, Synaptic tells me that hugin will be removed.
>> Let's try it and see what happens .. yup, Hugin's removed. Disabled
>> experimental repository, reinstalled Hugin from Sid, and it's back with
>> the 2011 version ... so doing it via Debian experimental repository
>> doesn't work.
> [...]
>
> something like
>
> apt-get install hugin=2012.0.0+dfsg-1 hugin-data=2012.0.0+dfsg-1 hugin-tools=2012.0.0+dfsg-1
>
> should work.

Thanks, Andreas, that worked.
Reply all
Reply to author
Forward
0 new messages