Bonjour,
Thank you very much, that’s very kind.
I put the modified gmic-3.4.3 sources for gimp-3.0.0rc1/gmic-qt6 on this link if you want to compile them:
https://github.com/GreycLab/gmic-community/releases/download/gmic-3.4.3/gmic3.4.3-gmic-qt-6-gimp3.0.0rc1-src.7z
:o)
Is this possible to have just a list of the modifications somewhere ?
Or a pull request ?
Bonjour,
I attach the archive where there are the modifications and the host_gimp.cpp file which is modified for gimp3.
I’m sorry but I don’t use git except to import data.
:o)
Modifications_GMIC-GIMP-3.0.0rc1.zip (10.5 KB)
Bonjour,
Merci pour cette nouvelle version qui fonctionne très bien sur Gimp 3.0.0-RC1 W64 et Gimp 3.0.0-RC2 W64.
:o)
Merci Sylvie, et bonne année 2025 !
Bonne année 2025 à vous aussi :o)
Thanks for the update and Happy New Year to you guys.
…but
I found out that the CNN scaler is once again broken after I updated to 3.5
In a new way though, it now says:
[gmic] *** Error in ./scale2x_cnn/run/__run/ *** Command ‘input’: File ‘IN’, format does not take any input options (options ‘32,32,1,1’ specified).
I did of course only supplied it with the sharpness factor and not anything else to be clear.
I tried a bunch of other random filters and found no others that had issues for me.
I’m not too upset, there are lots of filters to play with, including other scalers, but I thought I’d mention it so somebody can have a look when they have some spare time.
Oh I forgot to say: I get the error in both the GUI and CLI versions. And once again it might just be something on my system playing tricks, so if anybody else can try and see if they had the same issue it would clarify matters.
Hello @Whatnot .
It works for me, so could you please check:
If that still does not work, find all occurences of file gmic_scale2x_cnn.gmz on your system, and delete them (to force G’MIC reloading the latest version).
Thanks!
Thanks David, that update button fix it!
I feel stupid not trying that, but in my defense, the error I got gave no indication that there was any relation to the neural network, and I got the error in CLI and just quickly tested if it was there in the GUI version …too quickly I guess 
Anyway, many thanks for the help.
Nice to know it fixed your issue.
In version 3.5, I’ve indeed added a new feature in the G’MIC neural network library that allows to deal with multiple neural networks in the same command, and that broke the nn_lib API, so all “old” neural network file data are actually broken.
@samj
Hi 
For default values this problem occurs:
Just an unconfirmed guess: maybe the latest change (2024/12/17) in the fx_ball syntax has an impact on this?
Yes, actually, command ball has been recoded and is more strict regarding the parsing of its arguments. The first argument size has to be an integer (size of the image rendered).
You can fix your filter by modifying line 24670 of sylvie_alexandre.gmic:
ball {int($rayonA*2)},$R_DT,$V_DT,$B_DT,$Ball_Specular_light,$Ball_Specular_size,$Ball_Shadow
I found 2 occurences of the ball command in that file I found on my system, neither were on line 24670. However, that file was an old backup file and not one in operation.
Nevertheless if there are 2 ball commands I imagine you need to give both the ‘int’ modification, same for any old .gmic that has the ball command I would think
Thank You. Now it works after refreshing the filters.
OK; finally got around to installing 3.5 for 2.10x. More than a few of my favs no longer work, but David already explained why (response to others) so just need to update them using the new presets (have done a few of them already). Again, thanks a heap to you and your team, David for making G’MIC the gift that keeps on giving.
Is it just me or G’MIC is no longer prioritizing user.gmic for command? From the Paint.NET side of thing, I have to copy and paste into update350.gmic.
It has happened to me before. By this
do you copy the entire code block or just import user.gmic? I recommend the latter if you have not already done so (using command, m).
I just copy and paste code block. I didn’t use m really. I think it’s just me after testing for a bit.