From: Philippe V. <pa...@e-...> - 2009-05-13 20:34:09
|
Hello everybody! I was using for quite some time Panorama Gimp plugin on windows (binary found somewhere), but I recently moved to Mac OSX and could not find any compiled version of the plugin... I eventually decided to compile it myself starting from the trunk/gimp-plugin-ng sources. It gave me some headaches as it didn't worked out of the box and I initially thought the OS-X port was the culprit... Anyway, I eventually got it up and running! But I would like to raise 2 questions: - This plugin seems to be the best kept secret in the world: you can't find binaries for it and nobody talks about it... Is there any particular reason to avoid it? Are there better tools? (I use it mainly to extract nadir from Equirecangulars) - Is this list the best place to post patches for this plugin? (unless I am really the only user of this thing...) Regards -- Phil. |
From: Carl v. E. <ei...@gm...> - 2009-05-13 22:22:40
|
A description on http://wiki.panotools.org/ would be great! I mostly use Photoshop on Mac but I'd love to have a good reason to use the GIMP... Carl Philippe Vanhaesendonck wrote: > Hello everybody! > > I was using for quite some time Panorama Gimp plugin on windows (binary > found somewhere), but I recently moved to Mac OSX and could not find any > compiled version of the plugin... > > I eventually decided to compile it myself starting from the > trunk/gimp-plugin-ng sources. > > It gave me some headaches as it didn't worked out of the box and I > initially thought the OS-X port was the culprit... > > Anyway, I eventually got it up and running! > > But I would like to raise 2 questions: > > - This plugin seems to be the best kept secret in the world: you can't > find binaries for it and nobody talks about it... > Is there any particular reason to avoid it? > Are there better tools? > (I use it mainly to extract nadir from Equirecangulars) > > - Is this list the best place to post patches for this plugin? > (unless I am really the only user of this thing...) > > Regards > > -- > Phil. > > ------------------------------------------------------------------------------ > The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your > production scanning environment may not be a perfect world - but thanks to > Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700 > Series Scanner you'll get full speed at 300 dpi even with all image > processing features enabled. http://p.sf.net/sfu/kodak-com > _______________________________________________ > PanoTools-devel mailing list > Pan...@li... > https://lists.sourceforge.net/lists/listinfo/panotools-devel > |
From: Jim W. <jwa...@ph...> - 2009-05-13 22:42:27
|
Philippe Vanhaesendonck wrote: > Hello everybody! > > I was using for quite some time Panorama Gimp plugin on windows (binary > found somewhere), but I recently moved to Mac OSX and could not find any > compiled version of the plugin... > > I eventually decided to compile it myself starting from the > trunk/gimp-plugin-ng sources. > > It gave me some headaches as it didn't worked out of the box and I > initially thought the OS-X port was the culprit... > > Anyway, I eventually got it up and running! > Congratulations. I have not used the Gimp plugins. I use and have published the Photoshop plugins. I have started investigating improving the Photoshop plugins to use the pano13 code base but have not looked at it for a while. In doing so I noticed many places in the Gimp plugin code that looked out dated but I never built or used. After attending the LGM in Montreal last week I was thinking it is about time for me to look at the Gimp plugins. > But I would like to raise 2 questions: > > - This plugin seems to be the best kept secret in the world: you can't > find binaries for it and nobody talks about it... > Is there any particular reason to avoid it? > I believe the Gimp plugins are not being distributed because they are broken. I don't think anyone has distributed a Mac version. > Are there better tools? > (I use it mainly to extract nadir from Equirecangulars) > Exactly what I use them for. There is another photoshop plugin on Windows that in one go extracts only 90 deg views of both nadir and zenith, and can put them back again. It is also possible to create scripts to extract and insert the images. Or use PTEditor. > - Is this list the best place to post patches for this plugin? > (unless I am really the only user of this thing...) > Definitely submit the patch. It is very unlikely that the plugin will make it into the current pending release of Hugin. But the next version. > Regards > > -- > Phil. > Jim Watters jwatters @ photocreations . ca http://photocreations.ca |
From: Bruno P. <br...@po...> - 2009-05-13 23:18:11
|
On Wed 13-May-2009 at 22:07 +0200, Philippe Vanhaesendonck wrote: > >I was using for quite some time Panorama Gimp plugin on windows (binary >found somewhere), but I recently moved to Mac OSX and could not find any >compiled version of the plugin... It's possible that the last time anyone worked on the gimp plugin there was no OS X version of the gimp. >- This plugin seems to be the best kept secret in the world: you can't >find binaries for it and nobody talks about it... The 'old' gimp plugin needed a large amount of fixes and refactoring. This fixed version is what you find in the 'ng' branch, but it never had much testing or interest despite being in a much better state. >Is there any particular reason to avoid it? I don't use it anymore because I can do everything in hugin, the plugin was never much use for stitching though it is useful for correcting lenses and some simple remapping. >- Is this list the best place to post patches for this plugin? Yes please post any patches you have, you can have SVN access if you like too. -- Bruno |
From: Philippe V. <pa...@e-...> - 2009-05-14 20:29:02
|
Thank you for all your replies. Here is a first patch against the trunk. It addresses 3 points: - Quick fix in autogen.sh to build against automake 1.10 - Fix the sed command in the help makefile - Fix in Gimpmain.c -- this is a real bug: bitPerPixel should be set to the actual depth, not the desired depth; it is reset properly when ThreeToFour is invoked. With the above, it builds (and run) properly on Mac OS-X / Gimp 2.6 Compilation still spits a lot of warning, I'll do a second pass to clean up, now that I am more comfortable with the code. -- Phil. |
From: Philippe V. <pa...@e-...> - 2009-05-14 20:31:52
Attachments:
gimp-plugin-ng.patch
|
(With the patch this time -- apologies) Thank you for all your replies. Here is a first patch against the trunk. It addresses 3 points: - Quick fix in autogen.sh to build against automake 1.10 - Fix the sed command in the help makefile - Fix in Gimpmain.c -- this is a real bug: bitPerPixel should be set to the actual depth, not the desired depth; it is reset properly when ThreeToFour is invoked. With the above, it builds (and run) properly on Mac OS-X / Gimp 2.6 Compilation still spits a lot of warning, I'll do a second pass to clean up, now that I am more comfortable with the code. -- Phil. |
From: Bruno P. <br...@po...> - 2009-05-15 08:14:41
|
On Thu 14-May-2009 at 22:31 +0200, Philippe Vanhaesendonck wrote: > > Here is a first patch against the trunk. Thanks, I've commited them (svn 969 and svn 970). > It addresses 3 points: > > - Quick fix in autogen.sh to build against automake 1.10 > > - Fix the sed command in the help makefile This doesn't work for me "sed -i '' -e ..." just fails here. >-sed -i -e 's/<gimp-help>/<gimp-help xmlns:panoplugin="http:\/\/panotools.sourceforge.net\/panoplugin\/help">/g' \ >+sed -i '' -e 's/<gimp-help>/<gimp-help xmlns:panoplugin="http:\/\/panotools.sourceforge.net\/panoplugin\/help">/g' \ Building the documentation is a problem, ./configure && make just fails on a docbook error. However I can get everything to build with ./configure --enable-network --enable-build > - Fix in Gimpmain.c -- this is a real bug: bitPerPixel should be set to > the actual depth, not the desired depth; it is reset properly when > ThreeToFour is invoked. -- Bruno |