For the main website for enblend it's suggested to still use version 4.0 since there's the bug in version 4.1. Are there any Mercurial repositories of enblend that can be used that don't have the bug? If one looks at the development tab in sourceforge there are still commits happening to enblend, so code changes are occurring. Any repositories that could be used?
On Mon 05-Nov-2012 at 14:18 -0800, kevin360 wrote:
>For the main website for enblend it's suggested to still use version 4.0
>since there's the bug in version 4.1. Are there any Mercurial repositories
>of enblend that can be used that don't have the bug? If one looks at the
>development tab in sourceforge there are still commits happening to
>enblend, so code changes are occurring. Any repositories that could be
>used?
The default mercurial branch on sourceforge works well for me and is apparently near to a stable release, I think this note on the website is out of date.
On Monday, November 5, 2012 6:01:47 PM UTC-5, Bruno Postle wrote:
> On Mon 05-Nov-2012 at 14:18 -0800, kevin360 wrote: > >For the main website for enblend it's suggested to still use version 4.0 > >since there's the bug in version 4.1. Are there any Mercurial > repositories > >of enblend that can be used that don't have the bug? If one looks at the > >development tab in sourceforge there are still commits happening to > >enblend, so code changes are occurring. Any repositories that could be > >used?
> The default mercurial branch on sourceforge works well for me and is > apparently near to a stable release, I think this note on the > website is out of date.
I just down loaded Hugin 2011.4 and I am encountering a great many problems, for example under Hugin 2010.4 with a 13 image scene there were no problems automatically locating the control points (Cps) and it was easily stitched. I selected the same set of 13 TIFS and using 2011.4 I was forced to manually identify the Cps, in spite of the fact that I could easily see the CPs and they were quite sharp. When I tried to manually select the Cps, Hugin kept putting them some place other than the spot I selected. After a long and tedious stitching I finally achieved a pano that looked satisfactory and I then selected the button to finalize the pano. That is when the real problems began, specifically Hugin now continues to crash when I try to open the pano. I have attached the failure log.
Date/Time: 2012-11-06 17:43:29.229 -0500
OS Version: Mac OS X 10.7.5 (11G63)
Report Version: 9
Interval Since Last Report: 2802951 sec
Crashes Since Last Report: 6
Per-App Interval Since Last Report: 5085 sec
Per-App Crashes Since Last Report: 5
Anonymous UUID: D065BF1B-3E60-4902-8344-FB84B681A708
First of all: Version 2012.0 has just been released and Yesterday evening
the 2012 bundle has been uploaded. You might just have missed it.
When switching from 2010.4 to 2011.4 I assume you didn't read the "Read Me
First" document inside the dmg. It describes that the integrated openmp
enabled enblend is not compatible on (Mountain) Lion. You should use the
non-openmp version.
In 2011.4 (but also if you use the new 2012.0), you might also try to first
to set all preferences to their defaults on all the tabs of the Preferences
screen.
And finally: Since 2011.2 cpfind is the high-quality inthegrated control
point detector. autopano-sift-C and pan-o-matic are deprecated. Not because
they are worse but they are restricted by all kinds of patents.
Thanks for your response. In your email you mentioned that there was a problem with "Mountain Lion". However, I am using OS 10.7.5 (Lion) not 10.8.
I just down loaded 2012.0 and I am not impressed. I set all of the preferences to "Default" and used CPfind to create a quick-look pano. After spending considerable time manually finding Cps that CPfind was unable to find and then moref time in the Control Point Table discarding some badly mismatched control points (BTW, I then had to go back and manually select additional Cps) I ended up with a quick-look pano that has a horizon that looks like roller coaster. When I attempted to create the final pano I encountered a Tiff Library warning but ultimately got the final pano. On the "good news" side, the color rendition across the 13 images is MUCH better with 2012, however, the horizon is ugly. Version 2010.4 created a "flat horizon" pano with no problems but had an ugly color and brightness shift across the scene.
Do you think that I should go back to 2010.4?
Stan
On Nov 7, 2012, at 1:46 AM, Harry van der Wolf wrote:
> First of all: Version 2012.0 has just been released and Yesterday evening the 2012 bundle has been uploaded. You might just have missed it.
> When switching from 2010.4 to 2011.4 I assume you didn't read the "Read Me First" document inside the dmg. It describes that the integrated openmp enabled enblend is not compatible on (Mountain) Lion. You should use the non-openmp version.
> In 2011.4 (but also if you use the new 2012.0), you might also try to first to set all preferences to their defaults on all the tabs of the Preferences screen.
> And finally: Since 2011.2 cpfind is the high-quality inthegrated control point detector. autopano-sift-C and pan-o-matic are deprecated. Not because they are worse but they are restricted by all kinds of patents.
> Harry
> -- > 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+unsubscribe@googlegroups.com
> For more options, visit this group at http://groups.google.com/group/hugin-ptx
I think you should share your pto with us and you should give some
explanation of what source images you use like fisheye or rectilineair, and
what kind of panorama you are try to achieve, like full 360x180, 360 or
partial.
The set-up with 2010.4 was effortless, Hugin found all of the Control points and stitched the image with no problem. The set-up with 2012.0 is driving me crazy, CPfind is having problems finding the control points and the image is self explanatory.
My image source is a Canon 24/105 lens. I do not use Fisheye. I guess you would call my desired pano to be about 180 degrees (in this example 13 images wide x 1 image high)
Thanks for all your patience and help,
Stan
On Nov 7, 2012, at 5:34 PM, Harry van der Wolf wrote:
> I think you should share your pto with us and you should give some explanation of what source images you use like fisheye or rectilineair, and what kind of panorama you are try to achieve, like full 360x180, 360 or partial.
> Some setups are more difficult then others.
> Harry
> -- > 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+unsubscribe@googlegroups.com
> For more options, visit this group at http://groups.google.com/group/hugin-ptx
just to be sure, have you done this step Harry suggested? "In 2011.4 (but
also if you use the new 2012.0), you might also try to first to set all
preferences to their defaults on all the tabs of the Preferences screen."
> --
> 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+unsubscribe@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/hugin-ptx
> Here is a screen shot of the pano from 2010.4
> Here is the pto of the 2012.0 effort:
> The set-up with 2010.4 was effortless, Hugin found all of the Control
> points and stitched the image with no problem. The set-up with 2012.0 is
> driving me crazy, CPfind is having problems finding the control points and
> the image is self explanatory.
> My image source is a Canon 24/105 lens. I do not use Fisheye. I guess
> you would call my desired pano to be about 180 degrees (in this example 13
> images wide x 1 image high)
> Thanks for all your patience and help,
> Stan
> On Nov 7, 2012, at 5:34 PM, Harry van der Wolf wrote:
> I think you should share your pto with us and you should give some
> explanation of what source images you use like fisheye or rectilineair, and
> what kind of panorama you are try to achieve, like full 360x180, 360 or
> partial.
> Some setups are more difficult then others.
> Harry
> --
> 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+unsubscribe@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/hugin-ptx
> just to be sure, have you done this step Harry suggested? "In 2011.4 (but also if you use the new 2012.0), you might also try to first to set all preferences to their defaults on all the tabs of the Preferences screen."
> --
> 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+unsubscribe@googlegroups.com
> For more options, visit this group at http://groups.google.com/group/hugin-ptx
> Here is a screen shot of the pano from 2010.4
> Here is the pto of the 2012.0 effort:
> The set-up with 2010.4 was effortless, Hugin found all of the Control points and stitched the image with no problem. The set-up with 2012.0 is driving me crazy, CPfind is having problems finding the control points and the image is self explanatory.
> My image source is a Canon 24/105 lens. I do not use Fisheye. I guess you would call my desired pano to be about 180 degrees (in this example 13 images wide x 1 image high)
> Thanks for all your patience and help,
> Stan
> On Nov 7, 2012, at 5:34 PM, Harry van der Wolf wrote:
>> I think you should share your pto with us and you should give some explanation of what source images you use like fisheye or rectilineair, and what kind of panorama you are try to achieve, like full 360x180, 360 or partial.
>> Some setups are more difficult then others.
>> Harry
>> -- >> 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+unsubscribe@googlegroups.com
>> For more options, visit this group at http://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+unsubscribe@googlegroups.com
> For more options, visit this group at http://groups.google.com/group/hugin-ptx
Can we download your images to try to stitch them? It seams that they are
big files... Well, maybe more experienced people here can say something
from the pto itself.
I tried here using other images, but it was not good. I would need to
provide images that make sense for a better evaluation. One strange thing I
noticed is that each image is configured with a different lens and in a
first moment it doesn't make much sense for me. Did you do it yourself or
hugin did it? Has this file been generated with the auto wizard? If you are
trying to do manual stitch you can add CPs as horizontal lines in the
horizon. I couldn't see it your file have them. With the images I used
hugin had to eliminate some CPs that didn't make sense with my images.
I don't think this is the problem, but for this panorama you can also use
rectilinear as the final projection.
> Absolutely set ALL the prefs to default. I really loved using 2010.4,
> 2012.0 not so sure.
> On Nov 7, 2012, at 7:25 PM, Carlos Eduardo G. Carvalho (Cartola) wrote:
> Hi Stan,
> just to be sure, have you done this step Harry suggested? "In 2011.4 (but
> also if you use the new 2012.0), you might also try to first to set all
> preferences to their defaults on all the tabs of the Preferences screen."
>> --
>> 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+unsubscribe@googlegroups.com
>> For more options, visit this group at
>> http://groups.google.com/group/hugin-ptx
>> Here is a screen shot of the pano from 2010.4
>> Here is the pto of the 2012.0 effort:
>> The set-up with 2010.4 was effortless, Hugin found all of the Control
>> points and stitched the image with no problem. The set-up with 2012.0 is
>> driving me crazy, CPfind is having problems finding the control points and
>> the image is self explanatory.
>> My image source is a Canon 24/105 lens. I do not use Fisheye. I guess
>> you would call my desired pano to be about 180 degrees (in this example 13
>> images wide x 1 image high)
>> Thanks for all your patience and help,
>> Stan
>> On Nov 7, 2012, at 5:34 PM, Harry van der Wolf wrote:
>> I think you should share your pto with us and you should give some
>> explanation of what source images you use like fisheye or rectilineair, and
>> what kind of panorama you are try to achieve, like full 360x180, 360 or
>> partial.
>> Some setups are more difficult then others.
>> Harry
>> --
>> 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+unsubscribe@googlegroups.com
>> For more options, visit this group at
>> http://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+unsubscribe@googlegroups.com
> For more options, visit this group at
> http://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+unsubscribe@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/hugin-ptx
> In your Preferences, do you have vertical linefind on? If so, switch it
> off and try again please.
> Harry
To give some extra info: vertical linefind was NOT in 2010.4 and appeared
(as far as I can remember in 2011.4). Vertical linefind is really excellent
when making panos with vertical lines in it (I assume you guessed that one
already) like buildings and so on, but gives me headaches in landscapes,
especially if you have not really 90 degree vertical angles like trees. As
hugin tries to morph your images to make them fit, you will immediately get
a distorted hoizon.
Maybe that's happening in your pano even though I don't see a "vertical
looking" line in your pano apart from "maybe" the vertical shoulders of
some of the rocks.
Harry,
Vertical line was checked I set Preferences to "Default". I deselected "Detect Vertical Line" in Preferences and reran Hugin, "Roller Coaster" effect remains. CPfind still has trouble founding the Control Points; required some manual intervention. Perhaps I should consider reloading Autopano-sift-C or Panomatic?
Thanks,
Stan
On Nov 8, 2012, at 8:22 AM, Harry van der Wolf wrote:
> 2012/11/8 Harry van der Wolf <hvdw...@gmail.com>
> In your Preferences, do you have vertical linefind on? If so, switch it off and try again please.
> Harry
> To give some extra info: vertical linefind was NOT in 2010.4 and appeared (as far as I can remember in 2011.4). Vertical linefind is really excellent when making panos with vertical lines in it (I assume you guessed that one already) like buildings and so on, but gives me headaches in landscapes, especially if you have not really 90 degree vertical angles like trees. As hugin tries to morph your images to make them fit, you will immediately get a distorted hoizon.
> Maybe that's happening in your pano even though I don't see a "vertical looking" line in your pano apart from "maybe" the vertical shoulders of some of the rocks.
> Harry
> -- > 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+unsubscribe@googlegroups.com
> For more options, visit this group at http://groups.google.com/group/hugin-ptx
> Harry,
> Vertical line was checked I set Preferences to "Default". I deselected
> "Detect Vertical Line" in Preferences and reran Hugin, "Roller Coaster"
> effect remains. CPfind still has trouble founding the Control Points;
> required some manual intervention. Perhaps I should consider reloading
> Autopano-sift-C or Panomatic?
> Thanks,
> Stan
> Yes, you can always try that.
They all use different algorithms. one algorithm might work better in one
situation then another.
I can't give you a best solution.
> 2012/11/8 stan <green6...@verizon.net>
> Harry,
> Vertical line was checked I set Preferences to "Default". I deselected "Detect Vertical Line" in Preferences and reran Hugin, "Roller Coaster" effect remains. CPfind still has trouble founding the Control Points; required some manual intervention. Perhaps I should consider reloading Autopano-sift-C or Panomatic?
> Thanks,
> Stan
> Yes, you can always try that. > They all use different algorithms. one algorithm might work better in one situation then another.
> I can't give you a best solution.
> Harry
> -- > 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+unsubscribe@googlegroups.com
> For more options, visit this group at http://groups.google.com/group/hugin-ptx
>> Harry,
>> Vertical line was checked I set Preferences to "Default". I deselected
>> "Detect Vertical Line" in Preferences and reran Hugin, "Roller Coaster"
>> effect remains. CPfind still has trouble founding the Control Points;
>> required some manual intervention. Perhaps I should consider reloading
>> Autopano-sift-C or Panomatic?
>> Thanks,
>> Stan
>> Yes, you can always try that.
> They all use different algorithms. one algorithm might work better in one
> situation then another.
> I can't give you a best solution.
> Harry
> --
> 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+unsubscribe@googlegroups.com
> For more options, visit this group at
> http://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+unsubscribe@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/hugin-ptx
Harry,
I followed the instructions described in the "Read me folder", shown in red below. The Installer automatically placed the executables in the following location: User/Library/Application support/Hugin/Autopano. However, when I started Hugin and went to Preferences the executables are listed as "Configured, not installed", see the attached screen shot. How do I get Hugin 2012.0 to recognize the location that the Installer selected? I never experienced this problem in any of the previous versions of Hugin.
Stan
AutoCP binary Installers for Hugin.
In this dmg you will you will find:
- an "Install ..." application that will install the binary or binaries
- and the binary or binaries itself in the Generator folder.
You can either double click the "Install.." application or drop
the plugin onto the Install application.
After installtion you can configure the AutoCP generator. You can create multiple configurations based on one AutoCP generator.
You start Hugin, you load your images, select the AutoCP generator configuration of your choice and click "Create Control Points" to use the plugin.
> Harry,
> I followed the instructions described in the "Read me folder", shown in
> red below.
Make sure you follow all the ReadMe files out there: those coming with Hugin and those coming with the CP detectors.
> The Installer automatically placed the executables in the
> following location: *User/Library/Application support/Hugin/Autopano.
> *However, when I started Hugin and went to Preferences the executables
> are listed as "Configured, not installed", see the attached screen shot.
What you see as "Configured, not installed" is a part of the description of that particular CP detector setting. It's what you see in the list of available CP detector settings in the Images tab.
These preset names should give the user a hint that they need to be configured. Just double click on it in the Preferences to open a dialog window where you can edit everything just as it is mentioned in the ReadMe. That's also the place where you can edit the description. Hint: just delete that "Configured, not installed" part.
> How do I get Hugin 2012.0 to recognize the location that the Installer
> selected? I never experienced this problem in any of the previous
> versions of Hugin.
It's been there for quite some time. And it's one of the rare cases where I'd like to use the phrase "It's not a problem, it's a feature".
> AutoCP binary Installers for Hugin.
> In this dmg you will you will find:
> - an "Install ..." application that will install the binary or binaries
> - and the binary or binaries itself in the Generator folder.
> You can either double click the "Install.." application or drop
> the plugin onto the Install application.
> After installtion you can configure the AutoCP generator. You can create
> multiple configurations based on one AutoCP generator.
...means: open the Preferences -> "CP detectors", click on one setting and click on "edit"
> You start Hugin, you load your images, select the AutoCP generator
> configuration of your choice and click "Create Control Points" to use
> the plugin.
Carl,
I surrender! This is white flag time.
I got the Autopano-sift to function but it too has trouble finding the CPs, even in locations where there is good contrast and the CP features are sharp. As for the result, take a look at the attached screen shot, there are no words in English to describe this mess.
Stan
> stan schrieb am 09.11.12 13:35:
>> Harry,
>> I followed the instructions described in the "Read me folder", shown in
>> red below.
> Make sure you follow all the ReadMe files out there: those coming with Hugin and those coming with the CP detectors.
>> The Installer automatically placed the executables in the
>> following location: *User/Library/Application support/Hugin/Autopano.
>> *However, when I started Hugin and went to Preferences the executables
>> are listed as "Configured, not installed", see the attached screen shot.
> What you see as "Configured, not installed" is a part of the description of that particular CP detector setting. It's what you see in the list of available CP detector settings in the Images tab.
> These preset names should give the user a hint that they need to be configured. Just double click on it in the Preferences to open a dialog window where you can edit everything just as it is mentioned in the ReadMe. That's also the place where you can edit the description. Hint: just delete that "Configured, not installed" part.
>> How do I get Hugin 2012.0 to recognize the location that the Installer
>> selected? I never experienced this problem in any of the previous
>> versions of Hugin.
> It's been there for quite some time. And it's one of the rare cases where I'd like to use the phrase "It's not a problem, it's a feature".
>> AutoCP binary Installers for Hugin.
>> In this dmg you will you will find:
>> - an "Install ..." application that will install the binary or binaries
>> - and the binary or binaries itself in the Generator folder.
>> You can either double click the "Install.." application or drop
>> the plugin onto the Install application.
>> After installtion you can configure the AutoCP generator. You can create
>> multiple configurations based on one AutoCP generator.
> ...means: open the Preferences -> "CP detectors", click on one setting and click on "edit"
>> You start Hugin, you load your images, select the AutoCP generator
>> configuration of your choice and click "Create Control Points" to use
>> the plugin.
> Carl
> -- > 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+unsubscribe@googlegroups.com
> For more options, visit this group at http://groups.google.com/group/hugin-ptx
Surrender not accepted for such a simple partial panorama... ;-)
I'm not sure if one can expect good control point detection in the center images of your panorama. Waves are always a changing and yet so similar ;-)
For you scenario you'll need some manual alignment via the Fast Preview window. Hope you didn't you zoom during taking the shots? Make sure they all use the same fov. Did you shoot them handheld? Wouldn't be a problem, though.
In your case I'd reset all values (Camera and Lens tab) and step by step optimize while looking for some nasty misplaced CPs.
How about uploading the complete project somewhere so someone can have a look at it?
Cheers,
Carl
stan schrieb am 09.11.12 14:44:
> Carl,
> I surrender! This is white flag time.
> I got the Autopano-sift to function but it too has trouble
> finding the CPs, even in locations where there is good contrast
> and the CP features are sharp. As for the result, take a look
> at the attached screen shot, there are no words in English to
> describe this mess.
> Stan
How do you suggest I up load the images, I will change them to JPEG in order to keep the size down.
At the risk of blasphemy I went to Photo merge in PS 5.5, this was tediously, creepy, crawly slow (unacceptably, I had time to go up stairs and make a second cup of coffee and finished it before PS completed the operation) but PS found the CPs and the horizon was flat; the color was good too.
On Nov 9, 2012, at 9:26 AM, Carl von Einem wrote:
> Surrender not accepted for such a simple partial panorama... ;-)
> I'm not sure if one can expect good control point detection in the center images of your panorama. Waves are always a changing and yet so similar ;-) I did not use the waves, I manually selected CP features in the rocks.
> For you scenario you'll need some manual alignment via the Fast Preview window. Hope you didn't you zoom during taking the shots? (Did not zoom or otherwise alter the FOV) Make sure they all use the same fov. Did you shoot them handheld? I used a home made NPP on my tripod. Wouldn't be a problem, though.
> I also had to tweak the foggy horizon of this panorama and carefully select some CPs manually:
> http://worldwidepanorama.org/wwp_rss/go/n7775 I like the shot, it looked more complicated than mine.
> In your case I'd reset all values (Camera and Lens tab) and step by step optimize while looking for some nasty misplaced CPs. One problem I encountered while manually selecting the CPs was that Hugin kept trying to move them some place other than the feature I selected.
> How about uploading the complete project somewhere so someone can have a look at it?
> Cheers,
> Carl
> stan schrieb am 09.11.12 14:44:
>> Carl,
>> I surrender! This is white flag time.
>> I got the Autopano-sift to function but it too has trouble
>> finding the CPs, even in locations where there is good contrast
>> and the CP features are sharp. As for the result, take a look
>> at the attached screen shot, there are no words in English to
>> describe this mess.
>> Stan
> -- > 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+unsubscribe@googlegroups.com
> For more options, visit this group at http://groups.google.com/group/hugin-ptx
> How do you suggest I up load the images, I will change them to JPEG in
> order to keep the size down.
> At the risk of blasphemy I went to Photo merge in PS 5.5, this was
> tediously, creepy, crawly slow (unacceptably, I had time to go up stairs
> and make a second cup of coffee and finished it before PS completed the
> operation) but PS found the CPs and the horizon was flat; the color was
> good too.
> On Nov 9, 2012, at 9:26 AM, Carl von Einem wrote:
> Surrender not accepted for such a simple partial panorama... ;-)
> I'm not sure if one can expect good control point detection in the center
> images of your panorama. Waves are always a changing and yet so similar ;-)
> I did not use the waves, I manually selected CP features in the rocks.
> For you scenario you'll need some manual alignment via the Fast Preview
> window. Hope you didn't you zoom during taking the shots? (Did not zoom
> or otherwise alter the FOV) Make sure they all use the same fov. Did you
> shoot them handheld? I used a home made NPP on my tripod. Wouldn't be a
> problem, though.
> I also had to tweak the foggy horizon of this panorama and carefully
> select some CPs manually:
> http://worldwidepanorama.org/wwp_rss/go/n7775 I like the shot, it looked
> more complicated than mine.
> In your case I'd reset all values (Camera and Lens tab) and step by step
> optimize while looking for some nasty misplaced CPs. One problem I
> encountered while manually selecting the CPs was that Hugin kept trying to
> move them some place other than the feature I selected.
> How about uploading the complete project somewhere so someone can have a
> look at it?
> Cheers,
> Carl
> stan schrieb am 09.11.12 14:44:
> Carl,
> I surrender! This is white flag time.
> I got the Autopano-sift to function but it too has trouble
> finding the CPs, even in locations where there is good contrast
> and the CP features are sharp. As for the result, take a look
> at the attached screen shot, there are no words in English to
> --
> 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+unsubscribe@googlegroups.com
> For more options, visit this group at
> http://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+unsubscribe@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/hugin-ptx
Best is to zip your images together with the project file.
Either from Finder menu 'File' -> 'Create Archive' or use use Clean Archiver from http://www.sopht.jp/cleanarchiver/ which I prefer since it has an option to exclude those ".DS-Store" and "._*" files. They are invisible on Mac but typically confuse users on other platforms.
> How do you suggest I up load the images, I will change them to JPEG in
> order to keep the size down.
> At the risk of blasphemy I went to Photo merge in PS 5.5, this was
> tediously, creepy, crawly slow (unacceptably, I had time to go up stairs
> and make a second cup of coffee and finished it before PS completed the
> operation) but PS found the CPs and the horizon was flat; the color was
> good too.
> On Nov 9, 2012, at 9:26 AM, Carl von Einem wrote:
>> Surrender not accepted for such a simple partial panorama... ;-)
>> I'm not sure if one can expect good control point detection in the
>> center images of your panorama. Waves are always a changing and yet so
>> similar ;-) I did not use the waves, I manually selected CP features
>> in the rocks.
>> For you scenario you'll need some manual alignment via the Fast
>> Preview window. Hope you didn't you zoom during taking the shots? (Did
>> not zoom or otherwise alter the FOV) Make sure they all use the same
>> fov. Did you shoot them handheld? I used a home made NPP on my tripod.
>> Wouldn't be a problem, though.
>> I also had to tweak the foggy horizon of this panorama and carefully
>> select some CPs manually:
>> http://worldwidepanorama.org/wwp_rss/go/n7775 I like the shot, it
>> looked more complicated than mine.
>> In your case I'd reset all values (Camera and Lens tab) and step by
>> step optimize while looking for some nasty misplaced CPs. One problem
>> I encountered while manually selecting the CPs was that Hugin kept
>> trying to move them some place other than the feature I selected.
>> How about uploading the complete project somewhere so someone can have
>> a look at it?
>> Cheers,
>> Carl
>> stan schrieb am 09.11.12 14:44:
>>> Carl,
>>> I surrender! This is white flag time.
>>> I got the Autopano-sift to function but it too has trouble
>>> finding the CPs, even in locations where there is good contrast
>>> and the CP features are sharp. As for the result, take a look
>>> at the attached screen shot, there are no words in English to
>>> describe this mess.
>>> Stan
>> --
>> 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+unsubscribe@googlegroups.com
>> For more options, visit this group at
>> http://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+unsubscribe@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/hugin-ptx
Carl,
I've given up for now.
I was able to start at the left and create a fairly decent pano using 6 images. When I added the 7th image the pano folded back on its self. I then went to the right side and created a pano using 6 images, not too bad but it became clear that the waves were causing weird results in spite of manually selecting the CPs. I was planning to send the pile garbage to you via DropBox but DropBox has locked up my machine. Bottom line, I will take a new set of shots (without waves) and try again later.
Thanks for you help,
Stan
