Re: [hugin-ptx] Mac Build

2016-06-03 Thread Alexandr Krylovskiy
Trying the mentioned 2016.2 beta 1 release, everything related to my 
use (defishing) seems to work, but I'm getting an issue with Hugin and 
PTBatcherGUI in the OS X docker.
after the stitching process is finished and I close the PTBatcherGUI window 
/ exit Hugin, the PTBatcherGUI icon *always* remains in the OS X docker.
Sometimes if I close the Hugin it's icon also remains stuck in docker (see 
below), while the process is already finished. 

Sorry if this have already been reported and thanks again for the great 
work.

After processing a few images I'm basically getting something like this:



On Thursday, June 2, 2016 at 4:54:24 PM UTC+2, Niklas Mischkulnig wrote:
>
> I see you are working with the mac build, but just to know 
>> is there a version we can try ? 
>
>
> See the "Hugin 2016.2 beta 1 released" thread.
>
> Niklas
>

-- 
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/560201f2-6f2b-4b94-a5d9-cde3477ce72c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [hugin-ptx] Mac Build

2016-06-02 Thread Niklas Mischkulnig

>
> I see you are working with the mac build, but just to know 
> is there a version we can try ? 


See the "Hugin 2016.2 beta 1 released" thread.

Niklas

-- 
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/f130b3d6-2ad8-4390-b571-2a1d7ef23209%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [hugin-ptx] Mac Build

2016-06-01 Thread Claudio Soprano

I see you are working with the mac build, but just to know

is there a version we can try ?

Thanks in advance
Claudio

On 18/05/16 15:53, Niklas Mischkulnig wrote:

If you downloaded the zip sometime after my last post, then you already got the 
fixed version.

Niklas



--
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/574F091A.1000701%40lnf.infn.it.
For more options, visit https://groups.google.com/d/optout.


Re: [hugin-ptx] Mac Build

2016-05-31 Thread Niklas Mischkulnig


> Niklas, for the Mac Build are you planning to compile enblend and enfuse 
for multiprocessing support?

Yes.

> I notice that enblend and enfuse are in PTBatcherGUI now and before were 
in Hugin (if my memory serves me correct). Does that make a difference?

Yes,  they are only used by PTBatcherGui and StitchProject, not by Hugin 
itself.

Niklas



Am Montag, 30. Mai 2016 06:15:47 UTC+2 schrieb Donald Johnston:
>
> Niklas, for the Mac Build are you planning to compile enblend and enfuse 
> for multiprocessing support?
> When I check the version verbose I get:
> Extra feature: OpenMP: no
>
> I notice that enblend and enfuse are in PTBatcherGUI now and before were 
> in Hugin (if my memory serves me correct). Does that make a difference?
>
>

-- 
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/dbae3232-9f32-487c-a82f-aaa6fa66292b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [hugin-ptx] Mac Build

2016-05-30 Thread Niklas Mischkulnig
Am 30.05.2016 06:15 schrieb "Donald Johnston" :
>
> Niklas, for the Mac Build are you planning to compile enblend and enfuse
for multiprocessing support?

I'll look into that.

> I notice that enblend and enfuse are in PTBatcherGUI now and before were
in Hugin (if my memory serves me correct). Does that make a difference?

Yes,  they are only used by PTBatcherGui and StitchProject, not by Hugin
itself.

Niklas

-- 
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/CACd%3DvwCfKDOFNgj6A-4%2BhQ3O4z8La%3DmW5mh920-0Y2Z_xo3eiQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: [hugin-ptx] Mac Build

2016-05-21 Thread T. Modes
Hi Niklas,

Am Freitag, 20. Mai 2016 21:46:02 UTC+2 schrieb Niklas Mischkulnig:
>
> The sole error after updating to wxWidgets 3.1 is that the flag 
> wxFIXED_MINSIZE doesn't exist anymore (
> http://docs.wxwidgets.org/trunk/classwx_sizer.html).
>

Fixed in repository. 

>
> If I simply remove it, the text "Images are connected by * control points" 
> doesn't get a linebreak but runs off the window; 
>
I have not yet a good idea. Maybe the disabling auto resizing of the 
wxStaticBox helps (done in repository). Otherwise this is specific to 
wxMac, because here I get correctly line breaks with wxWidgets 3.1.
(You could try the widgets samples in wxWidgets if the linebreaks works 
here. So we can check if this is a wxWidgets issue or a issue in Hugin.)
 

> the warning about changing to another project has stripes and 
>
Seems to be a change of formatting/drawing of wxInfoBar in wxWidgets 3.1
 

> the background next to the area with the pano-preview is white instead of 
> grey.
>
We are using wxSystemSettings::GetColour() to retrieve the color from the 
system (src/hugin1/hugin/GLViewer.cpp, line 389)
wxColour col = wxSystemSettings::GetColour(wxSYS_COLOUR_APPWORKSPACE);
AFAIR the color settings for Mac OS changed in wxWidgets 3.1 (see 
http://trac.wxwidgets.org/ticket/17141 )
Propose another enum value which is more suitable for Mac OS (from 
http://docs.wxwidgets.org/3.1.0/settings_8h.html#a44ad26cbd8d579d1b7eff7015c8bd24b
 
)

Thomas

-- 
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/84428695-ddc4-4274-bfc3-a70f9255a651%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [hugin-ptx] Mac Build

2016-05-20 Thread Niklas Mischkulnig
Hi Thomas,

I can just update to wxWidgets 3.1. No big deal.

Niklas

Am Freitag, 20. Mai 2016 19:40:12 UTC+2 schrieb T. Modes:
>
> Hi Niklas,
>
> Am Freitag, 20. Mai 2016 17:56:39 UTC+2 schrieb Niklas Mischkulnig:
>>
>> Hi Thomas, 
>>
>> I thought of adding a override as well (it compiles), but it doesn't 
>> with wxOVERRIDE.
>>
>
> I forgot: wxOVERRIDE was introduced in wxWidgets 3.1. So it does not work 
> with 3.0. I drop the wxOVERRIDE Sorry for the disturbance.
>  
>
>> WxWidgets docs say one should include , but even then 
>> wxOVERRIDE isn't defined. There is not a single
>> occurence of wxOVERRIDE in any header in include/wx-3.0/wx , 
>>
>
> You look probably in the doc of wxWidgets 3.1 or trunk. There it is used.
>  
>
>> but it shouldn't cause a compile-time error?
>>
>> src/hugin1/ptbatcher/PTBatcherGUI.h:112:54: error: expected ';' at end of 
>> declaration list
>> void MacOpenFiles(const wxArrayString ) wxOVERRIDE;
>>
>
> When wxOVERRIDE is not define then the compiler has no idea what to do 
> with this part and barfs.
>
> Thomas
>
>

-- 
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/99ee78c0-12d6-4796-a692-09611f11e138%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [hugin-ptx] Mac Build

2016-05-20 Thread T. Modes
Hi Niklas,

Am Freitag, 20. Mai 2016 17:56:39 UTC+2 schrieb Niklas Mischkulnig:
>
> Hi Thomas, 
>
> I thought of adding a override as well (it compiles), but it doesn't 
> with wxOVERRIDE.
>

I forgot: wxOVERRIDE was introduced in wxWidgets 3.1. So it does not work 
with 3.0. I drop the wxOVERRIDE Sorry for the disturbance.
 

> WxWidgets docs say one should include , but even then 
> wxOVERRIDE isn't defined. There is not a single
> occurence of wxOVERRIDE in any header in include/wx-3.0/wx , 
>

You look probably in the doc of wxWidgets 3.1 or trunk. There it is used.
 

> but it shouldn't cause a compile-time error?
>
> src/hugin1/ptbatcher/PTBatcherGUI.h:112:54: error: expected ';' at end of 
> declaration list
> void MacOpenFiles(const wxArrayString ) wxOVERRIDE;
>

When wxOVERRIDE is not define then the compiler has no idea what to do with 
this part and barfs.

Thomas

-- 
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/97b4961a-83da-4a82-a1ec-ba742d5f8eca%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [hugin-ptx] Mac Build

2016-05-20 Thread Niklas Mischkulnig
Hi Thomas, 

I thought of adding a override as well (it compiles), but it doesn't 
with wxOVERRIDE.
WxWidgets docs say one should include , but even then wxOVERRIDE 
isn't defined. There is not a single
occurence of wxOVERRIDE in any header in include/wx-3.0/wx , but it 
shouldn't cause a compile-time error?

src/hugin1/ptbatcher/PTBatcherGUI.h:112:54: error: expected ';' at end of 
declaration list
void MacOpenFiles(const wxArrayString ) wxOVERRIDE;

Niklas

Am Freitag, 20. Mai 2016 17:27:32 UTC+2 schrieb T. Modes:
>
> Hi Niklas,
>
> Am Donnerstag, 19. Mai 2016 21:38:49 UTC+2 schrieb Niklas Mischkulnig:
>>
>> this should fix the duplicate projects.
>>
>
> Thanks for your patches. I committed both to the repository.
> The DuplicatePT.patch needed some massage. You have used 
> m_macFileNameToOpenOnStart also in the general part, but on Windows and 
> Unix this variable is not defined.
> So I moved the if statement before. Hopefully this works for you.
>
> Thomas
>
>

-- 
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/fda7e900-ea7b-4461-a09b-a42540a0e571%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [hugin-ptx] Mac Build

2016-05-20 Thread T. Modes
Hi Niklas,

Am Donnerstag, 19. Mai 2016 21:38:49 UTC+2 schrieb Niklas Mischkulnig:
>
> this should fix the duplicate projects.
>

Thanks for your patches. I committed both to the repository.
The DuplicatePT.patch needed some massage. You have used 
m_macFileNameToOpenOnStart also in the general part, but on Windows and 
Unix this variable is not defined.
So I moved the if statement before. Hopefully this works for you.

Thomas

-- 
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/c82e6ea5-c3c9-408a-ae3a-8a29beeebf6b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [hugin-ptx] Mac Build

2016-05-19 Thread Niklas Mischkulnig

Now PTBatcherGUI can open multiple files via the Finder.

Addition to the last post: If you find a better solution for the if 
condition, go ahead; adding yet another if statement around the inner if 
would make it
ever more unreadable.

Niklas

Am Donnerstag, 19. Mai 2016 21:38:49 UTC+2 schrieb Niklas Mischkulnig:
>
> Hi Thomas,
>
> this should fix the duplicate projects.
> If there is already a project in the queue the last time PTBatcher was 
> opened and Hugin adds a new one, then it starts to process immediately.
> If I add a second project via the finder, it doesn't do that.
>
> Niklas
>
>
> Am Donnerstag, 19. Mai 2016 20:28:36 UTC+2 schrieb T. Modes:
>>
>> Hi Niklas,
>>
>> Am Donnerstag, 19. Mai 2016 20:01:08 UTC+2 schrieb Niklas Mischkulnig:
>>>
>>>
>>> When Hugin called PTBatcher, it swapped the prefix and the project file. 
>>> PTBatcher tried to open the prefix and to save to the project file. See 
>>> Patch at 
>>> Working on the doubled project in PTBatcher...
>>>
>> Thanks. Committed the changes to PTBatcher.h|cpp and your patch to 
>> repository.
>>  
>>
>>>  
>>>
 What's the main point for you against PTBatcher (or why prefer you 
 hugin_stitch_project)?

>>> If there is only one file you want to process, then hugin_stitch_project 
>>> would be better. But if there are several files 
>>> then of course PTBatcher. This isn't much of a problem for the end user. 
>>> Just tell him to open it manually via the file chooser.
>>>
>>
>> Thanks for explanation.
>>
>> Thomas
>>
>

-- 
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/ef093bc6-70ca-4e75-b17c-6fe16c620f38%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
diff --git a/src/hugin1/ptbatcher/PTBatcherGUI.cpp b/src/hugin1/ptbatcher/PTBatcherGUI.cpp
--- a/src/hugin1/ptbatcher/PTBatcherGUI.cpp
+++ b/src/hugin1/ptbatcher/PTBatcherGUI.cpp
@@ -441,17 +443,19 @@
 }
 
 #ifdef __WXMAC__
-void PTBatcherGUI::MacOpenFile(const wxString& fileName)
+void PTBatcherGUI::MacOpenFiles(const wxArrayString )
 {
 if(!m_frame)
 {
-m_macFileNameToOpenOnStart = fileName;
+//fallback, shouldn't happen
+m_macFileNameToOpenOnStart = fileNames[0];
 }
 else
-{
-wxFileName fn(fileName);
-m_frame->AddToList(fn.GetFullPath());
+{   
+for(int i = 0; i < fileNames.GetCount(); i++){
+wxFileName fn(fileNames[i]);
+m_frame->AddToList(fn.GetFullPath());
+}
 }
 }
 #endif
diff --git a/src/hugin1/ptbatcher/PTBatcherGUI.h b/src/hugin1/ptbatcher/PTBatcherGUI.h
--- a/src/hugin1/ptbatcher/PTBatcherGUI.h
+++ b/src/hugin1/ptbatcher/PTBatcherGUI.h
@@ -107,7 +107,7 @@
 
 #ifdef __WXMAC__
 /** the wx calls this method when the app gets "Open file" AppleEvent */
- void MacOpenFile(const wxString& fileName);
+void MacOpenFiles(const wxArrayString );
 #endif
 
 private:


Re: [hugin-ptx] Mac Build

2016-05-19 Thread Niklas Mischkulnig
Hi Thomas,

this should fix the duplicate projects.
If there is already a project in the queue the last time PTBatcher was 
opened and Hugin adds a new one, then it starts to process immediately.
If I add a second project via the finder, it doesn't do that.

Niklas


Am Donnerstag, 19. Mai 2016 20:28:36 UTC+2 schrieb T. Modes:
>
> Hi Niklas,
>
> Am Donnerstag, 19. Mai 2016 20:01:08 UTC+2 schrieb Niklas Mischkulnig:
>>
>>
>> When Hugin called PTBatcher, it swapped the prefix and the project file. 
>> PTBatcher tried to open the prefix and to save to the project file. See 
>> Patch at 
>> Working on the doubled project in PTBatcher...
>>
> Thanks. Committed the changes to PTBatcher.h|cpp and your patch to 
> repository.
>  
>
>>  
>>
>>> What's the main point for you against PTBatcher (or why prefer you 
>>> hugin_stitch_project)?
>>>
>> If there is only one file you want to process, then hugin_stitch_project 
>> would be better. But if there are several files 
>> then of course PTBatcher. This isn't much of a problem for the end user. 
>> Just tell him to open it manually via the file chooser.
>>
>
> Thanks for explanation.
>
> Thomas
>

-- 
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/1ef2f1f0-cac8-4358-ab5e-a8f1156f6458%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
diff --git a/src/hugin1/ptbatcher/PTBatcherGUI.cpp b/src/hugin1/ptbatcher/PTBatcherGUI.cpp
--- a/src/hugin1/ptbatcher/PTBatcherGUI.cpp
+++ b/src/hugin1/ptbatcher/PTBatcherGUI.cpp
@@ -220,10 +220,23 @@
 return false;
 }
 };
+
+
+#ifdef __WXMAC__
+// see PTBatcherGUI::MacOpenFile for explanation
+m_macFileNameToOpenOnStart = wxT("");
+wxYield();
+if(m_macFileNameToOpenOnStart != wxT(""))
+{
+wxFileName fn(m_macFileNameToOpenOnStart);
+m_frame->AddToList(fn.GetFullPath());
+}
+#endif
+
 //m_frame->SetLocaleAndXRC(_locale,m_xrcPrefix);
 //projectsRunning=0;
 unsigned int count = 0;
-if(parser.Found(wxT("a")))
+if(parser.Found(wxT("a")) && !m_macFileNameToOpenOnStart.IsEmpty())
 {
 //added assistant files
 while(parser.GetParamCount()>count)
@@ -249,7 +262,7 @@
 };
 };
 }
-else
+else if(!m_macFileNameToOpenOnStart.IsEmpty())
 {
 bool projectSpecified = false;
 //we collect all parameters - all project files 
@@ -325,17 +338,6 @@
 }
 }
 
-#ifdef __WXMAC__
-// see PTBatcherGUI::MacOpenFile for explanation
-m_macFileNameToOpenOnStart = wxT("");
-wxYield();
-if(m_macFileNameToOpenOnStart != wxT(""))
-{
-wxFileName fn(m_macFileNameToOpenOnStart);
-m_frame->AddToList(fn.GetFullPath());
-}
-#endif
-
 if(IsFirstInstance)
 {
 wxConfigBase* config=wxConfigBase::Get();
@@ -441,7 +443,6 @@
 }
 
 #ifdef __WXMAC__
-// wx calls this method when the app gets "Open file" AppleEvent
 void PTBatcherGUI::MacOpenFile(const wxString& fileName)
 {
 if(!m_frame)


Re: [hugin-ptx] Mac Build

2016-05-19 Thread T. Modes
Hi Niklas,

Am Donnerstag, 19. Mai 2016 20:01:08 UTC+2 schrieb Niklas Mischkulnig:
>
>
> When Hugin called PTBatcher, it swapped the prefix and the project file. 
> PTBatcher tried to open the prefix and to save to the project file. See 
> Patch at 
> Working on the doubled project in PTBatcher...
>
Thanks. Committed the changes to PTBatcher.h|cpp and your patch to 
repository.
 

>  
>
>> What's the main point for you against PTBatcher (or why prefer you 
>> hugin_stitch_project)?
>>
> If there is only one file you want to process, then hugin_stitch_project 
> would be better. But if there are several files 
> then of course PTBatcher. This isn't much of a problem for the end user. 
> Just tell him to open it manually via the file chooser.
>

Thanks for explanation.

Thomas

-- 
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/1e30ef19-1343-45a2-b4a0-5e9f122e2419%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [hugin-ptx] Mac Build

2016-05-19 Thread Niklas Mischkulnig
Hi Thomas,


Am Donnerstag, 19. Mai 2016 19:03:47 UTC+2 schrieb Niklas Mischkulnig:
>>
>> if I open the file itself, it works fine. Via Hugin, it does get added 
>> twice, though not exactly (see attachment). 
>> Should I prepare a patch to open multiple files at once from finder?
>>
> Not before the problem with calling from Hugin is fixed. Maybe you can try 
> to debug it on your side?
>

When Hugin called PTBatcher, it swapped the prefix and the project file. 
PTBatcher tried to open the prefix and to save to the project file. See 
Patch at 
Working on the doubled project in PTBatcher...
 

> What's the main point for you against PTBatcher (or why prefer you 
> hugin_stitch_project)?
>
If there is only one file you want to process, then hugin_stitch_project 
would be better. But if there are several files 
then of course PTBatcher. This isn't much of a problem for the end user. 
Just tell him to open it manually via the file chooser.


Niklas

diff --git a/src/hugin1/hugin/PanoPanel.cpp b/src/hugin1/hugin/PanoPanel.cpp
--- a/src/hugin1/hugin/PanoPanel.cpp
+++ b/src/hugin1/hugin/PanoPanel.cpp
@@ -1257,7 +1257,7 @@
  //We need to call the binary from it's own bundle and not from the hugin 
bundle otherwise we get no menu as OSX assumes that the hugin bundle
  //will provide the menu
  cmd = hugin_utils::wxQuoteString(cmd);
-cmd += wxT(" 
")+switches+hugin_utils::wxQuoteFilename(projectFile)+wxT(" 
")+hugin_utils::wxQuoteFilename(dlg.GetPath());
+cmd += wxT(" 
")+switches+hugin_utils::wxQuoteFilename(dlg.GetPath())+wxT(" 
")+hugin_utils::wxQuoteFilename(projectFile);
  wxExecute(cmd);
  }
  else


-- 
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/13e2e0f5-d871-4232-8651-a54563849795%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
diff --git a/src/hugin1/hugin/PanoPanel.cpp b/src/hugin1/hugin/PanoPanel.cpp
--- a/src/hugin1/hugin/PanoPanel.cpp
+++ b/src/hugin1/hugin/PanoPanel.cpp
@@ -1257,7 +1257,7 @@
 			//We need to call the binary from it's own bundle and not from the hugin bundle otherwise we get no menu as OSX assumes that the hugin bundle
 			//will provide the menu
 			cmd = hugin_utils::wxQuoteString(cmd);
-cmd += wxT(" ")+switches+hugin_utils::wxQuoteFilename(projectFile)+wxT(" ")+hugin_utils::wxQuoteFilename(dlg.GetPath());
+cmd += wxT(" ")+switches+hugin_utils::wxQuoteFilename(dlg.GetPath())+wxT(" ")+hugin_utils::wxQuoteFilename(projectFile);
 			wxExecute(cmd);
 		}
 		else


Re: [hugin-ptx] Mac Build

2016-05-19 Thread T. Modes
Hi Niklas,

Am Donnerstag, 19. Mai 2016 19:03:47 UTC+2 schrieb Niklas Mischkulnig:
>
> if I open the file itself, it works fine. Via Hugin, it does get added 
> twice, though not exactly (see attachment). 
> Should I prepare a patch to open multiple files at once from finder?
>
Not before the problem with calling from Hugin is fixed. Maybe you can try 
to debug it on your side?

Why is stitchproject more difficult to fix (it would indeed make much more 
> sense than PTBatcherGUI)?
>
 
PTBatcherGUI is running all the time. So it's easier to react on the 
MacOpenFile. 

Hugin_stitch_project has all the logic to parse the project name and 
options in OnInit. When no project name is given it ask for the names. And 
at the end of OnInit all the parameter are feed to the window.
This flow becomes disturbed when MacOpenFile is called *after* OnInit. And 
hugin_stitch_project is a one-shot-program. It runs only once and end then. 
So it becomes more difficult to implement the MacOpenFile correctly.
Also I don't know how hugin_stitch_project works on MacOS when several 
instances are called. (PTBatcherGUI has code to handle this correctly. So 
only one instance of PTBatcherGUI is running and all other are passing 
their parameters to the one running instance.)

What's the main point for you against PTBatcher (or why prefer you 
hugin_stitch_project)?

Thomas

-- 
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/c9a22e19-ae81-4272-8c88-7bd4bc2f8131%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [hugin-ptx] Mac Build

2016-05-19 Thread Niklas Mischkulnig
Hi Thomas,

if I open the file itself, it works fine. Via Hugin, it does get added 
twice, though not exactly (see attachment). 
Should I prepare a patch to open multiple files at once from finder?

Why is stitchproject more difficult to fix (it would indeed make much more 
sense than PTBatcherGUI)?

Niklas

Am Donnerstag, 19. Mai 2016 18:39:16 UTC+2 schrieb T. Modes:
>
> Hi Niklas,
>
> Am Donnerstag, 19. Mai 2016 18:19:41 UTC+2 schrieb Niklas Mischkulnig:
>>
>> Am Donnerstag, 19. Mai 2016 18:00:18 UTC+2 schrieb T. Modes:
>>>
>>> Am Mittwoch, 18. Mai 2016 20:55:31 UTC+2 schrieb Niklas Mischkulnig:

 The problem with HuginStitchProject is that MacOpenFile gets called 
 AFTER the variable is checked and the file chooser dialog opens and you 
 having to open a project file. So sometime after it has already started 
 processing the manually specified project file.

