[digiKam-users] Bye bye digikam?

Gilles Caulier caulier.gilles at gmail.com
Wed Jul 28 14:52:17 BST 2021


Hi,

For a better interoperability with RT and DT, the better way is :

1/ to use XMP sidecar with RAW file.
2/ RT or DT must write the new RAW preview after editing in XMP metadata as
base64. DK use already this metadata entry with XMP digiKam namespace to
render a JPEG preview of file:

tag : Xmp.digiKam.Preview
Code :
https://invent.kde.org/graphics/digikam/-/blob/master/core/libs/metadataengine/engine/metaengine_item.cpp#L1244

Best

Gilles Caulier



Le mer. 28 juil. 2021 à 12:37, Olivier Croquette <ocroquette at free.fr> a
écrit :

> On 27/07/2021 13:14, Øystein Andresen-Sund wrote:
>
> Most RAW applications do this, including Adobe Lightroom (unless you go to
> edit mode). Rendering directly from RAW would slow down the viewing and
> browsing process considerably and you would probably see an image with
> different colors than what you see in your camera.
> Try using RawTherapee or Darktable for RAW processing.
>
> Lightroom does something that neither DK, RT or DT do: it caches the
> processed image, so that it is what I see when browsing. It is the best of
> both world: displaying is quick, but I see what matters to me. Once I have
> defined processing settings in RT or DT, the embedded preview in the RAW
> file is completely irrelevant and can even more hurt than it helps if the
> processing changes the image substantially, for instance major cropping.
>
> Questions to the developers: would it be thinkable to call RT or DT to
> render the image, and store this as preview in the DK database, instead of
> the embedded one?
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/digikam-users/attachments/20210728/333c0cbe/attachment.htm>


More information about the Digikam-users mailing list