[digikam] [Bug 374655] New: Working with raw processors

Juan José Casafranca bugzilla_noreply at kde.org
Fri Jan 6 20:40:52 GMT 2017


            Bug ID: 374655
           Summary: Working with raw processors
           Product: digikam
           Version: unspecified
          Platform: Other
                OS: All
            Status: UNCONFIRMED
          Severity: wishlist
          Priority: NOR
         Component: Thumbnails
          Assignee: digikam-devel at kde.org
          Reporter: jjcasmar at gmail.com
  Target Milestone: ---


digikam is a great software for photo management but when it comes to raw
processing, it's not sufficient. There are some specific tools that are much
more powerful than digikam when it comes to raw processing (eg darktable), but
its not easy to work with both of them. 

The issues I commonly see when trying to use digikam and darktable in my
workflow are the following:
-If I duplicate an image in darktable (which generates two different xmp
files), its not possible to have both of them in digikam
-When I process an image in darktable, digikam thumbnails stays inmutable so
it's difficult to know which picture is each one

My proposal is the following:
For raw files, allow the user to select if the thumbnail must be loaded from
the embedded jpg file or from an external source. This external source would be
the raw processor output. If there exist several xmp files for a specific raw
file, each one defining a specific proccesing pipeline, different views should
be created in digikam (one for each processed pipeline in the raw processor).
Raw processors will be feed with the xmp file and will output the thumbnail
(and maybe a full resolution image when the picture is opened in the viewer)

To make this work without consuming too much resources, thumbnails could be
marked as dirty for those whose xmp file has changed during startup and when
the picture is opened in a raw processor through the digikam interface. 

If you are interested in such feature, I would enjoy implementing it. If you
feel that this feature is not necessary, I would like to hear your raw
processing workflows when dealing with digikam and an external raw processor.


You are receiving this mail because:
You are the assignee for the bug.

More information about the Digikam-devel mailing list