Heya,
I’d like to use darktable and vkdt on the same folder. This creates some issues with how the sidecar files are handled. Usually I cull within darktable, assign tags, delete the culled photos from within darktable and then get to work on the images. Also I use darktable to move the raw files to their final destination after editing is done.
This creates to problems:
a) vkdt doesn’t know about the tags set in darktable
b) when deleting/moving photos vkdts sidecar files are left behind…which is solvable by manual intervention but inelegant.
I can totally live with these small issues but maybe someone has a good Idea on how to tackle this.
i don’t want to read xml if avoidable by any cost. also vkdt works on folders only. tags are implemented as folders with symlinks. it’s possible to write an external tool to convert such things, but i’d like to keep bloat like this out of the main program.
@mino if you first use dt and then move and only after that use vkdt on the resulting folder there won’t be any prior vkdt sidecars to move around? where in the workflow as you describe it would you even need vkdt? seems like any potential grading work wouldn’t be visible in darktable for moving around anyways.
I think that train already left the station. It is not avoidable when xml is the way most raw software handle metadata. Reading it should be a core functionality.
But I do want to use vtdk. It’s fast and cool to use the nodes. I also want to be able to handle some DAM functions. I haven’t used vtdk in a while, so I need to check it out again.