>>>
>>> Okay, that is explaining it.
>>>
>>  
>> If I comment out the line where the stitching starts (
>> frame->StitchProject(scriptFile...), and do a sleep(5) to keep the 
>> window from closing then it doesn't get called AT ALL (even with wxYield() 
>> in a while loop). And I can't debug using cout since I can't open a file 
>> "in the foreground". The only possibility is via wxMessageBox.
>>
>
> I had an additional look. It may be easier to make PTBatcherGUI to react 
> on apple file open event than to fix hugin_stitch_project (even it you 
> would prefer the latter one).
> PTBatcherGUI has already code to handle the mac events. But it is 
> commented out. The comment mentions a bug in wxWidgets 2.9.3. Maybe the bug 
> has been fixed upstreams.
> Could you test this?
> You need to edit src/hugin1/ptbatcher/PTBatcherGUI.h and .cpp
>
> In PTBatcherGUI.h, decomment line 111 (remove //): 
> void MacOpenFile(const wxString& fileName);
> in PTBatcherGUI.cpp, you need to edit 2 places: line 329 and 443
> change
> #if 0 //ifdef __WXMAC__
> to
> #ifdef __WXMAC__
>
> After this recompile and test. Please test from inside Hugin and from 
> finder? if it still works.
> To comment mentions that with wxWidgets 2.9.3 a project gets added twice. 
> To have a look on the batch queue that the project file is only added once.
>
> Thomas
>
>

-- 
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/024b55ad-1398-4f84-bd9a-4dcd6ddde76d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [hugin-ptx] Mac Build

2016-05-19 Thread T. Modes
Hi Niklas,

Am Donnerstag, 19. Mai 2016 18:19:41 UTC+2 schrieb Niklas Mischkulnig:
>
> Am Donnerstag, 19. Mai 2016 18:00:18 UTC+2 schrieb T. Modes:
>>
>> Am Mittwoch, 18. Mai 2016 20:55:31 UTC+2 schrieb Niklas Mischkulnig:
>>>
>>> The problem with HuginStitchProject is that MacOpenFile gets called 
>>> AFTER the variable is checked and the file chooser dialog opens and you 
>>> having to open a project file. So sometime after it has already started 
>>> processing the manually specified project file.
>>>
>>
>> Okay, that is explaining it.
>>
>  
> If I comment out the line where the stitching starts (
> frame->StitchProject(scriptFile...), and do a sleep(5) to keep the window 
> from closing then it doesn't get called AT ALL (even with wxYield() in a 
> while loop). And I can't debug using cout since I can't open a file "in the 
> foreground". The only possibility is via wxMessageBox.
>

I had an additional look. It may be easier to make PTBatcherGUI to react on 
apple file open event than to fix hugin_stitch_project (even it you would 
prefer the latter one).
PTBatcherGUI has already code to handle the mac events. But it is commented 
out. The comment mentions a bug in wxWidgets 2.9.3. Maybe the bug has been 
fixed upstreams.
Could you test this?
You need to edit src/hugin1/ptbatcher/PTBatcherGUI.h and .cpp

In PTBatcherGUI.h, decomment line 111 (remove //): 
void MacOpenFile(const wxString& fileName);
in PTBatcherGUI.cpp, you need to edit 2 places: line 329 and 443
change
#if 0 //ifdef __WXMAC__
to
#ifdef __WXMAC__

After this recompile and test. Please test from inside Hugin and from 
finder? if it still works.
To comment mentions that with wxWidgets 2.9.3 a project gets added twice. 
To have a look on the batch queue that the project file is only added once.

Thomas

-- 
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/4a5e2a62-3280-40d4-a13d-85b7408b2a48%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [hugin-ptx] Mac Build

2016-05-19 Thread Niklas Mischkulnig
Hi Thomas,

Am Donnerstag, 19. Mai 2016 18:00:18 UTC+2 schrieb T. Modes:
>
> Am Mittwoch, 18. Mai 2016 20:55:31 UTC+2 schrieb Niklas Mischkulnig:
>>
>> The problem with HuginStitchProject is that MacOpenFile gets called AFTER 
>> the variable is checked and the file chooser dialog opens and you having to 
>> open a project file. So sometime after it has already started processing 
>> the manually specified project file.
>>
>
> Okay, that is explaining it.
>
 
If I comment out the line where the stitching starts (
frame->StitchProject(scriptFile...), and do a sleep(5) to keep the window 
from closing then it doesn't get called AT ALL (even with wxYield() in a 
while loop). And I can't debug using cout since I can't open a file "in the 
foreground". The only possibility is via wxMessageBox.

Could you please save the specified output prefix in Hugin to file, 
>> currently it gets validated and then discarded (PanoPanel.cpp:1091). 
>>
>
> That does not fit into current infrastructure and would require some more 
> changes.
> But I can offer you the opposite. With the latest changes you can write 
> the project name into the metadata of the output image file. 
> You need to configure your exiftool arg file in the preferences to do this.
>
 
Sorry, mistake on my side. Hugin asks only for a prefix if you wanted to 
stitch the panorama and then forwards that to PTBatcher.  
I thought it asks also if you only saved the project.

Niklas
 

> Thomas
>

-- 
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/363b9b7b--426f-b6fb-4008a06d92e4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [hugin-ptx] Mac Build

2016-05-19 Thread T. Modes
Hi Niklas,

Am Mittwoch, 18. Mai 2016 20:55:31 UTC+2 schrieb Niklas Mischkulnig:
>
> The problem with HuginStitchProject is that MacOpenFile gets called AFTER 
> the variable is checked and the file chooser dialog opens and you having to 
> open a project file. So sometime after it has already started processing 
> the manually specified project file.
>

Okay, that is explaining it.
 

> Could you please save the specified output prefix in Hugin to file, 
> currently it gets validated and then discarded (PanoPanel.cpp:1091). 
>

That does not fit into current infrastructure and would require some more 
changes.
But I can offer you the opposite. With the latest changes you can write the 
project name into the metadata of the output image file. 
You need to configure your exiftool arg file in the preferences to do this.

Thomas

-- 
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/c22426bc-c312-4255-80d3-a35f068d1458%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [hugin-ptx] Mac Build

2016-05-18 Thread Niklas Mischkulnig
The problem with HuginStitchProject is that MacOpenFile gets called AFTER 
the variable is checked and the file chooser dialog opens and you having to 
open a project file. So sometime after it has already started processing 
the manually specified project file.

(I want to apologize in advance, I don't want to pressure you too much with 
all those feature requests and bugs.)

Could you please save the specified output prefix in Hugin to file, 
currently it gets validated and then discarded (PanoPanel.cpp:1091). 

Niklas


Am Mittwoch, 18. Mai 2016 19:09:35 UTC+2 schrieb T. Modes:
>
>
>
> Am Mittwoch, 18. Mai 2016 18:23:55 UTC+2 schrieb Niklas Mischkulnig:
>>
>>
>> A few questions concerning changes I made while updating the self 
 contained cmake build:
 What do you think about PTBatcherGui and HuginStitchProject opening 
 files (see my post from 17:10)?

>>>
>>> Does this referring to calling PTBatcherGUI and HuginStitchProject from 
>>> Hugin or direct from the bundle?
>>>
>>
>> So that you can open a file by right-clicking on it in the file-browser 
>> and then choosing "Open with..." (see Image).
>> (This would be more useful with StitchProject than with PTBatcherGui)
>>
>
> This is handled by MacOpenFile in the corresponding app class. This 
> function is specific to Mac OS. This is currently implemented for Hugin and 
> hugin_stitch_project, but not for PTBatcherGUI (it uses a normal command 
> line parsing of all the switches).
> Maybe there was a change between wxWidgets 2.8 and 3.0. You need to debug 
> it on a Mac. (Maybe adding std::cout or wxLogMessage in these function to 
> check if it processes correctly the files).
>
>  
>>
>>> Are these missing endl's in Executor.cpp intentional (see attached 
 patch)?

>>> I don't see an attached patch.
>>>
>>  Oops, now?
>>
>
> Yes. You are right. I committed your patch. 
>
>>
>> Can I include "hugin_config.h" in src/hugin1/base_wx/wxPlatform.h to 
 include the MAC_SELF_CONTAINED_BUNDLE definition in files like 
 Executor.cpp?

>>>
>>> I would prefer to include "hugin_config.h" into the source files 
>>> directly. Use it in the headers only when you need the variables in the 
>>> header.
>>>
>> Should I include  or "hugin_config.h" ? I have seen both 
>> in the code.
>>
>
> I prefer the "file.h" style for Hugin specific files and  for 
> external libs. But this is not used consistent.
>
> Addition to the includes:
>> Every file in hugin1 *except Executor.cpp* which needs 
>> MAC_SELF_CONTAINED_BUNDLE already includes , whose only
>> content is #include "hugin_config." So the only needed change would be 
>> to include :
>>
>
> that look good. Also committed to default branch.
>
> Thomas 
>
>
>

-- 
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/bc3ca5bd-a8e6-4ed3-b58f-d4bcb4e9d065%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [hugin-ptx] Mac Build

2016-05-18 Thread T. Modes


Am Mittwoch, 18. Mai 2016 18:23:55 UTC+2 schrieb Niklas Mischkulnig:
>
>
> A few questions concerning changes I made while updating the self 
>>> contained cmake build:
>>> What do you think about PTBatcherGui and HuginStitchProject opening 
>>> files (see my post from 17:10)?
>>>
>>
>> Does this referring to calling PTBatcherGUI and HuginStitchProject from 
>> Hugin or direct from the bundle?
>>
>
> So that you can open a file by right-clicking on it in the file-browser 
> and then choosing "Open with..." (see Image).
> (This would be more useful with StitchProject than with PTBatcherGui)
>

This is handled by MacOpenFile in the corresponding app class. This 
function is specific to Mac OS. This is currently implemented for Hugin and 
hugin_stitch_project, but not for PTBatcherGUI (it uses a normal command 
line parsing of all the switches).
Maybe there was a change between wxWidgets 2.8 and 3.0. You need to debug 
it on a Mac. (Maybe adding std::cout or wxLogMessage in these function to 
check if it processes correctly the files).

 
>
>> Are these missing endl's in Executor.cpp intentional (see attached patch)?
>>>
>> I don't see an attached patch.
>>
>  Oops, now?
>

Yes. You are right. I committed your patch. 

>
> Can I include "hugin_config.h" in src/hugin1/base_wx/wxPlatform.h to 
>>> include the MAC_SELF_CONTAINED_BUNDLE definition in files like Executor.cpp?
>>>
>>
>> I would prefer to include "hugin_config.h" into the source files 
>> directly. Use it in the headers only when you need the variables in the 
>> header.
>>
> Should I include  or "hugin_config.h" ? I have seen both 
> in the code.
>

I prefer the "file.h" style for Hugin specific files and  for 
external libs. But this is not used consistent.

Addition to the includes:
> Every file in hugin1 *except Executor.cpp* which needs 
> MAC_SELF_CONTAINED_BUNDLE already includes , whose only
> content is #include "hugin_config." So the only needed change would be to 
> include :
>

that look good. Also committed to default branch.

Thomas 


-- 
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/54429036-357f-4b61-9404-173fbcf3d64c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [hugin-ptx] Mac Build

2016-05-18 Thread Niklas Mischkulnig
Addition to the includes:
Every file in hugin1 *except Executor.cpp* which needs 
MAC_SELF_CONTAINED_BUNDLE already includes , whose only
content is #include "hugin_config." So the only needed change would be to 
include :

diff -r a297297b1beb src/hugin1/base_wx/Executor.cpp
--- a/src/hugin1/base_wx/Executor.cpp Tue May 17 18:58:10 2016 +0200
+++ b/src/hugin1/base_wx/Executor.cpp Wed May 18 18:53:12 2016 +0200
@@ -22,6 +22,7 @@
 */

 #include "Executor.h"
+#include 

 #include 
 #include 



Niklas

Am Mittwoch, 18. Mai 2016 18:23:55 UTC+2 schrieb Niklas Mischkulnig:
>
> Hi Thomas,
>
> A few questions concerning changes I made while updating the self 
>>> contained cmake build:
>>> What do you think about PTBatcherGui and HuginStitchProject opening 
>>> files (see my post from 17:10)?
>>>
>>
>> Does this referring to calling PTBatcherGUI and HuginStitchProject from 
>> Hugin or direct from the bundle?
>>
>
> So that you can open a file by right-clicking on it in the file-browser 
> and then choosing "Open with..." (see Image).
> (This would be more useful with StitchProject than with PTBatcherGui)
>  
>
>> Are these missing endl's in Executor.cpp intentional (see attached patch)?
>>>
>> I don't see an attached patch.
>>
>  Oops, now?
>
> Can I include "hugin_config.h" in src/hugin1/base_wx/wxPlatform.h to 
>>> include the MAC_SELF_CONTAINED_BUNDLE definition in files like Executor.cpp?
>>>
>>
>> I would prefer to include "hugin_config.h" into the source files 
>> directly. Use it in the headers only when you need the variables in the 
>> header.
>>
> Should I include  or "hugin_config.h" ? I have seen both 
> in the code.
>
> Niklas
>

-- 
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/db37968a-1961-4683-aa7c-8082a9756412%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [hugin-ptx] Mac Build

2016-05-18 Thread T. Modes
Hi Niklas,

Am Dienstag, 17. Mai 2016 19:30:31 UTC+2 schrieb Niklas Mischkulnig:
>
> The layout view works fine now.
>
Nice to hear.
 

> A few questions concerning changes I made while updating the self 
> contained cmake build:
> What do you think about PTBatcherGui and HuginStitchProject opening files 
> (see my post from 17:10)?
>

Does this referring to calling PTBatcherGUI and HuginStitchProject from 
Hugin or direct from the bundle?

Are these missing endl's in Executor.cpp intentional (see attached patch)?
>
I don't see an attached patch.
 

> Can I include "hugin_config.h" in src/hugin1/base_wx/wxPlatform.h to 
> include the MAC_SELF_CONTAINED_BUNDLE definition in files like Executor.cpp?
>

I would prefer to include "hugin_config.h" into the source files directly. 
Use it in the headers only when you need the variables in the header.

Thomas 

-- 
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/729bf65b-5cb8-4c71-85d1-1fffcd836641%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [hugin-ptx] Mac Build

2016-05-18 Thread Niklas Mischkulnig
If you downloaded the zip sometime after my last post, then you already got the 
fixed version. 

Niklas

-- 
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/d1271cdc-9892-4ff7-a433-4e5c9b91d8fc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [hugin-ptx] Mac Build

2016-05-17 Thread Donald Johnston
I just tried moving the cursor around quickly within the left window of the 
layout view of a three image pano and it all seems to work okay. NO crash!  I’m 
using the touch pad on may MacBook Pro.

As I move the mouse the highlighting in the left window changes to the photo 
the cursor is over. After a short while the big point shows up (I think OS X is 
assuming I’m moving the pointer really fast because I can’t find it (so it 
gives me the big pointer).  Is this about the time you get the crash?


> On May 17, 2016, at 9:10 AM, Niklas Mischkulnig  wrote:
> 
> Hello,
> 
> updated build, with correct file association, so that you can open a .pto 
> file using right-click>Open With... 
> This works properly with Hugin.app, but HuginStitchProject and PTBatcherGUI 
> start without opening the file.
> 
> The crash problem still exists (addition: only happens when I quickly move 
> around the mouse in those areas, not when I do it slowly)
> Could someone confirm this?
> 
> https://drive.google.com/uc?export=download=0B_seRjFxxDleN2V2VDVnS0hoSXc 
> 
> 
> Niklas
> 
> Am Montag, 16. Mai 2016 17:52:39 UTC+2 schrieb Niklas Mischkulnig:
> Hi Thomas, 
> 
> here is what consistently happens when I only around move the cursor in the 
> two boxes(see attachment) in the layout view using the new build from cmake
> https://drive.google.com/uc?export=download=0B_seRjFxxDleN2V2VDVnS0hoSXc 
> 
> 
> Thanks for your help, Habi!
> 
> Niklas
> 
> Get printed out over and over again, no crash
> 2016-05-16 17:35:22.007 Hugin[12251:255337] -[NSApplication runModalSession:] 
> may not be invoked inside of transaction commit (usually this means it was 
> invoked inside of a view's -drawRect: method.) The modal dialog has been 
> suppressed to avoid deadlock. (
>   0   AppKit  0x7fff87a7d4cf 
> -[NSApplication runModalSession:] + 211
>   1   libwx_osx_cocoau-3.0.0.dylib0x0001043332f0 
> _ZN14wxGUIEventLoop17DoDispatchTimeoutEm + 64
>   2   libwx_osx_cocoau-3.0.0.dylib0x000104252246 
> _ZN13wxCFEventLoop15DispatchTimeoutEm + 38
>   3   libwx_osx_cocoau-3.0.0.dylib0x0001042522f5 
> _ZN13wxCFEventLoop8OSXDoRunEv + 69
>   4   libwx_osx_cocoau-3.0.0.dylib0x0001043338c1 
> _ZN16wxModalEventLoop8OSXDoRunEv + 193
>   5   libwx_osx_cocoau-3.0.0.dylib0x0001042523a4 
> _ZN13wxCFEventLoop5DoRunEv + 52
>   6   libwx_osx_cocoau-3.0.0.dylib0x0001041b9de8 
> _ZN15wxEventLoopBase3RunEv + 88
>   7   libwx_osx_cocoau-3.0.0.dylib0x000104296242 
> _ZN8wxDialog9ShowModalEv + 98
>   8   libwx_osx_cocoau-3.0.0.dylib0x00010458099d 
> _ZNK23wxDebugReportPreviewStd4ShowER13wxDebugReport + 61
>   9   libhuginbasewx.0.0.dylib0x000104febfd4 
> _Z14GenerateReportN13wxDebugReport7ContextE + 212
>   10  libwx_osx_cocoau-3.0.0.dylib0x000104267d5c 
> wxFatalSignalHandler + 28
>   11  libsystem_platform.dylib0x7fff91d5552a _sigtramp + 
> 26
>   12  ??? 0x7fc9a64e2abc 0x0 + 
> 140504055294652
>   13  Hugin   0x0001034c31c1 
> _ZN17GLPreviewRenderer6RedrawEv + 305
>   14  Hugin   0x0001034c160a 
> _ZN8GLViewer6RedrawEv + 218
>   15  Hugin   0x0001034bfc75 
> _ZN8GLViewer7RedrawEER12wxPaintEvent + 101
>   16  libwx_osx_cocoau-3.0.0.dylib0x00010427119f 
> _ZN16wxEventHashTable11HandleEventER7wxEventP12wxEvtHandler + 351
>   17  libwx_osx_cocoau-3.0.0.dylib0x000104271ded 
> _ZN12wxEvtHandler19ProcessEventLocallyER7wxEvent + 93
>   18  libwx_osx_cocoau-3.0.0.dylib0x000104271cd7 
> _ZN12wxEvtHandler12ProcessEventER7wxEvent + 103
>   19  libwx_osx_cocoau-3.0.0.dylib0x0001042720af 
> _ZN12wxEvtHandler18SafelyProcessEventER7wxEvent + 15
>   20  libwx_osx_cocoau-3.0.0.dylib0x0001042a125b 
> _ZN8wxWindow11MacDoRedrawEl + 795
>   21  libwx_osx_cocoau-3.0.0.dylib0x00010434d887 
> _ZN17wxWidgetCocoaImpl8drawRectEPvP6NSViewS0_ + 791
>   22  libwx_osx_cocoau-3.0.0.dylib0x00010434c116 
> _Z14wxOSX_drawRectP6NSViewP13objc_selector6CGRect + 86
>   23  AppKit  0x7fff8778edd6 -[NSView 
> _drawRect:clip:] + 3626
>   24  AppKit  0x7fff877e6db1 -[NSView 
> _recursiveDisplayAllDirtyWithLockFocus:visRect:] + 1873
>   25  AppKit  0x7fff8778c4ff -[NSView 
> _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:topView:]
>  + 838
>   26  AppKit  0x7fff8778d889 -[NSView 
> 

Re: [hugin-ptx] Mac Build

2016-05-17 Thread Niklas Mischkulnig
Hi Thomas, 

I got the cmake-build completely working, so that the bundles are built 
after make (without CPack but with add_executable(... MACOSX_BUNDLE ...)). 
The layout view works fine now.
A few questions concerning changes I made while updating the self contained 
cmake build:
What do you think about PTBatcherGui and HuginStitchProject opening files 
(see my post from 17:10)?
Are these missing endl's in Executor.cpp intentional (see attached patch)?
Can I include "hugin_config.h" in src/hugin1/base_wx/wxPlatform.h to 
include the MAC_SELF_CONTAINED_BUNDLE definition in files like Executor.cpp?

https://drive.google.com/uc?export=download=0B_seRjFxxDleN2V2VDVnS0hoSXc

Niklas

Am Dienstag, 17. Mai 2016 19:08:20 UTC+2 schrieb T. Modes:
>
> Hi Niklas,
>
> Am Samstag, 14. Mai 2016 19:51:23 UTC+2 schrieb Niklas Mischkulnig:
>>
>> Recently, I have been trying to compile the self contained bundle using 
>> cmake, one problem is that the "built-in" libraries(celeste, huginbase, 
>> basewx, ...) all have a install name like @rpath/libhuginbase.0.0.dylib . 
>> Because of that the PackageMacAppBundleLibs.sh script doesn't know where to 
>> copy it from. Do you know how I can set cmake to use the absolute path?
>>
>
> no, I don't know. Maybe setting CMAKE_INSTALL_PREFIX to a path and then 
> run "make install". Then all libs and executables are copied to 
> CMAKE_INSTALL_PREFIX.
>
> Or you could test CPack inside CMake. As far as I understand CPack can 
> also create Mac bundles. But I don't know the details. It may require some 
> more changes to CMakeLists.txt.
>
> here is what consistently happens when I only around move the cursor in 
>> the two boxes(see attachment) in the layout view using the new build from 
>> cmake
>>
>
> This should be fixed in repository. 
>
> Thomas
>

-- 
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/b258b6a1-8221-4899-b47b-4a9e6b593b48%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [hugin-ptx] Mac Build

2016-05-17 Thread T. Modes
Hi Niklas,

Am Samstag, 14. Mai 2016 19:51:23 UTC+2 schrieb Niklas Mischkulnig:
>
> Recently, I have been trying to compile the self contained bundle using 
> cmake, one problem is that the "built-in" libraries(celeste, huginbase, 
> basewx, ...) all have a install name like @rpath/libhuginbase.0.0.dylib . 
> Because of that the PackageMacAppBundleLibs.sh script doesn't know where to 
> copy it from. Do you know how I can set cmake to use the absolute path?
>

no, I don't know. Maybe setting CMAKE_INSTALL_PREFIX to a path and then run 
"make install". Then all libs and executables are copied to 
CMAKE_INSTALL_PREFIX.

Or you could test CPack inside CMake. As far as I understand CPack can also 
create Mac bundles. But I don't know the details. It may require some more 
changes to CMakeLists.txt.

here is what consistently happens when I only around move the cursor in the 
> two boxes(see attachment) in the layout view using the new build from cmake
>

This should be fixed in repository. 

Thomas

-- 
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/1fc1de17-f311-4e2f-ba69-9a704970af2e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [hugin-ptx] Mac Build

2016-05-16 Thread Niklas Mischkulnig
Hi Thomas, 

here is what consistently happens when I only around move the cursor in the 
two boxes(see attachment) in the layout view using the new build from cmake
https://drive.google.com/uc?export=download=0B_seRjFxxDleN2V2VDVnS0hoSXc

Thanks for your help, Habi!

Niklas

*Get printed out over and over again, no crash*
2016-05-16 17:35:22.007 Hugin[12251:255337] -[NSApplication 
runModalSession:] may not be invoked inside of transaction commit (usually 
this means it was invoked inside of a view's -drawRect: method.) The modal 
dialog has been suppressed to avoid deadlock. (
0   AppKit  0x7fff87a7d4cf -[NSApplication 
runModalSession:] + 211
1   libwx_osx_cocoau-3.0.0.dylib0x0001043332f0 
_ZN14wxGUIEventLoop17DoDispatchTimeoutEm + 64
2   libwx_osx_cocoau-3.0.0.dylib0x000104252246 
_ZN13wxCFEventLoop15DispatchTimeoutEm + 38
3   libwx_osx_cocoau-3.0.0.dylib0x0001042522f5 
_ZN13wxCFEventLoop8OSXDoRunEv + 69
4   libwx_osx_cocoau-3.0.0.dylib0x0001043338c1 
_ZN16wxModalEventLoop8OSXDoRunEv + 193
5   libwx_osx_cocoau-3.0.0.dylib0x0001042523a4 
_ZN13wxCFEventLoop5DoRunEv + 52
6   libwx_osx_cocoau-3.0.0.dylib0x0001041b9de8 
_ZN15wxEventLoopBase3RunEv + 88
7   libwx_osx_cocoau-3.0.0.dylib0x000104296242 
_ZN8wxDialog9ShowModalEv + 98
8   libwx_osx_cocoau-3.0.0.dylib0x00010458099d 
_ZNK23wxDebugReportPreviewStd4ShowER13wxDebugReport + 61
9   libhuginbasewx.0.0.dylib0x000104febfd4 
_Z14GenerateReportN13wxDebugReport7ContextE + 212
10  libwx_osx_cocoau-3.0.0.dylib0x000104267d5c 
wxFatalSignalHandler + 28
11  libsystem_platform.dylib0x7fff91d5552a _sigtramp + 26
12  ??? 0x7fc9a64e2abc 0x0 + 
140504055294652
13  Hugin   0x0001034c31c1 
_ZN17GLPreviewRenderer6RedrawEv + 305
14  Hugin   0x0001034c160a 
_ZN8GLViewer6RedrawEv + 218
15  Hugin   0x0001034bfc75 
_ZN8GLViewer7RedrawEER12wxPaintEvent + 101
16  libwx_osx_cocoau-3.0.0.dylib0x00010427119f 
_ZN16wxEventHashTable11HandleEventER7wxEventP12wxEvtHandler + 351
17  libwx_osx_cocoau-3.0.0.dylib0x000104271ded 
_ZN12wxEvtHandler19ProcessEventLocallyER7wxEvent + 93
18  libwx_osx_cocoau-3.0.0.dylib0x000104271cd7 
_ZN12wxEvtHandler12ProcessEventER7wxEvent + 103
19  libwx_osx_cocoau-3.0.0.dylib0x0001042720af 
_ZN12wxEvtHandler18SafelyProcessEventER7wxEvent + 15
20  libwx_osx_cocoau-3.0.0.dylib0x0001042a125b 
_ZN8wxWindow11MacDoRedrawEl + 795
21  libwx_osx_cocoau-3.0.0.dylib0x00010434d887 
_ZN17wxWidgetCocoaImpl8drawRectEPvP6NSViewS0_ + 791
22  libwx_osx_cocoau-3.0.0.dylib0x00010434c116 
_Z14wxOSX_drawRectP6NSViewP13objc_selector6CGRect + 86
23  AppKit  0x7fff8778edd6 -[NSView 
_drawRect:clip:] + 3626
24  AppKit  0x7fff877e6db1 -[NSView 
_recursiveDisplayAllDirtyWithLockFocus:visRect:] + 1873
25  AppKit  0x7fff8778c4ff -[NSView 
_recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:topView:]
 
+ 838
26  AppKit  0x7fff8778d889 -[NSView 
_recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:topView:]
 
+ 5840
27  AppKit  0x7fff8778d889 -[NSView 
_recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:topView:]
 
+ 5840
28  AppKit  0x7fff8778d889 -[NSView 
_recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:topView:]
 
+ 5840
29  AppKit  0x7fff8778d889 -[NSView 
_recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:topView:]
 
+ 5840
30  AppKit  0x7fff8778bce4 -[NSThemeFrame 
_recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:topView:]
 
+ 334
31  AppKit  0x7fff8778a0ef -[NSView 
_displayRectIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:] + 2449
32  AppKit  0x7fff877854f9 -[NSView 
displayIfNeeded] + 1950
33  AppKit  0x7fff87784d40 -[NSWindow 
displayIfNeeded] + 232
34  AppKit  0x7fff87e094bb 
___NSWindowGetDisplayCycleObserver_block_invoke6365 + 476
35  AppKit  0x7fff877846da 
__37+[NSDisplayCycle currentDisplayCycle]_block_invoke + 941
36  QuartzCore  0x7fff8618af71 
_ZN2CA11Transaction19run_commit_handlersE18CATransactionPhase + 85
37  QuartzCore  0x7fff8618a42c 
_ZN2CA7Context18commit_transactionEPNS_11TransactionE + 160
38  QuartzCore  

Re: [hugin-ptx] Mac Build

2016-05-15 Thread David Haberthür
Ciao Niklas.

> On 14 May 2016, at 19:51, Niklas Mischkulnig  wrote:
> 
> first of all, here is a new build: (changeset 7380:912ab8ae8e70 , compiled 
> using XCode 7.3.1, wasn't able to crash Hugin [yet])
> https://drive.google.com/uc?export=download=0B_seRjFxxDleU1YtQ1Zka1BXM2c

Thanks for this new build.
I’ve also yet to produce a crash, so it seems that the “most obvious” problems 
are fixed.
Thanks for your perseverance!

Habi

-- 
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/67C8C0C4-B0E1-4579-93B8-F55E24AD0F18%40gmail.com.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: Message signed with OpenPGP using GPGMail


Re: [hugin-ptx] Mac Build

2016-05-14 Thread Niklas Mischkulnig
Hi Thomas,

first of all, here is a new build: (changeset 7380:912ab8ae8e70 , compiled 
using XCode 7.3.1, wasn't able to crash Hugin [yet])
https://drive.google.com/uc?export=download=0B_seRjFxxDleU1YtQ1Zka1BXM2c

Recently, I have been trying to compile the self contained bundle using 
cmake, one problem is that the "built-in" libraries(celeste, huginbase, 
basewx, ...) all have a install name like @rpath/libhuginbase.0.0.dylib . 
Because of that the PackageMacAppBundleLibs.sh script doesn't know where to 
copy it from. Do you know how I can set cmake to use the absolute path?

Niklas


Am Donnerstag, 12. Mai 2016 20:01:06 UTC+2 schrieb T. Modes:
>
> Hi Niklas
>
> Am Montag, 9. Mai 2016 14:18:44 UTC+2 schrieb Niklas Mischkulnig:
>>
>> there is still one problem remaining, Hugin sometimes hangs after 
>> clicking on one image in the layout view or after closing the window that 
>> opens thereafter:
>> atos[12096]: [fatal] 'pid_for_task' failed: (os/kern) failure (5)
>>
>
> I committed several small fixes. Not sure if they fix your issue. Could 
> you test? Thanks.
>
> Thomas
>
> PS: What version of XCode do you use? If found here an issue with XCode 
> 7.3 which shows the same error message 
> http://trac.wxwidgets.org/ticket/17511 
> But I don't know if both issues are related. But the mentioned issue was 
> fixed in XCode 7.3.1
>

-- 
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/320efb30-de81-4791-993f-33fd7b0e9ff8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [hugin-ptx] Mac Build

2016-05-12 Thread T. Modes
Hi Niklas

Am Montag, 9. Mai 2016 14:18:44 UTC+2 schrieb Niklas Mischkulnig:
>
> there is still one problem remaining, Hugin sometimes hangs after clicking 
> on one image in the layout view or after closing the window that opens 
> thereafter:
> atos[12096]: [fatal] 'pid_for_task' failed: (os/kern) failure (5)
>

I committed several small fixes. Not sure if they fix your issue. Could you 
test? Thanks.

Thomas

PS: What version of XCode do you use? If found here an issue with XCode 7.3 
which shows the same error message http://trac.wxwidgets.org/ticket/17511 
But I don't know if both issues are related. But the mentioned issue was 
fixed in XCode 7.3.1

-- 
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/c9cb0b27-5742-4bf7-932f-ccd630a59a31%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [hugin-ptx] Mac Build

2016-05-09 Thread T. Modes
Hi Niklas,

Am Montag, 9. Mai 2016 14:18:44 UTC+2 schrieb Niklas Mischkulnig:
>
> there is still one problem remaining, Hugin sometimes hangs after clicking 
> on one image in the layout view or after closing the window that opens 
> thereafter:
> atos[12096]: [fatal] 'pid_for_task' failed: (os/kern) failure (5)
>

such errors, which does not always appear, are difficult to track down.
And there error message does not point to a specific location.
I'm trying to fix some leaks or problems with uninitialized variables. But 
this will take some time. This is also new territory for me.
I could already fix some first issue. But they are probably not related to 
this error.

Thomas

-- 
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/2fad4769-e48c-40db-acc2-c43e7619fd8e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [hugin-ptx] Mac Build

2016-05-09 Thread Niklas Mischkulnig
Hi Thomas,

there is still one problem remaining, Hugin sometimes hangs after clicking 
on one image in the layout view or after closing the window that opens 
thereafter:
atos[12096]: [fatal] 'pid_for_task' failed: (os/kern) failure (5)


Niklas

Am Samstag, 7. Mai 2016 08:30:17 UTC+2 schrieb T. Modes:
>
> Hi Niklas,
>
> Am Freitag, 6. Mai 2016 23:49:07 UTC+2 schrieb Niklas Mischkulnig:
>>
>> Needed changes:
>> You need to add a cast in front of every 3rd parameter, i.e.:
>>
>> if (!CFDictionaryGetValueIfPresent(dict, kColorSyncDeviceClass, *(**const 
>> void)*)){
>>
>> Full Output:
>> wxCMS: Found profile: /Library/ColorSync/Profiles/Displays/Color 
>> LCD-68FE312B-5EF0-E0A1-BCD8-8890B73C7B3A.icc
>>
>>
> Thanks for testing and the changes. I committed to modified version to 
> default branch.
>
> Thomas
>

-- 
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/7961c589-1c58-4d6f-8295-4ead2c70d9d7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [hugin-ptx] Mac Build

2016-05-07 Thread T. Modes
Hi Niklas,

Am Freitag, 6. Mai 2016 23:49:07 UTC+2 schrieb Niklas Mischkulnig:
>
> Needed changes:
> You need to add a cast in front of every 3rd parameter, i.e.:
>
> if (!CFDictionaryGetValueIfPresent(dict, kColorSyncDeviceClass, *(**const 
> void)*)){
>
> Full Output:
> wxCMS: Found profile: /Library/ColorSync/Profiles/Displays/Color 
> LCD-68FE312B-5EF0-E0A1-BCD8-8890B73C7B3A.icc
>
>
Thanks for testing and the changes. I committed to modified version to 
default branch.

Thomas

-- 
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/80e0ca1b-ab8f-4127-a754-9780a89b13bc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [hugin-ptx] Mac Build

2016-05-06 Thread Niklas Mischkulnig
Needed changes:
You need to add a cast in front of every 3rd parameter, i.e.:

if (!CFDictionaryGetValueIfPresent(dict, kColorSyncDeviceClass, *(**const 
void)*)){

Full Output:
wxCMS: Found profile: /Library/ColorSync/Profiles/Displays/Color 
LCD-68FE312B-5EF0-E0A1-BCD8-8890B73C7B3A.icc

Niklas

Am Freitag, 6. Mai 2016 23:21:00 UTC+2 schrieb Niklas Mischkulnig:
>
> Hello,
>
> there are indeed some errors:
>
> Niklas
>
> Am Donnerstag, 5. Mai 2016 09:19:50 UTC+2 schrieb T. Modes:
>>
>> Ni Niklas,
>>
>> Am Donnerstag, 5. Mai 2016 09:16:43 UTC+2 schrieb Niklas Mischkulnig:
>>>
>>>
>>> today and tomorrow I'm visiting Vienna, so I can't test it until 
>>> Saturday morning.
>>>
>>
>> No problem. Have some nice days in Vienna.
>>
>> Thomas
>>
>>

-- 
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/818e3148-c0b9-4862-a2a2-2c0adae5ce8a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [hugin-ptx] Mac Build

2016-05-05 Thread T. Modes
Ni Niklas,

Am Donnerstag, 5. Mai 2016 09:16:43 UTC+2 schrieb Niklas Mischkulnig:
>
>
> today and tomorrow I'm visiting Vienna, so I can't test it until Saturday 
> morning.
>

No problem. Have some nice days in Vienna.

Thomas

-- 
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/2e62ae7b-e0f4-4e1c-b3d0-d5418f0cbfae%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [hugin-ptx] Mac Build

2016-05-05 Thread Niklas Mischkulnig
Hi Thomas,
today and tomorrow I'm visiting Vienna, so I can't test it until Saturday
morning.

Niklas
Am 05.05.2016 09:12 schrieb "T. Modes" :

> Hi Niklas,
>
> Am Mittwoch, 4. Mai 2016 19:50:41 UTC+2 schrieb Niklas Mischkulnig:
>>
>> Thank you for your help!
>>
>
> Now that it works, one problem remains: currently the active monitor
> profile is only loaded on Windows and Linux, but not on Mac.
> To retrieve the monitor profile we need platform specific code. Especially
> for Mac I have not found a good description.
> Nevertheless by combining different pieces I wrote now a first draft for
> the Mac. But I could not test it. It may not even compile (typos, missing
> includes or so).
> Could you please test it? (Please update your repository before. I
> committed a first general change (changeset 8deb93c66d5f). The patch is
> build on top of this changeset.)
>
> Thomas
>
> --
> A list of frequently asked questions is available at:
> http://wiki.panotools.org/Hugin_FAQ
> ---
> You received this message because you are subscribed to a topic in the
> Google Groups "hugin and other free panoramic software" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/hugin-ptx/Rz-LY9isDIs/unsubscribe.
> To unsubscribe from this group and all its topics, 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/bac16642-6888-4f90-af62-8c6256e51955%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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/CACd%3DvwDvuZkRMbJg0p63creT7u_BY94gXemytrmSX_MGPqgUMg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: [hugin-ptx] Mac Build

2016-05-04 Thread Niklas Mischkulnig
Thank you for your help!

Niklas
Am 04.05.2016 19:41 schrieb "T. Modes" :

> Hi Niklas,
>
> Am Mittwoch, 4. Mai 2016 19:32:16 UTC+2 schrieb Niklas Mischkulnig:
>>
>>
>> I found out why it isn't working: everything was linked against lcms(1)
>> instead of lcms2, though that only appeared to me after patch#4 resulted in
>> undefined symbols. So linking the correct library made it work(without any
>> change in the code).
>>
>
> Great works. Thanks. That are good new.
>
> Thomas
>
>
> --
> A list of frequently asked questions is available at:
> http://wiki.panotools.org/Hugin_FAQ
> ---
> You received this message because you are subscribed to a topic in the
> Google Groups "hugin and other free panoramic software" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/hugin-ptx/Rz-LY9isDIs/unsubscribe.
> To unsubscribe from this group and all its topics, 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/50c349a1-cabf-4d3f-94e2-c8617bc5d5ce%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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/CACd%3DvwBpZS4LNU_2L%3DzUJeiDOs6OMUrWuZOF6%2Br1nryc%3DizyKQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: [hugin-ptx] Mac Build

2016-05-04 Thread T. Modes
Hi Niklas,

Am Mittwoch, 4. Mai 2016 19:32:16 UTC+2 schrieb Niklas Mischkulnig:
>
>
> I found out why it isn't working: everything was linked against lcms(1) 
> instead of lcms2, though that only appeared to me after patch#4 resulted in 
> undefined symbols. So linking the correct library made it work(without any 
> change in the code).
>

Great works. Thanks. That are good new.

Thomas
 

-- 
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/50c349a1-cabf-4d3f-94e2-c8617bc5d5ce%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [hugin-ptx] Mac Build

2016-05-04 Thread Niklas Mischkulnig
Hello Thomas,

I found out why it isn't working: everything was linked against lcms(1) 
instead of lcms2, though that only appeared to me after patch#4 resulted in 
undefined symbols. So linking the correct library made it work(without any 
change in the code).
New build:
https://drive.google.com/uc?export=download=0B_seRjFxxDleU1YtQ1Zka1BXM2c

Niklas

Am Mittwoch, 4. Mai 2016 18:50:54 UTC+2 schrieb T. Modes:
>
> Hi Niklas,
>
> Am Montag, 2. Mai 2016 19:26:32 UTC+2 schrieb Niklas Mischkulnig:
>>
>> no change: 
>>
>
> That's really strange. I added some more debug code and some different 
> methods for creating the input profile.
> Could you please test?
>
> Thomas
>

-- 
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/67725729-6048-43ed-a9d3-8b33bed629d2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [hugin-ptx] Mac Build

2016-05-04 Thread T. Modes
Hi Niklas,

Am Montag, 2. Mai 2016 19:26:32 UTC+2 schrieb Niklas Mischkulnig:
>
> no change: 
>

That's really strange. I added some more debug code and some different 
methods for creating the input profile.
Could you please test?

Thomas

-- 
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/29cd121c-440f-4bbc-b122-c34c719294a6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
diff --git a/src/hugin1/hugin/TextureManager.cpp b/src/hugin1/hugin/TextureManager.cpp
--- a/src/hugin1/hugin/TextureManager.cpp
+++ b/src/hugin1/hugin/TextureManager.cpp
@@ -654,6 +654,12 @@
 glDeleteTextures(1, (GLuint*) );
 }
 
+static
+void ErrorReportingFunction(cmsContext ContextID, cmsUInt32Number ErrorCode, const char *Text)
+{
+std::cout << "Error: " << Text << " (" << ErrorCode << ")" << std::endl;
+}
+
 void TextureManager::TextureInfo::Bind()
 {
 BindImageTexture();
@@ -867,7 +873,27 @@
 cmsHPROFILE inputICC = NULL;
 if (!entry->iccProfile->empty())
 {
+cmsSetLogErrorHandler(ErrorReportingFunction);
 inputICC = cmsOpenProfileFromMem(entry->iccProfile->data(), entry->iccProfile->size());
+std::cout << "InputICC size: " << entry->iccProfile->size() << std::endl
+<< "iccProfile: " << hugin_utils::GetICCDesc(*entry->iccProfile) << std::endl
+<< "inputICC: " << hugin_utils::GetICCDesc(inputICC) << std::endl;
+{
+cmsContext context = cmsCreateContext(NULL, NULL);
+cmsHPROFILE profile = cmsOpenProfileFromMemTHR(context, entry->iccProfile->data(), entry->iccProfile->size());
+cmsSetLogErrorHandlerTHR(context, ErrorReportingFunction);
+if (profile != NULL)
+{
+std::cout << "ICC via context: " << hugin_utils::GetICCDesc(profile) << std::endl;
+cmsCloseProfile(profile);
+}
+else
+{
+std::cout << "ICC via context failed." << std::endl;
+};
+cmsSetLogErrorHandlerTHR(context, NULL);
+cmsDeleteContext(context);
+}
 };
 cmsHTRANSFORM transform = NULL;
 // do color correction only if input image has icc profile or if we found a monitor profile
@@ -880,17 +906,27 @@
 {
 cmsCloseProfile(inputICC);
 inputICC = NULL;
+std::cout << "No RGB profile" << std::endl;
 };
 };
 // if there is no icc profile in file fall back to sRGB
 if (inputICC == NULL)
 {
 inputICC = cmsCreate_sRGBProfile();
+std::cout << "Created generic profile" << std::endl;
 };
+std::cout << "TexManager" << std::endl
+<< "inputICC: " << hugin_utils::GetICCDesc(inputICC) << std::endl
+<< "monitorProfile: " << huginApp::Get()->GetMonitorProfileName().c_str() << std::endl
+<< "outputICC: " << hugin_utils::GetICCDesc(huginApp::Get()->GetMonitorProfile()) << std::endl
+<< "TYPE_RGB8: " << TYPE_RGB_8 << std::endl
+<< "INTENT_PERCEPTUAL: " << INTENT_PERCEPTUAL << std::endl
+<< "cmsFLAGS_BLACKPOINTCOMPENSATION: " << cmsFLAGS_BLACKPOINTCOMPENSATION << std::endl;
+cmsSetLogErrorHandler(NULL);
 // now build transform
-transform = cmsCreateTransform(inputICC, TYPE_RGB_8,
+/* transform = cmsCreateTransform(inputICC, TYPE_RGB_8,
 huginApp::Get()->GetMonitorProfile(), TYPE_RGB_8,
-INTENT_PERCEPTUAL, cmsFLAGS_BLACKPOINTCOMPENSATION);
+INTENT_PERCEPTUAL, cmsFLAGS_BLACKPOINTCOMPENSATION);*/
 };
 // now perform photometric correction
 if (photometric_correct)


Re: [hugin-ptx] Mac Build

2016-05-02 Thread Niklas Mischkulnig
Hi Thomas, 

no change: 

iccProfile size: 2672
CorrectImage
inputICC: farbverdreht
outputICC: sRGB built-in
TYPE_RGB8: 262169
INTENT_PERCEPTUAL: 0
cmsFLAGS_BLACKPOINTCOMPENSATION: 8192
iccProfile size: 2672
CorrectImage
inputICC: farbverdreht
outputICC: sRGB built-in
TYPE_RGB8: 262169
INTENT_PERCEPTUAL: 0
cmsFLAGS_BLACKPOINTCOMPENSATION: 8192
InputICC size: 2672
TexManager
inputICC:
monitorProfile:
outputICC: sRGB built-in
TYPE_RGB8: 262169
INTENT_PERCEPTUAL: 0
cmsFLAGS_BLACKPOINTCOMPENSATION: 8192


>From time to time this happens:
iccProfile size: 2672
CorrectImage
inputICC: farbverdreht
outputICC: sRGB built-in
TYPE_RGB8: 262169
INTENT_PERCEPTUAL: 0
cmsFLAGS_BLACKPOINTCOMPENSATION: 8192
iccProfile size: 2672
CorrectImage
inputICC: farbverdreht
outputICC: sRGB built-in
TYPE_RGB8: 262169
INTENT_PERCEPTUAL: 0
cmsFLAGS_BLACKPOINTCOMPENSATION: 8192
InputICC size: 2672
TexManager
atos[46128]: [fatal] 'pid_for_task' failed: (os/kern) failure (5)
then Hugin hangs/doesn't respond.


Niklas



Am Montag, 2. Mai 2016 18:55:29 UTC+2 schrieb T. Modes:
>
>
> Hi Niklas,
>
> Am Sonntag, 1. Mai 2016 20:13:30 UTC+2 schrieb Niklas Mischkulnig:
>>
>>
>> Here you go:
>>
>> iccProfile size: 2672
>>
>
> new try. I changed the creating of the input icc profile.
> All debug message are still in.
>
> Thomas
>

-- 
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/5b33c6be-524a-4e12-8628-09a3ecae64bc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [hugin-ptx] Mac Build

2016-05-02 Thread T. Modes

Hi Niklas,

Am Sonntag, 1. Mai 2016 20:13:30 UTC+2 schrieb Niklas Mischkulnig:
>
>
> Here you go:
>
> iccProfile size: 2672
>

new try. I changed the creating of the input icc profile.
All debug message are still in.

Thomas

-- 
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/c0a32af4-4266-4895-a940-dfd88a663a7c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
diff --git a/src/hugin1/base_wx/wxcms.cpp b/src/hugin1/base_wx/wxcms.cpp
--- a/src/hugin1/base_wx/wxcms.cpp
+++ b/src/hugin1/base_wx/wxcms.cpp
@@ -28,6 +28,7 @@
 #include 
 #include "hugin_utils/utils.h"
 #endif
+#include "hugin_utils/utils.h"
 
 namespace HuginBase
 {
@@ -129,6 +130,7 @@
 if (!iccProfile.empty())
 {
 inputICC = cmsOpenProfileFromMem(iccProfile.data(), iccProfile.size());
+std::cout << "iccProfile size: " << iccProfile.size() << std::endl;
 };
 // check type of input profile
 if (inputICC != NULL)
@@ -145,6 +147,13 @@
 inputICC = cmsCreate_sRGBProfile();
 };
 // now build transform
+std::cout << "CorrectImage" << std::endl
+<< "inputICC: " << hugin_utils::GetICCDesc(inputICC) << std::endl
+<< "outputICC: " << hugin_utils::GetICCDesc(monitorProfile) << std::endl
+<< "TYPE_RGB8: " << TYPE_RGB_8 << std::endl
+<< "INTENT_PERCEPTUAL: " << INTENT_PERCEPTUAL << std::endl
+<< "cmsFLAGS_BLACKPOINTCOMPENSATION: " << cmsFLAGS_BLACKPOINTCOMPENSATION << std::endl;
+
 cmsHTRANSFORM transform = cmsCreateTransform(inputICC, TYPE_RGB_8,
 monitorProfile, TYPE_RGB_8,
 INTENT_PERCEPTUAL, cmsFLAGS_BLACKPOINTCOMPENSATION);
diff --git a/src/hugin1/hugin/TextureManager.cpp b/src/hugin1/hugin/TextureManager.cpp
--- a/src/hugin1/hugin/TextureManager.cpp
+++ b/src/hugin1/hugin/TextureManager.cpp
@@ -867,7 +867,9 @@
 cmsHPROFILE inputICC = NULL;
 if (!entry->iccProfile->empty())
 {
-inputICC = cmsOpenProfileFromMem(entry->iccProfile->data(), entry->iccProfile->size());
+const vigra::ImageImportInfo::ICCProfile iccProfile(*(entry->iccProfile));
+inputICC = cmsOpenProfileFromMem(iccProfile.data(), iccProfile.size());
+std::cout << "InputICC size: " << iccProfile.size() << std::endl;
 };
 cmsHTRANSFORM transform = NULL;
 // do color correction only if input image has icc profile or if we found a monitor profile
@@ -880,17 +882,26 @@
 {
 cmsCloseProfile(inputICC);
 inputICC = NULL;
+std::cout << "No RGB profile" << std::endl;
 };
 };
 // if there is no icc profile in file fall back to sRGB
 if (inputICC == NULL)
 {
 inputICC = cmsCreate_sRGBProfile();
+std::cout << "Created generic profile" << std::endl;
 };
+std::cout << "TexManager" << std::endl
+<< "inputICC: " << hugin_utils::GetICCDesc(inputICC) << std::endl
+<< "monitorProfile: " << huginApp::Get()->GetMonitorProfileName().c_str() << std::endl
+<< "outputICC: " << hugin_utils::GetICCDesc(huginApp::Get()->GetMonitorProfile()) << std::endl
+<< "TYPE_RGB8: " << TYPE_RGB_8 << std::endl
+<< "INTENT_PERCEPTUAL: " << INTENT_PERCEPTUAL << std::endl
+<< "cmsFLAGS_BLACKPOINTCOMPENSATION: " << cmsFLAGS_BLACKPOINTCOMPENSATION << std::endl;
 // now build transform
-transform = cmsCreateTransform(inputICC, TYPE_RGB_8,
+/* transform = cmsCreateTransform(inputICC, TYPE_RGB_8,
 huginApp::Get()->GetMonitorProfile(), TYPE_RGB_8,
-INTENT_PERCEPTUAL, cmsFLAGS_BLACKPOINTCOMPENSATION);
+INTENT_PERCEPTUAL, cmsFLAGS_BLACKPOINTCOMPENSATION);*/
 };
 // now perform photometric correction
 if (photometric_correct)


Re: [hugin-ptx] Mac Build

2016-05-02 Thread Donald Johnston
Yes, that was the problem. I “usually” keep all that in a Hugin subdirectory 
under Applications but there was one in the Applications folder itself.  So it 
wasn’t deleted when I cleaned the old stuff out!

Thanks.


> On May 1, 2016, at 11:18 PM, Niklas Mischkulnig  wrote:
> 
> Do you have two instances of PTBatcherGui.app on your computer? Hugin might 
> try to start the one from the build before.
> 
> Am 02.05.2016 05:31 schrieb "Donald Johnston"  >:
> When I try to stitch a pano from Hugin I get the following error message:
> PTBatcherGUI cannot be opened because of a problem.
> 
> The error shown in the Terminal is:
> PTBatcherGui check returned  value 
> /Applications/PTBatcherGUI.app/Contents/MacOS/PTBatcherGUI
> 
> dyld: Library not loaded: @executable_path/../Frameworks/libpano13.3.dylib
>   Referenced from: /Applications/PTBatcherGUI.app/Contents/MacOS/PTBatcherGUI
>   Reason: image not found
> 
> However if I start PTBatcherGUI and load the pto file in it does the 
> stitching properly.
> 
> 
> 
> -- 
> A list of frequently asked questions is available at: 
> http://wiki.panotools.org/Hugin_FAQ 
> --- 
> You received this message because you are subscribed to a topic in the Google 
> Groups "hugin and other free panoramic software" group.
> To unsubscribe from this topic, visit 
> https://groups.google.com/d/topic/hugin-ptx/Rz-LY9isDIs/unsubscribe 
> .
> To unsubscribe from this group and all its topics, 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/124EE48F-C33C-4457-BBB7-6A040118A71A%40accesscomm.ca
>  
> .
> For more options, visit https://groups.google.com/d/optout 
> .
> 
> -- 
> 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/CACd%3DvwAu9ck9fzYu7KsToi_%2BXH%2BWTR5pymNfW%3D1NVTZEpqstDQ%40mail.gmail.com
>  
> .
> For more options, visit https://groups.google.com/d/optout 
> .

-- 
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/A3E9E278-5EA5-4D98-AF2C-5FE8A7A8%40accesscomm.ca.
For more options, visit https://groups.google.com/d/optout.


Re: [hugin-ptx] Mac Build

2016-05-01 Thread Niklas Mischkulnig
Do you have two instances of PTBatcherGui.app on your computer? Hugin might
try to start the one from the build before.
Am 02.05.2016 05:31 schrieb "Donald Johnston" :

> When I try to stitch a pano from Hugin I get the following error message:
>
> PTBatcherGUI cannot be opened because of a problem.
>
>
> The error shown in the Terminal is:
>
> PTBatcherGui check returned  value
> /Applications/PTBatcherGUI.app/Contents/MacOS/PTBatcherGUI
>
> dyld: Library not loaded: @executable_path/../Frameworks/libpano13.3.dylib
>   Referenced from:
> /Applications/PTBatcherGUI.app/Contents/MacOS/PTBatcherGUI
>   Reason: image not found
>
>
> However if I start PTBatcherGUI and load the pto file in it does the
> stitching properly.
>
>
> --
> A list of frequently asked questions is available at:
> http://wiki.panotools.org/Hugin_FAQ
> ---
> You received this message because you are subscribed to a topic in the
> Google Groups "hugin and other free panoramic software" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/hugin-ptx/Rz-LY9isDIs/unsubscribe.
> To unsubscribe from this group and all its topics, 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/124EE48F-C33C-4457-BBB7-6A040118A71A%40accesscomm.ca
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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/CACd%3DvwAu9ck9fzYu7KsToi_%2BXH%2BWTR5pymNfW%3D1NVTZEpqstDQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


[hugin-ptx] Mac Build

2016-05-01 Thread Donald Johnston
When I try to stitch a pano from Hugin I get the following error message:
PTBatcherGUI cannot be opened because of a problem.

The error shown in the Terminal is:
PTBatcherGui check returned  value 
/Applications/PTBatcherGUI.app/Contents/MacOS/PTBatcherGUI

dyld: Library not loaded: @executable_path/../Frameworks/libpano13.3.dylib
  Referenced from: /Applications/PTBatcherGUI.app/Contents/MacOS/PTBatcherGUI
  Reason: image not found

However if I start PTBatcherGUI and load the pto file in it does the stitching 
properly.


-- 
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/124EE48F-C33C-4457-BBB7-6A040118A71A%40accesscomm.ca.
For more options, visit https://groups.google.com/d/optout.


Re: [hugin-ptx] Mac Build

2016-05-01 Thread Niklas Mischkulnig

Here you go:

iccProfile size: 2672
CorrectImage
inputICC: farbverdreht
outputICC: sRGB built-in
TYPE_RGB8: 262169
INTENT_PERCEPTUAL: 0
cmsFLAGS_BLACKPOINTCOMPENSATION: 8192
iccProfile size: 2672
CorrectImage
inputICC: farbverdreht
outputICC: sRGB built-in
TYPE_RGB8: 262169
INTENT_PERCEPTUAL: 0
cmsFLAGS_BLACKPOINTCOMPENSATION: 8192
InputICC size: 2672
size2: 2672
TexManager
inputICC:
monitorProfile:
outputICC: sRGB built-in
TYPE_RGB8: 262169
INTENT_PERCEPTUAL: 0
cmsFLAGS_BLACKPOINTCOMPENSATION: 8192

Niklas


Am Sonntag, 1. Mai 2016 19:32:05 UTC+2 schrieb T. Modes:
>
> Hi Niklas,
>
> Am Sonntag, 1. Mai 2016 18:32:16 UTC+2 schrieb Niklas Mischkulnig:
>>
>> Hi Thomas, 
>>
>> yes it shows the image with wrong colors. Is it normal, that inputICC is 
>> empty in the TexManager?
>>
>
> no, it is not normal. Good catch. 
> I was looking all the time at the output side, but the output shows 
> clearly there is something wrong on the input side.
> Can you applied the extended patch? It will print more information about 
> the input profile.
>
> Thomas
>

-- 
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/0016b08d-4f6f-41f1-9ffd-a63e95beb9a8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [hugin-ptx] Mac Build

2016-05-01 Thread T. Modes
Hi Niklas,

Am Sonntag, 1. Mai 2016 18:32:16 UTC+2 schrieb Niklas Mischkulnig:
>
> Hi Thomas, 
>
> yes it shows the image with wrong colors. Is it normal, that inputICC is 
> empty in the TexManager?
>

no, it is not normal. Good catch. 
I was looking all the time at the output side, but the output shows clearly 
there is something wrong on the input side.
Can you applied the extended patch? It will print more information about 
the input profile.

Thomas

-- 
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/e79c238b-2d5c-4f9c-8545-557b690e435a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
diff --git a/src/hugin1/base_wx/wxcms.cpp b/src/hugin1/base_wx/wxcms.cpp
--- a/src/hugin1/base_wx/wxcms.cpp
+++ b/src/hugin1/base_wx/wxcms.cpp
@@ -28,6 +28,7 @@
 #include 
 #include "hugin_utils/utils.h"
 #endif
+#include "hugin_utils/utils.h"
 
 namespace HuginBase
 {
@@ -129,6 +130,7 @@
 if (!iccProfile.empty())
 {
 inputICC = cmsOpenProfileFromMem(iccProfile.data(), iccProfile.size());
+std::cout << "iccProfile size: " << iccProfile.size() << std::endl;
 };
 // check type of input profile
 if (inputICC != NULL)
@@ -145,6 +147,13 @@
 inputICC = cmsCreate_sRGBProfile();
 };
 // now build transform
+std::cout << "CorrectImage" << std::endl
+<< "inputICC: " << hugin_utils::GetICCDesc(inputICC) << std::endl
+<< "outputICC: " << hugin_utils::GetICCDesc(monitorProfile) << std::endl
+<< "TYPE_RGB8: " << TYPE_RGB_8 << std::endl
+<< "INTENT_PERCEPTUAL: " << INTENT_PERCEPTUAL << std::endl
+<< "cmsFLAGS_BLACKPOINTCOMPENSATION: " << cmsFLAGS_BLACKPOINTCOMPENSATION << std::endl;
+
 cmsHTRANSFORM transform = cmsCreateTransform(inputICC, TYPE_RGB_8,
 monitorProfile, TYPE_RGB_8,
 INTENT_PERCEPTUAL, cmsFLAGS_BLACKPOINTCOMPENSATION);
diff --git a/src/hugin1/hugin/TextureManager.cpp b/src/hugin1/hugin/TextureManager.cpp
--- a/src/hugin1/hugin/TextureManager.cpp
+++ b/src/hugin1/hugin/TextureManager.cpp
@@ -868,6 +868,8 @@
 if (!entry->iccProfile->empty())
 {
 inputICC = cmsOpenProfileFromMem(entry->iccProfile->data(), entry->iccProfile->size());
+std::cout << "InputICC size: " << entry->iccProfile->size() << std::endl
+<< "size2: " << entry->iccProfile.get()->size() << std::endl;
 };
 cmsHTRANSFORM transform = NULL;
 // do color correction only if input image has icc profile or if we found a monitor profile
@@ -880,17 +882,26 @@
 {
 cmsCloseProfile(inputICC);
 inputICC = NULL;
+std::cout << "No RGB profile" << std::endl;
 };
 };
 // if there is no icc profile in file fall back to sRGB
 if (inputICC == NULL)
 {
 inputICC = cmsCreate_sRGBProfile();
+std::cout << "Created generic profile" << std::endl;
 };
+std::cout << "TexManager" << std::endl
+<< "inputICC: " << hugin_utils::GetICCDesc(inputICC) << std::endl
+<< "monitorProfile: " << huginApp::Get()->GetMonitorProfileName().c_str() << std::endl
+<< "outputICC: " << hugin_utils::GetICCDesc(huginApp::Get()->GetMonitorProfile()) << std::endl
+<< "TYPE_RGB8: " << TYPE_RGB_8 << std::endl
+<< "INTENT_PERCEPTUAL: " << INTENT_PERCEPTUAL << std::endl
+<< "cmsFLAGS_BLACKPOINTCOMPENSATION: " << cmsFLAGS_BLACKPOINTCOMPENSATION << std::endl;
 // now build transform
-transform = cmsCreateTransform(inputICC, TYPE_RGB_8,
+/* transform = cmsCreateTransform(inputICC, TYPE_RGB_8,
 huginApp::Get()->GetMonitorProfile(), TYPE_RGB_8,
-INTENT_PERCEPTUAL, cmsFLAGS_BLACKPOINTCOMPENSATION);
+INTENT_PERCEPTUAL, cmsFLAGS_BLACKPOINTCOMPENSATION);*/
 };
 // now perform photometric correction
 if (photometric_correct)


Re: [hugin-ptx] Mac Build

2016-05-01 Thread Niklas Mischkulnig
Hi Thomas, 

yes it shows the image with wrong colors. Is it normal, that inputICC is 
empty in the TexManager?

Niklas

Output:
CorrectImage
inputICC: farbverdreht
outputICC: sRGB built-in
TYPE_RGB8: 262169
INTENT_PERCEPTUAL: 0
cmsFLAGS_BLACKPOINTCOMPENSATION: 8192
CorrectImage
inputICC: farbverdreht
outputICC: sRGB built-in
TYPE_RGB8: 262169
INTENT_PERCEPTUAL: 0
cmsFLAGS_BLACKPOINTCOMPENSATION: 8192
TexManager
*inputICC:*
monitorProfile:
outputICC: sRGB built-in
TYPE_RGB8: 262169
INTENT_PERCEPTUAL: 0
cmsFLAGS_BLACKPOINTCOMPENSATION: 8192



Am Sonntag, 1. Mai 2016 18:11:00 UTC+2 schrieb T. Modes:
>
> Hi Niklas,
>
> Am Sonntag, 1. Mai 2016 11:58:35 UTC+2 schrieb Niklas Mischkulnig:
>>
>> still crashes.
>>
>
> That's strange.
> Could you please apply the attached patch. It will print some more 
> information to stdout like:
>
> CorrectImage
> inputICC: farbverdreht
> outputICC: sRGB built-in
> TYPE_RGB8: 262169
> INTENT_PERCEPTUAL: 0
> cmsFLAGS_BLACKPOINTCOMPENSATION: 8192
> TexManager
> inputICC: farbverdreht
> monitorProfile: 
> outputICC: sRGB built-in
> TYPE_RGB8: 262169
> INTENT_PERCEPTUAL: 0
> cmsFLAGS_BLACKPOINTCOMPENSATION: 8192
>
> It should (hopefully) not crash, but will not take the icc profile in the 
> fast preview window into account.
> And we are testing all parameters which goes to cmsCreateTransform, which 
> is the function I assume is crashing.
>
> Thomas
>

-- 
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/990c407f-5a0e-4aca-b209-2aaab7bbc3fe%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [hugin-ptx] Mac Build

2016-05-01 Thread Donald Johnston
We can do that! Thanks again Niklas for all the work (and patience) you’ve put 
into this.

I’ll do some deeper testing on Hugin and let you know if I run into anything 
else.


> On May 1, 2016, at 10:11 AM, Niklas Mischkulnig  wrote:
> 
> This is about the only error which we are trying to solve right now. The 
> problem is that a color profile is embedded inside the image; for now, you'll 
> have to make panoramas out of pictures without color profiles.
> 
> Niklas
> 
> Am Sonntag, 1. Mai 2016 18:02:15 UTC+2 schrieb Donald Johnston:
> Okay, partially works for me.  I took a RAW image from my camera and used 
> Photomatix to convert it to jpeg. I used DxO Optics pro to convert the same 
> image to tif and jpeg.
> 
> Hugin opens and displays the jpeg from Photomatix.
> 
> When I open tif or jpeg image created by DxO; hugin crashed with:
> lcms: Error #12288; Output profile is operating on wrong colorspace
> 
> Here is a link to the three files if it helps:
> 
>   
> https://www.dropbox.com/sh/4hv4giyrbnur4no/AACG2K8BPLzeuDTXcQQo2fAea?dl=0 
> 
> 
> 
> 
> 
>> On May 1, 2016, at 7:49 AM, Niklas Mischkulnig > > wrote:
>> 
>> Here is a new build, hope it works:
>> 
>> https://drive.google.com/uc?export=download=0B_seRjFxxDleU1YtQ1Zka1BXM2c 
>> 
>> 
>> Niklas
>> 
>> 
>> Am Sonntag, 1. Mai 2016 11:58:35 UTC+2 schrieb Niklas Mischkulnig:
>> Hi Thomas,
>> 
>> still crashes.
>> 
>> Niklas
>> 
>> Am Sonntag, 1. Mai 2016 08:49:43 UTC+2 schrieb T. Modes:
>> Hi Niklas,
>> 
>> Am Samstag, 30. April 2016 13:47:47 UTC+2 schrieb Niklas Mischkulnig:
>> Hey,
>> 
>> I'm sorry, I didn't see that patch couldn't apply skip_profile.diff, I had 
>> to add --ignore-whitespace. 
>> It works now(see image).
>> 
>> Sorry, 
>> Niklas
>> 
>> No problem. So we have tracked down the problem. 
>> I had an idea. I committed a changeset to the repository. Could you please 
>> test it? (But check before that all patches are removed)
>> If this does not work, I will prepare another test patch.
>> 
>> Thomas
>> 
>> 
>> -- 
>> 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/2da31ea6-78c7-415c-8b11-53edaa4c10e7%40googlegroups.com
>>  
>> .
>> For more options, visit https://groups.google.com/d/optout 
>> .
> 
> 
> -- 
> 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/cff69924-3168-4042-a241-35205183c3e0%40googlegroups.com
>  
> .
> For more options, visit https://groups.google.com/d/optout 
> .

-- 
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/A4E3601E-EC62-4B27-88B3-A424175FE45C%40accesscomm.ca.
For more options, visit https://groups.google.com/d/optout.


Re: [hugin-ptx] Mac Build

2016-05-01 Thread Niklas Mischkulnig
This is about the only error which we are trying to solve right now. The 
problem is that a color profile is embedded inside the image; for now, 
you'll have to make panoramas out of pictures without color profiles.

Niklas

Am Sonntag, 1. Mai 2016 18:02:15 UTC+2 schrieb Donald Johnston:
>
> Okay, partially works for me.  I took a RAW image from my camera and used 
> Photomatix to convert it to jpeg. I used DxO Optics pro to convert the same 
> image to tif and jpeg.
>
> Hugin opens and displays the jpeg from Photomatix.
>
> When I open tif or jpeg image created by DxO; hugin crashed with:
>
> lcms: Error #12288; Output profile is operating on wrong colorspace
>
>
> Here is a link to the three files if it helps:
>
> https://www.dropbox.com/sh/4hv4giyrbnur4no/AACG2K8BPLzeuDTXcQQo2fAea?dl=0
>
>
>
>
> On May 1, 2016, at 7:49 AM, Niklas Mischkulnig  > wrote:
>
> Here is a new build, hope it works:
>
> https://drive.google.com/uc?export=download=0B_seRjFxxDleU1YtQ1Zka1BXM2c
>
> Niklas
>
>
> Am Sonntag, 1. Mai 2016 11:58:35 UTC+2 schrieb Niklas Mischkulnig:
>>
>> Hi Thomas,
>>
>> still crashes.
>>
>> Niklas
>>
>> Am Sonntag, 1. Mai 2016 08:49:43 UTC+2 schrieb T. Modes:
>>>
>>> Hi Niklas,
>>>
>>> Am Samstag, 30. April 2016 13:47:47 UTC+2 schrieb Niklas Mischkulnig:

 Hey,

 I'm sorry, I didn't see that patch couldn't apply skip_profile.diff, I 
 had to add --ignore-whitespace. 
 It works now(see image).

 Sorry, 
 Niklas

>>>
>>> No problem. So we have tracked down the problem. 
>>> I had an idea. I committed a changeset to the repository. Could you 
>>> please test it? (But check before that all patches are removed)
>>> If this does not work, I will prepare another test patch.
>>>
>>> Thomas
>>>
>>>
> -- 
> 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/2da31ea6-78c7-415c-8b11-53edaa4c10e7%40googlegroups.com
>  
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>
>
>

-- 
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/cff69924-3168-4042-a241-35205183c3e0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [hugin-ptx] Mac Build

2016-05-01 Thread T. Modes
Hi Niklas,

Am Sonntag, 1. Mai 2016 11:58:35 UTC+2 schrieb Niklas Mischkulnig:
>
> still crashes.
>

That's strange.
Could you please apply the attached patch. It will print some more 
information to stdout like:

CorrectImage
inputICC: farbverdreht
outputICC: sRGB built-in
TYPE_RGB8: 262169
INTENT_PERCEPTUAL: 0
cmsFLAGS_BLACKPOINTCOMPENSATION: 8192
TexManager
inputICC: farbverdreht
monitorProfile: 
outputICC: sRGB built-in
TYPE_RGB8: 262169
INTENT_PERCEPTUAL: 0
cmsFLAGS_BLACKPOINTCOMPENSATION: 8192

It should (hopefully) not crash, but will not take the icc profile in the 
fast preview window into account.
And we are testing all parameters which goes to cmsCreateTransform, which 
is the function I assume is crashing.

Thomas

-- 
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/f0d72d83-184c-44e7-bb47-52be7498eecf%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
diff --git a/src/hugin1/base_wx/wxcms.cpp b/src/hugin1/base_wx/wxcms.cpp
--- a/src/hugin1/base_wx/wxcms.cpp
+++ b/src/hugin1/base_wx/wxcms.cpp
@@ -28,6 +28,7 @@
 #include 
 #include "hugin_utils/utils.h"
 #endif
+#include "hugin_utils/utils.h"
 
 namespace HuginBase
 {
@@ -145,6 +146,13 @@
 inputICC = cmsCreate_sRGBProfile();
 };
 // now build transform
+std::cout << "CorrectImage" << std::endl
+<< "inputICC: " << hugin_utils::GetICCDesc(inputICC) << std::endl
+<< "outputICC: " << hugin_utils::GetICCDesc(monitorProfile) << std::endl
+<< "TYPE_RGB8: " << TYPE_RGB_8 << std::endl
+<< "INTENT_PERCEPTUAL: " << INTENT_PERCEPTUAL << std::endl
+<< "cmsFLAGS_BLACKPOINTCOMPENSATION: " << cmsFLAGS_BLACKPOINTCOMPENSATION << std::endl;
+
 cmsHTRANSFORM transform = cmsCreateTransform(inputICC, TYPE_RGB_8,
 monitorProfile, TYPE_RGB_8,
 INTENT_PERCEPTUAL, cmsFLAGS_BLACKPOINTCOMPENSATION);
diff --git a/src/hugin1/hugin/TextureManager.cpp b/src/hugin1/hugin/TextureManager.cpp
--- a/src/hugin1/hugin/TextureManager.cpp
+++ b/src/hugin1/hugin/TextureManager.cpp
@@ -887,10 +887,17 @@
 {
 inputICC = cmsCreate_sRGBProfile();
 };
+std::cout << "TexManager" << std::endl
+<< "inputICC: " << hugin_utils::GetICCDesc(inputICC) << std::endl
+<< "monitorProfile: " << huginApp::Get()->GetMonitorProfileName().c_str() << std::endl
+<< "outputICC: " << hugin_utils::GetICCDesc(huginApp::Get()->GetMonitorProfile()) << std::endl
+<< "TYPE_RGB8: " << TYPE_RGB_8 << std::endl
+<< "INTENT_PERCEPTUAL: " << INTENT_PERCEPTUAL << std::endl
+<< "cmsFLAGS_BLACKPOINTCOMPENSATION: " << cmsFLAGS_BLACKPOINTCOMPENSATION << std::endl;
 // now build transform
-transform = cmsCreateTransform(inputICC, TYPE_RGB_8,
+/* transform = cmsCreateTransform(inputICC, TYPE_RGB_8,
 huginApp::Get()->GetMonitorProfile(), TYPE_RGB_8,
-INTENT_PERCEPTUAL, cmsFLAGS_BLACKPOINTCOMPENSATION);
+INTENT_PERCEPTUAL, cmsFLAGS_BLACKPOINTCOMPENSATION);*/
 };
 // now perform photometric correction
 if (photometric_correct)


Re: [hugin-ptx] Mac Build

2016-05-01 Thread Donald Johnston
Okay, partially works for me.  I took a RAW image from my camera and used 
Photomatix to convert it to jpeg. I used DxO Optics pro to convert the same 
image to tif and jpeg.

Hugin opens and displays the jpeg from Photomatix.

When I open tif or jpeg image created by DxO; hugin crashed with:
lcms: Error #12288; Output profile is operating on wrong colorspace

Here is a link to the three files if it helps:


https://www.dropbox.com/sh/4hv4giyrbnur4no/AACG2K8BPLzeuDTXcQQo2fAea?dl=0 





> On May 1, 2016, at 7:49 AM, Niklas Mischkulnig  wrote:
> 
> Here is a new build, hope it works:
> 
> https://drive.google.com/uc?export=download=0B_seRjFxxDleU1YtQ1Zka1BXM2c 
> 
> 
> Niklas
> 
> 
> Am Sonntag, 1. Mai 2016 11:58:35 UTC+2 schrieb Niklas Mischkulnig:
> Hi Thomas,
> 
> still crashes.
> 
> Niklas
> 
> Am Sonntag, 1. Mai 2016 08:49:43 UTC+2 schrieb T. Modes:
> Hi Niklas,
> 
> Am Samstag, 30. April 2016 13:47:47 UTC+2 schrieb Niklas Mischkulnig:
> Hey,
> 
> I'm sorry, I didn't see that patch couldn't apply skip_profile.diff, I had to 
> add --ignore-whitespace. 
> It works now(see image).
> 
> Sorry, 
> Niklas
> 
> No problem. So we have tracked down the problem. 
> I had an idea. I committed a changeset to the repository. Could you please 
> test it? (But check before that all patches are removed)
> If this does not work, I will prepare another test patch.
> 
> Thomas
> 
> 
> -- 
> 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/2da31ea6-78c7-415c-8b11-53edaa4c10e7%40googlegroups.com
>  
> .
> For more options, visit https://groups.google.com/d/optout 
> .

-- 
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/381BB6B2-9394-4F78-939A-63E6654C2367%40accesscomm.ca.
For more options, visit https://groups.google.com/d/optout.


Re: [hugin-ptx] Mac Build

2016-05-01 Thread Niklas Mischkulnig
Here is a new build, hope it works:

https://drive.google.com/uc?export=download=0B_seRjFxxDleU1YtQ1Zka1BXM2c

Niklas


Am Sonntag, 1. Mai 2016 11:58:35 UTC+2 schrieb Niklas Mischkulnig:
>
> Hi Thomas,
>
> still crashes.
>
> Niklas
>
> Am Sonntag, 1. Mai 2016 08:49:43 UTC+2 schrieb T. Modes:
>>
>> Hi Niklas,
>>
>> Am Samstag, 30. April 2016 13:47:47 UTC+2 schrieb Niklas Mischkulnig:
>>>
>>> Hey,
>>>
>>> I'm sorry, I didn't see that patch couldn't apply skip_profile.diff, I 
>>> had to add --ignore-whitespace. 
>>> It works now(see image).
>>>
>>> Sorry, 
>>> Niklas
>>>
>>
>> No problem. So we have tracked down the problem. 
>> I had an idea. I committed a changeset to the repository. Could you 
>> please test it? (But check before that all patches are removed)
>> If this does not work, I will prepare another test patch.
>>
>> Thomas
>>
>>

-- 
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/2da31ea6-78c7-415c-8b11-53edaa4c10e7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [hugin-ptx] Mac Build

2016-05-01 Thread Niklas Mischkulnig
Hi Thomas,

still crashes.

Niklas

Am Sonntag, 1. Mai 2016 08:49:43 UTC+2 schrieb T. Modes:
>
> Hi Niklas,
>
> Am Samstag, 30. April 2016 13:47:47 UTC+2 schrieb Niklas Mischkulnig:
>>
>> Hey,
>>
>> I'm sorry, I didn't see that patch couldn't apply skip_profile.diff, I 
>> had to add --ignore-whitespace. 
>> It works now(see image).
>>
>> Sorry, 
>> Niklas
>>
>
> No problem. So we have tracked down the problem. 
> I had an idea. I committed a changeset to the repository. Could you please 
> test it? (But check before that all patches are removed)
> If this does not work, I will prepare another test patch.
>
> Thomas
>
>

-- 
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/f76d4790-29c9-4783-a86d-94669a9e5899%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [hugin-ptx] Mac Build

2016-05-01 Thread T. Modes
Hi Niklas,

Am Samstag, 30. April 2016 13:47:47 UTC+2 schrieb Niklas Mischkulnig:
>
> Hey,
>
> I'm sorry, I didn't see that patch couldn't apply skip_profile.diff, I had 
> to add --ignore-whitespace. 
> It works now(see image).
>
> Sorry, 
> Niklas
>

No problem. So we have tracked down the problem. 
I had an idea. I committed a changeset to the repository. Could you please 
test it? (But check before that all patches are removed)
If this does not work, I will prepare another test patch.

Thomas

-- 
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/e3a23ec4-e5bd-423c-aadb-3dd145692511%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [hugin-ptx] Mac Build

2016-04-30 Thread Niklas Mischkulnig
Hi Thomas, 

an excerpt from system.log is attached, maybe it's helpful.
I can't really debug it, because all the debug symbols seem to be stripped, 
even though I set Xcode to not do that (see gdb.log anyway).

Niklas

Am Samstag, 30. April 2016 12:33:31 UTC+2 schrieb T. Modes:
>
> Hi Niklas,
>
> Am Samstag, 30. April 2016 12:02:32 UTC+2 schrieb Niklas Mischkulnig:
>>
>> Same as before.
>>
>
> That's strange. At least the skip_profile.diff patch has disabled all lcms 
> code in the fast preview window.
> So I don't know why it still bring the "wrong colorspace" error from lcms. 
> Can you run Hugin in a debugger so we can get more information where it 
> crashes?
> Or are there other log files which could shed some light on the issue?
>
> Thomas
>

-- 
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/c4cdcaed-922e-4b45-b8c9-1b2088b0cdb7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Apr 30 12:59:11 nmb Hugin[43467]: 0   CarbonCore  
0x7fffa12376df ___Gestalt_SystemVersion_block_invoke + 113
Apr 30 12:59:11 nmb Hugin[43467]: 1   libdispatch.dylib   
0x7fff93c9240b _dispatch_client_callout + 8
Apr 30 12:59:11 nmb Hugin[43467]: 2   libdispatch.dylib   
0x7fff93c92303 dispatch_once_f + 67
Apr 30 12:59:11 nmb Hugin[43467]: 3   CarbonCore  
0x7fffa11c3fbc _Gestalt_SystemVersion + 987
Apr 30 12:59:11 nmb Hugin[43467]: 4   CarbonCore  
0x7fffa11c37d0 Gestalt + 139
Apr 30 12:59:11 nmb Hugin[43467]: 5   libwx_osx_cocoau-3.0.0.dylib
0x000106db9b8f _Z19UMAGetSystemVersionv + 31
Apr 30 12:59:11 nmb Hugin[43467]: 6   libwx_osx_cocoau-3.0.0.dylib
0x000106e06374 _ZNK8wxWindow21MacHasScrollBarCornerEv + 228
Apr 30 12:59:16 nmb launchservicesd[82]: SecTaskLoadEntitlements failed error=22
Apr 30 12:59:24 --- last message repeated 2 times ---
Apr 30 12:59:24 nmb WindowServer[194]: Received display connect changed for 
display 0x42730c0
Apr 30 12:59:25 nmb WindowServer[194]: Found 13 modes for display 0x042730c0 
[13, 0]
Apr 30 12:59:25 nmb WindowServer[194]: Received display connect changed for 
display 0x3f003d
Apr 30 12:59:25 nmb WindowServer[194]: Found 36 modes for display 0x003f003d 
[36, 0]
Apr 30 12:59:25 nmb WindowServer[194]: Display 0x003f003d changed state to 
online
Apr 30 12:59:25 nmb WindowServer[194]: Received display connect changed for 
display 0x3f003e
Apr 30 12:59:25 nmb WindowServer[194]: Found 1 modes for display 0x003f003e [1, 
0]
Apr 30 12:59:25 nmb WindowServer[194]: Received display connect changed for 
display 0x3f003f
Apr 30 12:59:25 nmb WindowServer[194]: Found 1 modes for display 0x003f003f [1, 
0]
Apr 30 12:59:25 nmb com.apple.AmbientDisplayAgent[43479]: AmbientDisplayAgent 
started
Apr 30 12:59:25 nmb WindowServer[194]: MPServiceForDisplayDevice: Invalid 
device alias (0)
Apr 30 12:59:25 nmb WindowServer[194]: Display 0x042730c0: GL mask 0x1; bounds 
(0, 0)[1280 x 800], 13 modes available
Main, Active, on-line, enabled, built-in, boot, OpenGL-accel, Vendor 
610, Model 9cc3, S/N 0, Unit 0, Rotation 0
UUID 0x68fe312b5ef0e0a1bcd88890b73c7b3a, ColorSpace { -1469449337 }
Apr 30 12:59:25 nmb WindowServer[194]: GLCompositor: GL renderer id 0x01024301, 
GL mask 0x001f, accelerator 0x41db, unit 0, caps QEX|MIPMAP, vram 451 MB
texture max 8192, viewport max {8192, 8192}, extensions NPOT|GLSL|FLOAT
Apr 30 12:59:25 nmb WindowServer[194]: Display 0x003f0040: GL mask 0x10; bounds 
(2304, 0)[1 x 1], 2 modes available
off-line, enabled, OpenGL-accel, Vendor , Model , S/N 
, Unit 4, Rotation 0
UUID 0x
Apr 30 12:59:25 nmb WindowServer[194]: GLCompositor: GL renderer id 0x01024301, 
GL mask 0x001f, accelerator 0x41db, unit 0, caps QEX|MIPMAP, vram 451 MB
texture max 8192, viewport max {8192, 8192}, extensions NPOT|GLSL|FLOAT
Apr 30 12:59:25 nmb WindowServer[194]: Display 0x003f003f: GL mask 0x8; bounds 
(2305, 0)[1 x 1], 1 modes available
off-line, enabled, Vendor , Model , S/N , Unit 
3, Rotation 0
UUID 0x
Apr 30 12:59:25 nmb WindowServer[194]: Display 0x003f003e: GL mask 0x4; bounds 
(2306, 0)[1 x 1], 1 modes available
off-line, enabled, Vendor , Model , S/N , Unit 
2, Rotation 0
UUID 0x
Apr 30 12:59:25 nmb WindowServer[194]: Display 0x0b42ec39: GL mask 0x2; bounds 
(1280, 0)[1920 x 1080], 36 modes 

Re: [hugin-ptx] Mac Build

2016-04-30 Thread T. Modes
Hi Niklas,

Am Samstag, 30. April 2016 12:02:32 UTC+2 schrieb Niklas Mischkulnig:
>
> Same as before.
>

That's strange. At least the skip_profile.diff patch has disabled all lcms 
code in the fast preview window.
So I don't know why it still bring the "wrong colorspace" error from lcms. 
Can you run Hugin in a debugger so we can get more information where it 
crashes?
Or are there other log files which could shed some light on the issue?

Thomas

-- 
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/db1456ef-30cc-43c7-a7a2-ade1d9da46bf%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [hugin-ptx] Mac Build

2016-04-30 Thread Niklas Mischkulnig
Same as before.

Niklas

Am Freitag, 29. April 2016 17:01:32 UTC+2 schrieb T. Modes:
>
> Hi Niklas,
>
> Am Freitag, 29. April 2016 13:00:40 UTC+2 schrieb Niklas Mischkulnig:
>>
>> Unfortunately neither is working.
>>
>
> That's strange. Maybe we need to locate the error more precise. I'm 
> attaching 2 patches.
> Please apply only one at once. If none of the both files prevents the 
> crashes, I have searched at the wrong place.
>
> Thomas
>

-- 
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/8830f5a6-b0e7-424d-8238-e195a9e319c8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [hugin-ptx] Mac Build

2016-04-29 Thread T. Modes
Hi Niklas,

Am Freitag, 29. April 2016 13:00:40 UTC+2 schrieb Niklas Mischkulnig:
>
> Unfortunately neither is working.
>

That's strange. Maybe we need to locate the error more precise. I'm 
attaching 2 patches.
Please apply only one at once. If none of the both files prevents the 
crashes, I have searched at the wrong place.

Thomas

-- 
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/e769c463-11e9-4d8b-a1d5-7acda94c6e28%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
diff --git a/src/hugin1/hugin/TextureManager.cpp b/src/hugin1/hugin/TextureManager.cpp
--- a/src/hugin1/hugin/TextureManager.cpp
+++ b/src/hugin1/hugin/TextureManager.cpp
@@ -936,23 +936,23 @@
 hugin_utils::FDiff2D(sx, sy));
 }
 // now take color profiles in file and of monitor into account
-if (transform != NULL)
+/* if (transform != NULL)
 {
 cmsDoTransform(transform, out_img[y], out_img[y], out_img.width());
-};
+};*/
 }
 }
 else
 {
 // no photometric correction
-if (transform != NULL)
+/* if (transform != NULL)
 {
 #pragma omp parallel for
 for (int y = 0; y < ho; y++)
 {
 cmsDoTransform(transform, out_img[y], out_img[y], out_img.width());
 };
-};
+};*/
 };
 if (transform != NULL)
 {
diff --git a/src/hugin1/hugin/TextureManager.cpp b/src/hugin1/hugin/TextureManager.cpp
--- a/src/hugin1/hugin/TextureManager.cpp
+++ b/src/hugin1/hugin/TextureManager.cpp
@@ -871,7 +871,7 @@
 };
 cmsHTRANSFORM transform = NULL;
 // do color correction only if input image has icc profile or if we found a monitor profile
-if (inputICC != NULL || huginApp::Get()->HasMonitorProfile())
+/* if (inputICC != NULL || huginApp::Get()->HasMonitorProfile())
 {
 // check input profile
 if (inputICC != NULL)
@@ -891,7 +891,7 @@
 transform = cmsCreateTransform(inputICC, TYPE_RGB_8,
 huginApp::Get()->GetMonitorProfile(), TYPE_RGB_8,
 INTENT_PERCEPTUAL, cmsFLAGS_BLACKPOINTCOMPENSATION);
-};
+};*/
 // now perform photometric correction
 if (photometric_correct)
 {


Re: [hugin-ptx] Mac Build

2016-04-29 Thread Niklas Mischkulnig
Unfortunately neither is working.

Am Donnerstag, 28. April 2016 21:13:46 UTC+2 schrieb T. Modes:
>
>
>
> Am Donnerstag, 28. April 2016 19:59:12 UTC+2 schrieb Niklas Mischkulnig:
>>
>> Hi Thomas,
>>
>> nope, that doesn't change anything.
>> But I found out, that it works in the non-OpenGL preview window (see 
>> screenshot)
>>
> That's a good news. That means that at least the internal profile is okay.
> I have attached 2 variants for testing. Both are using different 
> approaches. Hopefully one is working now.
>
> Thomas
>

-- 
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/4e905cb0-3073-4e5b-aa43-242d615c0a10%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [hugin-ptx] Mac Build

2016-04-28 Thread T. Modes


Am Donnerstag, 28. April 2016 19:59:12 UTC+2 schrieb Niklas Mischkulnig:
>
> Hi Thomas,
>
> nope, that doesn't change anything.
> But I found out, that it works in the non-OpenGL preview window (see 
> screenshot)
>
That's a good news. That means that at least the internal profile is okay.
I have attached 2 variants for testing. Both are using different 
approaches. Hopefully one is working now.

Thomas

-- 
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/fb87a7eb-10e8-4fd8-9d45-96740784da5a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
diff --git a/src/hugin1/hugin/TextureManager.cpp b/src/hugin1/hugin/TextureManager.cpp
--- a/src/hugin1/hugin/TextureManager.cpp
+++ b/src/hugin1/hugin/TextureManager.cpp
@@ -938,7 +938,7 @@
 // now take color profiles in file and of monitor into account
 if (transform != NULL)
 {
-cmsDoTransform(transform, out_img[y], out_img[y], out_img.width());
+cmsDoTransform(transform, out_img.rowBegin(y), out_img.rowBegin(y), out_img.width());
 };
 }
 }
@@ -950,7 +950,7 @@
 #pragma omp parallel for
 for (int y = 0; y < ho; y++)
 {
-cmsDoTransform(transform, out_img[y], out_img[y], out_img.width());
+cmsDoTransform(transform, out_img.rowBegin(y), out_img.rowBegin(y), out_img.width());
 };
 };
 };
diff --git a/src/hugin1/hugin/TextureManager.cpp b/src/hugin1/hugin/TextureManager.cpp
--- a/src/hugin1/hugin/TextureManager.cpp
+++ b/src/hugin1/hugin/TextureManager.cpp
@@ -934,12 +934,19 @@
 sy = (double)y * scale_y;
 out_img[y][x] = invResponse(out_img[y][x],
 hugin_utils::FDiff2D(sx, sy));
+if (transform != NULL)
+{
+vigra::UInt8 rgb[3];
+rgb[0] = out_img[y][x].red();
+rgb[1] = out_img[y][x].green();
+rgb[2] = out_img[y][x].blue();
+cmsDoTransform(transform, , , 1);
+out_img[y][x] = vigra::RGBValue(rgb[0], rgb[1], rgb[2]);
+}
+else
+{
+};
 }
-// now take color profiles in file and of monitor into account
-if (transform != NULL)
-{
-cmsDoTransform(transform, out_img[y], out_img[y], out_img.width());
-};
 }
 }
 else
