Dear all,
Unfortunately we needed to release another rc build due to a (very old)
error in OS X. Also the updated brazilian translation has been added.
NOTE: The translation is not yet complete for all languages for this release.
Please check further down in this mail for the status of the translations.
A number of users have built recent snapshots and executables are likely to
be
announced within a few days of this tarball release.
Watch http://groups.google.com/group/hugin-ptx for the announcements of
binary
releases. If you don't see a binary for your platform it has most likely
not
been produced yet. Consider stepping up to the task. Instructions at
The lensfun library for reading and writing lens parameters from/to
database has now been integrated into Hugin.
Users can now search the lensfun library and load lens parameters.
Added new tool pto_gen for generation of pto file from image files.
Other Improvements
* Various improvements to cpfind including a prealign matching strategy
and pair wise matching for multirow heuristic
* Added option to keep exposure fused stacks
* pano_modify: Added HDR autocrop option
* Many more improvements and bug fixes.
UPGRADING
Upgrading from previous versions of Hugin should be seamless. If you do have
problems with old settings, these can be reset in the Preferences by
clicking
'Load defaults'.
It is strongly recommeded to set the default control point detector to
Hugin's CPFind. It is the only control point generator endorsed by Hugin.
Third-party generators may be compatible with the plug-in architecture.
There is a known problem building Hugin with CMake 2.8.5rc2.
Workaround: Upgrade to a newer CMake version.
Mac OS X:
- Mac OS X Tiger (10.4) is no longer supported.
- The PPC platform is no longer supported.
- The OpenMP enabled enblend is now compatible on Mac OS X Lion (10.7).
- The cmake compilation of Hugin is currently broken due to the fact that
the boost library on OS X is currently at version 1.50 and boost versions
=> 1.48
conflict with a number of Mac OS X macros (from AssertMacros.h). This can
not be disabled as WxWindows for Mac (a.k.a. WxMac) needs these macros.
An XCode build, where a specific boost (<=1.46) can be specified, is
possible. The 2012.0 OSX bundle will be based on an XCode build with boost
1.46.
Thanks for the new release, Harry. About the "changes since 2011.4.0" section: is there a "Hugin-2012.0.0 Release Notes" already available somewhere for translation? I think these are useful e.g. for reviews and thus can help promoting hugin.
> Dear all,
> Unfortunately we needed to release another rc build due to a (very old)
> error in OS X. Also the updated brazilian translation has been added.
> NOTE: The translation is not yet complete for all languages for this
> release. Please check further down in this mail for the status of the
> translations.
> A number of users have built recent snapshots and executables are likely
> to be
> announced within a few days of this tarball release.
> Watch http://groups.google.com/group/hugin-ptx for the announcements of
> binary
> releases. If you don't see a binary for your platform it has most
> likely not
> been produced yet. Consider stepping up to the task. Instructions at
> The lensfun library for reading and writing lens parameters from/to
> database has now been integrated into Hugin.
> Users can now search the lensfun library and load lens parameters.
> Added new tool pto_gen for generation of pto file from image files.
> Other Improvements
> * Various improvements to cpfind including a prealign matching
> strategy and pair wise matching for multirow heuristic
> * Added option to keep exposure fused stacks
> * pano_modify: Added HDR autocrop option
> * Many more improvements and bug fixes.
> UPGRADING
> Upgrading from previous versions of Hugin should be seamless. If you do have
> problems with old settings, these can be reset in the Preferences by
> clicking
> 'Load defaults'.
> It is strongly recommeded to set the default control point detector to
> Hugin's CPFind. It is the only control point generator endorsed by Hugin.
> Third-party generators may be compatible with the plug-in architecture.
> There is a known problem building Hugin with CMake 2.8.5rc2.
> Workaround: Upgrade to a newer CMake version.
> Mac OS X:
> - Mac OS X Tiger (10.4) is no longer supported.
> - The PPC platform is no longer supported.
> - The OpenMP enabled enblend is now compatible on Mac OS X Lion (10.7).
> - The cmake compilation of Hugin is currently broken due to the fact that
> the boost library on OS X is currently at version 1.50 and boost
> versions => 1.48
> conflict with a number of Mac OS X macros (from AssertMacros.h). This can
> not be disabled as WxWindows for Mac (a.k.a. WxMac) needs these macros.
> An XCode build, where a specific boost (<=1.46) can be specified, is
> possible. The 2012.0 OSX bundle will be based on an XCode build with boost
> 1.46.
> A detailed changelog can be found in the file Changelog.
> --
> 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
Yes. They are available. Terry Duel wrote them. They are in the source
tarball. If you unpack it you will find them in doc/releases.
Just for convenience I attached them as well to this mail.
> Thanks for the new release, Harry. About the "changes since 2011.4.0"
> section: is there a "Hugin-2012.0.0 Release Notes" already available
> somewhere for translation? I think these are useful e.g. for reviews and
> thus can help promoting hugin.
> Carl
> Harry van der Wolf schrieb am 14.10.12 14:01:
>> Dear all,
>> Unfortunately we needed to release another rc build due to a (very old)
>> error in OS X. Also the updated brazilian translation has been added.
>> NOTE: The translation is not yet complete for all languages for this
>> release. Please check further down in this mail for the status of the
>> translations.
>> The lensfun library for reading and writing lens parameters from/to
>> database has now been integrated into Hugin.
>> Users can now search the lensfun library and load lens parameters.
>> Added new tool pto_gen for generation of pto file from image files.
>> Other Improvements
>> * Various improvements to cpfind including a prealign matching
>> strategy and pair wise matching for multirow heuristic
>> * Added option to keep exposure fused stacks
>> * pano_modify: Added HDR autocrop option
>> * Many more improvements and bug fixes.
>> UPGRADING
>> Upgrading from previous versions of Hugin should be seamless. If you do
>> have
>> problems with old settings, these can be reset in the Preferences by
>> clicking
>> 'Load defaults'.
>> It is strongly recommeded to set the default control point detector to
>> Hugin's CPFind. It is the only control point generator endorsed by Hugin.
>> Third-party generators may be compatible with the plug-in architecture.
>> There is a known problem building Hugin with CMake 2.8.5rc2.
>> Workaround: Upgrade to a newer CMake version.
>> Mac OS X:
>> - Mac OS X Tiger (10.4) is no longer supported.
>> - The PPC platform is no longer supported.
>> - The OpenMP enabled enblend is now compatible on Mac OS X Lion (10.7).
>> - The cmake compilation of Hugin is currently broken due to the fact that
>> the boost library on OS X is currently at version 1.50 and boost
>> versions => 1.48
>> conflict with a number of Mac OS X macros (from AssertMacros.h). This can
>> not be disabled as WxWindows for Mac (a.k.a. WxMac) needs these macros.
>> An XCode build, where a specific boost (<=1.46) can be specified, is
>> possible. The 2012.0 OSX bundle will be based on an XCode build with boost
>> 1.46.
> --
> 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<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 <hugin-ptx%2Bunsubscribe@googlegroups.com>
> For more options, visit this group at http://groups.google.com/** > group/hugin-ptx <http://groups.google.com/group/hugin-ptx>
> Yes. They are available. Terry Duel wrote them. They are in the source
> tarball. If you unpack it you will find them in doc/releases.
> Just for convenience I attached them as well to this mail.
> Harry
> 2012/10/14 Carl von Einem <c...@einem.net <mailto:c...@einem.net>>
> Thanks for the new release, Harry. About the "changes since
> 2011.4.0" section: is there a "Hugin-2012.0.0 Release Notes" already
> available somewhere for translation? I think these are useful e.g.
> for reviews and thus can help promoting hugin.
> Dear all,
> Unfortunately we needed to release another rc build due to a (very old)
> error in OS X. Also the updated brazilian translation has been added.
> NOTE: The translation is not yet complete for all languages for this
> release. Please check further down in this mail for the status of the
> translations.
> A number of users have built recent snapshots and executables are likely
> to be
> announced within a few days of this tarball release.
> Watch http://groups.google.com/group/hugin-ptx for the announcements of
> binary
> releases. If you don't see a binary for your platform it has most likely
> not
> been produced yet. Consider stepping up to the task. Instructions at
> The lensfun library for reading and writing lens parameters from/to
> database has now been integrated into Hugin.
> Users can now search the lensfun library and load lens parameters.
> Added new tool pto_gen for generation of pto file from image files.
> Other Improvements
> * Various improvements to cpfind including a prealign matching strategy
> and pair wise matching for multirow heuristic
> * Added option to keep exposure fused stacks
> * pano_modify: Added HDR autocrop option
> * Many more improvements and bug fixes.
> UPGRADING
> Upgrading from previous versions of Hugin should be seamless. If you do
> have
> problems with old settings, these can be reset in the Preferences by
> clicking
> 'Load defaults'.
> It is strongly recommeded to set the default control point detector to
> Hugin's CPFind. It is the only control point generator endorsed by Hugin.
> Third-party generators may be compatible with the plug-in architecture.
> There is a known problem building Hugin with CMake 2.8.5rc2.
> Workaround: Upgrade to a newer CMake version.
> Mac OS X:
> - Mac OS X Tiger (10.4) is no longer supported.
> - The PPC platform is no longer supported.
> - The OpenMP enabled enblend is now compatible on Mac OS X Lion (10.7).
> - The cmake compilation of Hugin is currently broken due to the fact that
> the boost library on OS X is currently at version 1.50 and boost versions
> => 1.48
> conflict with a number of Mac OS X macros (from AssertMacros.h). This can
> not be disabled as WxWindows for Mac (a.k.a. WxMac) needs these macros.
> An XCode build, where a specific boost (<=1.46) can be specified, is
> possible. The 2012.0 OSX bundle will be based on an XCode build with boost
> 1.46.
> An updated list of issues deemed to be critical, including discussions
> and workarounds is in the issue tracker.
Harry, thanks for continuing to work on the Mac versions of Hugin … very much appreciated.
When I start the Hugin GUI I get the error: "I am Hugin version 2012.0. I have found preferences from a newer version 2012.0.0."
I went into the "Preferences" and did a 'Load Defaults' on each tab and applied the changes. I quit hugin and started it up again and get the same error message.
I got the same error in the RC2 release.
On 2012-10-14, at 11:10 AM, Harry van der Wolf <hvdw...@gmail.com> wrote:
I have the same issue with RC2 on Windows, so this is not Mac-specific. On
Windows, I even tried to edit the version in the registry without any
success. I should have reported it, that's what RCs are for :-P
2012/10/14 Donald Johnston <dgjohns...@accesscomm.ca>
> Harry, thanks for continuing to work on the Mac versions of Hugin … very
> much appreciated.
> When I start the Hugin GUI I get the error: "I am Hugin version 2012.0. I
> have found preferences from a newer version 2012.0.0."
> I went into the "Preferences" and did a 'Load Defaults' on each tab and
> applied the changes. I quit hugin and started it up again and get the same
> error message.
> I got the same error in the RC2 release.
> On 2012-10-14, at 11:10 AM, Harry van der Wolf <hvdw...@gmail.com> wrote:
> Hi mac users,
> I built a rc3 bundle. What has changed to rc2 w.r.t OS X? => PTBatcherGui
> can now be called from the menu.
Me too,
But more. When I open the projects (even created with rc3) I get the message AND it has lost track of the input images and all the conrol point information (essentially no project, just an empty (?) pto file.
On Sunday, October 14, 2012 3:13:06 PM UTC-5, Donald Johnston wrote:
> Harry, thanks for continuing to work on the Mac versions of Hugin … very > much appreciated.
> When I start the Hugin GUI I get the error: "I am Hugin version 2012.0. I > have found preferences from a newer version 2012.0.0."
> I went into the "Preferences" and did a 'Load Defaults' on each tab and > applied the changes. I quit hugin and started it up again and get the same > error message.
> I got the same error in the RC2 release.
> On 2012-10-14, at 11:10 AM, Harry van der Wolf <hvd...@gmail.com<javascript:>> > wrote:
> Hi mac users,
> I built a rc3 bundle. What has changed to rc2 w.r.t OS X? => PTBatcherGui > can now be called from the menu.
I guess I should say that I was surprised it found "newer" preferences. Does it thinks see the previous "beta version" as newer? On is this the beta version kicking out the warning (even though the rc3 guy is the one that is launched.)
I ask as I had some strange interaction before when I assumed I could run multiple versions from the applications folder as needed. Anyway I did delete the beta version I have been using from the Applications file (after copying it to a folder on my desktop.)
Do I need to do more to prevent the versions from interacting?
(Sorry I'm not too smart on this.)
John
On Sunday, October 14, 2012 3:48:35 PM UTC-5, Frederic Da Vitoria wrote:
> Hello,
> I have the same issue with RC2 on Windows, so this is not Mac-specific. On > Windows, I even tried to edit the version in the registry without any > success. I should have reported it, that's what RCs are for :-P
> 2012/10/14 Donald Johnston <dgjoh...@accesscomm.ca <javascript:>>
>> Harry, thanks for continuing to work on the Mac versions of Hugin … very >> much appreciated.
>> When I start the Hugin GUI I get the error: "I am Hugin version 2012.0. >> I have found preferences from a newer version 2012.0.0."
>> I went into the "Preferences" and did a 'Load Defaults' on each tab and >> applied the changes. I quit hugin and started it up again and get the same >> error message.
>> I got the same error in the RC2 release.
>> On 2012-10-14, at 11:10 AM, Harry van der Wolf <hvd...@gmail.com<javascript:>> >> wrote:
>> Hi mac users,
>> I built a rc3 bundle. What has changed to rc2 w.r.t OS X? => PTBatcherGui >> can now be called from the menu.
On Sunday, October 14, 2012 6:40:13 PM UTC-5, JohnPW wrote:
> I guess I should say that I was surprised it found "newer" preferences. > Does it thinks see the previous "beta version" as newer? On is this the > beta version kicking out the warning (even though the rc3 guy is the one > that is launched.)
> I ask as I had some strange interaction before when I assumed I could run > multiple versions from the applications folder as needed. Anyway I did > delete the beta version I have been using from the Applications file (after > copying it to a folder on my desktop.)
> Do I need to do more to prevent the versions from interacting?
> (Sorry I'm not too smart on this.)
> John
> On Sunday, October 14, 2012 3:48:35 PM UTC-5, Frederic Da Vitoria wrote:
>> Hello,
>> I have the same issue with RC2 on Windows, so this is not Mac-specific. >> On Windows, I even tried to edit the version in the registry without any >> success. I should have reported it, that's what RCs are for :-P
>> 2012/10/14 Donald Johnston <dgjoh...@accesscomm.ca>
>>> Harry, thanks for continuing to work on the Mac versions of Hugin … very >>> much appreciated.
>>> When I start the Hugin GUI I get the error: "I am Hugin version 2012.0. >>> I have found preferences from a newer version 2012.0.0."
>>> I went into the "Preferences" and did a 'Load Defaults' on each tab and >>> applied the changes. I quit hugin and started it up again and get the same >>> error message.
>>> I got the same error in the RC2 release.
>>> On 2012-10-14, at 11:10 AM, Harry van der Wolf <hvd...@gmail.com> wrote:
>>> Hi mac users,
>>> I built a rc3 bundle. What has changed to rc2 w.r.t OS X? => >>> PTBatcherGui can now be called from the menu.
> Dear all,
> Unfortunately we needed to release another rc build due to a (very old)
> error in OS X. Also the updated brazilian translation has been added.
New binary packages of Hugin 2012.0.0~rc3 for Ubuntu Lucid, Natty,
Oneiric and Quantal are available at the Hugin PPA Packagers "next Hugin
builds" repository at
https://launchpad.net/~hugin/+archive/next
Enjoy!
Stefan Peter
-- In theory there is no difference between theory and practice. In
practice there is.
> When I start the Hugin GUI I get the error: "I am Hugin version 2012.0.
> I have found preferences from a newer version 2012.0.0."
> I went into the "Preferences" and did a 'Load Defaults' on each tab and
> applied the changes. I quit hugin and started it up again and get the
> same error message.
This is a left over from RC2 where the version string in the Hugin
preference file was reduced from 3 numbers (x.x.x) to two numbers (x.x).
IIRC, the main reason to get rid of the third number in the version
string, the patch level, was to simplify the handling of the api-max
values in the python scripts. Additionally it was felt that a patch
level increase should not have any influence on the default settings for
new projects.
Now it seams that the existing string will not be limited to the only
two numbers prior to making the comparison leading to the error message
you see. And, additionally, Hugin seems to refuse to "downgrade" the
default settings.
It has to be taken into account that only users having installed the
beta of 2012.0.0 are affected by this behavior.
I see two possible solutions for fixing this:
o Fix the code. This will result in another RC, though.
However, I feel that this should be done anyway.
o Instruct affected users to delete their .hugin
preference files. It will be rewritten by the current
Hugin RC with the proper notation at the next start.
As the number of users affected should be small and
reduced to the ones adventurous enough to install
beta software, this may be sufficient to get the current
release out of the door. This behavior should be
mentioned in the release notes as known issue, though.
Thoughts anyone?
With kind regards
Stefan Peter
-- In theory there is no difference between theory and practice. In
practice there is.
> Me too,
> But more. When I open the projects (even created with rc3) I get the
> message AND it has lost track of the input images and all the conrol
> point information (essentially no project, just an empty (?) pto file.
Because the preferences affect new projects only, this behavior should
not be related. I could not reproduce our problem with missing content
in pto files neither with older ptos nor with ones produced by RC3.
Can you send one of the pto files showing this behavior to the list or
make it available somewhere on the net for us to have a look at it?
With kind regards
Stefan Peter
-- In theory there is no difference between theory and practice. In
practice there is.
> Dear all,
> Unfortunately we needed to release another rc build due to a (very
> old) error in OS X. Also the updated brazilian translation has been added.
> NOTE: The translation is not yet complete for all languages for this
> release. Please check further down in this mail for the status of the
> translations.
> A number of users have built recent snapshots and executables are
> likely to be
> announced within a few days of this tarball release.
> Watch http://groups.google.com/group/hugin-ptx for the announcements
> of binary
> releases. If you don't see a binary for your platform it has most
> likely not
> been produced yet. Consider stepping up to the task. Instructions at
> The lensfun library for reading and writing lens parameters from/to
> database has now been integrated into Hugin.
> Users can now search the lensfun library and load lens parameters.
> Added new tool pto_gen for generation of pto file from image files.
> Other Improvements
> * Various improvements to cpfind including a prealign matching
> strategy and pair wise matching for multirow heuristic
> * Added option to keep exposure fused stacks
> * pano_modify: Added HDR autocrop option
> * Many more improvements and bug fixes.
> UPGRADING
> Upgrading from previous versions of Hugin should be seamless. If you
> do have
> problems with old settings, these can be reset in the Preferences by
> clicking
> 'Load defaults'.
> It is strongly recommeded to set the default control point detector to
> Hugin's CPFind. It is the only control point generator endorsed by Hugin.
> Third-party generators may be compatible with the plug-in architecture.
> There is a known problem building Hugin with CMake 2.8.5rc2.
> Workaround: Upgrade to a newer CMake version.
> Mac OS X:
> - Mac OS X Tiger (10.4) is no longer supported.
> - The PPC platform is no longer supported.
> - The OpenMP enabled enblend is now compatible on Mac OS X Lion (10.7).
> - The cmake compilation of Hugin is currently broken due to the fact that
> the boost library on OS X is currently at version 1.50 and boost
> versions => 1.48
> conflict with a number of Mac OS X macros (from AssertMacros.h). This can
> not be disabled as WxWindows for Mac (a.k.a. WxMac) needs these macros.
> An XCode build, where a specific boost (<=1.46) can be specified, is
> possible. The 2012.0 OSX bundle will be based on an XCode build with boost
> 1.46.
> A detailed changelog can be found in the file Changelog.
> -- > 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
Also, can you tell me which directory should contain the offending preferences (OS X Mountain Lion) so I can make sure I have deleted them? Thanks, John
[I keep getting error (#304) when I try to attach a file. So I pasted the plain text below.]
On Monday, October 15, 2012 5:03:42 AM UTC-5, Stefan wrote:
> On 14.10.2012 23:27, JohnPW wrote: > > Me too, > > But more. When I open the projects (even created with rc3) I get the > > message AND it has lost track of the input images and all the conrol > > point information (essentially no project, just an empty (?) pto file.
> Because the preferences affect new projects only, this behavior should > not be related. I could not reproduce our problem with missing content > in pto files neither with older ptos nor with ones produced by RC3.
> Can you send one of the pto files showing this behavior to the list or > make it available somewhere on the net for us to have a look at it?
> With kind regards
> Stefan Peter
> -- > In theory there is no difference between theory and practice. In > practice there is.
Hi, thanks for the note. I'm new to the Mac environment so it took a while to find the preferences file in the hidden directory. After deleting the file I got the same error message when I started Hugin. However after shutting Hugin down and starting it up again there was no error (I guess 'no preference file' isn't handle correctly by the code).
As to fixing the code, my vote (for what it's worth) is that code shouldn't be added to handle anomalies like this … unless it's something like adding a "Master Reset Preference" button that wipes out the old and creates a new.
On 2012-10-15, at 3:19 AM, Stefan Peter <s_pe...@swissonline.ch> wrote:
>> When I start the Hugin GUI I get the error: "I am Hugin version 2012.0.
>> I have found preferences from a newer version 2012.0.0."
>> I went into the "Preferences" and did a 'Load Defaults' on each tab and
>> applied the changes. I quit hugin and started it up again and get the
>> same error message.
> This is a left over from RC2 where the version string in the Hugin
> preference file was reduced from 3 numbers (x.x.x) to two numbers (x.x).
> IIRC, the main reason to get rid of the third number in the version
> string, the patch level, was to simplify the handling of the api-max
> values in the python scripts. Additionally it was felt that a patch
> level increase should not have any influence on the default settings for
> new projects.
> Now it seams that the existing string will not be limited to the only
> two numbers prior to making the comparison leading to the error message
> you see. And, additionally, Hugin seems to refuse to "downgrade" the
> default settings.
> It has to be taken into account that only users having installed the
> beta of 2012.0.0 are affected by this behavior.
> I see two possible solutions for fixing this:
> o Fix the code. This will result in another RC, though.
> However, I feel that this should be done anyway.
> o Instruct affected users to delete their .hugin
> preference files. It will be rewritten by the current
> Hugin RC with the proper notation at the next start.
> As the number of users affected should be small and
> reduced to the ones adventurous enough to install
> beta software, this may be sufficient to get the current
> release out of the door. This behavior should be
> mentioned in the release notes as known issue, though.
> Thoughts anyone?
> With kind regards
> Stefan Peter
> -- > In theory there is no difference between theory and practice. In
> practice there is.
> -- > 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
On Monday, October 15, 2012 8:03:27 PM UTC-5, Donald Johnston wrote:
> Hi, thanks for the note. I'm new to the Mac environment so it took a > while to find the preferences file in the hidden directory. After deleting > the file I got the same error message when I started Hugin. However after > shutting Hugin down and starting it up again there was no error (I guess > 'no preference file' isn't handle correctly by the code).
> As to fixing the code, my vote (for what it's worth) is that code > shouldn't be added to handle anomalies like this … unless it's something > like adding a "Master Reset Preference" button that wipes out the old and > creates a new.
> On 2012-10-15, at 3:19 AM, Stefan Peter <s_p...@swissonline.ch<javascript:>> > wrote:
> > Hi Donald
> > On 14.10.2012 22:13, Donald Johnston wrote:
> >> When I start the Hugin GUI I get the error: "I am Hugin version 2012.0. > >> I have found preferences from a newer version 2012.0.0."
> >> I went into the "Preferences" and did a 'Load Defaults' on each tab and > >> applied the changes. I quit hugin and started it up again and get the > >> same error message.
> > This is a left over from RC2 where the version string in the Hugin > > preference file was reduced from 3 numbers (x.x.x) to two numbers (x.x). > > IIRC, the main reason to get rid of the third number in the version > > string, the patch level, was to simplify the handling of the api-max > > values in the python scripts. Additionally it was felt that a patch > > level increase should not have any influence on the default settings for > > new projects.
> > Now it seams that the existing string will not be limited to the only > > two numbers prior to making the comparison leading to the error message > > you see. And, additionally, Hugin seems to refuse to "downgrade" the > > default settings.
> > It has to be taken into account that only users having installed the > > beta of 2012.0.0 are affected by this behavior.
> > I see two possible solutions for fixing this:
> > o Fix the code. This will result in another RC, though. > > However, I feel that this should be done anyway. > > o Instruct affected users to delete their .hugin > > preference files. It will be rewritten by the current > > Hugin RC with the proper notation at the next start. > > As the number of users affected should be small and > > reduced to the ones adventurous enough to install > > beta software, this may be sufficient to get the current > > release out of the door. This behavior should be > > mentioned in the release notes as known issue, though.
> > Thoughts anyone?
> > With kind regards
> > Stefan Peter
> > -- > > In theory there is no difference between theory and practice. In > > practice there is.
> > -- > > 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 hugi...@googlegroups.com<javascript:> > > To unsubscribe from this group, send email to > hugin-ptx+...@googlegroups.com <javascript:> > > For more options, visit this group at > http://groups.google.com/group/hugin-ptx
John … and others. It is in a system folder "Library" under your user name. I used Tinker Tool to turn on viewing of Hidden and System files in Finder. In Finder double click on your user name at the bottom of a finder window and select the grey "Library" folder to the right of your user name (not the black one to the left). There you'll find the "Preferences" folder within which you'll find the "hugin Preferences" file. As they say "easy peasy".
On 2012-10-15, at 7:45 PM, JohnPW <johnpwatk...@gmail.com> wrote:
> Donald,
> Perhaps you would share with me the path to the preference file that needs to be deleted?
> Thanks,
> John
> On Monday, October 15, 2012 8:03:27 PM UTC-5, Donald Johnston wrote:
> Hi, thanks for the note. I'm new to the Mac environment so it took a while to find the preferences file in the hidden directory. After deleting the file I got the same error message when I started Hugin. However after shutting Hugin down and starting it up again there was no error (I guess 'no preference file' isn't handle correctly by the code).
> As to fixing the code, my vote (for what it's worth) is that code shouldn't be added to handle anomalies like this … unless it's something like adding a "Master Reset Preference" button that wipes out the old and creates a new.
> On 2012-10-15, at 3:19 AM, Stefan Peter <s_p...@swissonline.ch> wrote:
> > Hi Donald
> > On 14.10.2012 22:13, Donald Johnston wrote:
> >> When I start the Hugin GUI I get the error: "I am Hugin version 2012.0. > >> I have found preferences from a newer version 2012.0.0."
> >> I went into the "Preferences" and did a 'Load Defaults' on each tab and > >> applied the changes. I quit hugin and started it up again and get the > >> same error message.
> > This is a left over from RC2 where the version string in the Hugin > > preference file was reduced from 3 numbers (x.x.x) to two numbers (x.x). > > IIRC, the main reason to get rid of the third number in the version > > string, the patch level, was to simplify the handling of the api-max > > values in the python scripts. Additionally it was felt that a patch > > level increase should not have any influence on the default settings for > > new projects.
> > Now it seams that the existing string will not be limited to the only > > two numbers prior to making the comparison leading to the error message > > you see. And, additionally, Hugin seems to refuse to "downgrade" the > > default settings.
> > It has to be taken into account that only users having installed the > > beta of 2012.0.0 are affected by this behavior.
> > I see two possible solutions for fixing this:
> > o Fix the code. This will result in another RC, though. > > However, I feel that this should be done anyway. > > o Instruct affected users to delete their .hugin > > preference files. It will be rewritten by the current > > Hugin RC with the proper notation at the next start. > > As the number of users affected should be small and > > reduced to the ones adventurous enough to install > > beta software, this may be sufficient to get the current > > release out of the door. This behavior should be > > mentioned in the release notes as known issue, though.
> > Thoughts anyone?
> > With kind regards
> > Stefan Peter
> > -- > > In theory there is no difference between theory and practice. In > > practice there is.
> > -- > > 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 hugi...@googlegroups.com > > To unsubscribe from this group, send email to hugin-ptx+...@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
OK, thanks.
I did find that file but thought there might be more.
Unless I misunderstand, that is not an invisible file, but in any case, deleting it has no effect for me. I still get the warning and the file corruption problem. I then tossed it, emptied the trash, immediately logged out, then back in. All to no effect. I still get the same problem.
I thought possibly I missed some system level preference file or something hidden away in the Hugin package or some invisible file.
If anyone has any suggestions, I would be glad to hear them.
On Monday, October 15, 2012 11:03:09 PM UTC-5, Donald Johnston wrote:
> John … and others. It is in a system folder "Library" under your user > name. I used Tinker Tool to turn on viewing of Hidden and System files in > Finder. In Finder double click on your user name at the bottom of a finder > window and select the grey "Library" folder to the right of your user name > (not the black one to the left). There you'll find the "Preferences" > folder within which you'll find the "hugin Preferences" file. As they say > "easy peasy".
> On 2012-10-15, at 7:45 PM, JohnPW <johnpw...@gmail.com <javascript:>> > wrote:
> Donald,
> Perhaps you would share with me the path to the preference file that needs > to be deleted?
> Thanks,
> John
> On Monday, October 15, 2012 8:03:27 PM UTC-5, Donald Johnston wrote:
>> Hi, thanks for the note. I'm new to the Mac environment so it took a >> while to find the preferences file in the hidden directory. After deleting >> the file I got the same error message when I started Hugin. However after >> shutting Hugin down and starting it up again there was no error (I guess >> 'no preference file' isn't handle correctly by the code).
>> As to fixing the code, my vote (for what it's worth) is that code >> shouldn't be added to handle anomalies like this … unless it's something >> like adding a "Master Reset Preference" button that wipes out the old and >> creates a new.
>> On 2012-10-15, at 3:19 AM, Stefan Peter <s_p...@swissonline.ch> wrote:
>> > Hi Donald
>> > On 14.10.2012 22:13, Donald Johnston wrote:
>> >> When I start the Hugin GUI I get the error: "I am Hugin version >> 2012.0. >> >> I have found preferences from a newer version 2012.0.0."
>> >> I went into the "Preferences" and did a 'Load Defaults' on each tab >> and >> >> applied the changes. I quit hugin and started it up again and get the >> >> same error message.
>> > This is a left over from RC2 where the version string in the Hugin >> > preference file was reduced from 3 numbers (x.x.x) to two numbers >> (x.x). >> > IIRC, the main reason to get rid of the third number in the version >> > string, the patch level, was to simplify the handling of the api-max >> > values in the python scripts. Additionally it was felt that a patch >> > level increase should not have any influence on the default settings >> for >> > new projects.
>> > Now it seams that the existing string will not be limited to the only >> > two numbers prior to making the comparison leading to the error message >> > you see. And, additionally, Hugin seems to refuse to "downgrade" the >> > default settings.
>> > It has to be taken into account that only users having installed the >> > beta of 2012.0.0 are affected by this behavior.
>> > I see two possible solutions for fixing this:
>> > o Fix the code. This will result in another RC, though. >> > However, I feel that this should be done anyway. >> > o Instruct affected users to delete their .hugin >> > preference files. It will be rewritten by the current >> > Hugin RC with the proper notation at the next start. >> > As the number of users affected should be small and >> > reduced to the ones adventurous enough to install >> > beta software, this may be sufficient to get the current >> > release out of the door. This behavior should be >> > mentioned in the release notes as known issue, though.
>> > Thoughts anyone?
>> > With kind regards
>> > Stefan Peter
>> > -- >> > In theory there is no difference between theory and practice. In >> > practice there is.
>> > -- >> > 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 hugi...@googlegroups.com >> > To unsubscribe from this group, send email to >> hugin-ptx+...@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 hugi...@googlegroups.com<javascript:>
> To unsubscribe from this group, send email to > hugin-ptx+...@googlegroups.com <javascript:>
> For more options, visit this group at > http://groups.google.com/group/hugin-ptx
> Now it seams that the existing string will not be limited to the only
> two numbers prior to making the comparison leading to the error message
> you see. And, additionally, Hugin seems to refuse to "downgrade" the
> default settings.
> It has to be taken into account that only users having installed the
> beta of 2012.0.0 are affected by this behavior.
> I see two possible solutions for fixing this:
> o Fix the code. This will result in another RC, though.
> However, I feel that this should be done anyway.
> o Instruct affected users to delete their .hugin
> preference files. It will be rewritten by the current
> Hugin RC with the proper notation at the next start.
> As the number of users affected should be small and
> reduced to the ones adventurous enough to install
> beta software, this may be sufficient to get the current
> release out of the door. This behavior should be
> mentioned in the release notes as known issue, though.
> Thoughts anyone?
I think as well that the code should be fixed. However, does that require
some extra code to compensate for older versions?
It's in the "src/hugin1/hugin/huginApp.cpp" file and the functionality has
been added by Yuval on 26 Dec 2011 in changeset 5715 c4c76a7dfdd5.
I looked at the code but I simply don't understand.
Some clever developer around?
Harry, (or anyone else :-) Don't know if you read my post. Can you or anyone else suggest how I should fix my install of rc3? Should tossing those user level preferences be enough? Do I need to do it a certain way for it to be effective? I understand if the solution is still unclear (or if I'm too damn thick to have read, recognized, and understood the explanation somewhere in the posts. :-)
On Tuesday, October 16, 2012 3:21:36 PM UTC-5, Harry van der Wolf wrote:
> 2012/10/15 Stefan Peter <s_p...@swissonline.ch <javascript:>>
>> Now it seams that the existing string will not be limited to the only >> two numbers prior to making the comparison leading to the error message >> you see. And, additionally, Hugin seems to refuse to "downgrade" the >> default settings.
>> It has to be taken into account that only users having installed the >> beta of 2012.0.0 are affected by this behavior.
>> I see two possible solutions for fixing this:
>> o Fix the code. This will result in another RC, though. >> However, I feel that this should be done anyway. >> o Instruct affected users to delete their .hugin >> preference files. It will be rewritten by the current >> Hugin RC with the proper notation at the next start. >> As the number of users affected should be small and >> reduced to the ones adventurous enough to install >> beta software, this may be sufficient to get the current >> release out of the door. This behavior should be >> mentioned in the release notes as known issue, though.
>> Thoughts anyone?
> I think as well that the code should be fixed. However, does that require > some extra code to compensate for older versions?
> It's in the "src/hugin1/hugin/huginApp.cpp" file and the functionality has > been added by Yuval on 26 Dec 2011 in changeset 5715 c4c76a7dfdd5.
> I looked at the code but I simply don't understand. > Some clever developer around?
> Harry, (or anyone else :-)
> Don't know if you read my post. Can you or anyone else suggest how I
> should fix my install of rc3?
> Should tossing those user level preferences be enough? Do I need to do it
> a certain way for it to be effective?
> I understand if the solution is still unclear (or if I'm too damn thick to
> have read, recognized, and understood the explanation somewhere in the
> posts. :-)
Sorry. didn't think of that.
The easiest way is to go in Finder to your home folder, to Library, to
Preferences.
In this folder you will find a file "hugin Preferences". Please delete it.
If you are already using hugin for a longer time you will also find
"net.sourceforge.hugin.Hugin.plist" and
"net.sourceforge.hugin.PTBatcherGui.plist". They can be removed as well as
they are not useful anymore.
Finally you might even find a "PTBatcherGui.hugin.sourceforge.net.plist.
That one is from my first PTBatcherGui bundle. That one can certainly be
removed.
The "hugin Preferences" is the most important one. Remove that one and you
have a clean slate.
Thanks Harry, Throwing out just the hugin Preferences didn't work. But when I threw it out along with *all* of the files you indicated (plus a few others I found,) it worked. Things are working fine now. Thanks again, John
On Tuesday, October 16, 2012 4:17:13 PM UTC-5, Harry van der Wolf wrote:
>> Harry, (or anyone else :-) >> Don't know if you read my post. Can you or anyone else suggest how I >> should fix my install of rc3? >> Should tossing those user level preferences be enough? Do I need to do it >> a certain way for it to be effective? >> I understand if the solution is still unclear (or if I'm too damn thick >> to have read, recognized, and understood the explanation somewhere in the >> posts. :-)
> Sorry. didn't think of that.
> The easiest way is to go in Finder to your home folder, to Library, to > Preferences. > In this folder you will find a file "hugin Preferences". Please delete it. > If you are already using hugin for a longer time you will also find > "net.sourceforge.hugin.Hugin.plist" and > "net.sourceforge.hugin.PTBatcherGui.plist". They can be removed as well as > they are not useful anymore. > Finally you might even find a "PTBatcherGui.hugin.sourceforge.net.plist. > That one is from my first PTBatcherGui bundle. That one can certainly be > removed.
> The "hugin Preferences" is the most important one. Remove that one and you > have a clean slate.
It is a simple tool that generates a .pto project from a list of photos, this is needed if you are going to stitch projects on the command-line - cpfind uses a .pto project to specify the input photos.
Also on Linux you get a right-click menu item in all the file and image browsers. This means you can identify all your panoramas by just opening folders and picking the photos, then stitch or batch process them later - I'm not sure if this functionality is available on Windows/OS X.
