Hugin doesn't find control points / Hugin ne trouve aucun point de contrôle

[Lucie]

Hello,

I use Hugin for a few years but only with simple photos to assemble simple panoramas. When I uploaded the latest version Hugin couldn't find any control points ! The error indicating that groups of images non connected have been find appears everytime I click on "Align". What's happening ? Can you help me ?

French version : J'utilise Hugin depuis plusieurs années, seulement pour assembler des panoramas simples de plusieurs photos classiques. J'ai récemment téléchargé la dernière version du logiciel et Hugin ne trouve plus aucun point de contrôle entre mes images. L'erreur "Attention, X groupes d'images non connectées ont été trouvés ..." apparait à chaque fois que je clique sur "Aligner". Que se passe-t-il ? A l'aide !!

Windows 7, Hugin 2013 downloaded from SourceForge, default settings.

Thank you / merci d'avance

[Lucie]

Hello ? Anyone please ?

[GaaB]

Pour une raison bizarre, il faut lancer *manuellement* la création des
points de contrôles, après le chargement des photos, dans "l'éditeur de
panorama" onglet "Photos" (et pour accéder à cet éditeur, il faut le
faire s'afficher en utilisant le menu Vue de l'assembleur de panorama.

Aligner devrait lancer la création des points de contrôle si on en
croit le "hint" lié au bouton.

Par ailleurs, la version de make.exe ne fonctionne pas avec certains nom
de répertoires, récupérez celle de la version 2013 !
-----

For a reason I don't understand you have to manually launch the creation
of control points on the editor panel after loading the pictures in the
assistant tab !
And you have to get this editor window using the view menu of the "main"
windows.

Align on the assistant tab should launch automatically the control point
generator as shown on the hint linked to the Align button !

Seams to be a BUG ???


(Hugin for Windows 2014.0 RC1 (2014.0.0.6951a0bde18c built by Matthew
Petroff)

[Frederic Da Vitoria]

I saw this happen a few times, but not systematically, as you seem to be suggesting. My first idea is that there is something wrong in your setup. Did you try uninstalling Hugin completely and reinstalling it?

--
Frederic Da Vitoria
(davitof)

Membre de l'April - « promouvoir et défendre le logiciel libre » - http://www.april.org

[Stefan Peter]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello Lucie

Am 03.04.2014 16:48, schrieb Lucie:
> Hello,
>
> I use Hugin for a few years but only with simple photos to
> assemble simple panoramas. When I uploaded the latest version Hugin
> couldn't find any control points ! The error indicating that groups
> of images non connected have been find appears everytime I click on
> "Align". What's happening ? Can you help me ?

Have you reset your preferences after the upgrade? It may be that the
preferences from an older version specifies a control point detector
that is no longer part of the new version. Open your preferences (File
- -> Preferences) and click on the "Load Defaults" button on the bottom
left of the screen.

Sorry, no French version from me.


Regards

Stefan Peter


- --
In theory there is no difference between theory and practice. In
practice there is.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.14 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJTQoCPAAoJEBgqi52L7+L/pNwIAKQtK9i0I3SvhYWtVLeKBBsL
Du51017uQA6YC4woGDIaVBYlEVyPy1dwweuxezsl7kS0hHhaLELPmb3c2TZSezrg
OQ/T8pZIaemp4vLfpaXeu28lZ1v4NKWVCTixp14enFf+ndxYajtheZpDGy8yo5Nb
HrdyzjUfsq0P9ozudlReUkdI492eUsjXMPseMN9FsVjsJV/dfNzvG9oj9tI4f3y2
eZyz0pJ852bwuu6+NLxeP2nuvWhG6pfO9I4CKn1PmG7/Z1VzGlFw3PtYgfhwLuU3
OUBwWKC2M+4mhlmm6s9RZXiaz63pVrnMwx9dH7cwOHJRtik1QL78hTXESfYoS30=
=XcSF
-----END PGP SIGNATURE-----

[Carlos Eduardo G. Carvalho (Cartola)]

2014-04-07 7:40 GMT-03:00 Stefan Peter <s_p...@swissonline.ch>:

Have you reset your preferences after the upgrade? It may be that the
preferences from an older version specifies a control point detector
that is no longer part of the new version. Open your preferences (File
- -> Preferences) and click on the "Load Defaults" button on the bottom
left of the screen.

Sorry, no French version from me.

I would also give this advice. Have you tried this?

Je parle un peut le français. Si vous voulez je peux essayer de traduire, mais vous pouvez utilisé google aussi :)

