Create sidecar files for altered raws only
I use a custom build on Windows from www.partha.com and a Sabayon linux build.
At folder import, darktable creates a sidecar/xmp file for each raw file in the folder.
It is unnecessary, for me, to make one xmp file for each raw, as it is not processed and exported every raw file, in my case.
Please add an option to create the sidecar for a raw file the first time a raw file is altered only.
#1 Updated by Tobias Ellinghaus over 3 years ago
- Status changed from New to Closed: won't fix
At first this might seem like a straight forward thing to do – after all, it's how dt used to work. However, the sidecars not only contain the edit history but also color labels, tags/keywords and, most importantly, the rating. Now by default there no color labels or tags assigned that needed to be stored in an XMP, however, every image gets a rating at import. And since that initial rating is configurable we can't even make it up from thin air the next time you import the image. So even if it's not obvious at first: in darktable there is no image without data that needs to be remembered. Thus every image gets a sidecar file.
#2 Updated by Mihai Sorin Dobrescu over 3 years ago
As software developer myself I understand the difficulties of some feature implementation.
However, I've always found a way to implement some task, no matter how tedious.
I accept the need of a database, in case of all Lightroom-like application, but still, I wouldn't do this in a sidecar file no matter how easy or flexible might look because it simply duplicates the files on a drive and it is unnecessary in most of the cases.
There is a success model already, Adobe Camera Raw, which uses a cache and it is enough for most of the cases, or Lightroom with its database that doesn't fill the folder with files. It is all in one place and I can clean it up easily. And, I can keep xmp for the files I need only.
Sorry if I hurt your feelings, I appreciate the effort of what you do, but initializing some attributes for files that never need doesn't stand.
I know, the simplest user experience means the most sophisticated implementation, usually... And btw, I have never used a rating before have really developed an image, so I don't really get what you mean... BTW, I've asked for an option, not a change in behavior. Meaning, I would accept the application would not initialize, as you say, that rating in the eventuality I chose that path... Rhetorically, why should a file get a configured rating at import only? Shouldn't be that available whenever after? I might change it anyway... If I think further, next time when it is imported, I should have a rating if I have altered the image, if not, it should be the default = keep the rating when it is altered the first time, otherwise the rating might be the default one anyway.