@@ -950,7 +957,15 @@
 #pragma omp parallel for
 for (int y = 0; y < ho; y++)
 {
-cmsDoTransform(transform, out_img[y], out_img[y], out_img.width());
+for (int x = 0; x < wo; x++)
+{
+vigra::UInt8 rgb[3];
+rgb[0] = out_img[y][x].red();
+rgb[1] = out_img[y][x].green();
+rgb[2] = out_img[y][x].blue();
+cmsDoTransform(transform, , , 1);
+out_img[y][x] = vigra::RGBValue(rgb[0], rgb[1], rgb[2]);
+};
 };
 };
 };


Re: [hugin-ptx] Mac Build

2016-04-28 Thread T. Modes
Hi Niklas,

Am Mittwoch, 27. April 2016 19:33:59 UTC+2 schrieb T. Modes:
>
>
>
> Am Mittwoch, 27. April 2016 19:32:15 UTC+2 schrieb Niklas Mischkulnig:
>>
>> I am working on the library errors, but compiling all dependencies will 
>> take a while.
>>
>> Here:
>>
>> 19:29:31: Created sRGB profile
>> 19:29:31: Profile: sRGB built-in
>> 19:29:31: Colorspace: RGB
>>
>
> That looks okay. I will have to search further.
>

Maybe in some Mac OS header conflict with our implementation.
Could you please test the attached patch?

