Previously, gimp has these limitations that prevented darktable-gimp
interoperability:
- 8-bit colour channel
- lack of non-destructive editing
However, the upcoming gimp has already solved the first problem by
switching to 16/32-bit channels, and their use of GEGL also claims
non-destructive editing support.
For point 2, how non-destructive is the current gimp git master?
To allow darktable-gimp interoperability and allow darktable to export to
gimp, should we start work on adapting darktable to use GEGL?
Also, is it a good idea to start working with GEGL for a pan-GEGL xmp
sidecar format
?
The workflow is:
RAW file -----------------------------> xcf file
----------------------------> final image file
darktable image editing
for corrections
and basic exposure
/ tone adjustments
sidecar file 1 sidecar file 2
Would it be feasible for us to use two set of sidecar files (darktable and
the downstream image editor) to "replay" the rendering of the final image
file from the RAW file (i.e., feed the raw file and both sidecar files
into the Makefile, and it spits out the final image?)
Or does the workflow have to be truncated...... and the image editing must
start from scratch whenever there are any changes made by darktable?
------------------------------------------------------------------------------
Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more!
Discover the easy way to master current and previous Microsoft technologies
and advance your career. Get an incredible 1,500+ hours of step-by-step
tutorial videos with LearnDevNow. Subscribe today and save!
http://pubads.g.doubleclick.net/gampad/clk?id=58040911&iu=/4140/ostg.clktrk
_______________________________________________
darktable-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/darktable-devel
