Hello everyone, I just figured out how to install third party GMIC plugins via editing a text file (update325.gmic) for me. Now its time to read GMIC tutorial PDFs I have saved on my computer in hopes of making a GMIC plugin. Let me just say that GMIC has FAR more documentation then GEGL does and sadly I cannot use GEGL and GMIC together in a easy way. So yeah...

I'll update everyone in a few days or weeks if I get anything interesting with GMIC going. So far I am just getting my feet wet in GMIC. No guarantee I will make a GMIC plugin, but I will try, and if successful we'll get some quality test styling plugins in GMIC.



*note I have been using GMIC for several years now but this is the first time that I actually desire to make plugins for it.

That's a good idea. If you use an existing filter and put-in your preferred settings you can save it as a filter. It goes in the home folder as ".gmic"
It is a text file. Multiple filters can be listed in this file and they come-up at the bottom of the G'MIC filters list.

There are details on this here.

G'MIC is an entire language but you maybe good at picking it up. (better than me hopefully)

G'MIC is also a plugin for Krita, Natron, Toshop, and so on and on...

Guys, can someone please give me basic code in GMIC that runs hue, saturation and gaussian blur together? I tried



and nothing happens. I have no clue how to chain all these filters together. I can easily do it with GEGL but not GMIC.


Share your GMIC knowledge and I'll share my GEGL knowledge.


If we get lucky I'll make a layer effects engine for GMIC but I don't know how to make a bevel with it and its outline filter can't chain right with other operations. Though I have not have the chance to study GMIC in deep depth like I have with GEGL.

I believe that until Gegl filters support every call/use of PDB (which plugins and scripts can), the revolution will not be possible.

I agree and somewhat disagree. Here's why.

Putting GEGL commands in the procedural browser will remove the ability of live preview GEGL Graphs all together. They will load just like any other script fu of today. Step by step.

Right now we already have that one guys (gegl_command.py) plugin that calls gegl:gegl; but it does not allow alt name spaces like gimp: and lb:. For example his gegl_command.py works on my gegl:bevel, but if the name changes to lb:bevel it doesn't work.
He needs to allow alt GEGL name spaces, as Gimp's team has told me to change ALL my plugins to an alt name space.

Also, the GEGL plugins I am making now I consider "second wave" GEGL plugins that are arbitrarily distinct from the GEGL plugins I made in 2022 and even early 2023, as some of them have insanely complex GEGL graphs, with hundreds of nodes and connections that I did not understand how to make into filters back in 2022 or even six-seven months ago. I am single handedly exploring GEGL and it is just a sad thing that others aren't exploring it with me.

Misunderstanding - Gegl's acceptance of PDB was quite the opposite.
There are already some Gimp operations.



Do you know where to find a full list of them?

I'm fully aware of those and use them all the time. Those are GEGL operations exclusive to Gimp and that depend on Gimp.

I don't know where they are all listed but I know almost all of them in terms of what they do.


GEGL can't even call Gimp Gradient and Gimp Curves and Gimp Hue Saturation correctly. Its there but it doesn't work

Try this: