I’m getting back into darktable (on Windows) after quite some time. My question is simple: can I go straight from 4.6 to 5.2 or should I incrementally update the versions in between?
just download the newest version. It will delete previous versions before installing the new one.
1 Like
Hi and welcome to the community.
You should be OK, but there is no substitute for having backups.
2 Likes
Thanks for the reply Bernhardt. Yeah I figured that the update will replace the software. I was more concerned though about whether the changes to the database between 4.6 and 5.2 would cascade right through without a problem. I will take backups of the whole configuration folder and go for it, I think.
Thanks for the reply paperdigits. I will most certainly be backing everything up before going through with it. I’ll also be migrating my whole dark table set up to a new machine but I thought I would do this one thing first.
Having the same problem since I hoped the issue Reimplement "AI detection of image edges" in color calibration · Issue #16730 · darktable-org/darktable · GitHub would be considered.
Now I have the same usecase - updating from 4.6 to even 5.4 tomorrow or the following days.
Reinstalling of course lifts the version of the binary, but I understand Stephen’s question as being targeted on the update of the library with all the stored edits.
Obviously updates are tested before every release from one version to the next one. But did ever someone really test a leap of 5 or so versions?
@paperdigits of course - backups are always the way to go to limit desaster. And since Stephen did not complain I assume that in his case all seems to have worked well …
You may be able to use sidecars in case the library upgrade fails. But that does mean you’ll have to re-import all images (through “add to library” !).
That said, I’d try a direct upgrade first, and if that fails, try again using 5.0.1 as an intermediate version (easy enough for me, as I can compile dt myself).
I think the leap is only 3 versions: 4.6 → 4.8 → 5.0 → 5.2 (odd versions “don’t count”). So, get the 5.2 now, even if you don’t install it yet, to limit the risk.
(As a sidenote, I fail to see the interest in not upgrading while waiting for a feature to be implemented, as that means you miss out on all the features that are added)
Thanks - will try this.
That’s a misunderstanding.
The feature has been there for quite a while and has been removed. I tried to have that reimplemented by providing lots of sample images - and so simply waited for the developers to decide (and continue using that feature in the meantime).
From the development side of things, we don’t upgrade from darktable release X to release Y.
Each module does its own upgrades, and if the database structure changes, each of those changes is applied separately, one after the other.
This means if there were fire example 5 DB changes between X and Y, then 5 DB migration steps will be performed, no matter whether it’s 3.2 to 5.2 (separated by several releases) or 5.2 to 5.4 (consecutive releases).
4 Likes
playing around with 5.4 - working almost fine with my old edits.
But I stumbled about this:
Some of my presets don’t seem to work anymore …
- why is that?
- since I can’t select those entries (greyed out) I can’t delete
Any ideas?
Can you export the preset and check the xml in the resulting .dtpreset file?
looks like this:
<?xml version="1.0" encoding="UTF-8"?>
<darktable_preset version="1.0"><preset><name>AUTO</name><description></description><operation>denoiseprofile</operation><op_params>gz04eJxjYGiwZ2B44MAApGuMJ4NxqPZK27NnztgygOUa9n/88cz8upi7RUZmgdH/miyjQM4WI2YGCFi9Sstu9apVdkCmPZBtHxoaag/RN6jkyMKMQAKGYcARxsjXkK4PZWBImAShYcAhT0OaXPtA+g2R7AMASs1QSA==</op_params><op_version>11</op_version><enabled>1</enabled><autoapply>0</autoapply><model>%</model><maker>%</maker><lens>%</lens><iso_min>0.000000</iso_min><iso_max>340282346638528859811704183484516925440.000000</iso_max><exposure_min>0.000000</exposure_min><exposure_max>340282346638528859811704183484516925440.000000</exposure_max><aperture_min>0.000000</aperture_min><aperture_max>340282346638528859811704183484516925440.000000</aperture_max><focal_length_min>0</focal_length_min><focal_length_max>1000</focal_length_max><blendop_params>gz11eJxjZGBgYAZiAQYYmObEgAYY0QVwggZ7CB6pfOqC/0AAogEOJhzK</blendop_params><blendop_version>14</blendop_version><multi_priority>0</multi_priority><multi_name></multi_name><multi_name_hand_edited>0</multi_name_hand_edited><filter>0</filter><def>0</def><format>7</format></preset></darktable_preset>
my XML Copy Editor does not show any obvious errors, but of course I don’t know if the content is valid.
additional information:
I updated from 4.6 to 5.2 as suggested above, then downloaded the appimage 5.4 and started that by creating an new config dir by the comand line option.
There I imported the presets I had exported from 5.2 before.
The version number of the module in the preset is 11:
<op_version>11</op_version>
In 5.2, the version of the module is 11, so that matches what you have in the preset – but it should have been migrated to version 12 (what we have in darktable 5.4). Is that the preset you exported from 5.2, or is it newly exported from 5.4?
Maybe open a bug report on GitHub. Off to catch my flight.
In the meantime I had a look at data.db:
The entry claimed that preset to be active.
After some restarts now I see
so it seems to work now. Happy to see this - but strange anyway 
That was exported from 5.4 in the state documented initially.
After those reboots I mentioned in my last post (resulting in that new screenshot) I exported again - and now indeed I see V12 in that xml.
Happy travel! Thanks for the helpful tips.
Is it possible that darktable requires a restart after importing preferences from a previous version?
Yes indeed, I think that is the case.
1 Like