5 ms·
The problem does not seem to be GIMP if I understand the article correct, but the GEGL code (or the developer of it) which it relies on.
by KNoureen 12y ago
The problem does not seem to be GIMP if I understand the article correct, but the GEGL code (or the developer of it) which it relies on.
- Sanddancer 12y agoGEGL and Gimp are pretty much joined at the hip. While they're in name separate projects, they're very much developed for one another.
- jononor 12y agoGEGL is developed for GIMP, and other projects. http://www.jonnor.com/2014/04/imgflo-0-1-an-image-processing-server-and-flowhub-runtime/ http://www.jonnor.com/2014/04/imgflo-0-1-an-image-processing... http://www.jonnor.com/2014/11/imgflo-0-2-the-grid-launched/ http://www.jonnor.com/2014/11/imgflo-0-2-the-grid-launched/ Disclosure: I'm a GEGL dev and the imgflo maintainer. The 'other projects' part is one of the reasons why the proposed solution 'just strip all colorspace info, assume it is the same throughout entire processing pipeline' is not acceptable for GEGL, even if that might somewhat close to the typical usecase for GIMP.