Informez nous si cet conseille a résolu votre problème.

Salut,

Carlos E G Carvalho (Cartola)
--- Inscrições abertas para o curso de Fotografia Panorâmica Imersiva
--- Rio de Janeiro, 3 e 4 de maio de 2014
http://cartola.org/360
http://www.panoforum.com.br/

[Lucie]

Hello, thanks you all for your answers. I understand and speak English with no difficulty, I translated myself just to inform French internauts that they can speak French with me ;)

To Frederic, Stefan and Cartola : I tried these with no result. In fact I reinstalled Hugin several times !

A gaab : j'ai fait ce que tu dis mais ça échoue au niveau du processeur de traitement par lot, la fenêtre d'indication d'état reste vide et le processeur de traitement par lot échoue immédiatement.

[Stefan Peter]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Licie

Am 07.04.2014 15:41, schrieb Lucie:
>
> To Frederic, Stefan and Cartola : I tried these with no result. In
> fact I reinstalled Hugin several times !

Reinstalling (unfortunately) won't change the preferences from the old
version.

Regards

Stefan Peter


- --
In theory there is no difference between theory and practice. In
practice there is.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.14 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJTQq5FAAoJEBgqi52L7+L/cHoH/07b/OHgYVHrv1HMNwbioLNh
AeqSdWO2tKaJepijRNQY1CkCYDu6uDYvF+1Ir4GBfKCnPIP+Pzu7cW1OUtKTX4bx
J8Mfcu/45njLBSMYWwvDVMqdJVdDBZR/ZqmQ5l+9jiq9p0bF6vePvxPMMg7Ib0BB
3sCsoSZIItXIMBpwHmdF6O4xr+PRySYu5L9/jpGQHUyda6Yg+xPZmMyT/STgQuco
oG1R296gRkSzwxdn9HjuXCUns8FMnNDy/JS2ZhJkleUy7ygTJKeVc0JsUpbjKN2i
3sG3R91kODkk5HMal3oPqiUfMrbISylIXdviyWGi402YJOVbYjFAKnCbS+dptbE=
=G/fs
-----END PGP SIGNATURE-----

[Lucie]

OK, I have to be more precise : I clicked several times on the button "load defaults" AND I reinstaller Hugin several times.

[Frederic Da Vitoria]

(For those who don't understand French, Lucie says she is having problems with the batch GUI.)

Lucie, which batch method are you using? In Preferences, Stitching tab, what is Procecssor set to? Hugin_stitch_project or PTBatcherGUI?

--
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/f997be34-52dc-4d39-bd2d-60fa2d05c0ad%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

[GaaB]

Quelle est ta version de Hugin - et quelle est la version de Make, la
version 4.0 rencontre des problèmes sous Windows (à regarder avec
"l'invite de commande", comme dit la version française de Windows...)
>

dans le répertoire de Hugin faire bin>make.exe -v

GNU Make 3.82 <== la version 4 rencontre des problèmes sous Windows
Built for Windows32
Copyright (C) 2010 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
<http://gnu.org/licenses/gpl.html>

[Lucie]

Lucie, which batch method are you using?

> PTBatcherGUI

Quelle est ta version de Hugin - et quelle est la version de Make,

> Hugin : 2013.0.0.0d404a7088e6
> Make : je ne sais pas comment me placer dans le répertoire de Hugin avec l'invite de commande pour obtenir la version de make.exe. Je peux vous dire qu'elle date du 27/12/2010.

[T. Modes]

Lucie,

Am Dienstag, 8. April 2014 17:05:51 UTC+2 schrieb Lucie:

Lucie, which batch method are you using?

> PTBatcherGUI

this has nothing to do with your problem (this seems to be Frederic favourite guess, even when it does have nothing to do with the problem).

First go to preferences, select tab "control point detector" and press now "load defaults" (Load default works only for the currently selected tab and not for all settings.)
Now try again.

If this does not help, please post the log file. To get the log file, go to preferences again, and on general tab tick the option "copy log messages to clipboard". Now run the assistant again. When it fails, there should be a log message in the clipboard. Please post this log, so we can see the cause for the trouble.

Thomas

[Frederic Da Vitoria]

2014-04-08 17:20 GMT+02:00 T. Modes <Thomas...@gmx.de>:

Lucie,

Am Dienstag, 8. April 2014 17:05:51 UTC+2 schrieb Lucie:

Lucie, which batch method are you using?

> PTBatcherGUI

this has nothing to do with your problem (this seems to be Frederic favourite guess, even when it does have nothing to do with the problem).

Well, apart from the crash due to the graphics board which was solved long ago, ptbatcher is the only thing in Hugin which gave me consistently problems. When you get hit by the hammer repeatedly, you tend to accuse the hammer even if it has nothing to do with it :-)