Thomas 

-- 
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/ed1041de-1c9a-4220-ba60-042fffc9f49c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
diff --git a/src/hugin1/hugin/TextureManager.cpp b/src/hugin1/hugin/TextureManager.cpp
--- a/src/hugin1/hugin/TextureManager.cpp
+++ b/src/hugin1/hugin/TextureManager.cpp
@@ -61,6 +61,8 @@
 #include "exiv2/exiv2.hpp"
 #include "exiv2/preview.hpp"
 
+#define TYPE_RGB_8 (COLORSPACE_SH(PT_RGB)|CHANNELS_SH(3)|BYTES_SH(1))
+
 TextureManager::TextureManager(HuginBase::Panorama *pano, ViewState *view_state_in)
 {
 m_pano = pano;


Re: [hugin-ptx] Mac Build

2016-04-27 Thread T. Modes


Am Mittwoch, 27. April 2016 19:32:15 UTC+2 schrieb Niklas Mischkulnig:
>
> I am working on the library errors, but compiling all dependencies will 
> take a while.
>
> Here:
>
> 19:29:31: Created sRGB profile
> 19:29:31: Profile: sRGB built-in
> 19:29:31: Colorspace: RGB
>

That looks okay. I will have to search further.

-- 
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/8bdb8a05-feee-4ca6-b3a2-3d1734a7fb44%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [hugin-ptx] Mac Build

2016-04-27 Thread Niklas Mischkulnig
I am working on the library errors, but compiling all dependencies will 
take a while.

Here:

19:29:31: Created sRGB profile
19:29:31: Profile: sRGB built-in
19:29:31: Colorspace: RGB


Am Mittwoch, 27. April 2016 18:29:22 UTC+2 schrieb T. Modes:
>
> Hi Niklas,
>
> Am Mittwoch, 27. April 2016 17:47:29 UTC+2 schrieb Niklas Mischkulnig:
>>
>> Crashes instantly on step 2.) after closing the dialog.
>>
>
> I feared this. But this excludes some issues.
> Can you please apply the attached patch with some more diagnostic output.
>
> When starting Hugin you should get a message box with some more 
> information (you may expand the box).
> It should print something like:
> 18:26:30: Created sRGB profile
> 18:26:30: Profile: sRGB built-in
> 18:26:30: Colorspace: RGB
>
> Thanks,
>
> Thomas
>
>

