Hi James, I haven't seen change yet, but can the warning (or maybe it already does) contain predicted output size and information what to do if this is not intentional ? For example: Warning output canvas size is 980000x980000 if this is not Your intention, use Sticher tab and set a different output image size then press "Stich Now" to create panorama.
I guess it's not possible to calculate how much memory algorithm will use ? I agree that not everyone's intention is to scale down panorama, so information about size of canvas or better if possible the approximate memory that algorithm will use, would help to tune those parameters. For example I would be able to set slightly smaller canvas in Sticher Tab, but still larger than it is by default and be able to compute it in rational time without freezing my system and running out of both swap and ram. Maybe something checking available system memory and comparing it to what algorithm can use, would also be helpful. I would really like to make as precise as possible output picture, but in feasible time on my hardware and without blocking entire OS. Thanks for fixing this ! On Oct 12, 1:16 am, James Legg <lankyle...@gmail.com> wrote: > On Sun, 2010-10-10 at 14:18 -0700, Mateusz wrote: > > I think, that it should not use entire memory 12Gb at once. > > The algorithm should be aware that there are machine limitations and > > should not allocate all possible memory even if the size of canvas is > > absurdity. > > For me the correct behaviour would be allocating less memory and > > freeing it when done, doing things at steps. > > This would help with large stitches, but I don't think all large > stitches are intentional. > > For instance if I take a 360 degree equirectangular panorama then just > change the projection to stereographic, Hugin sets the horizontal field > of view to 359 degrees. Stereographic projection cannot contain 360 > degrees, but I wouldn't want it to crop my image unexpectedly. > > Pressing "Create panorama" on the assistant tab now would try to make an > image likely to be hundreds of gigapixels, where only the very middle > has enough image data. But I wouldn't want Hugin to lose precession > unexpectedly either. > > If I notice that it looks bad in the preview, and understand why, I > might lower the field of view to contain only the bits I want. However, > it could look reasonable in the preview and still make images over a > gigapixel in size, where only the very middle has enough data. These > size images are difficult to store, display, and print too. > > > Also if this is not > > possible, then at least there should be a confirmation dialog, "Do You > > really want to do that ... or You wanted this..." and then choose. > > Anyway much better solution would be fixing algorithm then interface > > if possible. > > I added a warning for very large panoramas. > > I think fixing the interface includes making users aware of the > practical limits of the projections, which is important to this issue. > > > > > On Oct 10, 10:37 pm, Bruno Postle <br...@postle.net> wrote: > > > It is a bug (because Hugin should stop you from doing this), but > > > also the correct behaviour for what you are asking Hugin to do. > > > > The Assistant resets the pixel dimensions of the canvas to best fit > > > the data. In particular it ensures that the canvas is big enough to > > > represent all the detail without any part being downscaled. > > > > A 350° wide stereographic panorama probably really does need to be > > > rendered with hundreds of gigapixels, otherwise the middle section > > > has much less detail than the original photos - You really don't > > > intend to lose information do you? > > -James -- 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