And Lucie did write "le processeur de traitement par lot échoue immédiatement" which translates by "the batch processor fails immediately". But I understand that my little experience with Hugin can't be compared with your developer's experience of how Hugin really works. If you say PTBatcher has nothing to do with it, you are probably right.

Please note that this time I have not yet advised to stop using PTBatcher :-)

[David W. Jones]

On 04/08/2014 11:06 AM, Frederic Da Vitoria wrote:
> 2014-04-08 17:20 GMT+02:00 T. Modes <Thomas...@gmx.de

> <mailto:Thomas...@gmx.de>>:

>
> Lucie,
>
> Am Dienstag, 8. April 2014 17:05:51 UTC+2 schrieb Lucie:
>
> Lucie, which batch method are you using?
> > PTBatcherGUI
>
>
> this has nothing to do with your problem (this seems to be Frederic
> favourite guess, even when it does have nothing to do with the problem).
>
>
> Well, apart from the crash due to the graphics board which was solved
> long ago, ptbatcher is the only thing in Hugin which gave me
> consistently problems. When you get hit by the hammer repeatedly, you
> tend to accuse the hammer even if it has nothing to do with it :-)
>
> And Lucie did write "le processeur de traitement par lot échoue
> immédiatement" which translates by "the batch processor fails
> immediately". But I understand that my little experience with Hugin
> can't be compared with your developer's experience of how Hugin really
> works. If you say PTBatcher has nothing to do with it, you are probably
> right.
>
> Please note that this time I have not yet advised to stop using
> PTBatcher :-)

I've never had the problems with PT Batcher GUI that supposedly makes it
a problem.

--
David W. Jones
gnome...@gmail.com
wandering the landscape of god
http://dancingtreefrog.com

[Lucie]

Hello,

I loaded default settings in the tab "Control point detector" and I tried again : nothing changed, no control points detected. How do I access the clipboard with Windows 7 ?

To resume your discussion about PTBatcherGUI, I think there are two problems I'm facing :

- Hugin managed to find control points when I indicated to the assistant what to do, but it's not a viable solution for me. The assistant should do it itself as its name suggests !

- Then when the control points are detected the batch processor doesn't work and fails immediately.

Thank you for your help.

[GaaB]

Le 08/04/2014 17:05, Lucie a écrit :

> Quelle est ta version de Hugin - et quelle est la version de Make,
> > Hugin : 2013.0.0.0d404a7088e6
> > Make : je ne sais pas comment me placer dans le répertoire de Hugin
> avec l'invite de commande pour obtenir la version de make.exe. Je peux
> vous dire qu'elle date du 27/12/2010.
>

La version de Make qui est avec Hugin 2013 est Ok...

[T. Modes]

Hello,

Am Mittwoch, 9. April 2014 10:40:41 UTC+2 schrieb Lucie:

I loaded default settings in the tab "Control point detector" and I tried again : nothing changed, no control points detected. How do I access the clipboard with Windows 7 ?

Ctrl+C or menu Edit>Paste

To resume your discussion about PTBatcherGUI, I think there are two problems I'm facing :

- Hugin managed to find control points when I indicated to the assistant what to do, but it's not a viable solution for me. The assistant should do it itself as its name suggests !

One step after the other.
 

- Then when the control points are detected the batch processor doesn't work and fails immediately.

see FAQ for first help: http://wiki.panotools.org/Hugin_FAQ#Batch_processing
 

[Stefan Peter]

On 09.04.2014 10:40, Lucie wrote:
> Hello,
>
> I loaded default settings in the tab "Control point detector" and I
> tried again : nothing changed, no control points detected. How do I
> access the clipboard with Windows 7 ?