-- 
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/9b749075-8c81-4553-a8fd-6b8cef3bda05%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [hugin-ptx] Mac Build

2016-04-27 Thread Donald Johnston
Niclas, I get the same error with the new build:

> dyld: Library not loaded: 
> /Users/niklas/development/test/mac/ExternalPrograms/repository/lib/libasprintf.0.dylib
>   Referenced from: /Applications/Hugin/Hugin.app/Contents/MacOS/hugin
>   Reason: image not found
> Trace/BPT trap: 5


And here is the detailed report if it helps …

Process:   hugin [2715]
Path:  /Applications/Hugin/Hugin.app/Contents/MacOS/Hugin
Identifier:hugin
Version:   ???
Code Type: X86-64 (Native)
Parent Process:bash [1995]
Responsible:   Terminal [1993]
User ID:   501

Date/Time: 2016-04-27 10:54:35.398 -0600
OS Version:Mac OS X 10.11.4 (15E65)
Report Version:11
Anonymous UUID:A8B1503F-C972-23E6-559F-F8074FE4989B

Sleep/Wake UUID:   01B2B422-9831-4A0E-BF52-CCED392577BB

Time Awake Since Boot: 7400 seconds
Time Since Wake:   2400 seconds

System Integrity Protection: enabled

Crashed Thread:0

