So ive been playing with building for windows myself. As I keep encountering bugs (Not entirely unexpected), i wanted to downgrade back to Bills 3.9.0+798 build
However both the library db and xmp files appear to not be backwards compatible to 3.9.0+798. If i donwgrade i loose all my edits.
Even deleting the library file and import again with XMP files in 3.9.0+798 fails. I was able to recover by upgrading again and restore the library db from 3.9.0+873.
Anyone can think of a solution? Any way to convert the xmp files back? Im worried there is no way back now
It happens that some (needed) updates avoid to go back to earlier release. And this often appears as it’s when some database updates are made. On (nearly) all official releases, there’s a warning about that.
So there’s no solution (except using new versions) and that’s a risk when using development versions. Development version is what it is: a piece in development, so not stabilize. You could have all sort of issues when using development and you just have to accept that. Or use official, stable releases only.
If you do want to continue using development versions you might want to consider setting some of the storage options in the preferences to more suitable settings (create snapshots on exit or once a day and keep a rather decent amount of snapshots).
This isn’t full-proof but, together with emptying out your cache dir, might give you a better point to fall back upon when things go wrong.
I’m not sure why you use a development version. You can build yourself using the stable sources that are available on the release page (the assets section).
Personally I use 3 darktable versions to keep things separated and safe: The latest stable one for my official stuff (do not want to mess with those), I use the latest development version for testing (Play Raws for example) and a third one for stuff that has not been merged yet (future stuff still in development). All three are self build.
Simply to help the community by testing to pay back a bit for using open source software. As my background is IT i figured i both learn something and help by testing.
Perhaps, but Ive really only encountered 1 issue that i wasn’t able to reproduce on 798. (The chromatic aberration issue) And that was only on 1 single raw file. Its really not big issue for me, just wanted to report it in case it could help development. Its pretty easy to work around anyway.
The other issue I encountered I could also reproduce on Bills 798 build and 3.8.1.
Other than that the build I run seems fine. I doubt its a problem with my build environment. I run a fresh win 10 install and use a fresh msys2. Only thing i did was to downgrade pango and harfbuzz as per