Immediately after running the hugin process, open a new text document
(notepad.exe) or a new email message, click into the text portion of the
window and press Ctrl+v (or use the menu commands Edit -> Paste).
Whatver information hugin has put into your clipboard is then pasted
into the text file or eMail message.

>
> To resume your discussion about PTBatcherGUI, I think there are two
> problems I'm facing :
> - Hugin managed to find control points when I indicated to the assistant
> what to do, but it's not a viable solution for me. The assistant should
> do it itself as its name suggests !

It's an assistant, not a zombie. It is you who wants to be credited with
the result after all ...

> - Then when the control points are detected the batch processor doesn't
> work and fails immediately.

That's an entirely different problem, one that was not mentioned in the
English part of your eMails (the only part I really understood) and one
that would deserve an email on its own. However, this seems to be a
common problem with users upgrading from prior versions an interestingly
be limited to windows users.
A short search in the archive of hugin-ptx seems to indicate the
following reasons for this:
o Virus scanners prohibiting the execution of make files. After
having quite some problems with download-and-execute attacks,
most virus scanners seem to have taken the approach of erring
on the good side of things and therefore prohibit execution
of unknown binaries by default. Unfortunately, this definition
seems to include some vital parts of the hugin batch processing
system. Anyhow, there are reports that after excluding the path
used for the panorama images from the watch list of your virus
scanner, batching panoramas starts to work again.
A better solution, of course, would be for us to find out the
reason for this behavior of the virus scanners and find a way
around it.
o Another source of grief is the inability of make to account for
certain characters in file names or paths. Whenever make, which
basically is responsible for creating the final panorama, encounters
a file or path name containing anything else than [a-zA-Z0-9], it
fails, sometimes without being able to relate an appropriate error
message to the calling application. This does not only affect
windows users, but all of us. It is known that users had to add
an additional user account for hugin to their system if their
original user name contained a éöäàüè or whatever.
Finding a remedy for this is not easy as it would require either
a rewrite of make or a different execution back end. However,
hugin could be smarter in this respect and warn a user using
path or file names containing offending characters.
o Finally(?), the hugin -> batch processor interface operates
using a file containing batch jobs that is shared between
hugin and the batch processor. It now may happen between
jobs and versions that this file get corrupted and can not
be read anymore by the batch processor. In this case, deleting
the file would be a viable way to solve this problem. However,
location and name of this file seem to differ between the
various operating systems supported by hugin and, as far as
I know, hugin does not offer to fix this problem by deleting
the file (yet ?)
I don't have a W7 installation that I could use to find
out the name and path of the file in question, but I'm sure
that one of the windows users on this list can chime in here.
This list may not be final, btw.

With kind 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

[T. Modes]

Am Mittwoch, 9. April 2014 18:44:25 UTC+2 schrieb T. Modes:

Hello,

Am Mittwoch, 9. April 2014 10:40:41 UTC+2 schrieb Lucie:

I loaded default settings in the tab "Control point detector" and I tried again : nothing changed, no control points detected. How do I access the clipboard with Windows 7 ?

Ctrl+C or menu Edit>Paste

I meant naturally Ctrl+V (after Stefans answer I saw my typo.)

[T. Modes]

Hi Stefan,

Am Mittwoch, 9. April 2014 20:48:13 UTC+2 schrieb Stefan Peter:

o Another source of grief is the inability of make to account for
  certain characters in file names or paths. Whenever make, which
  basically is responsible for creating the final panorama, encounters
  a file or path name containing anything else than [a-zA-Z0-9], it
  fails, sometimes without being able to relate an appropriate error
  message to the calling application. This does not only affect
  windows users, but all of us. It is known that users had to add
  an additional user account for hugin to their system if their
  original user name contained a éöäàüè or whatever.
  Finding a remedy for this is not easy as it would require either
  a rewrite of make or a different execution back end. However,
  hugin could be smarter in this respect and warn a user using
  path or file names containing offending characters.

Hugin already warn if there are invalid characters in the filename (at least for known issues).
(A remaining point are international characters on Windows which does not work always, but this is another point. Also GNU Make 4.0 has problems with parentheses in filename. This works fine with make 3.82.)

 

o Finally(?), the hugin -> batch processor interface operates
  using a file containing batch jobs that is shared between
  hugin and the batch processor. It now may happen between
  jobs and versions that this file get corrupted and can not
  be read anymore by the batch processor. In this case, deleting
  the file would be a viable way to solve this problem. However,
  location and name of this file seem to differ between the
  various operating systems supported by hugin and, as far as
  I know, hugin does not offer to fix this problem by deleting
  the file (yet ?)

