Re: [hugin-ptx] Mac Build

[dgjohnston]

Yes thanks Niklas that was the fix. I remember seeing that in your first link 
but when I used the second link it totally went out of mine. Thanks again also 
for doing all this work. I've tested large pto files that I have and all seems 
to be working now. 

Don JohnstonSent from my Samsung device

 Original message 
From: Niklas Mischkulnig  
Date: 2016-04-18  11:05 PM  (GMT-06:00) 
To: hugin-ptx@googlegroups.com 
Subject: Re: [hugin-ptx] Mac Build 

I had to go into the Hugin.app settings, under programs and set alternative 
enblend/enfuse executables to ./enblend and ./enfuse to make PTBatcherGui work. 
Am 19.04.2016 00:53 schrieb "Donald Johnston" :
To add to this error information I did two additional tests with these 
images.1. the first three images so it was an exposure stack. All fine until 
“Create panorama…”; same failure.   Blender: Unknown blender (enblend —version 
failed)  Exposure fusion: Unknown exposure fusion (enfuse —version failed)
ExifTool: FAILED

2. images 1, 4, and 7; so no exposure stack just a three image pano … same 
failure (except no enfuse failed).   Blender: Unknown blender (enblend —version 
failed)  ExifTool: FAILED


On Apr 18, 2016, at 4:32 PM, Donald Johnston  wrote:
Another error. I loaded an old project with 18 images that requires exposure 
fusion and stitching. The project loaded fine, the preview window show the 
aligned preview as it should be.  When I ran the stitcher it goes for a while 
and then fails with the following Status Report. I then reloaded the original 
images as a new project, aligned the images, and got the same failure.



Stitching panorama…


Platform: Mac OS X (Darwin 15.4.0 x86_64)
Version: 2016.1.0 built by Niklas Mischkulnig
Working directory: /Users/donaldjohnston/Pictures/Panoramas/2011_03_17/Bridge
Output prefix: IMG_0809 - IMG_0826Test2016

Blender: Unknown blender (enblend —version failed)
Exposure fusion: Unknown exposure fusion (enfuse —version failed)
ExifTool: FAILED

Number of active images: 18
Output exposure value: 15.9
Canvas size: 7298x2179
ROI: (108, 190) - (7237, 1174) 
FOV: 144x43
Projection: Equirectangular(2)
Using GPU for remapping: false

Panorama Outputs:
* Exposure fused from stacks

First input image
Number: 0
Filename: 
/Users/donaldjohnston/Pictures/Panoramas/2011_03_17/Bridge/IMG_0809.JPG
Size: 2592x1728
Projection: Normal (rectilinear)
Response type: custom (EMoR)
HFOV: 34
Exposure value: 16.0


Remapping LDR images without exposure correction…
Multiple images output
loading IMG_0809.JPG
remapping IMG_0809.JPG
saving IMG_0809 - IMG_0826Test2016_exposure_layers_.tif
loading IMG_0810.JPG
remapping IMG_0810.JPG
saving IMG_0809 - IMG_0826Test2016_exposure_layers_0001.tif
loading IMG_0811.JPG
remapping IMG_0811.JPG
saving IMG_0809 - IMG_0826Test2016_exposure_layers_0002.tif
loading IMG_0812.JPG
remapping IMG_0812.JPG
saving IMG_0809 - IMG_0826Test2016_exposure_layers_0003.tif
loading IMG_0813.JPG
remapping IMG_0813.JPG
saving IMG_0809 - IMG_0826Test2016_exposure_layers_0004.tif
loading IMG_0814.JPG
remapping IMG_0814.JPG
saving IMG_0809 - IMG_0826Test2016_exposure_layers_0005.tif
loading IMG_0815.JPG
remapping IMG_0815.JPG
saving IMG_0809 - IMG_0826Test2016_exposure_layers_0006.tif
loading IMG_0816.JPG
remapping IMG_0816.JPG
saving IMG_0809 - IMG_0826Test2016_exposure_layers_0007.tif
loading IMG_0817.JPG
remapping IMG_0817.JPG
saving IMG_0809 - IMG_0826Test2016_exposure_layers_0008.tif
loading IMG_0818.JPG
remapping IMG_0818.JPG
saving IMG_0809 - IMG_0826Test2016_exposure_layers_0009.tif
loading IMG_0819.JPG
remapping IMG_0819.JPG
saving IMG_0809 - IMG_0826Test2016_exposure_layers_0010.tif
loading IMG_0820.JPG
remapping IMG_0820.JPG
saving IMG_0809 - IMG_0826Test2016_exposure_layers_0011.tif
loading IMG_0821.JPG
remapping IMG_0821.JPG
saving IMG_0809 - IMG_0826Test2016_exposure_layers_0012.tif
loading IMG_0822.JPG
remapping IMG_0822.JPG
saving IMG_0809 - IMG_0826Test2016_exposure_layers_0013.tif
loading IMG_0823.JPG
remapping IMG_0823.JPG
saving IMG_0809 - IMG_0826Test2016_exposure_layers_0014.tif
loading IMG_0824.JPG
remapping IMG_0824.JPG
saving IMG_0809 - IMG_0826Test2016_exposure_layers_0015.tif
loading IMG_0825.JPG
remapping IMG_0825.JPG
saving IMG_0809 - IMG_0826Test2016_exposure_layers_0016.tif
loading IMG_0826.JPG
remapping IMG_0826.JPG
saving IMG_0809 - IMG_0826Test2016_exposure_layers_0017.tif




