Greetings,

# Note: this forum insists I remove URLS, so "THIS" means this forum.

# Last month I embarked on another attempt to find an image-sharpening utility with minimum "Halo" effects. I learned two things: 1) the bright-and-dark secondary edges that invariably result from resizing and sharpening are called "Halos", and 2) the only mechanisms that offered any suggestion of minimizing the halos involves using one of two GIMP plugins - "Wavelet Decompose" and "Wavelet Sharpen".

# I installed GIMP, got it to work a little, and download the aforementioned plugins. They contained .c and .h files, the purpose of which I generally understand, and what I understand is that they need to be compiled. I searched the Internet for compilers that a non-Developer could use, came to the inevitable conclusion, which led me to posting a thread "what-windows-7-compiler-for-plugins" on the gimpforums forum, the opening of which is:

"Yes, I searched the Internet (I got 3-4 different answers form 3-4 experts). Yes, I did searches in this Forum. Yes, I'm familiar with Unix (it's been a while though). Yes, I have a technical background (BSEE, 8+ years in IT), Yes, I have an HP p7-1174 Windows 7 Pro PC. Yes, I'm familiar with Digital-Image applications (mostly Corel Paint Shop Pro, Photoshop Express, Image Magick, and Irfan View)."

# I think I have the Technical Savvy to install and use a Compiler. Excerpts from the contributors include:

"ofnuts" Wrote: However, on Windows this isn't for the unwary, and you'll normally find pre-compiled versions of these plugins available from sources other than their authors. You can also use the Gimp installers from partha, they include the more popular plugins so you don't even have to worry recompiling them for your PC.

"rich2005" Wrote: You could ask the question at THIS typically THIS=7218 however the samj links have gone [...] , but will give advice.

"paynekj" Wrote: If the recent discussions about the wavelet denoise plugin are anything to go by, there's still some windows compiling expertise over there: THIS=12199 THIS=12220

# All I found at partha was the full GIMP download. What I've found at the recommended GIMPCHAT threads and from my, admittedly minimal, searching is information about compilers and compiling, none of which addresses my question, which has been reduced to "Are there sources for 64-bit Windows 7 Pro versions of compiled GIMP plugins in general and for the "Wavelet Decompose" and "Wavelet Sharpen" in particular, and, if so, where are such sources?"

# I am not trying to avoid the "Rite of Passage" of doing the compiling myself, and I am prepared to make contributions to support and reward the efforts of others, but I can't find any compiled plugins. I have not contributed to GIMP itself because it is of no value to me without, at least, these two plugins. I use Corel PaintShop Pro, Jasco Paint Shop, Adobe Photoshop Express, Image Magick, Irfanview, et al. for my image editing, but like I said in the gimpforums thread: "[The two wavelet plugins are] used with [...] "GIMP" whose structure and "business model" I LIKE, and which has very impressive feature-rich functionality with breadth, width, and details, mostly fueled by plugins." I LIKE GIMP, and I'd like to start using it, but I KNOW I'll need plugins to get the features I have now, some of which are by way of plugins which I got compiled.

# I should also mention that, while preparing this thread, I ended up at Source Forge where I downloaded "GIMP Extensions Pack for Windows" (GIMP_Extensions_v2.8.20150403.exe) and "GIMP Massive Package for Windows and Mac" (GIMPMassiveWinPackage.iso). However, I don't want to tackle them until I get some selective information about just compiled plugins. I prefer to follow the advice I got at gimpforums, and if one of the GIMP packages has what I'm looking for, then I apologize for bothering you with this thread.

# Oh, and the Speed Of Dark is Zero. There is nothing of -or- in "Dark" to move. Well, nothing except for Dark Energy and Dark Matter. So, a better explanation would be that there is nothing of -or- in Dark, the movement of which can be detected by, let alone measured with, contemporary instrumentation.

George Harnett

Greetings,

The source code and the compiled binary executables for Windows (32bit & 64bit) for both of those filters can be found here:

Wavelet Decompose

Wavelet Sharpen

You might also want to investigate G'MIC Plug-in for GIMP, which includes quite a few sharpening filters, with lots of options.

By the way, as a new member, you should be able to use internal links. You will need 5 posts in order to use external links.

Greetings,

Thank you GnuTux and Graechan.

GnuTux: Those two "...Win.zip" files appear to be exactly what I'm looking for. I downloaded them and unzipped them and I think I can install them with all of the help I've seen on the Internet. I don't want to delay this reply while I'm doing that, and I'm sure that will go smoothly (relatively). Also, that "samj" thread has numerous Win plugins that I will be looking at too.

Graechan: I recognize the background of that website you sent me. It was one I visited last month when I was getting started in this process and couldn't distinguish between the Good, the Bad, and the Others. With your suggestion, I'll go back and revisit the compilation "challenge".

About G'MIC, I did look into that a little before - just enough to be unsure what it was. I didn't know if it was a stand-alone App or a Plugin. But, yes, it's not unusual for a super "Swiss Army Knife" plugin to beef-up even the best applications. I will look into that after I get these two Wavelet plugins installed.

George Harnett

While on the topic, I'd like to ask what type of images you're hoping to sharpen and for what purpose. After all, there are a few different way to approach "sharpening" both conceptually and computationally...after all, human perception is different from a printer is different from analysis is different from ...you get the idea.

There's a chance we could also advise you on other tools to get the results you need, besides these few plugins you originally sought to compile.

If you are using windows uncompress the zip to C directory.
All your NEW compiled plug-ins or src's need to be installed into This installs to GIMPs plug-in folder for that particular env build 32 or 64 bit.
To open the new cmd window use the start_msys.bat file that is included.
For c files only just do


For other src's which include c and h files use the Makefile or configure files included.
IF ./configure do
then


To install dependencies GIT has been built into the env for you.
do

Then cd BABL or GEGL or whatever the dependency name is.
Then do
you could also add the compiler name such as

To build a new version of GIMP do update all dependencies then GIT clone
BABL, build and install it
GEGL, build and install it then
GIMP , build and install it then type GIMP to open the program.
You shouild be able to bump up to GIMP-2.8.14 without updating any dependencies right away. I did.
I am using an older env though so it may already be the default version? let me know.
As far as i know PYGTK isn't working in the env so use --disable-python when building GIMP itself.
I was able to get pygtk and py console by downloading the latest mingw for 64 bit and placing the correct files in env/base/c

Hope this little bit of info gets you started a bit easier. Welcome to the Windows compiles for GIMP family.

Just noticed it is build GIMP-2.8.15. Excellent!

Rod, for these two plug-ins, would not make install be an optional step? Since the plug-ins are already compiled, the user would need only to copy the .exe that corresponds to their OS into their GIMP plug-ins folder.

Even if one were to compile the plug-ins, make install would be still optional and they could just manually copy over the .exe into the corresponding GIMP plug-ins folder.

Yes i was just for "the users" benefit using make install as "install to the base/c" (prefix=/mingw) directory for the dependencies to be found by the compiler in the future builds. The user could also adjust the ect/fstab file to a new PATH if need be.

Make install (manually moving the file) is possible after make but i think it's just as easy to do all in one command if GIMP is already installed into the env. Which it is in this case..

Besides if you have many libs or files to move it's much easier to let the compiler do it for you.

I wouldn't want to make GIMP and then move all the files manually myself. For single compiled c src files its fine though.

In fact when i do single c src plugin files i normally will do make and then test the file. Then i create a zip and upload it.