[hugin-ptx] Re: Any way to reuse control points on a different set of images?
Nicolas, That sounds like an awesome option except... Isn't there a limit to the number of photos that can be in hugin? Something like 120? I've hit it before which was one of the main reasons I never tried anything even close to what you're suggesting below... Thanks, Ricardo On Apr 19, 7:08 am, Nicolas Pelletier wrote: > I don't think it's in the official releases yet, but there is the new stack > feature. > > Basically, all the images that are different exposures of the same image, > you assign them the same stack number. Then, whatever the optimization you > do, all of them will end up at exactly the same place. > > Output your panorama with all exposure layers, and you get all your pano for > HDR. > > IMHO, it's the best option (and the one I currently use). > > nick > > > > > > On Fri, Apr 16, 2010 at 6:16 PM, RickyRicky wrote: > > cri, > > > I had originally renamed all my different exposure files to match up > > with the original exposure... That's not too bad but I think your > > "legit" method of just applying a different exposure's .pto file as a > > template is a bit better and more convenient. > > > I'll let you know how it works out! > > > BTW - Yes... Using a great tripod is a must when your panorama is 240 > > photos.. =) > > > Ricky > > > On Apr 16, 2:33 pm, cri wrote: > > > Have you tried to use a template? Just load all the photo at the same > > > exposure level and go through all the needed passages to get the final > > > panorama. Then save the project as pto file. Now start a new poject, > > > load all the images at a different exposure level and select "File->Apply > > template". In the dialog select the previously saved pto file > > > > and you will get all the parameters loaded on the new exposure level > > > images. In this way you could save a panorama for every exposure > > > level. > > > To get the best out of this procedure you need to take all the images > > > from a tripod. > > > > Regards > > > Cristian > > > > On 16 Apr, 20:52, RickyRicky wrote: > > > > > Gents, > > > > > I have shot a few high resolution night time 180 degree panorama but I > > > > think I've been doing it wrong. > > > > > My typical workflow is to shoot from three to six images of each > > > > frame, then to HDR or exposure blend these photos together and THEN to > > > > HDR the resulting images. > > > > > That workflow works but if you want to make any changes to how the > > > > image is HDR'ed or exposure blended, it means you have to start all > > > > over again from the beginning. > > > > > I've been thinking, why don't I create panoramas from each bracketed > > > > exposure using hugin, and then HDR and/or exposure blend the resulting > > > > panoramas? > > > > > The problem is.. Hugin will most likely not select the same control > > > > points for the various different panoramas since at varying exposures, > > > > some control points will be more visible, and others will not. > > > > > Is there any way to force hugin to use the same control points for a > > > > different set of images? > > > > > Thanks for any help! I'm happy to show my work if y'all are > > > > interested in seeing what I've been working on so far... > > > > >http://www.rickyricky.net/Photography/Panoramas/My-Panoramas > > > > > Thanks, > > > > Ricardo Meleschi > > > > > -- > > > > 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 > .com> > > > > For more options, visit this group athttp:// > > groups.google.com/group/hugin-ptx > > > > -- > > > 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
[hugin-ptx] Re: Any way to reuse control points on a different set of images?
cri, I had originally renamed all my different exposure files to match up with the original exposure... That's not too bad but I think your "legit" method of just applying a different exposure's .pto file as a template is a bit better and more convenient. I'll let you know how it works out! BTW - Yes... Using a great tripod is a must when your panorama is 240 photos.. =) Ricky On Apr 16, 2:33 pm, cri wrote: > Have you tried to use a template? Just load all the photo at the same > exposure level and go through all the needed passages to get the final > panorama. Then save the project as pto file. Now start a new poject, > load all the images at a different exposure level and select "File->Apply > template". In the dialog select the previously saved pto file > > and you will get all the parameters loaded on the new exposure level > images. In this way you could save a panorama for every exposure > level. > To get the best out of this procedure you need to take all the images > from a tripod. > > Regards > Cristian > > On 16 Apr, 20:52, RickyRicky wrote: > > > > > > > Gents, > > > I have shot a few high resolution night time 180 degree panorama but I > > think I've been doing it wrong. > > > My typical workflow is to shoot from three to six images of each > > frame, then to HDR or exposure blend these photos together and THEN to > > HDR the resulting images. > > > That workflow works but if you want to make any changes to how the > > image is HDR'ed or exposure blended, it means you have to start all > > over again from the beginning. > > > I've been thinking, why don't I create panoramas from each bracketed > > exposure using hugin, and then HDR and/or exposure blend the resulting > > panoramas? > > > The problem is.. Hugin will most likely not select the same control > > points for the various different panoramas since at varying exposures, > > some control points will be more visible, and others will not. > > > Is there any way to force hugin to use the same control points for a > > different set of images? > > > Thanks for any help! I'm happy to show my work if y'all are > > interested in seeing what I've been working on so far... > > >http://www.rickyricky.net/Photography/Panoramas/My-Panoramas > > > Thanks, > > Ricardo Meleschi > > > -- > > 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 > > athttp://groups.google.com/group/hugin-ptx > > -- > 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 athttp://groups.google.com/group/hugin-ptx -- 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] Any way to reuse control points on a different set of images?
Gents, I have shot a few high resolution night time 180 degree panorama but I think I've been doing it wrong. My typical workflow is to shoot from three to six images of each frame, then to HDR or exposure blend these photos together and THEN to HDR the resulting images. That workflow works but if you want to make any changes to how the image is HDR'ed or exposure blended, it means you have to start all over again from the beginning. I've been thinking, why don't I create panoramas from each bracketed exposure using hugin, and then HDR and/or exposure blend the resulting panoramas? The problem is.. Hugin will most likely not select the same control points for the various different panoramas since at varying exposures, some control points will be more visible, and others will not. Is there any way to force hugin to use the same control points for a different set of images? Thanks for any help! I'm happy to show my work if y'all are interested in seeing what I've been working on so far... http://www.rickyricky.net/Photography/Panoramas/My-Panoramas Thanks, Ricardo Meleschi -- 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: Powermac G5 compiling Hugin from svn. No joy. Possible LAPACK problem
Hello Harry, No, I do not have vigra or jhead installed as a part of MacPorts... BigDaddy:Application meleschi$ port installed | grep -i vigra BigDaddy:Application meleschi$ port installed | grep -i jhead Thanks... Anything else I can check? Ricardo On Apr 13, 1:29 pm, Harry van der Wolf wrote: > Hi Ricardo, > > Did you install vigra and/or jhead via MacPorts for some reason? If you did, > please deactivate them (sudo port deactivate vigra; sudo port deactivate > jhead) and reconfigure and recompile Hugin. > If the configure script finds vigra "outside" hugin it will use that one. > > You can find installed packages by running "port installed" or "port > installed | grep ". > The deactivate command will not uninstall the packages. It will only remove > them from the install libraries. If you want them back you can simply use > "sudo port activate ". > > Hoi, > Harry > > 2009/4/13 RickyRicky > > > > > Hey Seth, > > > Thanks for the tip on running Hugin from the command line. I did so, > > and here are the lines before the big crash. I hope someone can > > recognize my problem!: > > > Determining placement of the images: 53% > > Number of images 2 > > Hugin(77452,0xa06cd830) malloc: *** error for object 0x2a2c200: double > > free > > *** set a breakpoint in malloc_error_break to debug > > Optimizing Variables > > Strategy 1 > > Average (rms) distance between Controlpoints > > after 0 iteration(s): 801.152704448697 units > > Strategy 1 > > Average (rms) distance between Controlpoints > > after 1 iteration(s): 801.019725960169 units > > > Optimizing Variables > > Strategy 2 > > Average (rms) distance between Controlpoints > > after 0 iteration(s): 57.1154776303789 units > > Strategy 2 > > Average (rms) distance between Controlpoints > > after 1 iteration(s): 56.9698889445181 units > > Strategy 2 > > Average (rms) distance between Controlpoints > > after 2 iteration(s): 8.60724772529945 units > > Strategy 2 > > Average (rms) distance between Controlpoints > > after 3 iteration(s): 7.72758159217231 units > > Strategy 2 > > Average (rms) distance between Controlpoints > > after 4 iteration(s): 6.58494386005708 units > > Strategy 2 > > Average (rms) distance between Controlpoints > > after 5 iteration(s): 5.40204786941155 units > > Strategy 2 > > Average (rms) distance between Controlpoints > > after 6 iteration(s): 3.79597859019421 units > > Strategy 2 > > Average (rms) distance between Controlpoints > > after 7 iteration(s): 1.66872838105291 units > > Strategy 2 > > Average (rms) distance between Controlpoints > > after 8 iteration(s): 0.479946564550839 units > > Strategy 2 > > Average (rms) distance between Controlpoints > > after 9 iteration(s): 0.479481987047642 units > > Strategy 2 > > Average (rms) distance between Controlpoints > > after 10 iteration(s): 0.479481986986529 units > > > Bus error > > > Thanks, > > Ricardo Meleschi > > > On Apr 13, 10:58 am, Seth Berrier wrote: > > > Hmm, well I got this compiler problem while compiling on my MacBook > > > (incidentally, I didn't think 10.5 would run on powerpc arch anymore, > > glad > > > to know). However, I ignored the error message and things still seem to > > > work okay for me. The Hugin.app and all the supporting applications are > > > built and installed correctly. I had to monkey with the path setting a > > > little bit. For that, you can check out this > > > thread< > >http://groups.google.com/group/hugin-ptx/browse_thread/thread/3efbca4...>. > > > However, the path problem will come up when you do auto control point > > > detection or with the final stitch as this is when external programs are > > > used. I don't think this woulod cause problems at position optimization. > > > > My best advice would be to run hugin from the terminal shell (just run > > > > to hugin.app>/Hugin.app/Contents/MacOS/Hugin) You might get more > > messages > > > from the terminal output. > > > > Seth > > > > On Mon, Apr 13, 2009 at 9:34 AM, RickyRicky wrote: > > > > > Gents, > > > > > I've been working on compiling Hugin these last few days and have > > > > succeeded in getting it compiled, but for some reason whenever I run > > > > Hugin and attempt t
[hugin-ptx] Re: Powermac G5 compiling Hugin from svn. No joy. Possible LAPACK problem
Hey Seth, Thanks for the tip on running Hugin from the command line. I did so, and here are the lines before the big crash. I hope someone can recognize my problem!: Determining placement of the images: 53% Number of images 2 Hugin(77452,0xa06cd830) malloc: *** error for object 0x2a2c200: double free *** set a breakpoint in malloc_error_break to debug Optimizing Variables Strategy 1 Average (rms) distance between Controlpoints after 0 iteration(s): 801.152704448697 units Strategy 1 Average (rms) distance between Controlpoints after 1 iteration(s): 801.019725960169 units Optimizing Variables Strategy 2 Average (rms) distance between Controlpoints after 0 iteration(s): 57.1154776303789 units Strategy 2 Average (rms) distance between Controlpoints after 1 iteration(s): 56.9698889445181 units Strategy 2 Average (rms) distance between Controlpoints after 2 iteration(s): 8.60724772529945 units Strategy 2 Average (rms) distance between Controlpoints after 3 iteration(s): 7.72758159217231 units Strategy 2 Average (rms) distance between Controlpoints after 4 iteration(s): 6.58494386005708 units Strategy 2 Average (rms) distance between Controlpoints after 5 iteration(s): 5.40204786941155 units Strategy 2 Average (rms) distance between Controlpoints after 6 iteration(s): 3.79597859019421 units Strategy 2 Average (rms) distance between Controlpoints after 7 iteration(s): 1.66872838105291 units Strategy 2 Average (rms) distance between Controlpoints after 8 iteration(s): 0.479946564550839 units Strategy 2 Average (rms) distance between Controlpoints after 9 iteration(s): 0.479481987047642 units Strategy 2 Average (rms) distance between Controlpoints after 10 iteration(s): 0.479481986986529 units Bus error Thanks, Ricardo Meleschi On Apr 13, 10:58 am, Seth Berrier wrote: > Hmm, well I got this compiler problem while compiling on my MacBook > (incidentally, I didn't think 10.5 would run on powerpc arch anymore, glad > to know). However, I ignored the error message and things still seem to > work okay for me. The Hugin.app and all the supporting applications are > built and installed correctly. I had to monkey with the path setting a > little bit. For that, you can check out this > thread<http://groups.google.com/group/hugin-ptx/browse_thread/thread/3efbca4...>. > However, the path problem will come up when you do auto control point > detection or with the final stitch as this is when external programs are > used. I don't think this woulod cause problems at position optimization. > > My best advice would be to run hugin from the terminal shell (just run to hugin.app>/Hugin.app/Contents/MacOS/Hugin) You might get more messages > from the terminal output. > > Seth > > > > On Mon, Apr 13, 2009 at 9:34 AM, RickyRicky wrote: > > > Gents, > > > I've been working on compiling Hugin these last few days and have > > succeeded in getting it compiled, but for some reason whenever I run > > Hugin and attempt to align images, hugin always crashes when > > determining placement of the image, after Celeste is run. I don't see > > a log file being generated anywhere. I'm not too familiar with Hugin > > so I may be looking in the wrong places. > > > When I review my compile log, I see I was having problems with LAPACK: > > --- > > [ 3%] Building CXX object src/foreign/jhead/CMakeFiles/huginjhead.dir/ > > exif.o > > In file included from /Users/meleschi/src/hugin/src/foreign/levmar/ > > misc.c:42: > > /Users/meleschi/src/hugin/src/foreign/levmar/misc_core.c:562:2: > > warning: #warning LAPACK not available, LU will be used for matrix > > inversion when computing the covariance; this might be unstable at > > times > > In file included from /Users/meleschi/src/hugin/src/foreign/levmar/ > > misc.c:57: > > /Users/meleschi/src/hugin/src/foreign/levmar/misc_core.c:562:2: > > warning: #warning LAPACK not available, LU will be used for matrix > > inversion when computing the covariance; this might be unstable at > > times > > [ 3%] Building C object src/foreign/levmar/CMakeFiles/huginlevmar.dir/ > > lmlec.o > > /Users/meleschi/src/hugin/src/foreign/levmar/lmlec.c:39:2: warning: > > #warning Linearly constrained optimization requires LAPACK and was not > > compiled! > > - > > > I've searched on the above problem but haven't found exact > > instructions as to how to resolve it. The closest I've found is this: > > - > > I had the same problem with Xcode with OS 10.5. In OS 10.5 LAPACK is > > part of the Accelerate framework. > > I put this into the project
[hugin-ptx] Powermac G5 compiling Hugin from svn. No joy. Possible LAPACK problem
Gents, I've been working on compiling Hugin these last few days and have succeeded in getting it compiled, but for some reason whenever I run Hugin and attempt to align images, hugin always crashes when determining placement of the image, after Celeste is run. I don't see a log file being generated anywhere. I'm not too familiar with Hugin so I may be looking in the wrong places. When I review my compile log, I see I was having problems with LAPACK: --- [ 3%] Building CXX object src/foreign/jhead/CMakeFiles/huginjhead.dir/ exif.o In file included from /Users/meleschi/src/hugin/src/foreign/levmar/ misc.c:42: /Users/meleschi/src/hugin/src/foreign/levmar/misc_core.c:562:2: warning: #warning LAPACK not available, LU will be used for matrix inversion when computing the covariance; this might be unstable at times In file included from /Users/meleschi/src/hugin/src/foreign/levmar/ misc.c:57: /Users/meleschi/src/hugin/src/foreign/levmar/misc_core.c:562:2: warning: #warning LAPACK not available, LU will be used for matrix inversion when computing the covariance; this might be unstable at times [ 3%] Building C object src/foreign/levmar/CMakeFiles/huginlevmar.dir/ lmlec.o /Users/meleschi/src/hugin/src/foreign/levmar/lmlec.c:39:2: warning: #warning Linearly constrained optimization requires LAPACK and was not compiled! - I've searched on the above problem but haven't found exact instructions as to how to resolve it. The closest I've found is this: - I had the same problem with Xcode with OS 10.5. In OS 10.5 LAPACK is part of the Accelerate framework. I put this into the project options OTHER_LDFLAGS = "-framework Accelerate" I'm not sure if this is the correct syntax but it did get rid of the LAPACK warnings. Where exactly do I put the OTHER_LDFLAG option? I've tried multiple places with no joy. I'm running 12 GB of ram on a Dual 2 GHz PowerPC G5 with OSX 10.5.6 fully patched. The svn revision is 3784. I did follow the instructions on http://wiki.panotools.org/Hugin_Compiling_OSX. Here's the info on the ports I have installed... BigDaddy:Application meleschi$ sudo port info boost tiff jpeg libpng wxWidgets subversion openexr exiv2 glew boost @1.38.0 (devel) Variants:darwin, darwin_9, debug, docs, graphml, icu, openmpi, python24, python25, python26, st -- tiff @3.8.2, Revision 3 (graphics) Variants:macosx, universal -- jpeg @6b, Revision 3 (graphics) Variants:universal -- libpng @1.2.35 (graphics) Variants:universal -- wxWidgets @2.8.10 (graphics, devel) Variants:debug, nonmonolithic, universal -- subversion @1.6.1 (devel) Variants:bash_completion, darwin_7, disable_keychain, mac_os_x_server_mod_dav_svn, mod_dav_svn, no_bdb, no_neon, tools, unicode_path -- openexr @1.6.1, Revision 1 (graphics) Variants:universal -- exiv2 @0.18.1 (graphics) Variants:universal -- glew @1.5.1, Revision 1 (graphics, devel) Variants:universal Thanks for any help! Ricardo --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