This still exists: Start PTBatcherGUI with pressed Ctrl key. (see FAQ)
 
Thomas

[Lucie]

'C:\Users\PACME' n’est pas reconnu en tant que commande interne

ou externe, un programme exécutable ou un fichier de commandes.

Le chemin d’accès spécifié est introuvable.

make: *** [all] Error 1

It seems to be an error due to the user name, with is Pacôme, a french name with an accent. Will this be solved if I change the user name with Windows ?

I knew we couldn't use special caracters in filenames, but here I think it's very restrictive : no accent, no space, no special caracter of any kind... Au diable la créativité !

> - Then when the control points are detected the batch processor doesn't 
> work and fails immediately. 

That's an entirely different problem, one that was not mentioned in the 
English part of your eMails (the only part I really understood) and one 
that would deserve an email on its own.

I'm aware of that, each problem should deserve an email but I realized this problem when trying to solve the first one, thanks to gaab. Sorry for the disturbance.

[T. Modes]

Hi Lucie,

Am Donnerstag, 10. April 2014 10:20:13 UTC+2 schrieb Lucie:

'C:\Users\PACME' n’est pas reconnu en tant que commande interne

ou externe, un programme exécutable ou un fichier de commandes.

Le chemin d’accès spécifié est introuvable.

make: *** [all] Error 1

It seems to be an error due to the user name, with is Pacôme, a french name with an accent. Will this be solved if I change the user name with Windows ?

I knew we couldn't use special caracters in filenames, but here I think it's very restrictive : no accent, no space, no special caracter of any kind... Au diable la créativité !

No. Changing the user name will not change the name of your home directory (this is what makes the problem.).
Create a folder c:\temp and then set the temporary directory in Hugins preferences to this path. You could try if this is enough.
If not, you have to change the TEMP and TMP environment variable as described in FAQ http://wiki.panotools.org/Hugin_FAQ#Stitch_fails_when_.27.26.27_is_part_of_the_Windows_user-name
If this does not help, then you have to create a now user without special characters in the user name.

[Frederic Da Vitoria]

2014-04-10 10:20 GMT+02:00 Lucie <lucie...@gmail.com>:

'C:\Users\PACME' n’est pas reconnu en tant que commande interne

ou externe, un programme exécutable ou un fichier de commandes.

Le chemin d’accès spécifié est introuvable.

make: *** [all] Error 1

It seems to be an error due to the user name, with is Pacôme, a french name with an accent. Will this be solved if I change the user name with Windows ?

I knew we couldn't use special caracters in filenames, but here I think it's very restrictive : no accent, no space, no special caracter of any kind... Au diable la créativité !

