Good morning,
I encountered a strange behaviour yesterday, and though I spent a little time reading the doc and checking the forums, I found nothing.
When I export a raw file with the collection option (to export a high quality jpg version alongside my raw in the same folder and have it in the database), the keywords do not get transferred. I do this to save time on export when I want an image in multiple versions/places. The D&S module slows down my export time so much and my computer is unusable during this time.
When I use the āfile on diskā option, the keywords do get transferred but I donāt have the image in the collection to use it as an export template.
There may be an obvious explanation but I canāt figure it out.
Sorry if it is not clear.
In the export menu, go to ācollectionā and export a jpg. It will appear in the database next to the raw files but any keywords the raw file had will not be copied to the exported jpg.
You are using something that is part of a lua script I believeā¦
As it exports and then re-imports I wonder if this is when the information is lost as its being treated like a new file on import?? I have no idea but you would need to look at the code I guess to see and manually replicate the stepsā¦
Edit:
It seems like there is code in the script to save and restore the tags, rating and colors labelsā¦ if I read it correctly but maybe something has changed that impacted this function in the latest DT??
ā save image tags, rating and color
local tags = {}
for i, tag in ipairs(dt.tags.get_tags(image)) do
if not (string.sub(tag.name, 1, 9) == ādarktableā) then table.insert(tags, tag) end
end
local rating = image.rating
local red = image.red
local blue = image.blue
local green = image.green
local yellow = image.yellow
local purple = image.purple
I wonder if @wpferguson could comment as I believe he wrote this useful script. This is a feature I feel should be standard in the export module anyway, but thanks to the LUA script I can export to my collections.
Just an observation: With taget storage = files on disk, I can also set on conflict = overwrite. With target storage = collection, DT hides the on conflict =ā¦ and does not overwrite, it produces a new file on each export.
What software do you use to inspect metadata in exported images?
Yes, I am the author of the original ext_editor.lua script.
The target storage ācollectionā is meant to export a file, usually a 16 bpp tif, for further edit with and external program.
I donāt understand what is the problem here, as for me tags, ratings and colors are copied correctly.
Thanks for the script, I have used it for a while. Maybe it is a bug on my version (Mac) as keywords are not carried over.
As I explained, I donāt often use it for external editing but as a master jpg in my collection.
When I get home, I will try an export in other formats to see if there is a difference.
Having an overwrite option would be great.
I am curious but I might have misunderstoodā¦is all your missing by doing this is letās say you export to the same directory as the raw and then you have to do the import step for DT to recognize them but you have your tags?? Doing it direct to the collection just saves the import step but loses the tags?? Or is there a further differenceā¦if not at least for now I would just export and reimport the new filesā¦again I may have missed a nuance to this workflow