I plan on making this more automatic, symbolic links + pto2mk looks like a good place to start, just have not had the time to spend on this.
On Thu, Sep 3, 2009 at 12:27 PM, Seb Perez-D <[email protected]<sbprzd%[email protected]> > wrote: > > I have a similar but more automatic approach. I create the pto project > file for one exposure, and then use a custom script to generate the > panoramas for the different exposures. One feature of nona is very > useful: you can pass the names of the images on the command line and > it will use those images instead of the ones in the pto file. What the > script does is to increase the number in the filename of the images. > I plan on making this automatic, too; symbolic links + pto2mk looks like a good place to start, just have to find the time to spend on this. > An alternative would be to use the "Apply template" in Hugin (in the > File menu), which reuses the settings of another pto file. You could > then use ptomerge > (http://search.cpan.org/dist/Panotools-Script/bin/ptomerge) to merge > these different exposures into one. > I did not know about this "Apply template" option, will try it. > Cheers, > > Seb > > On Thu, Sep 3, 2009 at 12:16, Eduardo Perez > Esteban<[email protected]> wrote: > > I guess you are doing HDR panoramas, aren't you? Me too, but I take a > > completely different approach: instead of passing all the images to > Hugin, I > > make a separate panorama for each exposure, and merge them afterwards; > when > > the exposures are aligned, the control points and optimizations can be > > shared, I just change the images. > > > > My workflow is: > > > > * Copy the files from the first exposure to IMG1, IMG2, ..., IMGn > (actually, > > I use symbolic links in Linux, but Windows users will probably have to > copy > > the files). > > * Open IMG1, IMG2, ..., IMGn with Hugin, create the control points, > > optimize, ...; save the project and create a panorama named PANO1. > > * Now copy the files from the second exposure over IMG1, IMG2, ..., IMGn; > > execute the project again, but save the result to PANO2. > > * Repeat for each exposure, and you will obtain a set of bracketed > panoramas > > PANO1, PANO2, ..., PANOn. > > * Do all the HDR work. > > > > Hope this helps. > > > > On Thu, Sep 3, 2009 at 10:19 AM, RueiKe <[email protected]> wrote: > >> > >> I am looking for ways to simplify some of my more complex projects > >> which could be 217 images connected by >10,000 control points. In > >> these cases I am doing 7 shot brackets for 31 images for full 360 x > >> 180 degree pano. > >> > >> Seems like control points would be greatly simplified if I could just > >> get hugin to assume the bracketed images were already aligned. I have > >> done a case where I just picked alignment points on the 4 corners of a > >> few photos and it seemed to work fine. Is this a reasonable > >> approach? Would it be possible to have an option to add a set of > >> fixed control points for a specified set of aligned images? > >> > >> Thanks, > >> Rick > >> > > > > --~--~---------~--~----~------------~-------~--~----~ 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 [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/hugin-ptx -~----------~----~----~----~------~----~------~--~---
