Closed GoogleCodeExporter closed 8 years ago
Got the same issue. I think the issue is with the new 2.8.6 bugfix release of
Gimp.. I'll try to see if I can't hunt down the necessary libs and gmic
separately, and then see if it works.
Original comment by PsyComma...@gmail.com
on 24 Aug 2013 at 11:56
[deleted comment]
I found a workaround in the meantime.
Just install the latest version of gmic after gimp-extensions:
http://registry.gimp.org/node/13469
And then you'll have to get the "libtif-3.dll" dll from the 2.8.4 release of
gimp, and copy it in your "C:\Program Files\GIMP 2\bin" folder. I suggest
taking it from a gimp portable install, so you don't accidently overwrite your
install of gimp :
https://sourceforge.net/projects/portableapps/files/GIMP%20Portable/Additional%2
0Versions/
After that I'm not sure if its neccessary, but I also downloaded the latest
version of separate+ :
http://cue.yellowmagic.info/softwares/separate-plus/index.html
And then I extracted the zip and copied the files from the
"separate+-0.5.8.zip\separate+-0.5.8\bin\win32\" directory into my
"C:\Program Files\GIMP 2\lib\gimp\2.0\plug-ins" folder.
And it loads without any errors now ! However I got like 2 version of gmic
installed, but GIMP doesn't seem to mind at all..
Original comment by PsyComma...@gmail.com
on 25 Aug 2013 at 10:17
Derp, I actually forgot to mention that in GIMP 2.8.6, they've removed the
"libtif-3.dll" library for some reasons.. But I assume you got my meaning.
Original comment by PsyComma...@gmail.com
on 26 Aug 2013 at 6:16
I think maybe G'MIC and Seperate+ cause the problem.
Original comment by shanshan...@hotmail.com
on 27 Aug 2013 at 6:19
I can confirm that these errors occur on a Win 7 x64 system, with GIMP
Extensions v2.8.20130215 and that the issue can be resolved by working around
the G'MIC and Separate+ plugins.
One clean method to work around the issue on a fresh install is simply to not
install G'MIC and Separate+ during your installation of GIMP Extensions (i.e.,
clear their respective check boxes under Plugins in the installation dialog
box). GIMP 2.8 will should open without errors after this install.
Then follow PsyComma's advice and install the latest versions of each of the
extra plugins:
G'MIC (tested with version 1.5.5.0):
http://registry.gimp.org/node/13469
G'MIC installs automatically by running the exe installer.
Separate+ (tested with version 0.5.8 win32 binaries only version):
http://cue.yellowmagic.info/softwares/separate-plus/index.html
To install Separate+, follow the instructions in the readme file after
unzipping the folder. Basically, you should just copy the "bin\win32" folder
into (one of) your plugins folder, which you can find by checking Preferences
-> Folders -> Plugins.
And that's it. No duplicate plugins, no errors, everything clean.
Original comment by philk...@gmail.com
on 10 Sep 2013 at 2:47
[deleted comment]
This Separate+ plug-in is including libtiff3.dll, install this plugin you can
launch GIMP 2.8.6 without the notice about absence of libtiff3.dll.
Original comment by shanshan...@hotmail.com
on 21 Sep 2013 at 5:20
Attachments:
I was able to work around the missing libtiff3.dll by copying libtiff-5.dll to
libtiff3.dll.
Original comment by urko.ma...@gmail.com
on 24 Sep 2013 at 6:12
[deleted comment]
"I was able to work around the missing libtiff3.dll by copying libtiff-5.dll to
libtiff3.dll."
I strongly recommend against that. I'm not aware of the specifics of that
library, but being a C/C++ programmer with some experience, the interface for
the library might differ from one version to the other.
So even if it seems to work, its possible one days you'll get segmentation
faults or null pointer exceptions, because a function in the old dll isn't in
the new one, or one function was removed and thus another isn't at the same
place in the dll..
You should really get the right version, to avoid yourself future headaches !
Original comment by PsyComma...@gmail.com
on 24 Sep 2013 at 10:27
Problem solved in Version 2.8.20131021
Original comment by gimpexte...@gmail.com
on 21 Oct 2013 at 11:50
Original issue reported on code.google.com by
ladonna....@gmail.com
on 8 Aug 2013 at 4:08