Exception Type:EXC_BREAKPOINT (SIGTRAP)
Exception Codes:   0x0002, 0x

Application Specific Information:
dyld: launch, loading dependent libraries

Dyld Error Message:
  Library not loaded: 
/Users/niklas/development/test/mac/ExternalPrograms/repository/lib/libasprintf.0.dylib
  Referenced from: /Applications/Hugin/Hugin.app/Contents/MacOS/hugin
  Reason: image not found

Binary Images:
0x7fff65f5f000 - 0x7fff65f960d7  dyld (360.21) 
 /usr/lib/dyld
0x7fff933a8000 - 0x7fff9349aff7  libiconv.2.dylib (44) 
 /usr/lib/libiconv.2.dylib

Model: MacBookPro9,1, BootROM MBP91.00D3.B0D, 4 processors, Intel Core i7, 2.6 
GHz, 8 GB, SMC 2.1f175
Graphics: Intel HD Graphics 4000, Intel HD Graphics 4000, Built-In
Graphics: NVIDIA GeForce GT 650M, NVIDIA GeForce GT 650M, PCIe, 1024 MB
Memory Module: BANK 0/DIMM0, 4 GB, DDR3, 1600 MHz, 0x80AD, 
0x484D54333531533643465238432D50422020
Memory Module: BANK 1/DIMM0, 4 GB, DDR3, 1600 MHz, 0x80AD, 
0x484D54333531533643465238432D50422020
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0xF5), Broadcom 
BCM43xx 1.0 (7.21.95.175.1a6)
Bluetooth: Version 4.4.4f4 17685, 3 services, 19 devices, 1 incoming serial 
ports
Network Service: Wi-Fi, AirPort, en1
Serial ATA Device: APPLE HDD HTS541010A9E682, 1 TB
Serial ATA Device: HL-DT-ST DVDRW  GS31N
USB Device: USB 2.0 Bus
USB Device: Hub
USB Device: FaceTime HD Camera (Built-in)
USB Device: USB 2.0 Bus
USB Device: Hub
USB Device: Hub
USB Device: Apple Internal Keyboard / Trackpad
USB Device: IR Receiver
USB Device: BRCM20702 Hub
USB Device: Bluetooth USB Host Controller
USB Device: USB 3.0 Bus
Thunderbolt Bus: MacBook Pro, Apple Inc., 25.1






> On Apr 27, 2016, at 9:08 AM, Alexandr Krylovskiy 
>  wrote:
> 
> Unfortunately I can't launch the new build:
> > ./Hugin
> dyld: Library not loaded: 
> /Users/niklas/development/test/mac/ExternalPrograms/repository/lib/libasprintf.0.dylib
>   Referenced from: 
> /Users/krylovskiy/distr/photo/Hugin/Hugin.app/Contents/MacOS/./Hugin
>   Reason: image not found
> zsh: trace trap  ./Hugin
> 
> On Wednesday, April 27, 2016 at 3:34:35 PM UTC+2, Niklas Mischkulnig wrote:
> Here is a new build which correctly finds enblend and ExifTool in 
> PTBatcherGui.app, though the colorspace error still happens.
> 
> https://drive.google.com/uc?export=download=0B_seRjFxxDleU1YtQ1Zka1BXM2c 
> 
> 
> Niklas
> 
> 
> Am Dienstag, 26. April 2016 18:51:29 UTC+2 schrieb Donald Johnston:
> Thomas, I use a display profile created by Spyder4Pro.  The contents of the 
> system tab from Hugin are:
> 
> Operating System: Mac OS X (Darwin 15.4.0 x86_64)
> Architecture: 64 bit
> Free memory: 0 kiB
> 
> Hugin
> Version: 2016.1.0 built by Niklas Mischkulnig
> Path to resources: /Applications/Hugin_2016/Hugin.app/Contents/Resources/xrc/
> Path to data: /Applications/Hugin_2016/Hugin.app/Contents/Resources/xrc/
> Hugins camera and lens database: /Users/donaldjohnston/.hugindata/camlens.db
> Multi-threading using C++11 std::thread and OpenMP
> 
> Libraries
> wxWidgets: wxWidgets 3.0.2
> wxWidgets Library (wxMac port)
> Version 3.0.2 (Unicode: wchar_t, debug level: 0),
> compiled at Apr 17 2016 17:11:02
> 
> Runtime version of toolkit used is 10.11.
> 
> libpano13: 2.9.19 
> Boost: 1.60.0
> Exiv2: 0.25
> SQLite3: 3.8.10.2
> Vigra: 1.10.0
> LittleCMS2: 2.7
> 
> So I see no mention of a profile but I’ve attached the icc profile I use.
> 
> 
> -- 
> 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 
> 

Re: [hugin-ptx] Mac Build

2016-04-27 Thread Donald Johnston
I tried both to “cancel” the dialog box and to enter “50” and both ways it only 
crashes at step 6.

> On Apr 27, 2016, at 9:47 AM, Niklas Mischkulnig  wrote:
> 
> Crashes instantly on step 2.) after closing the dialog.
> 
> Am Mittwoch, 27. April 2016 17:37:55 UTC+2 schrieb T. Modes:
> 
> 
> Am Mittwoch, 27. April 2016 15:34:35 UTC+2 schrieb Niklas Mischkulnig:
> Here is a new build which correctly finds enblend and ExifTool in 
> PTBatcherGui.app, though the colorspace error still happens.
> 
> Concerning the colorspace error, can somebody please test the following:
> 
> 1.) Save the jpg from http://fotovideotec.de/browser_farbmanagement/ 
>  (sorry, the image is german, 
> but I found no english version)
> 2.) Load the image in Hugin (it will ask for the HFOV, simply use 50 deg or 
> cancel the dialog, it does not matter)
> 3.) Select the image on the photo tab -> Is is correctly displayed (blue sky, 
> yellow-green tree) or displayed with wrong colors or does Hugin crash?
> 
> If Hugin does not crash, continue
> 4.) Go to the control points tab -> Is the image displayed with correct 
> colors or with wrong colors?
> 5.) The same on the mask tab -> Is the image displayed with correct colors or 
> with wrong colors?
> 6.) Now open the fast preview windows -> Does it crash now? Or is the image 
> displayed with correct/wrong colors?
> 
> Thanks
> 
> -- 
> 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/57809224-b7b1-4b63-b544-494d4399f87b%40googlegroups.com
>  
> .
> For more options, visit https://groups.google.com/d/optout 
> .

-- 
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/805E7695-62E2-4923-8F3B-6E89EC7DC59A%40accesscomm.ca.
For more options, visit https://groups.google.com/d/optout.


Re: [hugin-ptx] Mac Build

2016-04-27 Thread Donald Johnston
3) it looks the same on the photos tab as it does on the web site.
4) good
5) good
6) crash

lcms: Error #12288; Output profile is operating on wrong colorspace


> On Apr 27, 2016, at 9:37 AM, T. Modes  wrote:
> 
> 
> 
> Am Mittwoch, 27. April 2016 15:34:35 UTC+2 schrieb Niklas Mischkulnig:
> Here is a new build which correctly finds enblend and ExifTool in 
> PTBatcherGui.app, though the colorspace error still happens.
> 
> Concerning the colorspace error, can somebody please test the following:
> 
> 1.) Save the jpg from http://fotovideotec.de/browser_farbmanagement/ (sorry, 
> the image is german, but I found no english version)
> 2.) Load the image in Hugin (it will ask for the HFOV, simply use 50 deg or 
> cancel the dialog, it does not matter)
> 3.) Select the image on the photo tab -> Is is correctly displayed (blue sky, 
> yellow-green tree) or displayed with wrong colors or does Hugin crash?
> 
> If Hugin does not crash, continue
> 4.) Go to the control points tab -> Is the image displayed with correct 
> colors or with wrong colors?
> 5.) The same on the mask tab -> Is the image displayed with correct colors or 
> with wrong colors?
> 6.) Now open the fast preview windows -> Does it crash now? Or is the image 
> displayed with correct/wrong colors?
> 
> Thanks
> 
> -- 
> 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/395956d4-6953-4c39-bdda-222a58db0e15%40googlegroups.com
>  
> .
> For more options, visit https://groups.google.com/d/optout 
> .

-- 
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/0F7B1DC6-0DD1-41FD-A70B-0FB922F6E577%40accesscomm.ca.
For more options, visit https://groups.google.com/d/optout.


Re: [hugin-ptx] Mac Build

2016-04-27 Thread Niklas Mischkulnig
Crashes instantly on step 2.) after closing the dialog.

Am Mittwoch, 27. April 2016 17:37:55 UTC+2 schrieb T. Modes:
>
>
>
> Am Mittwoch, 27. April 2016 15:34:35 UTC+2 schrieb Niklas Mischkulnig:
>>
>> Here is a new build which correctly finds enblend and ExifTool in 
>> PTBatcherGui.app, though the colorspace error still happens.
>>
>
> Concerning the colorspace error, can somebody please test the following:
>
> 1.) Save the jpg from http://fotovideotec.de/browser_farbmanagement/ 
> (sorry, the image is german, but I found no english version)
> 2.) Load the image in Hugin (it will ask for the HFOV, simply use 50 deg 
> or cancel the dialog, it does not matter)
> 3.) Select the image on the photo tab -> Is is correctly displayed (blue 
> sky, yellow-green tree) or displayed with wrong colors or does Hugin crash?
>
> If Hugin does not crash, continue
> 4.) Go to the control points tab -> Is the image displayed with correct 
> colors or with wrong colors?
> 5.) The same on the mask tab -> Is the image displayed with correct colors 
> or with wrong colors?
> 6.) Now open the fast preview windows -> Does it crash now? Or is the 
> image displayed with correct/wrong colors?
>
> Thanks
>

-- 
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/57809224-b7b1-4b63-b544-494d4399f87b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [hugin-ptx] Mac Build

2016-04-27 Thread T. Modes


Am Mittwoch, 27. April 2016 15:34:35 UTC+2 schrieb Niklas Mischkulnig:
>
> Here is a new build which correctly finds enblend and ExifTool in 
> PTBatcherGui.app, though the colorspace error still happens.
>

Concerning the colorspace error, can somebody please test the following:

1.) Save the jpg from http://fotovideotec.de/browser_farbmanagement/ 
(sorry, the image is german, but I found no english version)
2.) Load the image in Hugin (it will ask for the HFOV, simply use 50 deg or 
cancel the dialog, it does not matter)
3.) Select the image on the photo tab -> Is is correctly displayed (blue 
sky, yellow-green tree) or displayed with wrong colors or does Hugin crash?

If Hugin does not crash, continue
4.) Go to the control points tab -> Is the image displayed with correct 
colors or with wrong colors?
5.) The same on the mask tab -> Is the image displayed with correct colors 
or with wrong colors?
6.) Now open the fast preview windows -> Does it crash now? Or is the image 
displayed with correct/wrong colors?

Thanks

-- 
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/395956d4-6953-4c39-bdda-222a58db0e15%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [hugin-ptx] Mac Build

2016-04-27 Thread Alexandr Krylovskiy
Unfortunately I can't launch the new build:
> ./Hugin
dyld: Library not loaded: 
/Users/niklas/development/test/mac/ExternalPrograms/repository/lib/libasprintf.0.dylib
  Referenced from: 
/Users/krylovskiy/distr/photo/Hugin/Hugin.app/Contents/MacOS/./Hugin
  Reason: image not found
zsh: trace trap  ./Hugin

On Wednesday, April 27, 2016 at 3:34:35 PM UTC+2, Niklas Mischkulnig wrote:
>
> Here is a new build which correctly finds enblend and ExifTool in 
> PTBatcherGui.app, though the colorspace error still happens.
>
> https://drive.google.com/uc?export=download=0B_seRjFxxDleU1YtQ1Zka1BXM2c
>
> Niklas
>
>
> Am Dienstag, 26. April 2016 18:51:29 UTC+2 schrieb Donald Johnston:
>>
>> Thomas, I use a display profile created by Spyder4Pro.  The contents of 
>> the system tab from Hugin are:
>>
>> Operating System: Mac OS X (Darwin 15.4.0 x86_64)
>> Architecture: 64 bit
>> Free memory: 0 kiB
>>
>> Hugin
>> Version: 2016.1.0 built by Niklas Mischkulnig
>> Path to resources: 
>> /Applications/Hugin_2016/Hugin.app/Contents/Resources/xrc/
>> Path to data: /Applications/Hugin_2016/Hugin.app/Contents/Resources/xrc/
>> Hugins camera and lens database: 
>> /Users/donaldjohnston/.hugindata/camlens.db
>> Multi-threading using C++11 std::thread and OpenMP
>>
>> Libraries
>> wxWidgets: wxWidgets 3.0.2
>> wxWidgets Library (wxMac port)
>> Version 3.0.2 (Unicode: wchar_t, debug level: 0),
>> compiled at Apr 17 2016 17:11:02
>>
>> Runtime version of toolkit used is 10.11.
>>
>> libpano13: 2.9.19 
>> Boost: 1.60.0
>> Exiv2: 0.25
>> SQLite3: 3.8.10.2
>> Vigra: 1.10.0
>> LittleCMS2: 2.7
>>
>>
>> So I see no mention of a profile but I’ve attached the icc profile I use.
>>
>>

-- 
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/18ce314d-59ad-4056-a6b1-7fd3bd35c08a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [hugin-ptx] Mac Build

2016-04-27 Thread Niklas Mischkulnig
Here is a new build which correctly finds enblend and ExifTool in 
PTBatcherGui.app, though the colorspace error still happens.

https://drive.google.com/uc?export=download=0B_seRjFxxDleU1YtQ1Zka1BXM2c

Niklas


Am Dienstag, 26. April 2016 18:51:29 UTC+2 schrieb Donald Johnston:
>
> Thomas, I use a display profile created by Spyder4Pro.  The contents of 
> the system tab from Hugin are:
>
> Operating System: Mac OS X (Darwin 15.4.0 x86_64)
> Architecture: 64 bit
> Free memory: 0 kiB
>
> Hugin
> Version: 2016.1.0 built by Niklas Mischkulnig
> Path to resources: 
> /Applications/Hugin_2016/Hugin.app/Contents/Resources/xrc/
> Path to data: /Applications/Hugin_2016/Hugin.app/Contents/Resources/xrc/
> Hugins camera and lens database: 
> /Users/donaldjohnston/.hugindata/camlens.db
> Multi-threading using C++11 std::thread and OpenMP
>
> Libraries
> wxWidgets: wxWidgets 3.0.2
> wxWidgets Library (wxMac port)
> Version 3.0.2 (Unicode: wchar_t, debug level: 0),
> compiled at Apr 17 2016 17:11:02
>
> Runtime version of toolkit used is 10.11.
>
> libpano13: 2.9.19 
> Boost: 1.60.0
> Exiv2: 0.25
> SQLite3: 3.8.10.2
> Vigra: 1.10.0
> LittleCMS2: 2.7
>
>
> So I see no mention of a profile but I’ve attached the icc profile I use.
>
>

-- 
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/df5a4f63-0aa3-4036-b3f7-58a902f3975a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [hugin-ptx] Mac Build

2016-04-26 Thread Donald Johnston
Thomas, I use a display profile created by Spyder4Pro.  The contents of the system tab from Hugin are:Operating System: Mac OS X (Darwin 15.4.0 x86_64)Architecture: 64 bitFree memory: 0 kiBHuginVersion: 2016.1.0 built by Niklas MischkulnigPath to resources: /Applications/Hugin_2016/Hugin.app/Contents/Resources/xrc/Path to data: /Applications/Hugin_2016/Hugin.app/Contents/Resources/xrc/Hugins camera and lens database: /Users/donaldjohnston/.hugindata/camlens.dbMulti-threading using C++11 std::thread and OpenMPLibrarieswxWidgets: wxWidgets 3.0.2wxWidgets Library (wxMac port)Version 3.0.2 (Unicode: wchar_t, debug level: 0),compiled at Apr 17 2016 17:11:02Runtime version of toolkit used is 10.11.libpano13: 2.9.19 Boost: 1.60.0Exiv2: 0.25SQLite3: 3.8.10.2Vigra: 1.10.0LittleCMS2: 2.7So I see no mention of a profile but I’ve attached the icc profile I use.



-- 
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/48C2B989-58FA-4D1A-9366-5A17F1507456%40accesscomm.ca.
For more options, visit https://groups.google.com/d/optout.


DGJ MacBook Pro
Description: Binary data
On Apr 26, 2016, at 1:12 AM, T. Modes  wrote:Am Montag, 25. April 2016 21:50:44 UTC+2 schrieb Niklas Mischkulnig:I first noticed that error, when converting the raw images from Sukima's workflow thread to jpg using Adobe Camera Raw, the converted images are attached (in sRGB and AdobeRGB, though both cause the same error)lcms: Error #12288; Output profile is operating on wrong colorspaceAll affected files contains an icc profile. But I don't get an error.Can you check if Hugin has found a monitor profile? (Go to about screen, tab system, is there a line "Monitor profile:.."? If yes, please provide the file mentioned here.)Thomas

-- 
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/a7cff23c-8da6-4d1d-93a0-3ad150a5dfa5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.




-- 
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/48C2B989-58FA-4D1A-9366-5A17F1507456%40accesscomm.ca.
For more options, visit https://groups.google.com/d/optout.


Re: [hugin-ptx] Mac Build

2016-04-26 Thread Niklas Mischkulnig
 

Everything seems to be working now.

In patch-xrc.sh, I had to change line 12 to hugin_exiftool_arg=
"../src/hugin1/base_wx/hugin_exiftool_copy.arg"


*bash:*

INFO 18:43:49.061780 
(/Users/niklas/development/clean/src/hugin1/base_wx/platform.cpp:290) 
MacGetPathToBundledResourceFile(): Mac: the resource file's path in the 
application bundle: 
/Users/niklas/development/clean/mac/build/Release/PTBatcherGUI.app/Contents/Resources/xrc

INFO 18:43:49.062303 
(/Users/niklas/development/clean/src/hugin1/base_wx/platform.cpp:290) 
MacGetPathToBundledResourceFile(): Mac: the resource file's path in the 
application bundle: 
/Users/niklas/development/clean/mac/build/Release/PTBatcherGUI.app/Contents/Resources/de.lproj/locale

INFO 18:43:59.837025 
(/Users/niklas/development/clean/src/hugin1/base_wx/platform.cpp:375) 
MacGetPathToBundledExecutableFile(): Mac: executable's full path in the 
application bundle: 
/Users/niklas/development/clean/mac/build/Release/PTBatcherGUI.app/Contents/MacOS/enblend

Filename for 
enblend=/Users/niklas/development/clean/mac/build/Release/PTBatcherGUI.app/Contents/MacOS/enblend

INFO 18:43:59.837742 
(/Users/niklas/development/clean/src/hugin1/base_wx/platform.cpp:375) 
MacGetPathToBundledExecutableFile(): Mac: executable's full path in the 
application bundle: 
/Users/niklas/development/clean/mac/build/Release/PTBatcherGUI.app/Contents/MacOS/enblend

Filename for 
enblend=/Users/niklas/development/clean/mac/build/Release/PTBatcherGUI.app/Contents/MacOS/enblend

INFO 18:44:00.089661 
(/Users/niklas/development/clean/src/hugin1/base_wx/platform.cpp:290) 
MacGetPathToBundledResourceFile(): Mac: the resource file's path in the 
application bundle: 
/Users/niklas/development/clean/mac/build/Release/PTBatcherGUI.app/Contents/Resources/ExifTool

ExifTool, path to bundled res: 
/Users/niklas/development/clean/mac/build/Release/PTBatcherGUI.app/Contents/Resources/ExifTool

INFO 18:44:00.090335 
(/Users/niklas/development/clean/src/hugin1/base_wx/platform.cpp:290) 
MacGetPathToBundledResourceFile(): Mac: the resource file's path in the 
application bundle: 
/Users/niklas/development/clean/mac/build/Release/PTBatcherGUI.app/Contents/Resources/ExifTool

ExifTool, path to bundled res: 
/Users/niklas/development/clean/mac/build/Release/PTBatcherGUI.app/Contents/Resources/ExifTool

INFO 18:44:01.490650 
(/Users/niklas/development/clean/src/hugin1/base_wx/platform.cpp:375) 
MacGetPathToBundledExecutableFile(): Mac: executable's full path in the 
application bundle: 
/Users/niklas/development/clean/mac/build/Release/PTBatcherGUI.app/Contents/MacOS/nona

INFO 18:44:01.491851 
(/Users/niklas/development/clean/src/hugin1/base_wx/platform.cpp:375) 
MacGetPathToBundledExecutableFile(): Mac: executable's full path in the 
application bundle: 
/Users/niklas/development/clean/mac/build/Release/PTBatcherGUI.app/Contents/MacOS/enblend

Filename for 
enblend=/Users/niklas/development/clean/mac/build/Release/PTBatcherGUI.app/Contents/MacOS/enblend

INFO 18:44:01.492607 
(/Users/niklas/development/clean/src/hugin1/base_wx/platform.cpp:290) 
MacGetPathToBundledResourceFile(): Mac: the resource file's path in the 
application bundle: 
/Users/niklas/development/clean/mac/build/Release/PTBatcherGUI.app/Contents/Resources/ExifTool

ExifTool, path to bundled res: 
/Users/niklas/development/clean/mac/build/Release/PTBatcherGUI.app/Contents/Resources/ExifTool


*log:*

enblend: 
/Users/niklas/development/clean/mac/build/Release/PTBatcherGUI.app/Contents/MacOS/enblend

Blender: enblend 4.1.1

exiftool: 
/Users/niklas/development/clean/mac/build/Release/PTBatcherGUI.app/Contents/Resources/ExifTool/exiftool

ExifTool version: 9.76




Am Dienstag, 26. April 2016 18:22:50 UTC+2 schrieb T. Modes:
>
>
>
> Am Dienstag, 26. April 2016 17:46:23 UTC+2 schrieb Niklas Mischkulnig:
>>
>> I found the reason: In Xcode when I set the MAC_SELF_CONTAINED_BUNDLE 
>> flag, it applies it recursively to all other targets, *except* base_wx.
>>
>> I attached the compile errors in Executor.cpp.
>>
>
> Okay, we make progress. Mainly a simply include was missing.
> I committed the changes to the repository.
> Attached is a modified patch. It contains both former patches and some 
> little bugfixes from your last report.
>
> Thomas
>

-- 
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/e5f54b19-8137-4633-b81c-850b20af8b54%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [hugin-ptx] Mac Build

2016-04-26 Thread Alexandr Krylovskiy
Please disregard my previous E-mail, I've missed the third page of the 
thread.
There is no "Monitor profile: " line on my machine either (13'' macbook pro 
retina 2013 running 10.11.4)

On Tuesday, April 26, 2016 at 3:30:40 PM UTC+2, Niklas Mischkulnig wrote:
>
> At least on my machine, there is no such line.
>
> I will look into this error (comes up after opening the about screen): 
>  Kann Datei 
> '/Users/niklas/development/clean/mac/build/Release/Hugin.app/Contents/Resources/xrc/data/COPYING.txt'
>  
> nicht öffnen (Fehler 2: No such file or directory)
>
> Am Dienstag, 26. April 2016 09:12:55 UTC+2 schrieb T. Modes:
>>
>>
>>
>> Am Montag, 25. April 2016 21:50:44 UTC+2 schrieb Niklas Mischkulnig:
>>>
>>> I first noticed that error, when converting the raw images from Sukima's 
>>> workflow thread to jpg using Adobe Camera Raw, the converted images are 
>>> attached (in sRGB and AdobeRGB, though both cause the same error)
>>>
>>> lcms: Error #12288; Output profile is operating on wrong colorspace
>>>
>>
>> All affected files contains an icc profile. But I don't get an error.
>> Can you check if Hugin has found a monitor profile? (Go to about screen, 
>> tab system, is there a line "Monitor profile:.."? If yes, please provide 
>> the file mentioned here.)
>>
>> Thomas
>>
>

-- 
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/e042b9f5-35a0-4204-8757-e795baa5883b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [hugin-ptx] Mac Build

2016-04-26 Thread T. Modes


Am Dienstag, 26. April 2016 17:46:23 UTC+2 schrieb Niklas Mischkulnig:
>
> I found the reason: In Xcode when I set the MAC_SELF_CONTAINED_BUNDLE 
> flag, it applies it recursively to all other targets, *except* base_wx.
>
> I attached the compile errors in Executor.cpp.
>

Okay, we make progress. Mainly a simply include was missing.
I committed the changes to the repository.
Attached is a modified patch. It contains both former patches and some 
little bugfixes from your last report.

Thomas

