As you may know, we are currently implementing a brand new interface for the G’MIC plug-in, based on Qt. It is intended to become a kind of ‘universal’ plug-in that could be ported for other software than GIMP (in particular, we have Krita in mind, of course!).
By the way, this is still a beta project, but we have managed to build a version of this Qt-based plug-in for Windows, and I’d like to share the news with you.
So here is the new plug-in in action :
As you can notice, this plug-in has an adjustable preview, as well as a filter search engine (by keywords).
We would be really interested to get your feedback about it.
So, Windows users, if you want to test it, you can get it from these two URLs:
There are probably some regressions compared to the current GTK-based implementation, so please be indulgent
Any feedback, bug report and suggestions are welcome !
Note 1: The sources are not yet available for this plug-in, but they will someday Note 2: No Linux versions available due to probable library version mismatches.
Just downloaded the .exe installer to test it both on Windows 7 and Windows 8.1 (64 bit).
I have installed this new version with Gimp 2.8.20
Both on Windows 7 - 8.1 (Gimp 2.8.20) it fails to work
The new QT version is available as option in the Gimp > Filter Menu but it does not work when you hit the button to launch it.
Filter > colorize interactive does not work as expected (Gimp 2.8.20 - Windows 7 64 bit):
*** Error in ./ *** Command ‘-fx_colorize_interactive’: Undefined argument ‘$4’, in expression ‘$4’ (for 10 arguments specified).
On the contrary, same jpeg image works fine with Gmic 1.7.9 (Colorize interactive)
This same filter has been often reported as broken on Krita (Windows versions) in the past as well.
BTW, this new QT version is already extremely responsive and stable on Windows !
Tested for more than 2 hours now…
OK; after the error (about 30 seconds) the QT app does launch but continues to ask to import favorties but the import continues to fail. Regardless, it does work (and quick). Not sure what causes the error though and I’ll remove the plugin for now, but at least it appears, for the most part, to work.