[hugin-ptx] Image Remapping Matrix
Hello,everyone. I tried to develope a image remaping module. So I need to modify the existing remapping modules's code(like nona,PTmender) to get the remapping matrix between the images calculated by the nona,and feed the matrices to the remapping modules I developed. So where is the code of the image remapping matrix calculation of the nona or PTmender? I debug step-by-step the nona and PTmender using the 'simpleStitch' of libpano12,but I couldn't find the code out. Can anybody help me? Cheers Bob --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "hugin and other free panoramic software" group. A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ To post to this group, send email to hugin-ptx@googlegroups.com To unsubscribe from this group, send email to hugin-ptx+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/hugin-ptx -~--~~~~--~~--~--~---
[hugin-ptx] Control Points tab critique (was:hugin 09.02 - feedback)
This is all useful stuff, we could really do with a single place to collect these issues, maybe the comment pages on the wiki? On Sun 08-Nov-2009 at 13:31 +0100, Erik Krause wrote: > >Setting CPs manually still sucks but this is the case since version 0.1 >or whatever I tried first years ago. If I show the same image in both >panes hugin correctly assumes that I want to add a vertical CP. > >I click the point in the left pane and the other end of the vertical >line in the right one. If auto fine tune is on hugin takes ages until >the CP is added and it isn't in the place I choose. > >If auto fine tune is off the right pane magnifies as soon as I click but >there is no point. If I click the point it zooms out again with the >point set. The magnifying glass shows only if I move the mouse out of >the pane - I have to click the point again in order to correct it. > >Mouse movement when dragging a point is far too rough (in display >pixels) then, for a fine correction I have to zoom in manually. The >local magnifier is too small and magnifies too much. I didn't find >anything in the preferences to change this. > >To correct a point I must click on the cross. Clicking the flag creates >a new point. If zoomed in and the point is not in the middle of the pane >it scrolls to the middle as soon as I click the point. Sometimes the >point stays with the mouse pointer and sometimes it moves away with the >image. > >The CP list below doesn't react to the delete key. You need to press the >Delete with the mouse. The main CP table (F3) however does. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "hugin and other free panoramic software" group. A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ To post to this group, send email to hugin-ptx@googlegroups.com To unsubscribe from this group, send email to hugin-ptx+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/hugin-ptx -~--~~~~--~~--~--~---
[hugin-ptx] Re: libpano SVN 1137 fails to build
Jim Watters wrote:
> Jean-Luc Coulon (f5ibh) wrote:
>
>> Hi,
>>
>> I get the following:
>>
>> [...]
>> /bin/bash ./libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I.
>> -DHasJPEG -DHasPNG -DHasTIFF -DHasZLIB -D__Ansi__=1 -g -O2 -MT
>> PTDialogs.lo -MD -MP -MF .deps/PTDialogs.Tpo -c -o PTDialogs.lo
>> PTDialogs.c
>> libtool: compile: gcc -DHAVE_CONFIG_H -I. -DHasJPEG -DHasPNG -DHasTIFF
>> -DHasZLIB -D__Ansi__=1 -g -O2 -MT PTDialogs.lo -MD -MP -MF .deps/
>> PTDialogs.Tpo -c PTDialogs.c -fPIC -DPIC -o .libs/PTDialogs.o
>> In file included from PTDialogs.c:29:
>> sys_ansi.h:44: error: expected ‘)’ before ‘Owner’
>> sys_ansi.h:45: error: expected ‘)’ before ‘hDlg’
>> make[2]: *** [PTDialogs.lo] Error 1
>>
>>
>> I run Debian sid
>>
>> Regards
>>
>> Jean-Luc
>>
>>
> That was my doing. I got to run and will look at it in about 4 hours.
> In the mean time, can you test changing the two functions in sys_ansi.h
> I expect HWND is undefined.
> void SetWindowOwner(PVOID Owner);
> void CenterDialog(PVOID hDlg);
I have attached a patch. Does this work for you?
The two functions of question are exposed for use with GUI build of
libPano13 but are not reliant with the CMD version.
--
Jim Watters
http://photocreations.ca
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"hugin and other free panoramic software" group.
A list of frequently asked questions is available at:
http://wiki.panotools.org/Hugin_FAQ
To post to this group, send email to hugin-ptx@googlegroups.com
To unsubscribe from this group, send email to
hugin-ptx+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/hugin-ptx
-~--~~~~--~~--~--~---
Index: sys_ansi.c
===
--- sys_ansi.c (revision 1137)
+++ sys_ansi.c (working copy)
@@ -25,8 +25,8 @@
//-- Public functions required by filter.h
---
-void SetWindowOwner(HWND Owner) {return;}
-void CenterDialog(HWND hDlg) {return;}
+void SetWindowOwner(PVOID Owner) {return;}
+void CenterDialog(PVOID hDlg) {return;}
void filter_main( TrformStr *TrPtr, struct size_Prefs *spref)
{
Index: sys_ansi.h
===
--- sys_ansi.h (revision 1137)
+++ sys_ansi.h (working copy)
@@ -41,8 +41,8 @@
\
return( FALSE );
-void SetWindowOwner(HWND Owner);
-void CenterDialog(HWND hDlg);
+void SetWindowOwner(PVOID Owner);
+void CenterDialog(PVOID hDlg);
#definekSetRemapPrefs_dlg
"REMAP"
#definekSetRemapPrefs_InRect 350
[hugin-ptx] Re: hugin 09.02 - feedback
On Sun 08-Nov-2009 at 19:27 +0100, Erik Krause wrote: >Bruno Postle wrote: > >> There is an 'automatically align images after loading' option, but >> this is disabled by default - It didn't seem like a good idea to >> configure Hugin so the first user experience was waiting for Align >> to finish. > >But that's what actually happens if I use the Assistant to load images. >The first action is that hugin starts a CP finder which loads the images >and tries to find control points. After that hugin loads and aligns the >images and shows the result in the fast preview. This may be a bug or something gone wrong. If I 'Load defaults' in the Assistant preferences, I get 'automatically align images after loading' unselected. If I delete my preferences file (unfortunately this isn't so easy on Windows) then it is unselected when I restart Hugin. Does anyone else see aligning-on-load by default? -- Bruno --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "hugin and other free panoramic software" group. A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ To post to this group, send email to hugin-ptx@googlegroups.com To unsubscribe from this group, send email to hugin-ptx+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/hugin-ptx -~--~~~~--~~--~--~---
[hugin-ptx] Re: hugin 09.02 - feedback
Bruno Postle wrote: > >Alignment is automatic if I press "1. Load images". No need for an > >additional button in a straight forward workflow. > > There is an 'automatically align images after loading' option, but > this is disabled by default - It didn't seem like a good idea to > configure Hugin so the first user experience was waiting for Align > to finish. But that's what actually happens if I use the Assistant to load images. The first action is that hugin starts a CP finder which loads the images and tries to find control points. After that hugin loads and aligns the images and shows the result in the fast preview. best regards -- Erik Krause http://www.erik-krause.de --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "hugin and other free panoramic software" group. A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ To post to this group, send email to hugin-ptx@googlegroups.com To unsubscribe from this group, send email to hugin-ptx+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/hugin-ptx -~--~~~~--~~--~--~---
[hugin-ptx] Re: hugin 09.02 - feedback
On Sun 08-Nov-2009 at 18:48 +0100, Erik Krause wrote: > >Orientation sensors cause more confusion than they solve. In a spherical > the up and down shot have a random orientation. You get mixed >orientation then. And if you shoot RAW it's even worse. Some RAW >converters rotate the image according to the orientation data, some >don't. Could be some rotate and store the unmodified flag in the result >image... So the current Hugin behaviour of ignoring orientation metadata is probably the best option. I just tried stitching a horizontal partial panorama taken in portrait orientation and Hugin indeed assumes it is a vertical panorama (which would be correct with different content). >Alignment is automatic if I press "1. Load images". No need for an >additional button in a straight forward workflow. There is an 'automatically align images after loading' option, but this is disabled by default - It didn't seem like a good idea to configure Hugin so the first user experience was waiting for Align to finish. -- Bruno --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "hugin and other free panoramic software" group. A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ To post to this group, send email to hugin-ptx@googlegroups.com To unsubscribe from this group, send email to hugin-ptx+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/hugin-ptx -~--~~~~--~~--~--~---
[hugin-ptx] Re: hugin 09.02 - feedback
Bruno Postle wrote: > >In this case I'd consider it better if there was an intermediate manual > >step where I could choose image orientation. > > ..or at least pull it from the EXIF info, as modern cameras have > orientation sensors. Orientation sensors cause more confusion than they solve. In a spherical the up and down shot have a random orientation. You get mixed orientation then. And if you shoot RAW it's even worse. Some RAW converters rotate the image according to the orientation data, some don't. Could be some rotate and store the unmodified flag in the result image... >From a GUI point of view it's wrong anyway: There is a button named > >"2. Align", but I don't need to push it... > > I'm not sure what you mean here. Alignment is automatic if I press "1. Load images". No need for an additional button in a straight forward workflow. I assume that I can press "2. Align" after I added manual CPs, but in this case I can as well press "Optimize". If the first button would only load images, then allow for manual rotation, then press Align it would be more logical... best regards -- Erik Krause http://www.erik-krause.de --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "hugin and other free panoramic software" group. A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ To post to this group, send email to hugin-ptx@googlegroups.com To unsubscribe from this group, send email to hugin-ptx+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/hugin-ptx -~--~~~~--~~--~--~---
[hugin-ptx] Re: hugin 09.02 - feedback
On Sun 08-Nov-2009 at 15:01 +0100, Erik Krause wrote: > >However, most panoramas are shot with camera in portrait orientation >anyway. So perhaps this could be the default. This is a problem, although Hugin works ok with photos taken with the camera rotated 90°, a lot of the workflow assumes that you have rotated the photos to the right orientation before importing them into Hugin. i.e. this is what I do when I shoot portrait, I have a script that rotates the files with jpegtran before I start. >In this case I'd consider it better if there was an intermediate manual >step where I could choose image orientation. ..or at least pull it from the EXIF info, as modern cameras have orientation sensors. >From a GUI point of view it's wrong anyway: There is a button named >"2. Align", but I don't need to push it... I'm not sure what you mean here. -- Bruno --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "hugin and other free panoramic software" group. A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ To post to this group, send email to hugin-ptx@googlegroups.com To unsubscribe from this group, send email to hugin-ptx+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/hugin-ptx -~--~~~~--~~--~--~---
[hugin-ptx] Re: hugin 09.02 - feedback
Bruno Postle wrote: > >Hugin deals very good with the above mentioned exposure differences once > >exposure is unlinked on "Camera and Lens" tab. Vignetting, slight white > >balance differences and further exposure differences where optimized > >very good. > > This shouldn't happen, the EV Exposure values are not linked by > default here, can you reproduce this? No, I can't. Must have checked it accidentially. best regards -- Erik Krause http://www.erik-krause.de --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "hugin and other free panoramic software" group. A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ To post to this group, send email to hugin-ptx@googlegroups.com To unsubscribe from this group, send email to hugin-ptx+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/hugin-ptx -~--~~~~--~~--~--~---
[hugin-ptx] Re: libpano SVN 1137 fails to build
Jean-Luc Coulon (f5ibh) wrote: > Hi, > > I get the following: > > [...] > /bin/bash ./libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. > -DHasJPEG -DHasPNG -DHasTIFF -DHasZLIB -D__Ansi__=1 -g -O2 -MT > PTDialogs.lo -MD -MP -MF .deps/PTDialogs.Tpo -c -o PTDialogs.lo > PTDialogs.c > libtool: compile: gcc -DHAVE_CONFIG_H -I. -DHasJPEG -DHasPNG -DHasTIFF > -DHasZLIB -D__Ansi__=1 -g -O2 -MT PTDialogs.lo -MD -MP -MF .deps/ > PTDialogs.Tpo -c PTDialogs.c -fPIC -DPIC -o .libs/PTDialogs.o > In file included from PTDialogs.c:29: > sys_ansi.h:44: error: expected ‘)’ before ‘Owner’ > sys_ansi.h:45: error: expected ‘)’ before ‘hDlg’ > make[2]: *** [PTDialogs.lo] Error 1 > > > I run Debian sid > > Regards > > Jean-Luc > That was my doing. I got to run and will look at it in about 4 hours. In the mean time, can you test changing the two functions in sys_ansi.h I expect HWND is undefined. void SetWindowOwner(PVOID Owner); void CenterDialog(PVOID hDlg); -- Jim Watters http://photocreations.ca --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "hugin and other free panoramic software" group. A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ To post to this group, send email to hugin-ptx@googlegroups.com To unsubscribe from this group, send email to hugin-ptx+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/hugin-ptx -~--~~~~--~~--~--~---
[hugin-ptx] Re: Help compiling Hugin in fresh install of Ubuntu 9.10
Fixed in rev f312b1189a2d. /cls --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "hugin and other free panoramic software" group. A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ To post to this group, send email to hugin-ptx@googlegroups.com To unsubscribe from this group, send email to hugin-ptx+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/hugin-ptx -~--~~~~--~~--~--~---
[hugin-ptx] Re: hugin 09.02 - feedback
Bruno Postle wrote: > >In my opinion straighten should optimize pitch such that the values are > >more or less equal - at least for horizontal projections like > >cylindrical or equirect. Don't know how to achieve this... > > That what it does, it minimises the variation of roll and pitch. > > Currently if you supply Hugin with rotated photos it has no way of > knowing that you have shot a horizontal panorama and not a vertical > one. Usually the panorama has roughly the direction the user intended. Hence the rotation can be estimated. If hugin minimizes roll and pitch variation it apparently starts with a zero value for both. If it would start with the given values it most likely would be successful. Another hint is the chosen projection. If the user choose cylindrical he most likely wants a horizontal panorama. Ok, this is no help for the Assistant which attempts to align the images even before loading. However, most panoramas are shot with camera in portrait orientation anyway. So perhaps this could be the default. In this case I'd consider it better if there was an intermediate manual step where I could choose image orientation. From a GUI point of view it's wrong anyway: There is a button named "2. Align", but I don't need to push it... best regards -- Erik Krause http://www.erik-krause.de --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "hugin and other free panoramic software" group. A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ To post to this group, send email to hugin-ptx@googlegroups.com To unsubscribe from this group, send email to hugin-ptx+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/hugin-ptx -~--~~~~--~~--~--~---
[hugin-ptx] Re: hugin 09.02 - feedback
On Sun 08-Nov-2009 at 12:24 +0100, Erik Krause wrote: > >In my opinion straighten should optimize pitch such that the values are >more or less equal - at least for horizontal projections like >cylindrical or equirect. Don't know how to achieve this... That what it does, it minimises the variation of roll and pitch. Currently if you supply Hugin with rotated photos it has no way of knowing that you have shot a horizontal panorama and not a vertical one. -- Bruno --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "hugin and other free panoramic software" group. A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ To post to this group, send email to hugin-ptx@googlegroups.com To unsubscribe from this group, send email to hugin-ptx+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/hugin-ptx -~--~~~~--~~--~--~---
[hugin-ptx] Re: hugin 09.02 - feedback
On Sat 07-Nov-2009 at 20:44 -0500, Yuval Levy wrote: >Bruno Postle wrote: >> The default image cache size is very small (75 MB I think), 17 five >> megapixel photos will result in churn with images being reloaded. >it seems that the default value is a fixed constant in a header file. >Easy to change, but to which value? IIRC there are occasional reports of >crashes because of an excessively high value. I'm not sure I have ever seen this. Other software (e.g. firefox) manage image caches without needing the user to size it, we should get rid of this option and just do the right thing. >> The straighten function doesn't use control points, which is why the >> vertical points were ignored - It should probably do something >> different (or even nothing at all) when there are vertical or >> horizontal control points. > >does anybody find that function useful? I never use it. When it works it is like magic. It is broken with panoramas without much yaw variation (e.g. single stacks and vertical panoramas), this should be fixed. It should change behaviour when there are horizontal/vertical control points in the project, and switch to a simple 'positions' optimisation. -- Bruno --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "hugin and other free panoramic software" group. A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ To post to this group, send email to hugin-ptx@googlegroups.com To unsubscribe from this group, send email to hugin-ptx+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/hugin-ptx -~--~~~~--~~--~--~---
[hugin-ptx] Re: hugin 09.02 - feedback
Erik Krause wrote: > After that hugin optimizes an almost perfect panorama (very slightly > curved up compared to PTGui) - may be due to CPs clustered in the > middle of the overlap (possibly other autopano parameters might > change this). This can be easily corrected with some vertical control points... Setting CPs manually still sucks but this is the case since version 0.1 or whatever I tried first years ago. If I show the same image in both panes hugin correctly assumes that I want to add a vertical CP. I click the point in the left pane and the other end of the vertical line in the right one. If auto fine tune is on hugin takes ages until the CP is added and it isn't in the place I choose. If auto fine tune is off the right pane magnifies as soon as I click but there is no point. If I click the point it zooms out again with the point set. The magnifying glass shows only if I move the mouse out of the pane - I have to click the point again in order to correct it. Mouse movement when dragging a point is far too rough (in display pixels) then, for a fine correction I have to zoom in manually. The local magnifier is too small and magnifies too much. I didn't find anything in the preferences to change this. To correct a point I must click on the cross. Clicking the flag creates a new point. If zoomed in and the point is not in the middle of the pane it scrolls to the middle as soon as I click the point. Sometimes the point stays with the mouse pointer and sometimes it moves away with the image. The CP list below doesn't react to the delete key. You need to press the Delete with the mouse. The main CP table (F3) however does. best regards -- Erik Krause http://www.erik-krause.de --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "hugin and other free panoramic software" group. A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ To post to this group, send email to hugin-ptx@googlegroups.com To unsubscribe from this group, send email to hugin-ptx+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/hugin-ptx -~--~~~~--~~--~--~---
[hugin-ptx] Re: hugin 09.02 - feedback
Yuval Levy wrote: > > Apparently autopano-sift found control points on > > non-overlapping images: Lots of same looking lego blocks. > > how do other tools available to you deal with the same set of images? Panomatic runs about the same time as autopano-sift and finds about the same amount of wrong points. Jenny Autopano 1.03 works about 2 minutes and finds no wrong points. hugin however doesn't choose the right orientation, the anchor image needs to be rotated manually by 90°. After that hugin optimizes an almost perfect panorama (very slightly curved up compared to PTGui) - may be due to CPs clustered in the middle of the overlap (possibly other autopano parameters might change this). PTGui "Align images" on assistant tab takes roughly 2 minutes to align the images perfectly - correct orientation, straightened panorama pitched down the correct amount, no control points between non-adjacent images. best regards -- Erik Krause http://www.erik-krause.de --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "hugin and other free panoramic software" group. A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ To post to this group, send email to hugin-ptx@googlegroups.com To unsubscribe from this group, send email to hugin-ptx+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/hugin-ptx -~--~~~~--~~--~--~---
[hugin-ptx] Re: hugin 09.02 - feedback
Bruno Postle wrote: > The straighten function doesn't use control points, which is why the > vertical points were ignored - It should probably do something > different (or even nothing at all) when there are vertical or > horizontal control points. In my opinion straighten should optimize pitch such that the values are more or less equal - at least for horizontal projections like cylindrical or equirect. Don't know how to achieve this... > Straighten assumes the photo orientation is 'correct', Hugin doesn't > use any orientation EXIF info, perhaps this would be a good use for > it. The images don't have orientation info and there apparently is no possibility to initially rotate them correctly. best regards -- Erik Krause http://www.erik-krause.de --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "hugin and other free panoramic software" group. A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ To post to this group, send email to hugin-ptx@googlegroups.com To unsubscribe from this group, send email to hugin-ptx+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/hugin-ptx -~--~~~~--~~--~--~---
[hugin-ptx] Re: hugin 09.02 - feedback
Bruno Postle wrote: > The default image cache size is very small (75 MB I think), 17 five > megapixel photos will result in churn with images being reloaded. Wouldn't it be better to have a disk cache if memory cache is full? Loading the original images can take very long if there are many and they are large. Disk cache could store smaller versions and in a format that is easier to read. best regards -- Erik Krause http://www.erik-krause.de --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "hugin and other free panoramic software" group. A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ To post to this group, send email to hugin-ptx@googlegroups.com To unsubscribe from this group, send email to hugin-ptx+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/hugin-ptx -~--~~~~--~~--~--~---
[hugin-ptx] libpano SVN 1137 fails to build
Hi, I get the following: [...] /bin/bash ./libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -DHasJPEG -DHasPNG -DHasTIFF -DHasZLIB -D__Ansi__=1 -g -O2 -MT PTDialogs.lo -MD -MP -MF .deps/PTDialogs.Tpo -c -o PTDialogs.lo PTDialogs.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -DHasJPEG -DHasPNG -DHasTIFF -DHasZLIB -D__Ansi__=1 -g -O2 -MT PTDialogs.lo -MD -MP -MF .deps/ PTDialogs.Tpo -c PTDialogs.c -fPIC -DPIC -o .libs/PTDialogs.o In file included from PTDialogs.c:29: sys_ansi.h:44: error: expected ‘)’ before ‘Owner’ sys_ansi.h:45: error: expected ‘)’ before ‘hDlg’ make[2]: *** [PTDialogs.lo] Error 1 I run Debian sid Regards Jean-Luc pgpZ1kpvyV1hs.pgp Description: PGP signature
[hugin-ptx] Re: hugin 09.02 - feedback
Am Sonntag 08 November 2009 schrieb Yuval Levy: > Bruno Postle wrote: > > The default image cache size is very small (75 MB I think), 17 five > > megapixel photos will result in churn with images being reloaded. > > > > Hmm the wiki says it is 200MB. Either value is too low for any > > modern system, this number should be revisited. > > it seems that the default value is a fixed constant in a header file. > Easy to change, but to which value? IIRC there are occasional reports of > crashes because of an excessively high value. Is there a C / C++ > function to determine how much memory is available? > how about making it > a % of this? how would this account for swap memory on Linux? Don't know, if this would help. I had to set this limit 200MB. But making a small program here shows me, that this limit has nothing to do with real available memory. It was able to allocate up to 2GB of memory in _one_ chunk. > > The straighten function doesn't use control points, which is why the > > vertical points were ignored - It should probably do something > > different (or even nothing at all) when there are vertical or > > horizontal control points. > > does anybody find that function useful? I never use it. I use it. It is very handy for a first visual improvement after optimizing, when there are no vertical or horizontal control points. > Yuv Kornel -- Kornel Benko kornel.be...@berlin.de signature.asc Description: This is a digitally signed message part.
