Digikam and Darktable

[digikam-2]

Hi,

Am a current DarkTable user, but the DAM portion is on the barebone
side.

Is there somebody using both? How does/would it work?

DT doesn't alter the raw, it creates its own xmp file:

original: 123456.cr2
DT creates: 123456.cr2.xmp with all the steps

Then the question is: What does DK do? Does it read the DT changes? or
Do I have to save the changes to JPEG/TIFF, then reimport these in
DK?

How would DK know that 123456.cr2 has become 123456.jpg or 123456.tiff
and to keep them together?

--
sknahT

vyS

[Remco Viëtor]

On mercredi 14 septembre 2016 13:25:41 CEST [hidden email] wrote:
> Hi,
>
> Am a current DarkTable user, but the DAM portion is on the barebone
> side.
>
> Is there somebody using both? How does/would it work?
>
I use Digikam to sort and rate my pictures, and to add title, captions and
such. Then I use Darktable to prepare the jpegs. That means Digikam creates
the sidecar .XMP files, which are read (and updated) by Darktable.
So basically, my work flow is :
camera -> Digikam -> Darktable -> output (web album or sometimes print)

> DT doesn't alter the raw, it creates its own xmp file:
>
> original: 123456.cr2
> DT creates: 123456.cr2.xmp with all the steps
>
> Then the question is: What does DK do? Does it read the DT changes? or
> Do I have to save the changes to JPEG/TIFF, then reimport these in
> DK?
As I do my tagging and titling in Digikam (ideally before going to Darktable),
I don't know (and don't care). The processing instructions that Darktable adds
are irrelevant as far as Digikam is concerned.

Note that Darktable notices changes made by Digikam if they are written to the
.XMP files.
>
> How would DK know that 123456.cr2 has become 123456.jpg or 123456.tiff
> and to keep them together?
I don't export all developed images automatically (not much reason to, and
certainly not to the same directory tree as Digikam uses). Instead, I export
when needed at the size and settings needed (print or screen need different
export settings. So for me, it's irrelevant whether Digikam knows which jpg/
png/tiff goes with which raw file.

[digikam-2]

On Thu, 15 Sep 2016 08:06:38 +0200
Remco Viëtor <[hidden email]> wrote:

> I don't export all developed images automatically (not much reason
> to, and certainly not to the same directory tree as Digikam uses).
> Instead, I export when needed at the size and settings needed
> (print or screen need different export settings. So for me, it's
> irrelevant whether Digikam knows which jpg/ png/tiff goes with
> which raw file.

Thanks.

But if I'm in DK, how do I know that this image is already processed
and ready in DT?

Does DK reads the DT tags, like darktable|changed and
darktable|exported, ...?


--
sknahT

vyS

[Remco Viëtor]

On jeudi 15 septembre 2016 07:24:29 CEST [hidden email] wrote:
> On Thu, 15 Sep 2016 08:06:38 +0200
>
> Remco Viëtor <[hidden email]> wrote:
...
>
> Thanks.
>
> But if I'm in DK, how do I know that this image is already processed
> and ready in DT?
>
> Does DK reads the DT tags, like darktable|changed and
> darktable|exported, ...?

That's not a problem for me:
When/if I need an image, I look for it in Digikam, then open it in Darktable.
_There_ I can see immediately if that image is ready for export.

As I said, I don't export systematically, but as needed and at the size/format
needed. So changes are I will need to export the image anyway.

If you want to have the processed images always available, the easiest is to
export to the directory where you have the corresponding raw file. Digikam
will not realise that the two are versions of the same images (afaik), but
they will be shown next to one another if you sort by file name.

This system works for *me* with the way I take and use my pictures. But I
can't say if it's suitable for anyone else, as I don't know his/her needs.

[digikam-2]

On Thu, 15 Sep 2016 19:06:07 +0200
Remco Viëtor <[hidden email]> wrote:

> If you want to have the processed images always available, the
> easiest is to export to the directory where you have the
> corresponding raw file. Digikam will not realise that the two are
> versions of the same images (afaik), but they will be shown next to
> one another if you sort by file name.

Thanks for the help, very appreciated


--
sknahT

vyS

[Olli Lupton]

Hi,

My workflow is similar to this (raw + jpg from the camera in the same directory, occasionally I use darktable to make a different jpg from the raw).

In digikam you can group the raw+jpg together, so that you don't see every photo twice: open an album, select all the photos, right click -> group -> group selected by type.

For me, this means the raw images are hidden and I only see the jpg versions (I don't know how digikam decides to show jpg and hide raw instead of the other way around, but it's what I want!).

Cheers, Olli

On Thu, 15 Sep 2016 at 19:18 <[hidden email]> wrote:

On Thu, 15 Sep 2016 19:06:07 +0200
Remco Viëtor <[hidden email]> wrote:

> If you want to have the processed images always available, the
> easiest is to export to the directory where you have the
> corresponding raw file. Digikam will not realise that the two are
> versions of the same images (afaik), but they will be shown next to
> one another if you sort by file name.

Thanks for the help, very appreciated


--
sknahT

vyS