Update With 2.80

[saphtea]

Hey! I absolutely love that you've done this and have no idea personally how haha. Would you be curious in porting this to Blender 2.80/making a custom build for 2.8? Hope to see it man, thanks for the work :3

[myselfhimself]

Hello, I will be working full-time on a G'MIC Blender plugin in the same direction as this (texture nodes), leveraging this new Python binding instead: https://github.com/myselfhimself/gmic-py . Blender will not need any patching anymore. Note that we have bad support for OSes other than MacOSX and Linux 32&64 bit, so any help in this direction or any will be welcome. This year, I am part of the lab developing G'MIC.. and we are really open to any co-design and software collaboration on Github.

[myselfhimself]

Blender 2.80 plug-in development shall start latest mid-february 2020, once the G'MIC Python binding is ready enough.

[MasterJames]

How's this coming along? waiting for the delayed 2.83 or 2.9 maybe?

[myselfhimself]

Hello, I am not the official maintainer of this project, but I want to finish a work on gmic-py, still WIP because of personal issues, then discuss architecture with the node compositing team of Blender.org for how G'MIC could be tied to Blender as an addon/patch for good. It seems that the blender-custom-nodes patch has already been studied by some people in the Blender team but seemed big. My aim is that noone would need to have any custom blender build to be able to run G'MIC in it.

[IPv6]

would be great to see this in Blender... G`MIC is awesome!

[myselfhimself]

Hello, I am improving the numpy support for G'MIC Python binding (gmic-py) for version 2.9.1 and will write pygame and/processing.py examples leveraging gmic-py soon.
The progress related to Blender is not more than what is showcased in this video for now, especially related to architecture:
https://www.youtube.com/watch?v=qbJv7QScs3s&list=PLe-w9p--aJKvIs3toDqF0m27rs8wR4W4Y&index=2&t=0s
I now think that the blender-custom-nodes patch should be forked to isolate the G'MIC node from other custom node types and that it should be improved from there, as well as reviewed more simply by the Blender core developers.
Another idea, shared with my boss (G'MIC's author), is to develop a node or node group in pure Python G'MIC without patching Blender, to show to the Blender team what is possible at most in Python without patching, and where a C/C++ patch is needed. For now, it seems that a Python-scripted node cannot get an input image socket, tell if I am mistaken. Such a limitation would not prevent a hack where there is no link between a disconnected input image node and a G'MIC node, but the G'MIC node logic would have to grab programmatically the input image buffer.
My contract will last till end of december 2020 for now, I am unsure whether I will achieve one of the two possibilities above in time before then. Anyway gmic-py is a funny enough project to continue contributing on it through 2021.

[IPv6]

Thanks for information!

"develop a node or node group in pure Python G'MIC"
"For now, it seems that a Python-scripted node cannot get an input image socket, tell if I am mistaken. Such a limitation would not prevent a hack where there is no link between a disconnected input image node and a G'MIC node"
Wow, even with this limitation it would be very powerful approach!!! Imho.

Blender devs has interest in "everything nodes" project, imho "python script node" may fit this perfectly. I mean, they may incorporate such possibility (custom python node) into master someday

[myselfhimself]

Thank you @IPv6, I have just commented on the Everything nodes Blender tracker ticket related to a Python compositing node.

[myselfhimself]

Hello, the gmic qt option would control only one node or video sequencer effect at a time... This is not stupid as an early workaround. po 8. 3. 2021 v 7:45 odesílatel ekswathi <notifications@github.com> napsal:

…

Sorry if it is a dump question. The G'mic qt option done previously was working nicely right? Instead of adding all to blender and make it heavy is it better to link it as an external program? — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#5 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAJU5QW57OMIWEJ3DKFVLU3TCRXBDANCNFSM4ISSS6BQ> .