Yes exactly that. I just imported the images but did no changes to them. Therefore the history and the xmp files are empty. xmp files are not zero length but do not contain any history steps.
 
"However, the defaults get written to history when the thumbnail is generated..."
This I cannot confirm. I regenerated all thumbanils (deleted cache directory) some time ago (about 2 months, I had 3.x there already) and furthermore tried with single affected images. The thumbnail got created but there were no history entries added. Neither in the history table in the library database nor the xmp files.
 
Gesendet: Montag, 12. April 2021 um 03:23 Uhr
Von: "William Ferguson" <wpfergu...@gmail.com>
An: "darktable-dev@lists.darktable.org" <darktable-dev@lists.darktable.org>
Betreff: Re: [darktable-dev] Add missing histories
In dt 2.x history only contained changes from the defaults, therefore if you didn't edit an image then there was no history and the xmp file wasn't updated.  With 3.x we started saving all history including defaults.  However, the defaults get written to history when the thumbnail is generated, but don't get written to the xmp file until the image is opened in darkroom mode.
 
On Sun, Apr 11, 2021 at 5:29 PM paka <p...@opensuse.org> wrote:
On Sunday, April 11, 2021, 4:48:11 PM EDT, Thomas Werzmirzowsky <werzi2...@gmx.de> wrote:
On 11.04.21 18:47, paka wrote:
> * werzi2...@gmx.de <werzi2...@gmx.de> [04-11-21 04:35]:
>> Hello everybody,
>>
>> during the last days I had a closer look at my library database because
>> of incorrect white balances of old images because of changed defaults. I
>> could solve the white balance problem but during the research I noticed
>> that about 10% of my images (about 7000 images) do not have any history
>> entries in the database. By that I mean that in the history table is not
>> a single entry for the image. As soon as I open the image in Darktable a
>> default history is added.
>>
>> Because of the white balance problems I'm worried that this might also
>> cause problems in the future when defaults might change again. Is there
>> a way to set the default history for all of these images (image ids are
>> known)? Maybe via a LUA script? Fruthermore is it possible to update all
>> sidecar files based on the current library database?
> import *subject* images and dt will read the xmp files into your db.
>
> or set dt to search for new/changed xmp files on loading and direct dt to
> read those files.


Sadly the xmp files for the affected images are also empty. I tried to
trigger a reload in the hope that darktable would apply the default
history in the process but that didn't happen. I got the dialog telling
me that a xmp file was changed and if I want to update the database or
update the xmp file. But both options do not insert anything in the
history table and create an empty xmp file again. So no defaults are
added during that process.

I guess importing the subject images would work but therefore I would
have to import each single file manually. That would gain nothing
compared to just open each file once in darktable.

============================
sorry, I cannot understand how you got "empty" xmp files.  are you not working raw images?

you have no backups where you can restore the "empty" xmp files.

explain "empty" xmp tiles.  you have zero length xmp files?


--
(paka)Patrick Shanahan       Plainfield, Indiana, USA          @ptilopteri
http://en.opensuse.org    openSUSE Community Member    facebook/ptilopteri
Photos: http://wahoo.no-ip.org/piwigo               paka @ IRCnet freenode

___________________________________________________________________________
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

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

Reply via email to