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
signature.asc
Description: OpenPGP digital signature