On Apr 18, 2016, at 11:26 AM, Niklas Mischkulnig  wrote:
Thank you for your tips! 
Here is a new link (just being 
cautious):https://drive.google.com/uc?export=download=0B_seRjFxxDleU1YtQ1Zka1BXM2c






-- 

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 

Re: [hugin-ptx] Mac Build

[Niklas Mischkulnig]

First I thought the following: 
I looked through the code and noticed that PTBatcherGui first tries to use 
the "alternative path" and then falls back to the bundled version of 
enblend. Now I can't get it to fail to find enblend. There is no other 
reason for not finding enblend apart from it not being bundled in MacOS/ .
But then: #if defined __WXMAC__ && defined *MAC_SELF_CONTAINED_BUNDLE ; *sure 
__WXMAC__ is set but MAC_SELF_CONTAINED_BUNDLE isn't (doing that creates a 
whole lot more compile errors).  That means that it searches in path.
What's going on, especially with ExifTool, the code, which searches it, is 
quite complex?

Am Dienstag, 19. April 2016 15:27:41 UTC+2 schrieb Harry van der Wolf:

> The problem in this case is that macos is not the working directory, but 
> the directory one higher.
> The directory that contains pkginfo and Info.plist is the working folder.
> I'm not sure (as I can not test myself) that a path like ./MacOS/enblend 
> might work
>
> Harry
>
> 2016-04-19 14:13 GMT+02:00 Niklas Mischkulnig  >:
>
>> Exiftool and enblend/enfuse are in there: (both PTBatcherGUI.app and 
>> Hugin.app), see the attachments
>>
>> when enblend is called, it is exspected to be somewhere in PATH, i.e. 
>> /usr/local/bin; 
>> ./enblend , however,  searches in the current dir, next to Hugin
>> You can try that out in bash.  That is why I set enblend and enfuse to 
>> alternative paths, since I couldn't find a path to enblend and enfuse in 
>> the src. Or could Hugin change PATH ?
>>
>>
>> Am Dienstag, 19. April 2016 09:41:10 UTC+2 schrieb Harry van der Wolf:
>>>
>>> With regard to the exiftool error: In the previous builds exiftool was 
>>> also incorporated in the bundles. I assume that was forgotten for this 
>>> bundle.
>>>
>>> W.r.t. enblend and enfuse: Please check whether they are inside the 
>>> bundles. If not: then it is the same error as above. If the enblend 
>>> --version command works it means that enblend is available.
>>>
>>> If you have an external enfuse and enblend you can point hugin towards 
>>> these versions.
>>>
>>> Harry
>>>
>>> 2016-04-19 7:05 GMT+02:00 Niklas Mischkulnig :
>>>
 *I had to go into the Hugin.app settings, under programs and set 
 alternative enblend/enfuse **executables** to **./**enblend** and **./*
 *enfuse** to make **PTBatcherGui** work. *
 Am 19.04.2016 00:53 schrieb "Donald Johnston" :

> To add to this error information I did two additional tests with these 
> images.
> 1. the first three images so it was an exposure stack. All fine until 
> “Create panorama…”; same failure.
> Blender: Unknown blender (enblend —version failed)
> Exposure fusion: Unknown exposure fusion (enfuse —version failed)
> ExifTool: FAILED
>
> 2. images 1, 4, and 7; so no exposure stack just a three image pano … 
> same failure (except no enfuse failed).
> Blender: Unknown blender (enblend —version failed)
> ExifTool: FAILED
>
>
>
> On Apr 18, 2016, at 4:32 PM, Donald Johnston  
> wrote:
>
> Another error. I loaded an old project with 18 images that requires 
> exposure fusion and stitching. The project loaded fine, the preview 
> window 
> show the aligned preview as it should be.  When I ran the stitcher it 
> goes 
> for a while and then fails with the following Status Report. I then 
> reloaded the original images as a new project, aligned the images, and 
> got 
> the same failure.
>
>
>
> 
> Stitching panorama…
> 
>
> Platform: Mac OS X (Darwin 15.4.0 x86_64)
> Version: 2016.1.0 built by Niklas Mischkulnig
> Working directory: 
> /Users/donaldjohnston/Pictures/Panoramas/2011_03_17/Bridge
> Output prefix: IMG_0809 - IMG_0826Test2016
>
> Blender: Unknown blender (enblend —version failed)
> Exposure fusion: Unknown exposure fusion (enfuse —version failed)
> ExifTool: FAILED
>
> Number of active images: 18
> Output exposure value: 15.9
> Canvas size: 7298x2179
> ROI: (108, 190) - (7237, 1174) 
> FOV: 144x43
> Projection: Equirectangular(2)
> Using GPU for remapping: false
>
> Panorama Outputs:
> * Exposure fused from stacks
>
> First input image
> Number: 0
> Filename: 
> /Users/donaldjohnston/Pictures/Panoramas/2011_03_17/Bridge/IMG_0809.JPG
> Size: 2592x1728
> Projection: Normal (rectilinear)
> Response type: custom (EMoR)
> HFOV: 34
> Exposure value: 16.0
>
>
> Remapping LDR images without exposure correction…
> Multiple images output
> loading IMG_0809.JPG
> remapping IMG_0809.JPG
> saving IMG_0809 - IMG_0826Test2016_exposure_layers_.tif
> loading IMG_0810.JPG
> remapping 

Re: [hugin-ptx] Control points editor / Line detection / Projection of a single image

[Bruno Postle]

On 19 April 2016 08:53:33 BST, "David W. Jones" wrote:
>
> Now, I am one of the people who has
> always wondered why the process
> that finds vertical lines couldn't also be
> adapted to somehow find horizontal 
> lines.

It can, and the same code in the lens correct GUI tool finds lines in all 
directions.

But in Hugin, horizontal lines are rarely very useful. For a normal panorama, 
the only line that will ever be horizontal is the horizon at sea. Whereas there 
are often lots of objects that are exactly vertical and parallel.

-- 
Bruno

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/22E1F3BC-D1AE-4CA7-A44D-35B79493F575%40postle.net.
For more options, visit https://groups.google.com/d/optout.

Re: [hugin-ptx] Mac Build

[Harry van der Wolf]

The problem in this case is that macos is not the working directory, but
the directory one higher.
The directory that contains pkginfo and Info.plist is the working folder.
I'm not sure (as I can not test myself) that a path like ./MacOS/enblend
might work

Harry

2016-04-19 14:13 GMT+02:00 Niklas Mischkulnig :

> Exiftool and enblend/enfuse are in there: (both PTBatcherGUI.app and
> Hugin.app), see the attachments
>
> when enblend is called, it is exspected to be somewhere in PATH, i.e. 
> /usr/local/bin;
> ./enblend , however,  searches in the current dir, next to Hugin
> You can try that out in bash.  That is why I set enblend and enfuse to
> alternative paths, since I couldn't find a path to enblend and enfuse in
> the src. Or could Hugin change PATH ?
>
>
> Am Dienstag, 19. April 2016 09:41:10 UTC+2 schrieb Harry van der Wolf:
>>
>> With regard to the exiftool error: In the previous builds exiftool was
>> also incorporated in the bundles. I assume that was forgotten for this
>> bundle.
>>
>> W.r.t. enblend and enfuse: Please check whether they are inside the
>> bundles. If not: then it is the same error as above. If the enblend
>> --version command works it means that enblend is available.
>>
>> If you have an external enfuse and enblend you can point hugin towards
>> these versions.
>>
>> Harry
>>
>> 2016-04-19 7:05 GMT+02:00 Niklas Mischkulnig :
>>
>>> *I had to go into the Hugin.app settings, under programs and set
>>> alternative enblend/enfuse **executables** to **./**enblend** and **./*
>>> *enfuse** to make **PTBatcherGui** work. *
>>> Am 19.04.2016 00:53 schrieb "Donald Johnston" :
>>>
 To add to this error information I did two additional tests with these
 images.
 1. the first three images so it was an exposure stack. All fine until
 “Create panorama…”; same failure.
 Blender: Unknown blender (enblend —version failed)
 Exposure fusion: Unknown exposure fusion (enfuse —version failed)
 ExifTool: FAILED

 2. images 1, 4, and 7; so no exposure stack just a three image pano …
 same failure (except no enfuse failed).
 Blender: Unknown blender (enblend —version failed)
 ExifTool: FAILED



 On Apr 18, 2016, at 4:32 PM, Donald Johnston 
 wrote:

 Another error. I loaded an old project with 18 images that requires
 exposure fusion and stitching. The project loaded fine, the preview window
 show the aligned preview as it should be.  When I ran the stitcher it goes
 for a while and then fails with the following Status Report. I then
 reloaded the original images as a new project, aligned the images, and got
 the same failure.



 
 Stitching panorama…
 

 Platform: Mac OS X (Darwin 15.4.0 x86_64)
 Version: 2016.1.0 built by Niklas Mischkulnig
 Working directory:
 /Users/donaldjohnston/Pictures/Panoramas/2011_03_17/Bridge
 Output prefix: IMG_0809 - IMG_0826Test2016

 Blender: Unknown blender (enblend —version failed)
 Exposure fusion: Unknown exposure fusion (enfuse —version failed)
 ExifTool: FAILED

 Number of active images: 18
 Output exposure value: 15.9
 Canvas size: 7298x2179
 ROI: (108, 190) - (7237, 1174)
 FOV: 144x43
 Projection: Equirectangular(2)
 Using GPU for remapping: false

 Panorama Outputs:
 * Exposure fused from stacks

 First input image
 Number: 0
 Filename:
 /Users/donaldjohnston/Pictures/Panoramas/2011_03_17/Bridge/IMG_0809.JPG
 Size: 2592x1728
 Projection: Normal (rectilinear)
 Response type: custom (EMoR)
 HFOV: 34
 Exposure value: 16.0


 Remapping LDR images without exposure correction…
 Multiple images output
 loading IMG_0809.JPG
 remapping IMG_0809.JPG
 saving IMG_0809 - IMG_0826Test2016_exposure_layers_.tif
 loading IMG_0810.JPG
 remapping IMG_0810.JPG
 saving IMG_0809 - IMG_0826Test2016_exposure_layers_0001.tif
 loading IMG_0811.JPG
 remapping IMG_0811.JPG
 saving IMG_0809 - IMG_0826Test2016_exposure_layers_0002.tif
 loading IMG_0812.JPG
 remapping IMG_0812.JPG
 saving IMG_0809 - IMG_0826Test2016_exposure_layers_0003.tif
 loading IMG_0813.JPG
 remapping IMG_0813.JPG
 saving IMG_0809 - IMG_0826Test2016_exposure_layers_0004.tif
 loading IMG_0814.JPG
 remapping IMG_0814.JPG
 saving IMG_0809 - IMG_0826Test2016_exposure_layers_0005.tif
 loading IMG_0815.JPG
 remapping IMG_0815.JPG
 saving IMG_0809 - IMG_0826Test2016_exposure_layers_0006.tif
 loading IMG_0816.JPG
 remapping IMG_0816.JPG
 saving IMG_0809 - IMG_0826Test2016_exposure_layers_0007.tif
 loading IMG_0817.JPG
 remapping IMG_0817.JPG
 saving IMG_0809 - 

Re: [hugin-ptx] Mac Build

[Niklas Mischkulnig]

Exiftool and enblend/enfuse are in there: (both PTBatcherGUI.app and 
Hugin.app), see the attachments

when enblend is called, it is exspected to be somewhere in PATH, i.e. 
/usr/local/bin; 
./enblend , however,  searches in the current dir, next to Hugin
You can try that out in bash.  That is why I set enblend and enfuse to 
alternative paths, since I couldn't find a path to enblend and enfuse in 
the src. Or could Hugin change PATH ?


Am Dienstag, 19. April 2016 09:41:10 UTC+2 schrieb Harry van der Wolf:
>
> With regard to the exiftool error: In the previous builds exiftool was 
> also incorporated in the bundles. I assume that was forgotten for this 
> bundle.
>
> W.r.t. enblend and enfuse: Please check whether they are inside the 
> bundles. If not: then it is the same error as above. If the enblend 
> --version command works it means that enblend is available.
>
> If you have an external enfuse and enblend you can point hugin towards 
> these versions.
>
> Harry
>
> 2016-04-19 7:05 GMT+02:00 Niklas Mischkulnig  >:
>
>> *I had to go into the Hugin.app settings, under programs and set 
>> alternative enblend/enfuse **executables** to **./**enblend** and **./*
>> *enfuse** to make **PTBatcherGui** work. *
>> Am 19.04.2016 00:53 schrieb "Donald Johnston" > >:
>>
>>> To add to this error information I did two additional tests with these 
>>> images.
>>> 1. the first three images so it was an exposure stack. All fine until 
>>> “Create panorama…”; same failure.
>>> Blender: Unknown blender (enblend —version failed)
>>> Exposure fusion: Unknown exposure fusion (enfuse —version failed)
>>> ExifTool: FAILED
>>>
>>> 2. images 1, 4, and 7; so no exposure stack just a three image pano … 
>>> same failure (except no enfuse failed).
>>> Blender: Unknown blender (enblend —version failed)
>>> ExifTool: FAILED
>>>
>>>
>>>
>>> On Apr 18, 2016, at 4:32 PM, Donald Johnston >> > wrote:
>>>
>>> Another error. I loaded an old project with 18 images that requires 
>>> exposure fusion and stitching. The project loaded fine, the preview window 
>>> show the aligned preview as it should be.  When I ran the stitcher it goes 
>>> for a while and then fails with the following Status Report. I then 
>>> reloaded the original images as a new project, aligned the images, and got 
>>> the same failure.
>>>
>>>
>>>
>>> 
>>> Stitching panorama…
>>> 
>>>
>>> Platform: Mac OS X (Darwin 15.4.0 x86_64)
>>> Version: 2016.1.0 built by Niklas Mischkulnig
>>> Working directory: 
>>> /Users/donaldjohnston/Pictures/Panoramas/2011_03_17/Bridge
>>> Output prefix: IMG_0809 - IMG_0826Test2016
>>>
>>> Blender: Unknown blender (enblend —version failed)
>>> Exposure fusion: Unknown exposure fusion (enfuse —version failed)
>>> ExifTool: FAILED
>>>
>>> Number of active images: 18
>>> Output exposure value: 15.9
>>> Canvas size: 7298x2179
>>> ROI: (108, 190) - (7237, 1174) 
>>> FOV: 144x43
>>> Projection: Equirectangular(2)
>>> Using GPU for remapping: false
>>>
>>> Panorama Outputs:
>>> * Exposure fused from stacks
>>>
>>> First input image
>>> Number: 0
>>> Filename: 
>>> /Users/donaldjohnston/Pictures/Panoramas/2011_03_17/Bridge/IMG_0809.JPG
>>> Size: 2592x1728
>>> Projection: Normal (rectilinear)
>>> Response type: custom (EMoR)
>>> HFOV: 34
>>> Exposure value: 16.0
>>>
>>>
>>> Remapping LDR images without exposure correction…
>>> Multiple images output
>>> loading IMG_0809.JPG
>>> remapping IMG_0809.JPG
>>> saving IMG_0809 - IMG_0826Test2016_exposure_layers_.tif
>>> loading IMG_0810.JPG
>>> remapping IMG_0810.JPG
>>> saving IMG_0809 - IMG_0826Test2016_exposure_layers_0001.tif
>>> loading IMG_0811.JPG
>>> remapping IMG_0811.JPG
>>> saving IMG_0809 - IMG_0826Test2016_exposure_layers_0002.tif
>>> loading IMG_0812.JPG
>>> remapping IMG_0812.JPG
>>> saving IMG_0809 - IMG_0826Test2016_exposure_layers_0003.tif
>>> loading IMG_0813.JPG
>>> remapping IMG_0813.JPG
>>> saving IMG_0809 - IMG_0826Test2016_exposure_layers_0004.tif
>>> loading IMG_0814.JPG
>>> remapping IMG_0814.JPG
>>> saving IMG_0809 - IMG_0826Test2016_exposure_layers_0005.tif
>>> loading IMG_0815.JPG
>>> remapping IMG_0815.JPG
>>> saving IMG_0809 - IMG_0826Test2016_exposure_layers_0006.tif
>>> loading IMG_0816.JPG
>>> remapping IMG_0816.JPG
>>> saving IMG_0809 - IMG_0826Test2016_exposure_layers_0007.tif
>>> loading IMG_0817.JPG
>>> remapping IMG_0817.JPG
>>> saving IMG_0809 - IMG_0826Test2016_exposure_layers_0008.tif
>>> loading IMG_0818.JPG
>>> remapping IMG_0818.JPG
>>> saving IMG_0809 - IMG_0826Test2016_exposure_layers_0009.tif
>>> loading IMG_0819.JPG
>>> remapping IMG_0819.JPG
>>> saving IMG_0809 - IMG_0826Test2016_exposure_layers_0010.tif
>>> loading IMG_0820.JPG
>>> remapping IMG_0820.JPG
>>> saving IMG_0809 - IMG_0826Test2016_exposure_layers_0011.tif
>>> loading IMG_0821.JPG
>>> remapping IMG_0821.JPG
>>> saving IMG_0809 

Re: [hugin-ptx] Control points editor / Line detection / Projection of a single image

[David W. Jones]

On 04/18/2016 05:39 PM, Abrimaal wrote:

*Build 2016: *

The line find routine detects horizontal lines in the images, but they
are listed as vertical. It causes problems with straightening of panoramas.


I have the same issue. Throws my workflow off because now I have to go 
to the list of control points, sort them by type, then delete the 
horizontal lines that show large errors. And when I look at them in the 
images, some of them are clearly horizontal lines, not vertical lines at 
all. Also, it will sometimes find extremely short vertical lines, like 
lines only a few pixels long.


2015 build didn't have these problems.

Now, I am one of the people who has always wondered why the process that 
finds vertical lines couldn't also be adapted to somehow find horizontal 
lines. (Conceptually, just rotate the image in memory, run the 
'vertical' line find; mark those found lines as 'horizontal' lines, then 
rotate image back if needed for continued processing.) Is the new 
linefind also searching for horizontal lines? If so, it's not nmaking 
the horizontal lines it finds into horizontal lines.


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

--
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/5715E3FD.3030900%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [hugin-ptx] Mac Build

[Harry van der Wolf]

With regard to the exiftool error: In the previous builds exiftool was also
incorporated in the bundles. I assume that was forgotten for this bundle.

W.r.t. enblend and enfuse: Please check whether they are inside the
bundles. If not: then it is the same error as above. If the enblend
--version command works it means that enblend is available.

If you have an external enfuse and enblend you can point hugin towards
these versions.

Harry

2016-04-19 7:05 GMT+02:00 Niklas Mischkulnig :

> *I had to go into the Hugin.app settings, under programs and set
> alternative enblend/enfuse **executables** to **./**enblend** and **./*
> *enfuse** to make **PTBatcherGui** work. *
> Am 19.04.2016 00:53 schrieb "Donald Johnston" :
>
>> To add to this error information I did two additional tests with these
>> images.
>> 1. the first three images so it was an exposure stack. All fine until
>> “Create panorama…”; same failure.
>> Blender: Unknown blender (enblend —version failed)
>> Exposure fusion: Unknown exposure fusion (enfuse —version failed)
>> ExifTool: FAILED
>>
>> 2. images 1, 4, and 7; so no exposure stack just a three image pano …
>> same failure (except no enfuse failed).
>> Blender: Unknown blender (enblend —version failed)
>> ExifTool: FAILED
>>
>>
>>
>> On Apr 18, 2016, at 4:32 PM, Donald Johnston 
>> wrote:
>>
>> Another error. I loaded an old project with 18 images that requires
>> exposure fusion and stitching. The project loaded fine, the preview window
>> show the aligned preview as it should be.  When I ran the stitcher it goes
>> for a while and then fails with the following Status Report. I then
>> reloaded the original images as a new project, aligned the images, and got
>> the same failure.
>>
>>
>>
>> 
>> Stitching panorama…
>> 
>>
>> Platform: Mac OS X (Darwin 15.4.0 x86_64)
>> Version: 2016.1.0 built by Niklas Mischkulnig
>> Working directory:
>> /Users/donaldjohnston/Pictures/Panoramas/2011_03_17/Bridge
>> Output prefix: IMG_0809 - IMG_0826Test2016
>>
>> Blender: Unknown blender (enblend —version failed)
>> Exposure fusion: Unknown exposure fusion (enfuse —version failed)
>> ExifTool: FAILED
>>
>> Number of active images: 18
>> Output exposure value: 15.9
>> Canvas size: 7298x2179
>> ROI: (108, 190) - (7237, 1174)
>> FOV: 144x43
>> Projection: Equirectangular(2)
>> Using GPU for remapping: false
>>
>> Panorama Outputs:
>> * Exposure fused from stacks
>>
>> First input image
>> Number: 0
>> Filename:
>> /Users/donaldjohnston/Pictures/Panoramas/2011_03_17/Bridge/IMG_0809.JPG
>> Size: 2592x1728
>> Projection: Normal (rectilinear)
>> Response type: custom (EMoR)
>> HFOV: 34
>> Exposure value: 16.0
>>
>>
>> Remapping LDR images without exposure correction…
>> Multiple images output
>> loading IMG_0809.JPG
>> remapping IMG_0809.JPG
>> saving IMG_0809 - IMG_0826Test2016_exposure_layers_.tif
>> loading IMG_0810.JPG
>> remapping IMG_0810.JPG
>> saving IMG_0809 - IMG_0826Test2016_exposure_layers_0001.tif
>> loading IMG_0811.JPG
>> remapping IMG_0811.JPG
>> saving IMG_0809 - IMG_0826Test2016_exposure_layers_0002.tif
>> loading IMG_0812.JPG
>> remapping IMG_0812.JPG
>> saving IMG_0809 - IMG_0826Test2016_exposure_layers_0003.tif
>> loading IMG_0813.JPG
>> remapping IMG_0813.JPG
>> saving IMG_0809 - IMG_0826Test2016_exposure_layers_0004.tif
>> loading IMG_0814.JPG
>> remapping IMG_0814.JPG
>> saving IMG_0809 - IMG_0826Test2016_exposure_layers_0005.tif
>> loading IMG_0815.JPG
>> remapping IMG_0815.JPG
>> saving IMG_0809 - IMG_0826Test2016_exposure_layers_0006.tif
>> loading IMG_0816.JPG
>> remapping IMG_0816.JPG
>> saving IMG_0809 - IMG_0826Test2016_exposure_layers_0007.tif
>> loading IMG_0817.JPG
>> remapping IMG_0817.JPG
>> saving IMG_0809 - IMG_0826Test2016_exposure_layers_0008.tif
>> loading IMG_0818.JPG
>> remapping IMG_0818.JPG
>> saving IMG_0809 - IMG_0826Test2016_exposure_layers_0009.tif
>> loading IMG_0819.JPG
>> remapping IMG_0819.JPG
>> saving IMG_0809 - IMG_0826Test2016_exposure_layers_0010.tif
>> loading IMG_0820.JPG
>> remapping IMG_0820.JPG
>> saving IMG_0809 - IMG_0826Test2016_exposure_layers_0011.tif
>> loading IMG_0821.JPG
>> remapping IMG_0821.JPG
>> saving IMG_0809 - IMG_0826Test2016_exposure_layers_0012.tif
>> loading IMG_0822.JPG
>> remapping IMG_0822.JPG
>> saving IMG_0809 - IMG_0826Test2016_exposure_layers_0013.tif
>> loading IMG_0823.JPG
>> remapping IMG_0823.JPG
>> saving IMG_0809 - IMG_0826Test2016_exposure_layers_0014.tif
>> loading IMG_0824.JPG
>> remapping IMG_0824.JPG
>> saving IMG_0809 - IMG_0826Test2016_exposure_layers_0015.tif
>> loading IMG_0825.JPG
>> remapping IMG_0825.JPG
>> saving IMG_0809 - IMG_0826Test2016_exposure_layers_0016.tif
>> loading IMG_0826.JPG
>> remapping IMG_0826.JPG
>> saving IMG_0809 - IMG_0826Test2016_exposure_layers_0017.tif
>>
>>
>>
>>
>> On Apr 18, 2016, at 11:26 AM, Niklas Mischkulnig