[hugin-ptx] Re: cropping gone bad?
On Fri, Aug 14, 2009 at 9:43 PM, slaterson wrote: > > will send it tomorrow morning... this is from an hdr pano, there are > actually three raws, each of the raws was exposed several times and > fused. > > thanks > > Ah, I was wondering how the exposure was so evenly lit. You say each of the raws was exposed multiple times...If you bracketed with the camera, did you also apply exposure compensation with UFRaw to get even more range? I noticed you also downsize your final result within Hugin. I remember reading that nona's interpolaters weren't very good at downsizing and it was better to render to optimal size and then downsize in another application such as gimp or imagemagick that had better reducing interpolation routines. Can someone confirm or deny this? I am curious about your nadir shot. Do you use some sort of extension to offset the camera from the tripod? Best Regards, - Gerry --~--~-~--~~~---~--~~ 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: cropping gone bad?
will send it tomorrow morning... this is from an hdr pano, there are actually three raws, each of the raws was exposed several times and fused. thanks On Aug 14, 7:24 pm, Gerry Patterson wrote: > On Fri, Aug 14, 2009 at 3:44 PM, slaterson > wrote: > > > > > i converted my project to jpg to upload. it can be downloaded here: > >https://rcpt.yousendit.com/726357889/d3635cbcd4b284c9118a79dd55e85e9e > > > i ran a test on the jpgs it stitches perfectly, just as i expected the > > tifs to stitch. this seems to indicate there there is something wrong > > with tif input? to run the test, i converted each tif to jpg, then > > copied my pto file and did a global search and replace, replacing .tif > > with .jpg. i then opened the new pto file in hugin and stitched it. > > the output was fine, no missed cropping so my tripod and camera mount > > aren't showing the final image. i also noticed the remapped images > > were cropped properly using jpgs, while image 11 is not cropped > > properly using tifs. > > Hello, > > I was able to remap the 11th image, and indeed it does work properly with > the JPG you sent. I see that the tiff you sent does not have the area > cropped out. However, you didn't attached the input tiff. I would like to > try to repeat the error so one can try to diagnose the problem. Would send > in the tiff file? Perhaps you could also attach the RAW file (as I use > ufraw as well) so I can start from the very beginning of your workflow. You > don't need to send all of the images, just the 11th one. > > Best Regards, > > - Gerry --~--~-~--~~~---~--~~ 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: cropping gone bad?
On Fri, Aug 14, 2009 at 3:44 PM, slaterson wrote: > > i converted my project to jpg to upload. it can be downloaded here: > https://rcpt.yousendit.com/726357889/d3635cbcd4b284c9118a79dd55e85e9e > > i ran a test on the jpgs it stitches perfectly, just as i expected the > tifs to stitch. this seems to indicate there there is something wrong > with tif input? to run the test, i converted each tif to jpg, then > copied my pto file and did a global search and replace, replacing .tif > with .jpg. i then opened the new pto file in hugin and stitched it. > the output was fine, no missed cropping so my tripod and camera mount > aren't showing the final image. i also noticed the remapped images > were cropped properly using jpgs, while image 11 is not cropped > properly using tifs. > > Hello, I was able to remap the 11th image, and indeed it does work properly with the JPG you sent. I see that the tiff you sent does not have the area cropped out. However, you didn't attached the input tiff. I would like to try to repeat the error so one can try to diagnose the problem. Would send in the tiff file? Perhaps you could also attach the RAW file (as I use ufraw as well) so I can start from the very beginning of your workflow. You don't need to send all of the images, just the 11th one. Best Regards, - Gerry --~--~-~--~~~---~--~~ 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: [OSX] Howto build a Hugin bundle on MacOSX
on topic: we have a few GSoC projects coming to maturity and we will issue a series of incremental releases. this is to avoid the protracted freeze that bogged us during 0.8.0 because we tried to release too much at the same time. this means that we need OSX testers to make sure that what we release builds. I am confident that even if our OSX users community is small, it is very active and forthcoming and will find the resources to test that snapshot releases build. The next expected release is 2009.02.0, with the added feature of GPU stitching and some incremental improvements to the user interface by Thomas, Gerry, and others. Guido Kohlmeyer wrote: > I even mourn my dying laptop and thought about buying a MacBook Pro > although I never used OSX before. I looked for a lightweight solid > long-run laptop with good display resolution. I found a macbook which > fulfill nearly all my requirements. I looked for a similar hardware but > it is not much cheaper. Particular when I take only big manufactures > into acount. Now that a matt display is available for a 15 inch macbook > too, I didn't see any drawbacks. Ok, the trackpoint of my thinkpad was > very ergonomic and I will miss it. current generation MacBooks are fantastic. The first time since a long while that an Apple products convince me that it is worth the price tag. My only concern is that in a few months it will be obsolete as Apple will move to a Nehalim based platform, so probably 30% more power (or more efficiency) for the same price. If the acquisition is not urgent, I'd wait. My Thinkpad a20m is still around. By now it is underspecified even compared with a NetBook. I had my son playing on it and it is rock-solid. Yuv --~--~-~--~~~---~--~~ 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: No Hugin 0.8 for Windows?
Hi Vladimir, JeCh wrote: > I think your answer to Flo wasn't quite right. I > tested Hugin 0.8 on win32 and except of the problem I mentioned at > http://groups.google.com/group/hugin-ptx/browse_thread/thread/3aaf8a5c7219a25c > I didn't run into any problems. well, I did run into problems. > So I think the short and right answer should have been "There are some > 3rd party dependencies broken on Windows." I think it would be a good > idea to post this somewhere on the homepage, because it is really > confusing. The homepage says that 0.8 has been released, I go to > "Download" and I get 0.7 without any explanation. I think it is good > idea to point to 0.7 until all dependencies for 0.8 are fixed, but it > should be said and explained somewhere on the Hugin site. We can't add explanations to the "Download" link - it is automatically generated by SourceForge. Explaining on the homepage? I am not sure how. I am not inclined to do so in the detail that you write above. First: because we'd have to do it for all platforms, not only Windows. Binary distribution on Ubuntu is not much better. Second: because as far as I am concerned, hugin-0.8.0.tar.gz is what the Hugin developers team released. It is source code that has been superficially tested to build on the supported platforms. It's a recipe to build the binary; it is not the binary itself. Building the binaries is left to the users community. Once there are binaries of appropriate quality level, we add them to the SF archive. It's like a movie studio releasing a film. First the film is released to theatres. A few weeks/months later it is released on DVD for home use. If you know how to deal with the recipe, you can take what the Hugin released to theatres and enjoy it right away. If not, you will have to wait patiently until the binary release. We have no resources for binaries. I have limited time and I rather put it to work on the next features than on making a binary work that I won't even use. Some users communities are smaller, some are bigger, some are faster, some are slower. We can and should not wait for all binaries to be ready and tested before releasing. But we should not distribute unfinished binaries as official. And we can and should not bend to the expectations of a minority of vocal users who mistake this for a commercial software company; have unreasonable expectations; talk of money and competition with commercial software without walking their talk. http://sourceforge.net/project/project_donations.php?group_id=77506 Yuv Yuv --~--~-~--~~~---~--~~ 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: cropping gone bad?
i converted my project to jpg to upload. it can be downloaded here: https://rcpt.yousendit.com/726357889/d3635cbcd4b284c9118a79dd55e85e9e i ran a test on the jpgs it stitches perfectly, just as i expected the tifs to stitch. this seems to indicate there there is something wrong with tif input? to run the test, i converted each tif to jpg, then copied my pto file and did a global search and replace, replacing .tif with .jpg. i then opened the new pto file in hugin and stitched it. the output was fine, no missed cropping so my tripod and camera mount aren't showing the final image. i also noticed the remapped images were cropped properly using jpgs, while image 11 is not cropped properly using tifs. On Aug 13, 2:08 pm, Bruno Postle wrote: > On Wed 12-Aug-2009 at 15:33 -0700, slaterson wrote: > > > > >i am working on a 360x180 pano using a fisheye lens. i have cropped > >the nadir shot heavily as well as the bottom 'row' of photos to remove > >the tripod. when i show the pano in the preview window, everything > >looks great. when i stitch the pano the output has a huge chunk of > >tripod and some of my toes included. > > Are you erasing data in the photos with an image editor or using the > hugin Crop tab? > > Can you upload an image somewhere? There is a minor bug in enblend > where data hidden by alpha channel transparency in the first photo > gets revealed in the final stitch, maybe you are seeing that. > > -- > 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: Pure JavaScript pano viewer
On Wed 01-Apr-2009 at 09:30 +0100, Bruno Postle wrote: >On Wed 01-Apr-2009 at 01:11 -0700, Bart.van.Andel wrote: >> >>Well, this page here suggests that 3D is very well possible with the >>canvas element: >> >>http://www.xs4all.nl/~peterned/3d/ > >That's exactly how it can be done, there is everything here for a >no-plugin cubic panorama viewer, and the speed is comparable to >flash panoramas. Here's another very lively example, just using and javascript: http://gyu.que.jp/jscloth/touch.html BSD licensed too: http://gyu.que.jp/jscloth/parpevision.js http://www.slideshare.net/gyuque/mozilla-party-2009-canvas-programming -- 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] bug in shear parameter handling: READ IT if you use them!
Hi Everybody, There was a bug in panotools. It involves the parameters g and t (it has survived since their conception). In a nutshell, they have never worked properly. More specifically, its inverse was wrongly computed when both g and t were different from zero (I can elaborate on why, if there is interest). I have a patch now, that I'll commit in the following hours. This patch might disrupt some people's panoramas iff they use a script with both g and t <> 0. I think almost nobody does, because the parameters were useless. I suspect this is the reason they were never included in the hugin interface (besides the fact that they are of little practical use). Dev is finishing the code to add a new feature to the evaluation stack, called 'tilt'. This will be similar to shear, but will allow an effect similar to "shear" with independent parameters in each side of the image (think in terms of holding a photo and "tilting" it in any angle). Once his tilt code is finalized, the next step is to add code to the optimizer, in order for the new parameters of the tilt function to work. --dmg -- -- Daniel M. German http://turingmachine.org/ http://silvernegative.com/ dmg (at) uvic (dot) ca replace (at) with @ and (dot) with . --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: {Spam?} [hugin-ptx] Double quotes in pathnames and error handling by align_image_stack
Bruno Postle wrote: > On Mon 10-Aug-2009 at 09:19 +0200, Adriaan van Os wrote: >>> 1. align_image_stack silently fails if the pathname to the source >>> files contains a name between double quotes > >>> 2. align_image_stack does some error reporting in this situation, >>> e.g. > >>> but, as far as I know, these messages are written to >>> standard-output rather than standard-error. >>> >>> 3. align_image_stack ignores the internal errors, happily >>> produces unaligned output images and returns exit code success >>> (exit code 0). > >> The response to my bug report is truly overwhelming. > > I guess you are just faster than the rest of us. This is a good > report and this bug needs to be fixed, but it will get lost on the > mailing list. It really needs to be put in the bug tracker, I've > pasted it here: > > https://sourceforge.net/tracker/?func=detail&aid=2837155&group_id=77506&atid=550441 Thanks for looking into this. I didn't know there is a bug-tracker. Regards, Adriaan van Os --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: {Spam?} [hugin-ptx] Double quotes in pathnames and error handling by align_image_stack
Sorry, looking back on this, I should have done this. Harry 2009/8/13 Bruno Postle > > On Mon 10-Aug-2009 at 09:19 +0200, Adriaan van Os wrote: > >> > >> 1. align_image_stack silently fails if the pathname to the source > >> files contains a name between double quotes > > >> 2. align_image_stack does some error reporting in this situation, > >> e.g. > > >> but, as far as I know, these messages are written to > >> standard-output rather than standard-error. > >> > >> 3. align_image_stack ignores the internal errors, happily > >> produces unaligned output images and returns exit code success > >> (exit code 0). > > >The response to my bug report is truly overwhelming. > > I guess you are just faster than the rest of us. This is a good > report and this bug needs to be fixed, but it will get lost on the > mailing list. It really needs to be put in the bug tracker, I've > pasted it here: > > > https://sourceforge.net/tracker/?func=detail&aid=2837155&group_id=77506&atid=550441 > > -- > 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 -~--~~~~--~~--~--~---