-- 
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/8221219a-e48e-4bee-8c8f-bc3405450a95%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
diff --git a/src/hugin1/base_wx/Executor.cpp b/src/hugin1/base_wx/Executor.cpp
--- a/src/hugin1/base_wx/Executor.cpp
+++ b/src/hugin1/base_wx/Executor.cpp
@@ -155,6 +155,7 @@
 if (config->Read(name + wxT("/Custom"), 0l))
 {
 wxString fn = config->Read(name + wxT("/Exe"), wxT(""));
+std::cerr << "Testing custom: " << fn.c_str() << std::endl;
 if (wxFileName::FileExists(fn))
 {
 return fn;
@@ -168,6 +169,7 @@
 if (name == wxT("exiftool"))
 {
 wxString exiftoolDirPath = MacGetPathToBundledResourceFile(CFSTR("ExifTool"));
+std::cerr << "ExifTool, path to bundled res: " << exiftoolDirPath.c_str() << std::endl;
 if (exiftoolDirPath != wxT(""))
 {
 return exiftoolDirPath + wxT("/exiftool");
@@ -182,6 +184,7 @@
 CFStringRef filename = MacCreateCFStringWithWxString(name);
 wxString fn = MacGetPathToBundledExecutableFile(filename);
 CFRelease(filename);
+std::cerr << "Filename for " << name.c_str() << "=" << fn.c_str() << std::endl;
 
 if (fn == wxT(""))
 {
diff --git a/src/hugin1/base_wx/StitchingExecutor.cpp b/src/hugin1/base_wx/StitchingExecutor.cpp
--- a/src/hugin1/base_wx/StitchingExecutor.cpp
+++ b/src/hugin1/base_wx/StitchingExecutor.cpp
@@ -227,6 +227,7 @@
 case HuginBase::PanoramaOptions::ENBLEND_BLEND:
 {
 wxArrayString version;
+output << wxT("enblend: ") << GetExternalProgram(config, bindir, wxT("enblend")) << wxEndl;
 if (wxExecute(wxEscapeFilename(GetExternalProgram(config, bindir, wxT("enblend"))) + wxT(" --version"), version, wxEXEC_SYNC) == 0l)
 {
 output << _("Blender:") << wxT(" ") << version[0] << wxEndl;
@@ -246,6 +247,7 @@
 if (opts.outputLDRExposureBlended || opts.outputLDRExposureLayersFused || opts.outputLDRStacks )
 {
 wxArrayString version;
+output << wxT("enfuse: ") << GetExternalProgram(config, bindir, wxT("enfuse")) << wxEndl;
 if (wxExecute(wxEscapeFilename(GetExternalProgram(config, bindir, wxT("enfuse"))) + wxT(" --version"), version, wxEXEC_SYNC) == 0l)
 {
 output << _("Exposure fusion:") << wxT(" ") << version[0] << wxEndl;
@@ -258,6 +260,7 @@
 if (config->Read(wxT("/output/useExiftool"), HUGIN_USE_EXIFTOOL) == 1l)
 {
 wxArrayString version;
+output << wxT("exiftool: ") << GetExternalProgram(config, bindir, wxT("exiftool")) << wxEndl;
 if (wxExecute(wxEscapeFilename(GetExternalProgram(config, bindir, wxT("exiftool"))) + wxT(" -ver"), version, wxEXEC_SYNC) == 0l)
 {
 output << _("ExifTool version:") << wxT(" ") << version[0] << wxEndl;
diff --git a/src/hugin1/base_wx/platform.cpp b/src/hugin1/base_wx/platform.cpp
--- a/src/hugin1/base_wx/platform.cpp
+++ b/src/hugin1/base_wx/platform.cpp
@@ -37,6 +37,7 @@
 #include 
 #include 
 #include "wx/utils.h"
+#define DEBUG_INFO(msg) { std::cerr << "INFO " << DEBUG_HEADER << msg << std::endl; }
 
 using namespace std;
 


Re: [hugin-ptx] Mac Build

2016-04-26 Thread T. Modes


Am Dienstag, 26. April 2016 17:10:23 UTC+2 schrieb Niklas Mischkulnig:
>
> This is the output with the two patches:
>
> *cout:*
> INFO 17:04:06.828634 
> (/Users/niklas/development/clean/src/hugin1/base_wx/platform.cpp:290) 
> MacGetPathToBundledResourceFile(): Mac: the resource file's path in the 
> application bundle: 
> /Users/niklas/development/clean/mac/build/Release/PTBatcherGUI.app/Contents/Resources/xrc
> INFO 17:04:06.829864 
> (/Users/niklas/development/clean/src/hugin1/base_wx/platform.cpp:290) 
> MacGetPathToBundledResourceFile(): Mac: the resource file's path in the 
> application bundle: 
> /Users/niklas/development/clean/mac/build/Release/PTBatcherGUI.app/Contents/Resources/de.lproj/locale
>

There should be more output to cerr. Something is missing.


> *log:*
> enblend: enblend
> Blender: Unknown blender (enblend --version failed)
> exiftool: exiftool
> ExifTool: FAILED
>
> By the way, the colorspace crash still happens (if 
> http://hg.code.sf.net/p/hugin/hugin/rev/ca640dfdbf7f was related to this)
>

I know, that's why I want know if there is monitor profile.
 

>
>

-- 
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/7e7f7ffd-e98d-4858-8502-ef9e6ebdee4d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [hugin-ptx] Mac Build

2016-04-26 Thread Niklas Mischkulnig
This is the output with the two patches:

*cout:*
INFO 17:04:06.828634 
(/Users/niklas/development/clean/src/hugin1/base_wx/platform.cpp:290) 
MacGetPathToBundledResourceFile(): Mac: the resource file's path in the 
application bundle: 
/Users/niklas/development/clean/mac/build/Release/PTBatcherGUI.app/Contents/Resources/xrc
INFO 17:04:06.829864 
(/Users/niklas/development/clean/src/hugin1/base_wx/platform.cpp:290) 
MacGetPathToBundledResourceFile(): Mac: the resource file's path in the 
application bundle: 
/Users/niklas/development/clean/mac/build/Release/PTBatcherGUI.app/Contents/Resources/de.lproj/locale

*log:*
enblend: enblend
Blender: Unknown blender (enblend --version failed)
exiftool: exiftool
ExifTool: FAILED

By the way, the colorspace crash still happens (if 
http://hg.code.sf.net/p/hugin/hugin/rev/ca640dfdbf7f was related to this)

Am Dienstag, 26. April 2016 17:02:11 UTC+2 schrieb T. Modes:
>
> Hi Nikolas,
> Am Dienstag, 26. April 2016 15:30:40 UTC+2 schrieb Niklas Mischkulnig:
>>
>> At least on my machine, there is no such line.
>>
>> I will look into this error (comes up after opening the about screen): 
>>  Kann Datei 
>> '/Users/niklas/development/clean/mac/build/Release/Hugin.app/Contents/Resources/xrc/data/COPYING.txt'
>>  
>> nicht öffnen (Fehler 2: No such file or directory)
>>
>
> The file COPYING was renamed to COPYING.txt. I updated already one shell 
> script, but maybe the XCode project files still addresses the old file 
> COPYING and needs be updated.
>

-- 
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/2db574e5-56bf-413f-8521-3b4d4e02dc37%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [hugin-ptx] Mac Build

2016-04-26 Thread T. Modes
Hi Nikolas,
Am Dienstag, 26. April 2016 15:30:40 UTC+2 schrieb Niklas Mischkulnig:
>
> At least on my machine, there is no such line.
>
> I will look into this error (comes up after opening the about screen): 
>  Kann Datei 
> '/Users/niklas/development/clean/mac/build/Release/Hugin.app/Contents/Resources/xrc/data/COPYING.txt'
>  
> nicht öffnen (Fehler 2: No such file or directory)
>

The file COPYING was renamed to COPYING.txt. I updated already one shell 
script, but maybe the XCode project files still addresses the old file 
COPYING and needs be updated.

-- 
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/63bb8ba5-6730-4178-8f5d-cf8a01e700f7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [hugin-ptx] Mac Build

2016-04-26 Thread Niklas Mischkulnig
At least on my machine, there is no such line.

I will look into this error (comes up after opening the about screen): 
 Kann Datei 
'/Users/niklas/development/clean/mac/build/Release/Hugin.app/Contents/Resources/xrc/data/COPYING.txt'
 
nicht öffnen (Fehler 2: No such file or directory)

Am Dienstag, 26. April 2016 09:12:55 UTC+2 schrieb T. Modes:
>
>
>
> Am Montag, 25. April 2016 21:50:44 UTC+2 schrieb Niklas Mischkulnig:
>>
>> I first noticed that error, when converting the raw images from Sukima's 
>> workflow thread to jpg using Adobe Camera Raw, the converted images are 
>> attached (in sRGB and AdobeRGB, though both cause the same error)
>>
>> lcms: Error #12288; Output profile is operating on wrong colorspace
>>
>
> All affected files contains an icc profile. But I don't get an error.
> Can you check if Hugin has found a monitor profile? (Go to about screen, 
> tab system, is there a line "Monitor profile:.."? If yes, please provide 
> the file mentioned here.)
>
> Thomas
>

-- 
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/f2bed6d2-a365-44ba-a8e9-9ce0748ab6b9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [hugin-ptx] Mac Build

2016-04-26 Thread Alexandr Krylovskiy
Hi Niklas,

first of all, thank you for your efforts! 
I'll be keeping an eye on this thread, so you've got yourself another 
tester :)

Trying that build from goole drive, Hugin crashed loading a single 16-bit 
TIFF file with the following error in terminal:
lcms: Error #12288; Output profile is operating on wrong colorspace

Couldn't find this error being discussed here, so I thought it might be of 
help.

Best regards,
Alex

On Monday, April 18, 2016 at 7:26:10 PM UTC+2, 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
>
>
> Am Montag, 18. April 2016 18:50:23 UTC+2 schrieb Harry van der Wolf:
>>
>> In the time that I built the bundles I once build the Hugin.app as a full 
>> bundle and made symlinks to all redundant libraries in both other apps. 
>> That decreased the size of the apps indeed but it required all thee apps to 
>> be in the same folder (which as such is quite logical).
>> However, this build scenario made the compilation even harder and even 
>> though the 3 apps are a big chunk of data: What is 180 MB even on a (small) 
>> 128 GB solid state disk. Leave alone on a 750+ GB disk.
>>
>> At that time I simply wanted to try, but it wasn't worth all the hassle.
>> Besides: If a user wants it differently then he/she can buid it 
>> himself/herself.
>>
>> Note that I have left OSX about 2½ years ago. 
>>
>> I think you did an awesome job in building the new 2016 version for Mac. 
>> If enough users have tested the builds I would suggest to upload them to 
>> sourceforge where the other older bundles reside as well.
>> If you get too many downloads on your dropbox account it will be 
>> completely blocked for others to download. Only you yourself can use it 
>> then.
>> I experienced that myself with another build (not for mac). I used 
>> dropbox mainly to share things with my family. Even that was no longer 
>> possible. With 180 MB bundles this might go faster then you expect.
>>
>> Harry
>>
>> 2016-04-18 18:29 GMT+02:00 Niklas Mischkulnig :
>>
>>> The main duplicate and large part are the dylibs under 
>>> Hugin.app/Libraries/. These could be in a folder alongside Hugin.app, 
>>> PTBatchGui.app and calibratelensgui.app, reducing the total filesize from 
>>> 231 mb to 231-(2*35)=180mb. Putting the Resources/xrc folder there as well 
>>> would shave off another 15 mb (resulting in 165mb).
>>> Is it worth the effort?
>>>
>>> Niklas
>>>
>>> Am Montag, 18. April 2016 18:05:10 UTC+2 schrieb Harry van der Wolf:

 The fact the mac bundles are that big is due to the "bundle all 
 dependencies" inside the app. That gives a lot of redundancy in the apps. 
 That is already for years and years a fact and as long as Apple doesn't 
 change their policy it will stay that way.
 When compiling with XCode this strip functionality is automatically 
 executed but results in about 10% size reduction. But my information is 
 going years back.

 Harry

 2016-04-18 17:07 GMT+02:00 Jan Dubiec :

> On 2016-04-18 14:40, Niklas Mischkulnig wrote:
> [...]
> > Maybe there is someone who can tell me exactly what program needs 
> which
> > libraries (especially which boost library) and binaries(like cpfind,
> > celeste, ...)  to shrink down the application sizes (currently 2* 
> ~80mb
> > and 1* ~50mb) ?
> I don't know Macs but I'm quite sure that there is strip utility
> (https://en.wikipedia.org/wiki/Strip_%28Unix%29) for Macs.
>
> If you want to know about dependencies, read about CMake's --graphviz
> option. It allows you to generate graphs like this:
> * for the whole project –
> https://www.dropbox.com/s/qunx5o8frhav6lj/HuginHg.pdf?dl=0
> * for the whole project with external dependencies –
> https://www.dropbox.com/s/qunx5o8frhav6lj/HuginHg.pdf?dl=0
> * for a module (hugin in this case) –
> https://www.dropbox.com/s/bfsz6byb86o2l89/HuginHg.hugin.pdf?dl=0
> * for a module with external dependencies –
> https://www.dropbox.com/s/7h1yauyooqo0ggj/HuginHg.hugin-ext.pdf?dl=0.
>
> /J.D.
>
> --
> 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/5714F841.2020009%40onet.pl
> .
> For more options, visit https://groups.google.com/d/optout.
>

 -- 
>>> A list of frequently asked questions is available at: 
>>> http://wiki.panotools.org/Hugin_FAQ
>>> --- 
>>> You received this message 

Re: [hugin-ptx] Mac Build

2016-04-26 Thread T. Modes


Am Montag, 25. April 2016 21:50:44 UTC+2 schrieb Niklas Mischkulnig:
>
> I first noticed that error, when converting the raw images from Sukima's 
> workflow thread to jpg using Adobe Camera Raw, the converted images are 
> attached (in sRGB and AdobeRGB, though both cause the same error)
>
> lcms: Error #12288; Output profile is operating on wrong colorspace
>

All affected files contains an icc profile. But I don't get an error.
Can you check if Hugin has found a monitor profile? (Go to about screen, 
tab system, is there a line "Monitor profile:.."? If yes, please provide 
the file mentioned here.)

Thomas

-- 
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/a7cff23c-8da6-4d1d-93a0-3ad150a5dfa5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [hugin-ptx] Mac Build

2016-04-26 Thread T. Modes
Hi Niklas

Am Montag, 25. April 2016 18:55:00 UTC+2 schrieb Niklas Mischkulnig:
>
> Here you go:
>
> enblend: enblend
>
> Blender: Unknown blender (enblend —version failed)
>
> exiftool: exiftool
>
> ExifTool: FAILED
>
> Okay, it does not find the executables. So we need to dig deeper.
The attached patch activates more debug information (it goes to the 
console). Maybe it helps to find which functions fails.

Thomas

-- 
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/d3341591-eca7-470a-bfd2-d163f5801695%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
diff --git a/src/hugin1/base_wx/Executor.cpp b/src/hugin1/base_wx/Executor.cpp
--- a/src/hugin1/base_wx/Executor.cpp
+++ b/src/hugin1/base_wx/Executor.cpp
@@ -152,6 +152,7 @@
 if (config->Read(name + wxT("/Custom"), 0l))
 {
 wxString fn = config->Read(name + wxT("/Exe"), wxT(""));
+std::cerr << "Testing custom: " << fn.c_str() << std::endl;
 if (wxFileName::FileExists(fn))
 {
 return fn;
@@ -165,6 +166,7 @@
 if (name == wxT("exiftool"))
 {
 wxString exiftoolDirPath = MacGetPathToBundledResourceFile(CFSTR("ExifTool"));
+std::cerr << "ExifTool, path to bundled res: " << exiftoolDirPath.c_str() << std::endl;
 if (exiftoolDirPath != wxT(""))
 {
 return exiftoolDirPath + wxT("/exiftool");
@@ -179,6 +181,7 @@
 CFStringRef filename = MacCreateCFStringWithWxString(name);
 wxString fn = MacGetPathToBundledExecutableFile(filename);
 CFRelease(filename);
+std::cerr << "Filename for " << name.c_str() << "=" << filename.c_str() << std::endl;
 
 if (fn == wxT(""))
 {
diff --git a/src/hugin1/base_wx/platform.cpp b/src/hugin1/base_wx/platform.cpp
--- a/src/hugin1/base_wx/platform.cpp
+++ b/src/hugin1/base_wx/platform.cpp
@@ -37,6 +37,7 @@
 #include 
 #include 
 #include "wx/utils.h"
+#define DEBUG_INFO(msg) { std::cerr << "INFO " << DEBUG_HEADER << msg << std::endl; }
 
 using namespace std;
 


Re: [hugin-ptx] Mac Build

2016-04-25 Thread Niklas Mischkulnig
Here you go:

enblend: enblend

Blender: Unknown blender (enblend —version failed)

exiftool: exiftool

ExifTool: FAILED

Am Montag, 25. April 2016 18:17:20 UTC+2 schrieb T. Modes:
>
>
>
> Am Montag, 25. April 2016 17:44:32 UTC+2 schrieb Niklas Mischkulnig:
>>
>> Compiling works(see attached errors and patch) 
>>
> Thanks, applied the patch (but the patch was backwards)
>
> But the problems in PTBatcherGUI remain, although enblend and ExifTool are 
>> bundled inside the .app (see screenshots)
>>
>> Blender: Unknown blender (enblend —version failed)
>>
>> ExifTool: FAILED
>>
>
> Could you apply the attached patch and try again? It will print the used 
> path additionally, so maybe this helps us a bit further.
>
> Thomas
>

-- 
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/983c62ed-1adf-4f02-8832-d00f6ff8cc1b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [hugin-ptx] Mac Build

2016-04-25 Thread T. Modes
Hi David

Am Montag, 25. April 2016 17:59:16 UTC+2 schrieb David Haberthür:
>
> When I open Hugin this way in the Terminal, I get a single line after the 
> crash, namely 
> — 
> lcms: Error #12288; Output profile is operating on wrong colorspace 
> — 
>
Could you provide a file which shows this error?
Maybe I can reproduce the error also on other systems.

Thomas

-- 
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/60699a9c-4a51-4acf-b1a2-0cb1d0c67e11%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [hugin-ptx] Mac Build

2016-04-25 Thread T. Modes


Am Montag, 25. April 2016 17:44:32 UTC+2 schrieb Niklas Mischkulnig:
>
> Compiling works(see attached errors and patch) 
>
Thanks, applied the patch (but the patch was backwards)

But the problems in PTBatcherGUI remain, although enblend and ExifTool are 
> bundled inside the .app (see screenshots)
>
> Blender: Unknown blender (enblend —version failed)
>
> ExifTool: FAILED
>

Could you apply the attached patch and try again? It will print the used 
path additionally, so maybe this helps us a bit further.

Thomas

-- 
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/431bde46-63c8-46c2-9194-85c79fed9e34%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
diff --git a/src/hugin1/base_wx/StitchingExecutor.cpp b/src/hugin1/base_wx/StitchingExecutor.cpp
--- a/src/hugin1/base_wx/StitchingExecutor.cpp
+++ b/src/hugin1/base_wx/StitchingExecutor.cpp
@@ -227,6 +227,7 @@
 case HuginBase::PanoramaOptions::ENBLEND_BLEND:
 {
 wxArrayString version;
+output << wxT("enblend: ") << GetExternalProgram(config, bindir, wxT("enblend")) << wxEndl;
 if (wxExecute(wxEscapeFilename(GetExternalProgram(config, bindir, wxT("enblend"))) + wxT(" --version"), version, wxEXEC_SYNC) == 0l)
 {
 output << _("Blender:") << wxT(" ") << version[0] << wxEndl;
@@ -246,6 +247,7 @@
 if (opts.outputLDRExposureBlended || opts.outputLDRExposureLayersFused || opts.outputLDRStacks )
 {
 wxArrayString version;
+output << wxT("enfuse: ") << GetExternalProgram(config, bindir, wxT("enfuse")) << wxEndl;
 if (wxExecute(wxEscapeFilename(GetExternalProgram(config, bindir, wxT("enfuse"))) + wxT(" --version"), version, wxEXEC_SYNC) == 0l)
 {
 output << _("Exposure fusion:") << wxT(" ") << version[0] << wxEndl;
@@ -258,6 +260,7 @@
 if (config->Read(wxT("/output/useExiftool"), HUGIN_USE_EXIFTOOL) == 1l)
 {
 wxArrayString version;
+output << wxT("exiftool: ") << GetExternalProgram(config, bindir, wxT("exiftool")) << wxEndl;
 if (wxExecute(wxEscapeFilename(GetExternalProgram(config, bindir, wxT("exiftool"))) + wxT(" -ver"), version, wxEXEC_SYNC) == 0l)
 {
 output << _("ExifTool version:") << wxT(" ") << version[0] << wxEndl;


Re: [hugin-ptx] Mac Build

2016-04-25 Thread David Haberthür
Ciao Niklas.

> You could try to open Hugin using the Terminal, maybe there are more 
> meaningful error messages there.
> - Open Terminal
> - drag Hugin.app over the Terminal window and let go
> - remove one space and add /Contents/MacOS/Hugin  to the path
> - press enter, Hugin should start; look at the terminal window for error 
> messages during the crash.

Great idea, I haven’t though of this [1].
When I open Hugin this way in the Terminal, I get a single line after the 
crash, namely
—
lcms: Error #12288; Output profile is operating on wrong colorspace
—

I thought that’s maybe something related to the .tiff Images I’m using as an 
input for this panorama.
So I tried to make a new panorama with only .jpg images, which worked fine 
apart from a small note in the Terminal regarding
—
ERROR: 17:52:45.166226 
(/Users/niklas/development/test/src/hugin1/hugin/ProjectionGridTool.cpp:371) 
createTexture(): GL Error when building mipmap levels: invalid frame buffer 
operation
—

But then I re-opened an old panorama, and got the same lcms error again when 
opening the fast preview.
On others I don’t get it, which makes it quite hard to pin down to an exact 
cause…

How can I continue to help with debugging?

Habi


[1: ]Or more precisely I did `cd /Applications/Hugin_2016/ && open Hugin.app/‘, 
which gives no output after a crash…

> Niklas
> 
> 
> Am Montag, 25. April 2016 08:36:57 UTC+2 schrieb David Haberthür:
> Dear Niklas
> Thanks for providing us Mac users with a fresh build.
> Unfortunately, I’m hitting quite a severe bug on OS X 10.11.4 (El Capitan) 
> with it.
> I can open a panorama, but when I want to see the OpenGL preview, Hugin 
> instantly crashes hug
> 
> Unfortunately, I cannot get anything useful from the Console-App which would 
> hint at the bug I’m hitting.
> The only thing I get in the console is
> —
> 25/04/16 07:06:50.509 com.apple.xpc.launchd[1]: 
> (net.sourceforge.hugin.Hugin.219552[31102]) Service exited with abnormal 
> code: 1
> —
> 
> When I work with the ‘old’ preview window I can stitch some of my recent 
> panoramas without problems.
> Will try to make a new one for testing soon.
> Habi
> 
> > On 13 Apr 2016, at 17:37, Niklas Mischkulnig  wrote:
> >
> > Hello again,
> >
> >
> >
> > I copied the include, bin and lib files from the homebrew packages, but now 
> > it's Xcode:
> >
> > When compiling the "vigra_impex Framework", this is the error;
> >
> >
> > no such file or directory: 
> > '/Users/niklas/development/test/src/foreign/vigra/vigra_impex/bmp.cxx'
> >
> > The whole vigra folder is missing (was removed in 2011 
> > http://hg.code.sf.net/p/hugin/hugin/rev/9e26ccb0d3d0 ). Does someone know 
> > why there is still something in the XCode project? Downloading the source 
> > gives the errors on the screenshot.
> >
> >
> >
> > The whole mac thing seems to be really outdated.
> >
> >
> > Am Sonntag, 10. April 2016 17:29:12 UTC+2 schrieb Niklas Mischkulnig:
> > Anyone an idea?
> >
> > Here is the full output: 
> > https://gist.github.com/mischnic/a40fc98594af70256e95559112fe87ef
> >
> > Am Samstag, 9. April 2016 23:57:54 UTC+2 schrieb Niklas Mischkulnig:
> > I got most of the required deps compiled, but enblend still resists:
> >
> > In file included from enblend.cc:147:
> > In file included from ./common.h:39:
> > In file included from 
> > /Users/niklas/development/hugin/mac/ExternalPrograms/repository/include/boost/lambda/lambda.hpp:23:
> > /Users/niklas/development/hugin/mac/ExternalPrograms/repository/include/boost/lambda/detail/operator_return_type_traits.hpp:835:65:
> >  error: reference to 'map' is ambiguous
> > struct plain_return_type_2 > Cmp, Allocator>, B> {
> >~^
> > /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../include/c++/v1/map:830:29:
> >  note: candidate found by name lookup is 'std::__1::map'
> > class _LIBCPP_TYPE_VIS_ONLY map
> > ^
> > /Users/niklas/development/hugin/mac/ExternalPrograms/repository/include/boost/detail/container_fwd.hpp:87:73:
> >  note: candidate found by name lookup is 'std::map'
> > template  class map;
> > ^
> >
> >
> > Am Samstag, 9. April 2016 16:19:55 UTC+2 schrieb T. Modes:
> >
> > Am Samstag, 9. April 2016 11:11:54 UTC+2 schrieb Niklas Mischkulnig:
> > Ok, so symlinking gcc to gcc-4.2 fixed that error message, but I have to 
> > feeling that boost isn't really built,  ## Now building architecture x86_64 
> > ## is printed out, and nearly immediately after that mv: rename 
> > ./stage-x86_64/lib/libboost_thread.dylib to 
> > ./stage-x86_64/lib/libboost_thread-1_46.dylib: No such file or directory . 
> > That should be the compiled output boost library, right?
> >
> > These Mac scripts needs probably some tweaking. Since they were used last 
> > some dependencies have 

Re: [hugin-ptx] Mac Build

2016-04-25 Thread Niklas Mischkulnig
Compiling works(see attached errors and patch) 
But the problems in PTBatcherGUI remain, although enblend and ExifTool are 
bundled inside the .app (see screenshots)

Blender: Unknown blender (enblend —version failed)

ExifTool: FAILED

Niklas

Am Montag, 25. April 2016 15:57:41 UTC+2 schrieb T. Modes:
>
>
>
> Am Dienstag, 19. April 2016 20:36:18 UTC+2 schrieb Niklas Mischkulnig:
>>
>> 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?
>>
>
> When MAC_SELF_CONTAINED_BUNDLE is defined special code for the Mac bundles 
> is used to look for the binaries in the bundle (it calls the function 
> MacGetPathToBundledExecutableFile).
> So I assume for a bundled version this define is needed. (And may explain 
> the problems with enblend/enfuse/assistant).
> I changed the code from the makefile version to now the wxWidgets version 
> for stitching and assistant some time ago. Since then nobody has build a 
> Mac bundle. So it may be that there are some glitches which I introduced 
> when I reworked the code. Maybe only an include is missing? But without the 
> (exact) error messages this is impossible to say.
>
> Thomas
>
>

-- 
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/69dd77bf-8a04-4228-b7a3-ab685bdd475f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
diff --git a/clean/src/hugin1/hugin/PanoPanel.cpp b/cmake/hugin/src/hugin1/hugin/PanoPanel.cpp
index 2c232f8..14d3151 100644
--- a/clean/src/hugin1/hugin/PanoPanel.cpp
+++ b/cmake/hugin/src/hugin1/hugin/PanoPanel.cpp
@@ -1072,7 +1072,7 @@ void PanoPanel::DoStitch()
 DEBUG_ERROR("hugin_stitch_project could not be found in the bundle.");
 return;
 }
-hugin_stitch_project = hugin_utils::wxQuoteFilename(hugin_stitch_project);
+hugin_stitch_project = wxQuoteFilename(hugin_stitch_project);
 #elif defined __WXMAC__
 // HuginStitchProject installed in INSTALL_OSX_BUNDLE_DIR
 wxFileName hugin_stitch_project_app(wxT(INSTALL_OSX_BUNDLE_DIR), wxEmptyString);
@@ -1256,7 +1256,7 @@ void PanoPanel::DoSendToBatch()
 			//Found PTBatcherGui inside the (registered) PTBatcherGui bundle. Call it directly.
 			//We need to call the binary from it's own bundle and not from the hugin bundle otherwise we get no menu as OSX assumes that the hugin bundle
 			//will provide the menu
-			cmd = hugin_utils::wxQuoteString(cmd);
+			cmd = wxQuoteString(cmd); 
 cmd += wxT(" ")+switches+hugin_utils::wxQuoteFilename(projectFile)+wxT(" ")+hugin_utils::wxQuoteFilename(dlg.GetPath());	
 			wxExecute(cmd);
 		}
@@ -1341,7 +1341,7 @@ void PanoPanel::DoUserDefinedStitch()
 DEBUG_ERROR("hugin_stitch_project could not be found in the bundle.");
 return;
 }
-hugin_stitch_project = hugin_utils::wxQuoteFilename(hugin_stitch_project);
+hugin_stitch_project = wxQuoteFilename(hugin_stitch_project);
 #elif defined __WXMAC__
 // HuginStitchProject installed in INSTALL_OSX_BUNDLE_DIR
 wxFileName hugin_stitch_project_app(wxT(INSTALL_OSX_BUNDLE_DIR), wxEmptyString);


Re: [hugin-ptx] Mac Build

2016-04-25 Thread T. Modes


Am Dienstag, 19. April 2016 20:36:18 UTC+2 schrieb Niklas Mischkulnig:
>
> 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?
>

When MAC_SELF_CONTAINED_BUNDLE is defined special code for the Mac bundles 
is used to look for the binaries in the bundle (it calls the function 
MacGetPathToBundledExecutableFile).
So I assume for a bundled version this define is needed. (And may explain 
the problems with enblend/enfuse/assistant).
I changed the code from the makefile version to now the wxWidgets version 
for stitching and assistant some time ago. Since then nobody has build a 
Mac bundle. So it may be that there are some glitches which I introduced 
when I reworked the code. Maybe only an include is missing? But without the 
(exact) error messages this is impossible to say.

Thomas

-- 
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/90d2f454-7572-452a-a556-aba911d294b4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [hugin-ptx] Mac Build

2016-04-25 Thread T. Modes


Am Montag, 18. April 2016 14:40:54 UTC+2 schrieb Niklas Mischkulnig:
>
>
> https://trac.macports.org/attachment/ticket/41463/patch-src-hugin1-icpfind-AutoCtrlPointCreator.cpp.diff
> (Discussion here: https://trac.macports.org/ticket/41463)
>

Thanks, I committed a slightly modified patch (the line mentioned has 
already changed).
 

>
> Maybe there is someone who can tell me exactly what program needs which 
> libraries (especially which boost library) and binaries(like cpfind, 
> celeste, ...)  to shrink down the application sizes (currently 2* ~80mb and 
> 1* ~50mb) ?
>
 
>From boost we need only boost::filesystem. It is used by huginbase,  
hugin_lensdb and pto_move.
The README file contains an uptodate list of all dependencies for Hugin. 
Most of them are used in huginbase and therefor also pulled into all other 
programs.

-- 
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/8bcf1172-43dc-4290-9631-717f5a3d97a0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [hugin-ptx] Mac Build

2016-04-25 Thread Niklas Mischkulnig
You could try to open Hugin using the Terminal, maybe there are more 
meaningful error messages there.
- Open Terminal
- drag Hugin.app over the Terminal window and let go
- remove one space and add /Contents/MacOS/Hugin  to the path
- press enter, Hugin should start; look at the terminal window for error 
messages during the crash.

Niklas


Am Montag, 25. April 2016 08:36:57 UTC+2 schrieb David Haberthür:
>
> Dear Niklas 
> Thanks for providing us Mac users with a fresh build. 
> Unfortunately, I’m hitting quite a severe bug on OS X 10.11.4 (El Capitan) 
> with it. 
> I can open a panorama, but when I want to see the OpenGL preview, Hugin 
> instantly crashes hug 
>
> Unfortunately, I cannot get anything useful from the Console-App which 
> would hint at the bug I’m hitting. 
> The only thing I get in the console is 
> — 
> 25/04/16 07:06:50.509 com.apple.xpc.launchd[1]: 
> (net.sourceforge.hugin.Hugin.219552[31102]) Service exited with abnormal 
> code: 1 
> — 
>
> When I work with the ‘old’ preview window I can stitch some of my recent 
> panoramas without problems. 
> Will try to make a new one for testing soon. 
> Habi 
>
> > On 13 Apr 2016, at 17:37, Niklas Mischkulnig  > wrote: 
> > 
> > Hello again, 
> > 
> > 
> > 
> > I copied the include, bin and lib files from the homebrew packages, but 
> now it's Xcode: 
> > 
> > When compiling the "vigra_impex Framework", this is the error; 
> > 
> > 
> > no such file or directory: 
> '/Users/niklas/development/test/src/foreign/vigra/vigra_impex/bmp.cxx' 
> > 
> > The whole vigra folder is missing (was removed in 2011 
> http://hg.code.sf.net/p/hugin/hugin/rev/9e26ccb0d3d0 ). Does someone know 
> why there is still something in the XCode project? Downloading the source 
> gives the errors on the screenshot. 
> > 
> > 
> > 
> > The whole mac thing seems to be really outdated. 
> > 
> > 
> > Am Sonntag, 10. April 2016 17:29:12 UTC+2 schrieb Niklas Mischkulnig: 
> > Anyone an idea? 
> > 
> > Here is the full output: 
> https://gist.github.com/mischnic/a40fc98594af70256e95559112fe87ef 
> > 
> > Am Samstag, 9. April 2016 23:57:54 UTC+2 schrieb Niklas Mischkulnig: 
> > I got most of the required deps compiled, but enblend still resists: 
> > 
> > In file included from enblend.cc:147: 
> > In file included from ./common.h:39: 
> > In file included from 
> /Users/niklas/development/hugin/mac/ExternalPrograms/repository/include/boost/lambda/lambda.hpp:23:
>  
>
> > 
> /Users/niklas/development/hugin/mac/ExternalPrograms/repository/include/boost/lambda/detail/operator_return_type_traits.hpp:835:65:
>  
> error: reference to 'map' is ambiguous 
> > struct plain_return_type_2 T, Cmp, Allocator>, B> { 
> >~^ 
> > 
> /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../include/c++/v1/map:830:29:
>  
> note: candidate found by name lookup is 'std::__1::map' 
> > class _LIBCPP_TYPE_VIS_ONLY map 
> > ^ 
> > 
> /Users/niklas/development/hugin/mac/ExternalPrograms/repository/include/boost/detail/container_fwd.hpp:87:73:
>  
> note: candidate found by name lookup is 'std::map' 
> > template  class 
> map; 
> > 
> ^ 
> > 
> > 
> > Am Samstag, 9. April 2016 16:19:55 UTC+2 schrieb T. Modes: 
> > 
> > Am Samstag, 9. April 2016 11:11:54 UTC+2 schrieb Niklas Mischkulnig: 
> > Ok, so symlinking gcc to gcc-4.2 fixed that error message, but I have to 
> feeling that boost isn't really built,  ## Now building architecture x86_64 
> ## is printed out, and nearly immediately after that mv: rename 
> ./stage-x86_64/lib/libboost_thread.dylib to 
> ./stage-x86_64/lib/libboost_thread-1_46.dylib: No such file or directory . 
> That should be the compiled output boost library, right? 
> > 
> > These Mac scripts needs probably some tweaking. Since they were used 
> last some dependencies have changes. 
> > From boost Hugins needs now only boost::filesystem (instead of 
> boost::thread we are using std::thread) 
> > In build-all.sh there are references to glib, lensfun, make, tclap, 
> liblcms which are not needed anymore (maybe also libffi - I don't know 
> which lib is using it). 
> > So this needs also some more work. 
> > 
> > -- 
> > 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/1079014f-8c6c-43b0-a780-45a3d4671ba1%40googlegroups.com.
>  
>
> > For more options, visit https://groups.google.com/d/optout. 
> >  
>
>

-- 
A list of frequently 

[hugin-ptx] Mac Build Hugin 2016

2016-04-25 Thread David Haberthür
Dear Niklas
Thanks for providing us Mac users with a fresh build.
Unfortunately, I’m hitting quite a severe bug on OS X 10.11.4 (El Capitan) with 
it.
I can open a panorama, but when I want to see the OpenGL preview, Hugin 
instantly crashes hug

Unfortunately, I cannot get anything useful from the Console-App which would 
hint at the bug I’m hitting.
The only thing I get in the console is
—
25/04/16 07:06:50.509 com.apple.xpc.launchd[1]: 
(net.sourceforge.hugin.Hugin.219552[31102]) Service exited with abnormal code: 1
—

When I work with the ‘old’ preview window I can stitch some of my recent 
panoramas without problems.
Will try to make a new one for testing soon.
Habi



>> On Apr 17, 2016, at 2:09 PM, Niklas Mischkulnig  
>> wrote:
>> 
>> Here is a (hopefully working) build (version 2016) . Please test it and tell 
>> me if something crashes (there might still be a wrong dylib install path 
>> lurking in a dark corner :D ).
>> 
>> https://www.dropbox.com/s/oi6etuyobwkxwbb/Hugin.zip?dl=1
>> 
>> Am Samstag, 2. April 2016 08:45:28 UTC+2 schrieb Niklas Mischkulnig:
>> Why hasn't there been a Mac build on sourceforge for over one year (there 
>> isn't a windows build for the 2016.0.0 yet)?
>> 
>> --
>> 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/b54aec89-34a4-4cbd-a43e-5f7722dfb213%40googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
> 
> 
> --
> 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/CF33958A-A2F2-4C66-9EBB-0ABF135B2A5F%40accesscomm.ca.
> For more options, visit https://groups.google.com/d/optout.

-- 
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/0B8DB2D5-DE9D-4730-A525-4D4D8E3EF5C8%40gmail.com.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: Message signed with OpenPGP using GPGMail


Re: [hugin-ptx] Mac Build

2016-04-25 Thread David Haberthür
Dear Niklas
Thanks for providing us Mac users with a fresh build.
Unfortunately, I’m hitting quite a severe bug on OS X 10.11.4 (El Capitan) with 
it.
I can open a panorama, but when I want to see the OpenGL preview, Hugin 
instantly crashes hug

Unfortunately, I cannot get anything useful from the Console-App which would 
hint at the bug I’m hitting.
The only thing I get in the console is
—
25/04/16 07:06:50.509 com.apple.xpc.launchd[1]: 
(net.sourceforge.hugin.Hugin.219552[31102]) Service exited with abnormal code: 1
—

When I work with the ‘old’ preview window I can stitch some of my recent 
panoramas without problems.
Will try to make a new one for testing soon.
Habi

> On 13 Apr 2016, at 17:37, Niklas Mischkulnig  wrote:
> 
> Hello again,
> 
> 
> 
> I copied the include, bin and lib files from the homebrew packages, but now 
> it's Xcode:
> 
> When compiling the "vigra_impex Framework", this is the error;
> 
> 
> no such file or directory: 
> '/Users/niklas/development/test/src/foreign/vigra/vigra_impex/bmp.cxx'
> 
> The whole vigra folder is missing (was removed in 2011 
> http://hg.code.sf.net/p/hugin/hugin/rev/9e26ccb0d3d0 ). Does someone know why 
> there is still something in the XCode project? Downloading the source gives 
> the errors on the screenshot.
> 
> 
> 
> The whole mac thing seems to be really outdated.
> 
> 
> Am Sonntag, 10. April 2016 17:29:12 UTC+2 schrieb Niklas Mischkulnig:
> Anyone an idea?
> 
> Here is the full output: 
> https://gist.github.com/mischnic/a40fc98594af70256e95559112fe87ef
> 
> Am Samstag, 9. April 2016 23:57:54 UTC+2 schrieb Niklas Mischkulnig:
> I got most of the required deps compiled, but enblend still resists:
> 
> In file included from enblend.cc:147:
> In file included from ./common.h:39:
> In file included from 
> /Users/niklas/development/hugin/mac/ExternalPrograms/repository/include/boost/lambda/lambda.hpp:23:
> /Users/niklas/development/hugin/mac/ExternalPrograms/repository/include/boost/lambda/detail/operator_return_type_traits.hpp:835:65:
>  error: reference to 'map' is ambiguous
> struct plain_return_type_2 Cmp, Allocator>, B> {
>~^
> /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../include/c++/v1/map:830:29:
>  note: candidate found by name lookup is 'std::__1::map'
> class _LIBCPP_TYPE_VIS_ONLY map
> ^
> /Users/niklas/development/hugin/mac/ExternalPrograms/repository/include/boost/detail/container_fwd.hpp:87:73:
>  note: candidate found by name lookup is 'std::map'
> template  class map;
> ^
> 
> 
> Am Samstag, 9. April 2016 16:19:55 UTC+2 schrieb T. Modes:
> 
> Am Samstag, 9. April 2016 11:11:54 UTC+2 schrieb Niklas Mischkulnig:
> Ok, so symlinking gcc to gcc-4.2 fixed that error message, but I have to 
> feeling that boost isn't really built,  ## Now building architecture x86_64 
> ## is printed out, and nearly immediately after that mv: rename 
> ./stage-x86_64/lib/libboost_thread.dylib to 
> ./stage-x86_64/lib/libboost_thread-1_46.dylib: No such file or directory . 
> That should be the compiled output boost library, right?
> 
> These Mac scripts needs probably some tweaking. Since they were used last 
> some dependencies have changes.
> From boost Hugins needs now only boost::filesystem (instead of boost::thread 
> we are using std::thread)
> In build-all.sh there are references to glib, lensfun, make, tclap, liblcms 
> which are not needed anymore (maybe also libffi - I don't know which lib is 
> using it).
> So this needs also some more work.
> 
> --
> 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/1079014f-8c6c-43b0-a780-45a3d4671ba1%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
> 

-- 
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/4E8315A1-1EC4-46B8-9620-6213D467A201%40gmail.com.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: Message signed with OpenPGP using GPGMail


Re: [hugin-ptx] Mac Build

2016-04-22 Thread Sukima
The spinning ball of heaven is happening to me on el capitain with Hugin 
version 2014 so it is possible there are Mac bugs long lived that are not 
unique to this new build.

For reference to reproduce open Hugin and set interface to expert. Then select 
mask. Click crop. Click mask. Force quit cause it should have frozen. 

Again this with version 2014 downloaded from sourceforge. I will try this new 
build tomorrow and see if 2016 fixes it.

-- 
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/d10d1708-f8b1-4f69-ad5c-774d913e0f0a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [hugin-ptx] Mac Build

2016-04-19 Thread 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 <nik...@mischkulnig.de> 
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" <dgjohns...@accesscomm.ca>:
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 <dgjohns...@accesscomm.ca> 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 <nik...@mischkulnig.de> 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 subsc

Re: [hugin-ptx] Mac Build

2016-04-19 Thread 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] Mac Build

2016-04-19 Thread 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

2016-04-19 Thread 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] Mac Build

2016-04-19 Thread 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 

Re: [hugin-ptx] Mac Build

2016-04-18 Thread 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 
> 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 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
> 

  1   2   >