Hi Bertwim,

I’m a user and not a developer and I want to answer your request from a users 
perspective. I’m using the duplicate-feature in a different way: I’m always 
exporting one of the duplicates and I’m expecting, that it does not matter 
which copy I have exported. Hence, the current behavior is perfectly right for 
me.

But your problem can simply be solved by using the right variable substitution 
in input field „target storage - file on disk“. Using $(VERSION) as part of the 
filename should resolve your problem. See also: 
https://docs.darktable.org/usermanual/4.0/en/special-topics/variables/

Best regards
Andreas


> Am 17.07.2022 um 23:01 schrieb BWH vanBeest <b...@xs4all.nl>:
> 
> Dear DT developers, 
> 
> With the duplicate manager, multiple images from the same original (raw) 
> image can be generated, DT does that by creating xmp-files with the base name 
> extended by _01, _02, etc. 
> For instance (nikon nef format), when the original image is <myrawimage>.nef, 
> the associated sidecar is <myrawimage>.nef.xmp. After creating duplicates one 
> gets <myrawimage>_01.nef.xmp, <myrawimages>_02.nef.xmp etc. 
> 
> However, when jpgs are exported from these xmps, the resulting filename is 
> the same for these different xmp-files. That is, it may be nice to have 
> duplicates in DT, efficiently managed and so. But as soon as an export is 
> done, the different variants overwrite each other. Apparently, for the output 
> file, the name of the raw is file taken, whereas I think this should be the 
> name of the xmp-file. 
> 
> In order to fix this, I tried to find the relevant piece of the source code, 
> but I cannot find in the code where the relationship between raw and xmp 
> files is apparent. I guess it must be somewhere hidden in eport.c? Is there 
> somebody who can point me to the relevant pieces? 
> 
> Kind Regards, 
> Bertwim 
> 
> ___________________________________________________________________________ 
> darktable developer mailing list to unsubscribe send a mail to 
> darktable-dev+unsubscr...@lists.darktable.org 

___________________________________________________________________________
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Reply via email to