I’m trying to understand some strange DT behaviours.
First I would like to understand what I ask in the subject.
If DT finds, at startup, a sidecar with the classic name convention imagename_version.ext should create automatically a image duplicate with the version found in the filename ?
Thanks in advance
If you import an image, darktable will attempt to load all sidecars, assigning them version numbers according to their filenames. There is a function that scans for updated sidecar files each time you open darktable but this must be enabled by the user. My understanding is that it looks for updated sidecar files that match images/versions already imported and prompts you if differences are found. I’m not sure it looks for non-matching sidecars, but I’ve not used this functionality.
The naming convention is described in the user manual. Sidecar files that do not match this naming convention are ignored, apart from xmp files created by other applications, which have a slightly different naming convention. See this page for more information.
Chris, thank you for your explanation.
After some test I understand what’s happens.
My scenario:
- pictures are store on a NAS
- master DT installation is a workstation
- secondary DT installation on a laptop
My goal is keep editing synchronized (in some way) between workstation and laptop.
Write sidecar file for each picture is dislabled (I save It manually).
1st test:
I created a RAW image duplicate (version 1) on the laptop; I applyed some modules and I saved the XMP file pressing ‘write sidecar files’, so the XMP file has been saved on the shared folder.
Then I opened DT on the workstation and automatically DT had create the duplicate (version 1) with the applyed modules and keep the original (version 0).
Then I did the same test with a JPG file.
At the end, on the workstation, I had only one version (version 1) without the original version 0.
I believe that problem in on the XMP file gernerate for the JPG because is: .jpg.xmp and not .xmp
Is it a bug ? Or can be fixed with some settings ? (I did not find).
This is how darktable does it and you can’t change it.
Do you use or intend to use the library database?? If not then actually turn on creating sidecar files…now just use --library :memory: switch on your commandline . This will just treat DT more like an editor using a virtual library for each session…it will open your file and read in the associated sidecar to apply the edits. If you work this way on both machines you don’t have to worry about database conflicts…this won’t work if you want to use the library database though…
Iirc, dt ignores jpeg files by default, which is not illogical for a raw developer.
Did you change that setting (in the import dialog)?
Thanks
I will try with library in memory
1 Like
I know that DT for raw processing, but It is so useful, full of powerful features that I’m using It, nott only for raw images but also for jpeg processing. It’s my intention.
1 Like
My point was that darktable by default ignores jpegs, unless you tell it explicitly not to…
So that could be why .jpg.xmp’s are ignored
That is incorrect as far as I know there is no such default setting …on import there is a checkbox that is not the default that allows you to ignore any jpgs for the selected import…I suspect if you leave that checked each time you import or have done so at some time in the past you will not import jpgs…however normally if you have both they should be imported unless you have selected not to…
Just to inform all that the check box for importing jpg works perfectly for me.
Intentionally I checked It in order to import jpg picture also.
The only problem is the name of saved sidecar file the is file is like this img1017_01.jpg.xmp
You are right in that there’s no setting in the config dialog.
I seemed to remember that the corresponding box was ticked on a new install, but I could very well be wrong
The setting is sticky, so I can’t check that easily (as I don’t mix jpegs and raws in one directory, it doesn’t matter for me which state it’s in)
Anyway, what’s important is whether @Ric_Developer had that box checked when trying to import a jpeg with versioned sidecar.
1 Like
I think you check to ignore jpg not import them but I see that you have an issue with naming…as for version numbers if you are editing from two different computers and for a time you did not have the xmp files writing but you were manually writing them then I am sure there is an opportunity for conflicts in version number added to your file names…
I actually though there was an option to treat jpg and raw as one…and I thought that was in preferences so I went looking but I must be thinking of another application… 
1 Like
Maybe saving jpg sidecar in this way img1017.jpg_01.xmp could fix the issue.
Yes, I’m aware that picture version numbering is not synchronised.
This is another problem that at the moment not has a workaround.
I have my images in the cloud and use DT as I mentioned …as I don’t need the database I am just opening an closing files in the folders that they live in…nothing to sync or manage…otherwise what you would need is to setup your config directory on your nas and point both versions to that if it can be accessible…then they are both working with the same database…this should keep your versions correct…I don’t use it and can’t be bothered to worry about it I just us DT to edit the photos…
Todd,
Great !!!
It works also for jpg ! Thank you very much !