In addition, other programs often use date/time of photo as an indication of loading to the grid. For example, the first photo having a time of 11:00 and the next having a time of 11:00:15 would indicate the first and next photos of the set, and their relationship to one another. This method is can also be used to extract multiple pano's from a group of photos. One would expect photos taken on the 1st of the month to be a set and photos taken on the second of the month to be a set as well.
Using a date/time sequence, when photo 12 and photo 13 does not match, one can assume a new row. One only needs to indicate direction at this point. On Mon, 2011-01-03 at 09:31 -0600, Dale Beams wrote: > Not as complicated as one might seem. There are many programs that ask > for table sizes. This is essentially a table > > Dialog: > > How many rows & columns > Which direction > Etc. > > The other option is to present a table layout. It's then easy to mark > each cell in the table as row/column, set the direction, set the > starting row, etc. Rows with different number of photos sets would have > empty cells where the rows were shorter. > > Comparison is a good measuring stick to be subject to, unless the > project is so creative and so groundbreaking it becomes the measuring > stick. > > Even the simplest stitchers have layout options, direction, rotation, > etc. > > Dale > > > On Mon, 2011-01-03 at 14:49 +0000, Bruno Postle wrote: > > On Sun 02-Jan-2011 at 22:15 -0500, Yuval Levy wrote: > > > > >> I see very little value in a wizard that asks you a number of rows > > >> and columns, this will only add complication to the GUI and won't > > >> help a significant proportion of people who do seriously large > > >> panoramas. > > > > > >and yet there is demand for that? > > > > People ask for it. But we had a determined attempt to design a GUI > > for it as part of James's Layout Summer of Code project and > > immediately encountered so many special cases that it would be the > > most complex interface in the whole software. Some of the issues: > > > > Different numbers of photos in each row is normal (actually it's > > preferred for spherical panoramas). > > > > Left to right, or right to left, or up and down sequences are all > > valid. > > > > Zig-zagging sequences are valid and preferable for partial > > panoramas. > > > > Middle-row first is almost always preferable to starting top-left. > > > > All this is why the multi-row procedure exists in Hugin, in > > principle it deals with all these cases automatically without a GUI. > > > > -- > > 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