I got hit by that one a few years ago (and I believe it wasn't in Hugin), so I decided to find other paths to creativity since then. At least Hugin has an option to avoid the issue, back then I had to create another user.

> - Then when the control points are detected the batch processor doesn't 

> work and fails immediately. 

That's an entirely different problem, one that was not mentioned in the 
English part of your eMails (the only part I really understood) and one 
that would deserve an email on its own.

I'm aware of that, each problem should deserve an email but I realized this problem when trying to solve the first one, thanks to gaab. Sorry for the disturbance.

I am sorry too, I hadn't realised English-speaking users had missed that part.

[GaaB]

Le 09/04/2014 20:48, Stefan Peter a écrit :
> On 09.04.2014 10:40, Lucie wrote:

>> - Hugin managed to find control points when I indicated to the assistant
>> what to do, but it's not a viable solution for me. The assistant should
>> do it itself as its name suggests !
>
> It's an assistant, not a zombie. It is you who wants to be credited with
> the result after all ...
>

I am very sorry, but I fully desagree with your above statement
It's CLEARLY indicated in the hint AND in the documentation that the
assistant will run the default Control Point Detector when clicking on
Align.

When "Simple Interface" is selected (which is the default if I remember
well) the Panorama Editor windows is not opened and *discovering* the
button "Create control points" is really a *challenge* !

Hence the initial message of Lucie.

---------------- Extract from the Assistant tab help ----
2. Align...
Clicking on Align... will use an automatic tool (the one set as Default
in the Control Point Detectors tab of the Preferences) to match images,
then use the internal Hugin optimiser to align them, correct exposure
and white balance.

[David W. Jones]

Hmm, how hard would it be to change Hugin and supporting panotools to
handle such characters? I'd think that if the underlying OS can handle
the characters, so should Hugin.

[Lucie]

I set the temporary directory in Hugins preferences to C:/temp, it doesn't change anything ; here is the new log file :

Finding control points...

"C:/Program Files/Hugin/bin/icpfind" -o "C:/temp/ha1F81.tmp" "C:/temp/ha1F81.tmp"

Error: cpfind requires at least an input project file.

09:17:39: Error: Failed to create a temporary file name (error 3: le chemin d’accès spécifié est introuvable.)

09:17:39: Error: Failed to create a temporary file name (error 3: le chemin d’accès spécifié est introuvable.)

C:\Program Files\Hugin\bin\cpfind.exe: option requires an argument -- o

Could not open  for reading

This is an indicator that the control point detector call failed,

or incorrect command line parameters have been used.

Executed command: C:\Program Files\Hugin\bin\cpfind.exe --multirow -o  

make: *** [all] Error 1

It seems to be a different error though... But I don't really understand. Do the temp directory has to be empty ?

I'll try the second solution when I can access the FAQ website (currently "experiencing technical difficulties").

Dear gaab and GnomeNomad : I couldn't agree more ! :)

[Lucie]

If not, you have to change the TEMP and TMP environment variable as described in FAQ http://wiki.panotools.org/Hugin_FAQ#Stitch_fails_when_.27.26.27_is_part_of_the_Windows_user-name

Whohooo, this works perfectly !! I did what explained in the FAQ and let blank the temporary directory in Hugins preferences. Make and PTBatcherGUI seem to be very happy after this change ! 

Thank you all for your help, just a last question : will I have to delete regularly the files created in C:/temp ?

[T. Modes]

Am Freitag, 11. April 2014 07:07:41 UTC+2 schrieb GnomeNomad:

Hmm, how hard would it be to change Hugin and supporting panotools to
handle such characters? I'd think that if the underlying OS can handle
the characters, so should Hugin.

Ask the guys from GNU make. Most special characters work with the introduction of the makefilelib.
E.g. for me it works with German umlauts ÄäÖöÜü  and also ß and characters with accents.

Some international characters make problems, but this is a problem of the underlying system and can't be so easily changed.

The biggest issue are parenthesis in filename (with worked in GNU make 3.81 and not in 3.82 and 4.0) and the ampersand and other characters in the user name. But this needs to fixed by GNU Make and can't bypassed by Hugin.

[David W. Jones]

And those issues have been reported to GNU make's team?

[Frederic Da Vitoria]

Hugin does leave some files behind on my Windows, nothing systematic, but it does happen. I don't complain because so many software (even non-free) leave things in the temp folder... But it would probably be a good idea to do some cleanup from time to time.

[David W. Jones]

On 04/11/2014 08:38 AM, Frederic Da Vitoria wrote:
> 2014-04-11 9:46 GMT+02:00 Lucie <lucie...@gmail.com

> <mailto:lucie...@gmail.com>>:

>
> If not, you have to change the TEMP and TMP environment variable as
> described in FAQ

> http://wiki.panotools.org/__Hugin_FAQ#Stitch_fails_when_.__27.26.27_is_part_of_the___Windows_user-name

> <http://wiki.panotools.org/Hugin_FAQ#Stitch_fails_when_.27.26.27_is_part_of_the_Windows_user-name>
>
> Whohooo, this works perfectly !! I did what explained in the FAQ and
> let blank the temporary directory in Hugins preferences. Make and
> PTBatcherGUI seem to be very happy after this change !
> Thank you all for your help, just a last question : will I have to
> delete regularly the files created in C:/temp ?
>
>
> Hugin does leave some files behind on my Windows, nothing systematic,
> but it does happen. I don't complain because so many software (even
> non-free) leave things in the temp folder... But it would probably be a
> good idea to do some cleanup from time to time.

I'd say that when Hugin/stitcher is done with the files, clean them up.

I use Windows 7 at work, and it litters the temp folder with a whole lot
more stuff than Windows XP did.

[T. Modes]

Fine that it works now.
If no errors occur there should be no files left in c:\temp; all temporary files will in this case deleted automatically.
Only if errors happen the temporary files are not automatically deleted. So you can delete the files in c:\temp by hand.