Main menu
User login
Syndicate
You are here
Resynthesizer v1.0 released
This is a suite of revised and new resynthesizer plugins.
I have assumed maintenance of the Resynthesizer from the original author Paul Harrison.
This is version 1.0.
The source is now at github.com (a public repository like SourceForge). Search for user "bootchk", repository "resynthesizer." For more information, see the README and ChangeLog and NEWS files there (you don't have to download them.)
!!! The attached executables are Linux files. DO NOT download them for Windows. Also do NOT download the Python scripts for Windows (they won't work with the old resynthesizer.exe.) I have built the resynthesizer and tested on Windows, but have not finished an installer for Windows. If you are adept at building, download the source and build Windows executables yourselves.
A short summary of changes for users is:
- bugs are fixed
- alpha-agnostic: less hassle with alpha channels
- its bundled: most plugins that use the resynthesizer
For programmers:
- rewritten in C and Python, in Gimp style
- GNU build tool makefiles
- engine separated from the GUI control panel
| Attachment | Size |
|---|---|
 resynthesizer.tar.gz | 67.32 KB |
- Log in to post comments
Comments
Plugin fails to load
Hi, I'm trying to use the Resynthesizer plugin 1.0 in Arch Linux 64 bit but when I start Gimp I get the following:
(gimp:17993): Gimp-Widgets-CRITICAL **: gimp_device_info_set_device: assertion '(info->device == NULL && GDK_IS_DEVICE (device)) || (GDK_IS_DEVICE (info->device) && device == NULL)' failed
/usr/lib/gimp/2.0/plug-ins/resynthesizer: error while loading shared libraries: libgimpui-2.0.so.0: cannot open shared object file: No such file or directory
(gimp:17993): LibGimpBase-WARNING **: gimp: gimp_wire_read(): error
/usr/lib/gimp/2.0/plug-ins/resynthesizer-gui: error while loading shared libraries: libgimpui-2.0.so.0: cannot open shared object file: No such file or directory
(gimp:17993): LibGimpBase-WARNING **: gimp: gimp_wire_read(): error
Thank you in advance for any assistance you may be able to offer!
resynthesizer plugin Arch Linux
Who built and installed the plugin?
It should be installed to your home directory, not to /usr/lib. In other words installed to ~/.gimp-2.8/plug-ins/resynthesizer-gui.py, not to /usr/lib/.... The usual advice is not to mess with the /usr/lib directory, because it is 'managed' by package managers (install programs.) So for example, if you reinstalled Gimp, it would change that directory, installing the 'official' plugins shipped with Gimp, and possibly overwriting any 'third party' plugins (like resynthesizer) that you installed separately. (Many are sorry that Gimp doesn't ship with the resynthesizer.)
The resynthesizer dynamically links to /usr/lib/gimp/2.0/libgimpui-2.0.so. (That is one of the libraries that is an interface between plugins and Gimp.) It is '2.0' because the interface (the API) has been frozen since Gimp version 2.0. I am not sure why the error message says '... so.0'. If all else fails you might try: in /usr/lib/gimp/2.0 directory make a soft link from libgimpui.so.0 to libgimpui.so .
similar problem resynthesizer
Sorry in advance for this question. I've researched this but just cannot find an answer. I'm using version 2.8.6 on linux and I've downloaded the resynthesizer plugin. I extracted everything and moved it into the gimp plugin folder in home but it doesn't show in gimp. So then I moved everything over to usr/lib/gimp/plugin folder and still nothing. Does someone have an idea on what the problem could be? Thanks
python plugin files must have property>permission to execute
Gimp, when looking for Python plugins, looks for files having permission to execute. It is not enough to copy a plugin file to the directory of plugins, you must also give permission to execute.
So, if you fail to change permission, Gimp quietly ignores the plugin file that is in the correct place but not having the correct permissions.
This is a known wart: Gimp should probably give a warning on the console that it is ignoring such a file.
Well, that is done on purpose
Well, that is done on purpose - to be able to have python files that are not considered plug-ins.
And the actual problem is that this doesn't (or didn't) work on some Windows platforms, and all python files are treated like plug-ins.
Purposeful does not imply good
It seems to me that you could require every .py file in that directory to be a plugin. Why would you want a Python file in the directory that was NOT a plugin? I can see that you might want other Python things, but you could require the things to be packages, which are directories. Which is a strategy that I favor: the only thing in the topmost .py file for a plugin is the boilerplate PyGimp stuff, and the engine is a separate package.
BTW, where did everyone go? I rarely visit, but it seems like few others do either.
You could suggest the package
You could suggest the package approach on the gimp-developer mailing list.
As to where everyone went, my impression is that many stopped posting when discussions were fragmented into questions per item (scripts, plug-ins, ...).
Windows build
Hello,
I was wondering if the windows build is available from anywhere by now?
Thanks!
Re: Windows build
Yes here it is on the registry: http://registry.gimp.org/node/27986
Re Windows
I think some people may be missing a trick here, the plug-in is Python - it's already multi-platform - I use this version on GIMP 2.8.4 in Windows 7. All you need is something like 7zip to extract the tar.gz - copy and paste all the .py files into your plug-ins folder. Tadah!!
Pages